Invoice for Work Completed: Wording, Template, and When to Send
When you finish a job, the document you send next has a specific function: it marks the work as complete, references what was agreed, applies any prior payments, and triggers the final payment. That's a completion invoice — sometimes called a final invoice — and the wording matters more than for any other invoice in the project lifecycle. This guide covers what to title the document, what completion-specific fields to include, three industry samples, the cover email that goes with it, and what to do if the client pushes back on the word "completed."
What "Invoice for Work Completed" Actually Means
The phrase describes a specific type of invoice within the project lifecycle. It's the invoice that says: "the work we agreed to is finished — here is the final amount due." Distinct from:
| Invoice Type | When Sent | What It Says |
|---|---|---|
| Pro forma invoice | Before the contract | "Here's what this will cost — review before agreeing" |
| Deposit invoice | Before work begins | "Pay X% now to commit" |
| Progress / milestone invoice | At defined points during work | "This phase is done — pay for it" |
| Recurring / retainer invoice | On a fixed schedule | "This period's amount is due" |
| Invoice for work completed | When the job is done | "All agreed work is finished — here is the final balance" |
A completion invoice has a closing function. It signals that the engagement is wrapping up, that no more work is coming, and that whatever payment is due now is the final amount on this project. That framing matters for both you and the client.
For where a completion invoice sits in the broader project lifecycle, see our complete freelance invoicing workflow guide — completion invoicing is Stage 4 of the 9-stage workflow it covers.
When to Send a Completion Invoice (Timing)
Same day. Within 48 hours at the absolute latest.
The most common — and most expensive — mistake on completion invoicing is delay. You finish the job Friday afternoon, plan to invoice Monday, end up sending Wednesday, the client's AP cycles weekly, payment lands two weeks later. By choosing not to invoice on Friday, you cost yourself a full week of cash flow.
If you genuinely can't invoice the same day (it's a Friday evening, you're travelling), send a one-line email acknowledging the work is done and committing to send the invoice within 24 hours: "Project deliverables sent — formal invoice landing in your inbox tomorrow." This locks in the completion moment without letting the timing slip indefinitely.
The Exact Wording for the Document Title
Three common phrasings; each carries slightly different connotations.
"Invoice for Work Completed"
The most descriptive option. Tells the AP clerk processing the document exactly what it is. Best for one-off project work where there's no ambiguity about completion. Particularly common in trades and physical-work contexts.
"Final Invoice"
Shorter, also clear. Implies (correctly) that no further invoices are coming on this engagement. Best for engagements where the client has been receiving multiple invoices (milestone billing or a long project) and you're signalling the closing one.
"Project Completion Invoice"
The most formal. Reads well on engagements governed by a Statement of Work. Best for B2B work with enterprise clients whose AP systems benefit from the explicit "completion" framing.
Recommendation: Pick one and stay consistent across a single engagement. If the client received "Milestone Invoice 1" and "Milestone Invoice 2," the closing one should be "Final Invoice" — symmetric, predictable, and visually distinct. If the deposit invoice was "Deposit Invoice — Project Acme," the closing one can be "Invoice for Work Completed — Project Acme." Don't switch terminology mid-project; it creates ambiguity in audit and AP systems.
What Must Appear on a Completion Invoice (Beyond Standard Fields)
A completion invoice has every field a regular invoice has — see our freelance invoice template guide for the standard fields. Layered on top, six completion-specific elements distinguish it:
1. Scope Acknowledgment Line
A single line referencing the agreement under which the work was performed: "Final invoice for services per Quote Q-2026-014 dated April 15, 2026" or "Work completed per Statement of Work signed May 1, 2026." This is your defensive line if the client later disputes scope.
2. Completion Date Stated Explicitly
Not the invoice date — the work-completed date. They may be the same day (ideally) or one or two days apart. Stating completion date explicitly closes off "the work isn't really done" arguments after the fact.
3. Acceptance / Sign-Off Acknowledgment
If you received written acceptance — even a Slack message or email saying "looks great, thanks" — reference it: "Deliverables accepted by [name] on [date]." Doesn't need to be a formal sign-off document; the acknowledgment is what matters.
4. Prior Deposits and Progress Payments as Credits
Every dollar already received against this project appears as a negative line. The completion invoice nets to the final balance, not the project total. This prevents accidental double-payment by the client.
5. "Final Payment" or "Final Balance" Language in the Total Row
"Final balance due" or "Final payment due" instead of just "Total due." Reinforces the closing function of the invoice.
6. Warranty or Scope-Complete Clause (Optional)
A one-line note confirming the scope is complete and any warranty terms apply going forward: "All work in agreed scope complete. Any subsequent change requests will be quoted separately." Sets the boundary for future scope creep cleanly.
Three Sample Completion Invoices
Sample A: Trades (Renovation Contractor)
Mike's Renovations completes a basement renovation for a homeowner. The original quote was $18,000; a 30% deposit ($5,400) was paid at contract signing. Work is complete and the homeowner has signed off.
| Invoice for Work Completed — #2026-014 | Issued: May 25, 2026 | Due: June 8, 2026 (Net 14) | |
|---|---|
| From | Mike's Renovations — HST/BN: 123456789 RT0001 |
| To | Sarah and David Chen, 47 Maple Lane, Mississauga, ON L5B 2K9 |
| Final invoice for basement renovation per signed quote Q-2026-031 dated March 10, 2026. Work completion date: May 23, 2026. Final walkthrough and homeowner sign-off completed May 24, 2026. | |
| Basement renovation — full scope per quote (framing, drywall, electrical, flooring, paint, trim) | $18,000.00 |
| Less: deposit received March 12, 2026 (Invoice #2026-008) | −$5,400.00 |
| Subtotal | $12,600.00 |
| HST (13%) on subtotal | $1,638.00 |
| Final Balance Due | $14,238.00 |
| All work in agreed scope complete. Workmanship warranty: 12 months from completion date. Any subsequent change requests will be quoted separately. | |
Sample B: Service Freelancer (Graphic Designer)
Jane Smith Design completes a brand identity project. Total fee $5,000; a 25% deposit ($1,250) was paid at kickoff. Final deliverables were sent and acknowledged.
| Final Invoice — #2026-022 | Issued: May 25, 2026 | Due: June 9, 2026 (Net 15) | |
|---|---|
| From | Jane Smith o/a Smith Design Studio — HST/BN: 234567890 RT0001 |
| To | Acme Marketing Ltd. — 500 Client Street, Toronto, ON M5V 1A1 |
| Final invoice for brand identity project per SOW dated April 1, 2026. Deliverables (logo files, brand guidelines, business card design) sent May 23, 2026. Acceptance acknowledged by Mark Reyes (Acme) on May 24, 2026. | |
| Brand identity package — full scope per SOW | $5,000.00 |
| Less: kickoff deposit received April 5, 2026 (Invoice #2026-018) | −$1,250.00 |
| Subtotal | $3,750.00 |
| HST (13%) on subtotal | $487.50 |
| Final Payment Due | $4,237.50 |
| All deliverables in agreed scope complete. Subsequent revisions or new deliverables will be quoted as a change order. | |
Sample C: Project Consultant (SOW Wrap-Up)
A consultant has billed 25% + 35% milestone invoices. This is the final 40%. Total project value $15,000; $9,000 already invoiced and paid.
| Project Completion Invoice — #2026-031 | Issued: May 25, 2026 | Due: June 24, 2026 (Net 30) | |
|---|---|
| From | Strategy Partners — HST/BN: 345678901 RT0001 |
| To | Enterprise Client Inc. — Accounts Payable, 1 Bay Street, Toronto, ON M5J 2N8 — PO: 4500078212 |
| Final invoice — Milestone 3 of 3 — for strategic planning engagement per SOW dated February 14, 2026. Completion date: May 22, 2026. Final deliverables (strategic roadmap, board deck, implementation plan) presented and accepted May 22, 2026. | |
| Milestone 3 — final deliverables and presentation (40% of project) | $6,000.00 |
| Subtotal | $6,000.00 |
| HST (13%) | $780.00 |
| Final Balance Due | $6,780.00 |
| Engagement complete. Total project value $15,000 + HST ($9,000 invoiced previously — Inv. #2026-019 and #2026-025, both paid). | |
Note how each sample includes (1) the scope-acknowledgment line at the top, (2) the explicit completion date, (3) the sign-off acknowledgment, (4) prior payments shown as credit lines (Samples A and B) or referenced (Sample C), (5) "Final" language in the total row, and (6) a scope-closure clause at the bottom. These six elements turn a regular invoice into a completion invoice.
The Cover Email That Goes With a Completion Invoice
The email accompanying a completion invoice is shorter than most freelancers make it. Three lines maximum.
Subject Line
Final Invoice — [Project Name] — INV-2026-022 — Due [Date] — $[Amount]
Or for trades: Invoice for Work Completed — [Property/Project] — Due [Date]
Body Template
Hi [Name],
Final invoice attached for [project name] — work completed on [date]. Final balance is $[amount], due [date].
Let me know if you need anything to process the payment.
Thanks,
[Your name]
That's it. No long thank-you paragraphs, no requests for testimonials, no upselling to next projects. The email's only job is to deliver the invoice and confirm the work is done. Save the thank-you and the next-project conversation for separate emails — bundling them into the invoice cover dilutes the AP-processing purpose of the email.
For broader email-sending mechanics including PO handling and AP cc'ing, see our how to send invoices professionally by email guide.
What Happens If the Client Disputes "Completion"
Occasionally a client receives the completion invoice and pushes back: "actually, the work isn't really done." Three possibilities:
- Scope dispute — they're claiming you didn't do something they expected. Refer to the original quote/SOW. If the disputed item wasn't in the agreed scope, this is a change-order conversation, not a completion dispute. Keep the completion invoice intact and offer to quote the additional work separately.
- Quality dispute — they're claiming what you did doesn't meet the standard. Address the specific defect, complete the fix, then re-issue the completion invoice. This is the right outcome: you maintain the completion framing but acknowledge the legitimate issue.
- Stall tactic — they're using "not really done" as a way to delay payment. The scope-acknowledgment line, completion date, and sign-off reference on your invoice are your evidence. Hold the position firmly and proceed with normal follow-up cadence.
The defensive language built into your completion invoice — "per quote Q-2026-031," "completion date May 23," "sign-off acknowledged" — is what makes the difference between a recoverable conversation and a hard standoff. For the full playbook when a dispute escalates, see what to do when a client disputes your invoice.
Completion Invoice vs Final Invoice — Are They the Same?
In day-to-day practice, yes. The phrases are interchangeable in most contexts and refer to the same document — the last invoice in the project lifecycle, marking work as complete.
Two subtle distinctions:
- "Completion invoice" emphasizes the work-completion event. More common in trades and physical-work contexts where there's a discrete moment of completion (inspection passed, walkthrough done).
- "Final invoice" emphasizes the position in the invoice sequence (the last one). More common in milestone-billed engagements where "final" is symmetric with "first" deposit invoice and intermediate milestone invoices.
Functionally identical. Pick whichever fits the context and stay consistent across a single client engagement.
Completion Invoice Mistakes
1. Sending Before the Work Is Genuinely Complete
Sending the completion invoice before the last deliverable is done — to "lock in" the payment timeline — backfires. If anything still needs to be completed, the client uses that as leverage to delay payment indefinitely. Wait until completion is real.
2. Using Vague Descriptions Like "Services Rendered"
"Consulting services rendered: $6,000" tells the AP system nothing and gives the client no record of what they're paying for. Describe the specific deliverable: "Strategic roadmap (40 pages), board presentation deck (28 slides), 6-month implementation plan."
3. Forgetting to Apply Deposits and Progress Payments as Credits
Sending a completion invoice for the full project total without crediting the deposit invites the client to pay only the net (subtracting the deposit themselves) — which is correct but creates an accounting mismatch in your records. Always show the deposit as an explicit credit line.
4. Including Disputed Scope Items Without Separating Them
If there's an outstanding scope question, don't slip it into the completion invoice as a hopeful charge. Either resolve it before issuing the invoice or issue the completion invoice for the agreed scope only and handle the disputed item as a separate change-order conversation.
5. No Cover Email Or Inconsistent Subject Line
An invoice attached to a blank email or a subject line that doesn't identify the invoice gets lost in AP queues. The subject line should be processable from the inbox preview without opening the email.
Frequently Asked Questions
Is "invoice for work completed" different from a regular invoice?
Functionally identical — both request payment. The difference is in framing: a completion invoice marks the work as done, references the original scope, applies prior payments, and triggers the final amount. It's the last invoice in the project lifecycle.
When should I send a completion invoice?
The same day the work is delivered or signed off — within 48 hours at most. Delayed invoicing is the single biggest avoidable cause of slow collection.
What if the client says the work isn't actually complete?
Distinguish scope disputes (something they expected wasn't agreed — handle as change order) from quality disputes (fix the defect, re-issue invoice) from stall tactics (hold the position, lean on your scope-acknowledgment line).
Do I need a signed sign-off before sending the completion invoice?
Not always required, but always helpful. A brief written acceptance — even an informal "looks good, thanks" message — protects you in a later dispute. Reference it on the completion invoice when you have one.
Can I send a partial-completion invoice if some work is still pending?
That's a progress or milestone invoice, not a completion invoice. Keep the distinction clear: completion invoices mark the engagement as done; progress invoices bill for completed phases of work that's still ongoing. Mixing the two creates ambiguity about what payment is final.