Troubleshooting & Reference · Article 7.9
"The receipt or final-invoice email shows an amount that doesn't match"
After an amendment, the final invoice and receipt should reflect the amended total — not the original. A bug fixed in May 2026 (PR #173 / #179) had emails using the original total. Post-fix, all docs use `effective_total`.
Amendments and final-invoice math get tangled because of a legal subtlety: the deposit invoice (Anzahlungsrechnung) is immutable once issued — under German GoBD rules and EU VAT timing, you can't retroactively change a deposit invoice. So when an amendment changes the total, only the final invoice and receipt reflect the new amount. Pre-fix, the final invoice email was incorrectly using the original total too; post-fix it uses effective_total.
Step by step
Confirm the issue.
Compare the email amount to the proposal's current
effective_total(visible on the proposal detail page header).If pre-fix proposal
: the email was sent with the wrong amount. Don't try to retroactively fix the email — it's a sent artefact. The PDF in Documents (regenerated post-fix) should be correct; share that with the client if needed.
If post-fix proposal
: the email should be correct. If it isn't, that's a regression — contact support.
Why this works this way
The data model post-fix:
- proposal.total: original total at signing time. Immutable thereafter.
- proposal.effective_total: derived from the original total + the sum of all signed amendment deltas. Recomputed on every amendment sign.
- Deposit invoice (DEP): always shows original_deposit_amount. Never changes.
- Final invoice (INV): shows effective_total - deposit_amount. Updates on amendment.
- Receipts: split per VAT stage; the deposit receipt stays anchored to the deposit, the final receipt uses effective_total.
Email copy after the fix uses effective_total consistently — final invoice email, payment confirmation email, and refund-completed email all read from the live amended total.
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
The Clozo invoice family: DEP, INV, STR, DCR, CRN, REC
Six document types make up the full Clozo invoicing chain. Each has a distinct legal role under EU VAT Directive Art. 220 and §14 UStG. This article maps which document fires when and what it references.
Refunds & Notifications
Email: "Final invoice — please pay {{amount}}"
Sent when you click `Issue final invoice` after work is complete. Carries the final invoice (Schlussrechnung) PDF and the payment CTA.