Revising a sent invoice should take less time than reading this paragraph. The reason it usually doesn't is that most freelancers' tools weren't designed for it. The default workflow becomes: open the original invoice, copy the data, paste into a new template, make the edit, save as a new file, and email it with a confused note about which one to pay. The right workflow is to treat the revision as a state change, not a new document. The original invoice goes back into edit mode, you make the change, and you resend it — same invoice number, same audit trail, no version pollution.
What "revising" means (and what it doesn't)
Revising a sent invoice means correcting it before payment is made. The invoice retains its original number, the change is logged, and the client gets the updated version. This is different from issuing a credit note (which creates a new financial record reducing an already-paid invoice) and different from voiding an invoice (which marks it as never valid and replaces it with a new one). For the typical revision use case — wrong PO number, missing line item, incorrect rate — the right action is in-place revision.
The legal and accounting status of in-place revision is well-established. Standard accounting practice allows invoices to be corrected before payment, provided the changes are documented (most modern invoicing systems handle this automatically by versioning the invoice internally). The IRS in the US, HMRC in the UK, and CRA in Canada all permit corrected invoices for unpaid items. The thing to avoid is silent revision — quietly changing an invoice without notifying the client, who then might pay the original (incorrect) amount or feel like something was slipped past them.
Step-by-step: the right way to revise
Step 1: Confirm receipt of the request in writing
Reply to the revision request before you make the change. The reply has three jobs: confirm what you understood the change to be, set a timeline ("within the hour" works for most reference-data revisions), and confirm whether the total amount is changing. This creates a written record that protects both sides if there's a dispute later.
Step 2: Open the original invoice in your billing tool
Don't create a new invoice document. Find the original — by invoice number, by client, or by date — and open it in whatever state your tool keeps sent invoices. If the tool supports a "revise" or "reopen for editing" action, use it. If it doesn't, you're using the wrong tool for ongoing client relationships and the rest of this guide will only partially work.
Step 3: Make the specific change requested
Edit only the field the client asked about. Resist the urge to clean up other things you noticed (the slightly awkward line item description, the date format you've since updated). Every additional change you make is a chance to introduce a new error that triggers a second revision request. Make the requested change, verify it, and stop.
Step 4: Verify the changed total (if applicable)
If the revision changed the total — even by adding a tax line or removing a line item — calculate the new total manually and confirm the system arrived at the same number. The most common silent error in revision is a recalculation gone wrong (tax recomputed against the new subtotal, discount applied to a different base). Two minutes of math now prevents the embarrassment of sending a revision with the wrong total.
Step 5: Resend with a clear notification email
Don't just update the invoice and assume the client will notice. Send a brief email: "Invoice X has been revised per your request — same invoice number, updated [field]. New total: $X,XXX. Payment terms unchanged." The notification is what closes the loop. Without it, the client might pay the original (cached) amount, or — if they were waiting for the revision before approving payment internally — your update sits silently in the system while AP keeps waiting.
Step 6: Update underlying source data if needed
If the revision was about wrong tracked time ("those Friday hours were Project A, not Project B"), edit the time entries in your tracking system too — not just the invoice line. Otherwise the next month's invoice for the same project will inherit the same wrong allocation, and you'll be doing the same revision a second time. This is the step most freelancers skip and pay for later.
How Clockout's revision flow works
Clockout invoices have a `revised` status that re-opens a sent invoice for editing. From any post-send state (sent, viewed, partially-paid), you can transition the invoice to revised — at which point the invoice becomes editable again, but its identity (invoice number, audit trail, original send date) stays intact. Make the change, then transition back to sent. The client sees the updated version with the same invoice number and a clear indication it's been revised.
The structural advantage is that session-backed line items re-sync automatically. If your invoice line was "Project Alpha — 24 hrs at $150/hr" and you correct an hour entry in the underlying time tracker, the invoice line updates to match when the invoice goes into revised state. You don't have to manually re-enter the corrected hours. This eliminates the most common silent revision error: the invoice and the underlying time data drift apart over time.
File attachments work the same way — you can upload corrected supporting documents (a revised SOW, a corrected expense receipt) only while the invoice is in draft or revised state, which prevents accidental changes to invoices that are already in the client's payment workflow. See the full editable invoice flow for the technical details.
When NOT to use in-place revision
Three situations call for a credit note or new invoice instead of in-place revision:
- The invoice was already paid. Once money has changed hands, the original invoice is a permanent record. Adjustments need to happen via credit notes (for refunds or partial reductions) or new invoices (for additional charges). Don't revise paid invoices — it breaks bookkeeping reconciliation.
- Tax law in your jurisdiction requires it. Some VAT and GST regimes (e.g., specific EU member states, certain Indian GST scenarios) require formal credit notes rather than invoice edits when the change exceeds a threshold or affects tax amounts. If you bill internationally, check the specific rules.
- The invoice is part of a finalized financial period. If the invoice is in a closed accounting period (e.g., year-end books are sealed), revising it changes prior-period numbers in ways your accountant or auditor may not allow. Issue a credit note in the current period instead.
The bookkeeping cleanup question
If you've been creating new PDF versions for revisions in the past ("Invoice-2347-v2.pdf", "Invoice-2347-final.pdf"), the cleanup is worth doing. For each pair, identify which version was actually paid (cross-reference your bank statement against the invoice totals) and mark the others as superseded in your records. Going forward, use one tool that handles revision as a state and the cleanup never happens again.
Common errors and how to avoid them
- Editing without notifying. Always send a follow-up email when an invoice is revised. The 30-second message prevents the much longer cleanup that happens when the client pays the wrong amount.
- Recalculating tax incorrectly. If the revision touches the subtotal, double-check the tax calculation. Most invoice tools auto-recompute, but the formula they use (tax-inclusive vs tax-exclusive, compounded vs flat) can produce surprising results.
- Losing track of which version is current. If you must use multiple PDF versions, keep a one-line note in your billing log: "Invoice 2347 — v3 sent 2026-04-22, paid 2026-05-08, $4,250." Future-you will need this.
- Not updating the source data. Whatever fed the wrong invoice line — tracked time, expense receipt, project rate — needs to be corrected at the source. Otherwise the same wrong data feeds the next invoice.
- Apologizing in a way that signals weakness. A brief professional confirmation works better than an apology spiral. "Updated and resent" beats "so sorry about that, here's the corrected version, I'll be more careful next time."
The summary
Revising a sent invoice should be a 30-second action: confirm the change, edit in place, resend with notification, update source data. The reason it often takes longer is that the underlying tools weren't built for it — they treat invoices as immutable PDFs that have to be replaced rather than as living records that can be corrected. If your billing tool doesn't have a revise-in-place flow, the recurring cost of working around that limitation is more than the cost of switching to one that does.