Refunds & Notifications · Article 6.8
Email: "Amendment signed — [details]"
Confirms the client signed the change-order. Body and attachments are phase-aware — you and the client see different copy depending on whether the amendment increases scope, decreases scope, or is neutral.
The amendment signing event has the same legal weight as the original proposal signing — both parties need confirmation, and the financial ripple effects (new invoice, refund, or no-op) need to be communicated clearly.
Step by step
Client signs the amendment.
A timestamp is captured; the amendment status flips to
Signed.Post-sign hook runs.
Depending on the branch, new INV / Storno / Credit Note PDFs render in R2.
Both emails dispatch.
Once all required PDFs are in R2, the freelancer-copy and client-copy tasks fire.
Status loses the "Amendment in progress" sub-state; main proposal status updates per branch (e.g., Final invoice issued for Δ+, Refunding for Δ−). Documents dropdown gains the relevant new PDFs. Inbox: archive copy of the freelancer-side amendment-signed email.
Why this works this way
Three branches drive the copy ([D-111]):
- Δ+ (cost increase): Body explains the new total, references the new final invoice (INV-XXXX revision 2 supersedes the original), and includes a payment CTA for the additional amount. The new INV PDF is attached. - Δ− (cost decrease, refund triggered): Body explains the refund — "We've issued a credit note for €Z; the refund will reach your account within 5-10 business days for SEPA, 1-2 days for Stripe." Storno (the void of the original invoice) and Credit Note PDFs are attached. No payment CTA — this is a refund flow. - Δ=0 (neutral, e.g., timeline-only change): Body simply confirms "the amendment is now in effect." No new financial documents; only the signed addendum is attached.
The phase-aware copy is the result of bug-fix work in May 2026 ([D-111] / PR #173/#179) — earlier versions sent the same Δ+ copy regardless of branch, which confused clients on refund amendments.
Troubleshooting
Keep reading
Proposals & Invoices
The 4 delta branches: Δ+, Δ−, Δ=0, Δ_REFUND
Every signed amendment falls into one of four branches based on (a) the sign of the cost change and (b) whether the proposal was already paid. Each branch fires a different document chain. This is the central conceptual map for the entire amendment system.
Refunds & Notifications
Email: "Refund completed — €X returned"
The closing email of a refund flow. Fires when Stripe confirms the refund succeeded (or when you mark a SEPA refund as complete). Carries the credit note PDF.
Refunds & Notifications
The Credit Notes page
A first-class section in the freelancer dashboard that lists every credit note across all your proposals, with status, refund amount, linked proposal, and action buttons. Use this when you want to manage refunds without drilling into each proposal individually.