Final Invoice: How to Close a Project So the Math Defends Itself

A final invoice is the last invoice of a project: the one that bills the remaining balance after the work is delivered, credits everything already paid — deposits, milestone payments — and closes the engagement. It's a real payment request with a real number in your sequence, and it's usually the largest single payment event of the project.

It's also the invoice most likely to get questioned, because it arrives at the exact moment the client's leverage peaks (they have the work) and yours drops (you've delivered it). The defense is arithmetic: a final invoice whose math reconciles itself against the contract gets paid; one that just says "balance due: $4,300" starts an email thread. This guide covers the format, the timing, and the traps. For where the final invoice sits in the wider family, see types of invoices.

What a final invoice is (and isn't)

The confusion cluster, untangled:

| Document | When | What it does | |---|---|---| | Proforma invoice | Before work | Preview of costs — not a payment request | | Deposit invoice | Project start | Bills the upfront portion (30–50%) | | Interim / milestone invoice | Mid-project | Bills completed phases | | Final invoice | Delivery / acceptance | Bills the balance, credits all prior payments, closes the project |

Two boundaries worth drawing precisely:

• Final invoice ≠ "the only invoice." A one-shot project with no deposit just has an invoice. The word "final" earns its place when there were prior payments to reconcile — that reconciliation is the document's entire job.
• Final ≠ last-ever. Post-delivery additions (a change order after acceptance, extra revision rounds) are billed as new invoices or a debit note against the final one — never by editing an issued invoice.

The format: show the arithmetic

The final invoice should read as a complete financial record of the engagement — total agreed, already paid, still owed — so the client's AP can reconcile it without emailing you:

DESCRIPTION                                       AMOUNT
--------------------------------------------------------
Website redesign — full project fee            $12,000.00
  (per agreement dated 2026-04-02)
Change order #1 — CMS training session, 2026-07    $600.00

                              Project total   $12,600.00

Less: deposit paid (inv. 2026-041)            -$4,000.00
Less: milestone 2 paid (inv. 2026-052)        -$4,000.00
--------------------------------------------------------
                              BALANCE DUE      $4,600.00

The rules embedded in that block:

1. The full project fee appears — not just the balance. A final invoice for a bare "$4,600" forces the client to reconstruct the history; a visible total − paid = due chain answers the question before it's asked.
2. Prior payments are credited by invoice number. "Less: deposit paid (inv. 2026-041)" ties each credit to a document both sides already have. This is the cross-referencing habit from the deposit invoice workflow, completed.
3. Change orders are itemized separately with their approval date. Scope additions folded silently into the project fee line are the single biggest source of final-invoice disputes.
4. Everything else is a normal invoice — number in sequence, issue and due dates, payment instructions. The skeleton is the standard one from how to write an invoice.

Timing and terms

Send it at delivery — against acceptance, not silence. The right moment is when the agreed deliverable is handed over or the client signs off, per whatever acceptance language your contract has. Invoicing weeks after delivery costs you urgency (the project has mentally closed for the client); invoicing before the client agrees the work is done invites a dispute instead of a payment.

Use shorter terms than your mid-project invoices. The work is complete, so there's nothing left to wait for — due upon receipt or Net 7–15 is reasonable and normal on a final balance; Net 30 mostly gives a finished project a month to fade from memory. Whatever you pick, it should match the contract — the options are in invoice payment terms.

Tie final deliverables to final payment where you can. Source files, credentials, license transfers, the DNS cutover — whatever the contract lets you hold until the balance clears is leverage that costs nothing to keep. This clause belongs in your terms and conditions from day one, not improvised at the end.

The traps

• Forgetting to credit the deposit. The classic. The client pays the over-billed total or — more likely — catches it, and now the last document of the project is the one with the error in your favor. Cross-reference every prior payment by invoice number, every time.
• A final invoice that doesn't match the quote. If the number is bigger than the last figure the client approved and nothing on the document explains why, expect the thread. Any drift from the original quote must appear as named, dated change-order lines.
• Sending it before sign-off, then negotiating from behind it. An issued invoice under dispute is worse than no invoice — you can't quietly change it (that breaks your sequence; adjustments need a credit note). Get acceptance first, invoice second.
• Letting it age like a mid-project invoice. The final balance is the payment most exposed to "the project's done, this can wait." A short-terms invoice plus the standard follow-up ladder, starting the day after due, is what keeps closed projects from becoming open receivables.
• Retainage ambiguity (construction and trades): if the contract holds back 5–10%, the final invoice must state whether it includes the retainage release or a separate retainage invoice follows. The contractor invoice template covers that structure.

A final invoice is also a small marketing document: it's the last thing the client sees, arriving at peak goodwill. Clean math, a thank-you line in the notes, and correct entity details finish the project the way the kickoff deck started it. A free invoice generator handles the layout, numbering, and totals so the only thing you're producing by hand is the reconciliation itself.

FAQ

What does "final invoice" mean?

The last invoice of a project: it bills the remaining balance after delivery, credits all payments already made (deposit, milestones), and closes the engagement. Unlike a proforma, it's a genuine payment request with a number in your normal sequence.

What's the difference between a final invoice and a proforma invoice?

A proforma is a preview sent before work — no payment obligation, no real invoice number. The final invoice is the opposite end of the project: a real, numbered payment request for the closing balance. The proforma often says "final invoice will follow upon delivery" — that document is this one.

Can I send another invoice after the final invoice?

Yes. "Final" closes the agreed scope, not the client relationship. New work after acceptance gets a new invoice; corrections to the final invoice itself go through a credit note (reduce) or debit note (increase) — an issued invoice is never edited.

What payment terms should a final invoice have?

Shorter than your usual. The work is delivered, so due upon receipt or Net 7–15 is standard and defensible — provided the contract says so. Long terms on a final balance mainly extend the window in which a finished project loses urgency.

What if the client doesn't pay the final invoice?

Same escalation as any unpaid invoice — reminder, call, final notice — but with two extra levers: withheld deliverables (source files, credentials) if your contract supports it, and the documented sign-off proving the work was accepted. The ladder is in how to follow up on an unpaid invoice.

Should the final invoice show the whole project or just the balance?

The whole project. Full fee, change orders, each prior payment credited by invoice number, then the balance due. The client pays only the balance — but showing the arithmetic is what lets their AP approve it without a question round.