Proposals & Invoices · Article 5.1
When to use an amendment (vs a new proposal vs withdraw)
Three paths exist to change a deal: amend it, withdraw and resend, or start a new proposal. Pick the wrong one and you'll either break the audit trail or scare the client. Here's the decision tree.
Amendments are designed for the moment a contract you've already signed needs to change. The client added a feature, removed a deliverable, asked for a discount, or you discovered the original quote was wrong after starting the work. Without amendments, your only legal options are to start a new contract or fight about the old one — both messy. With them, you produce a fresh signed document that supersedes the original, references it explicitly, and triggers the right invoice or refund automatically.
Step by step
Check the current status.
From
/proposals/{id}look at the badge.DraftorSent(not yet signed) → useWithdrawand edit.Signed,Deposit paid,In work,Awaiting final payment,Paid,Completed→ usePropose scope change(amendment).Confirm the change is to this contract, not a new one.
Rule of thumb: if the line items still describe the same project for the same client, amend. If it's a separate scope (new project, follow-on work), create a new proposal — easier to track financially and legally cleaner.
Make sure no draft amendment already exists.
Only one open amendment per proposal at any time. If a previous draft is hanging around (you started one and never sent it), the wizard will resume it instead of creating a duplicate.
Open
/proposals/{id}/amend.From the Actions panel click
Propose scope change. The wizard takes over from there — see article 7.3.
On any proposal in Signed or later state, the Actions panel exposes Propose scope change. If a draft amendment is already in progress, the same button reads Continue draft amendment. Withdraw is only present in Sent / Viewed states; once signed, it disappears (you can't unwind a signed contract).
Why this works this way
The reason this matters legally: an EU invoice is a permanent legal record. You cannot delete it, edit it, or quietly replace it under §14 UStG (Germany), CGI Art. 289 (France), Art. 6 Reglamento de Facturación (Spain), or BTW Art. 35 (Netherlands). When the contract changes, the documents must reflect that change in a paper trail any tax inspector can follow: original invoice → cancellation invoice (Stornorechnung) → new invoice. Clozo's amendment flow produces exactly that trail. A "I'll just edit the invoice" approach would invalidate your books in every EU jurisdiction.
The "withdraw and resend" path stays open only until the client signs. Once signed, the proposal is a contract; you can no longer pretend it never existed. Amendment is the only legitimate path forward.
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.
Proposals & Invoices
Creating an amendment (the 4-step wizard)
The amendment wizard at `/proposals/{id}/amend` walks you through line items, reason, preview, and email — in that order. Five minutes for a simple change, ten minutes for a complex one. The client doesn't see anything until you click Send on Step 4.
Lifecycle
Status: Sent — the proposal is in your client's inbox
You've clicked `Send`. The PDF is rendered, the email is on its way, the proposal number is assigned, and the audit trail starts here. Now you wait — until the client opens it (`Viewed`) or signs (`Signed`).