Should each revised invoice get a new invoice number?

That is your billing decision, not something this folder dictates. Many people keep the same number across revisions of one invoice and use the version label to distinguish them; others issue a new number. Either way, the version history folder keeps the documents that belong to that one invoice together and marks which is current. This is organizational guidance, not accounting or tax advice.

Is this the same as voiding or cancelling an invoice?

No. A void is cancelling an invoice that should never have stood, and it gets its own record with a void reason. Version history is for an invoice that is still valid but has been corrected one or more times. Keep the two separate — file cancellations under a voided-invoice record.

What if I just re-sent the exact same invoice without changing it?

That is a resend, not a new version, and it belongs in a resend or reissue log rather than here. The version history folder is specifically for documents whose content differs from the prior version. If nothing changed, do not add a new version.

Does Cash Workspace detect the differences between versions for me?

No. Cash Workspace stores and orders the documents you attach and lets you set each one's status and change note. It does not read your PDFs, compare them, or extract what changed — you write the change note yourself. It also does not sync with your bank or any invoicing app.

How many old versions should I keep?

Keep all of them. The whole purpose of the folder is the complete ordered trail, so a superseded version is still part of the record. Mark old ones Superseded rather than deleting them; how long you retain records overall is a separate retention question outside this page's scope.

Cash Workspace

Use the Freelancer template

Invoice lifecycle organization

Keep an invoice version history folder for revised invoices

When an invoice gets corrected more than once — a quantity fixed, a rate updated, a bill-to address changed — you can end up with three or four files all named something like "Invoice 1042." A version history folder solves that: it holds every revision of that one invoice as an ordered set of documents, with exactly one marked as the current version and the rest marked superseded. The point is traceability, not bookkeeping. Anyone opening the folder — you, a teammate, or your accountant — should be able to see which document the client is working from now, and read backward through the earlier versions to understand what changed and why. Cash Workspace gives you a record per invoice where you attach each revised PDF in order and note its status. This page covers version control of a revised invoice only. It does not cover cancelling an invoice (a void is a separate event), and it does not cover logging that you re-sent the same unchanged file.

Start a free workspace See the invoice lifecycle stage map

The problem

Why three files named "Invoice 1042" cause trouble

A single invoice rarely stays single once it gets revised. The first version goes out, the client flags an error, you fix it and resend, then a second correction lands a week later. Now the same invoice number exists as several different PDFs scattered across email drafts, your desktop, and a shared drive — and nothing tells you which one is live. A version history folder keeps all of them together, in order, with one clearly marked current.

You and the client end up referencing different PDFs of the same invoice number, and neither of you is sure which figure is the agreed one.
Earlier corrected versions get deleted to 'clean up,' so when a question comes up later there is no record of what the original said or why it changed.
Filenames like 'Invoice 1042 final FINAL v2.pdf' pile up with no reliable signal for which is actually current.
A teammate covering for you opens the folder and cannot tell a superseded draft from the version the client is paying against.
At handoff your accountant sees multiple documents for one invoice number and has to ask you which one is real.

Setup

Build the version history folder for one invoice

Do this per invoice that has been revised. The goal is a single record holding every version of that invoice in order, with the current one obvious at a glance. You attach each PDF manually — Cash Workspace stores and orders the documents you add; it does not read them or pull versions in automatically.

1
Create one record for the invoice, keyed by its number
Make a single invoice record named for the invoice it tracks, for example 'Invoice 1042 — Brightline Studio.' Every version of this invoice lives in this one record, not in separate records. The invoice number stays constant across all versions; only the version marker changes.
2
Attach each version as a separate dated document
Upload every revision as its own file — original plus each correction — rather than overwriting. Name each file so the order is unmistakable: 'Invoice-1042_v1_2026-05-03.pdf', 'Invoice-1042_v2_2026-05-09.pdf', 'Invoice-1042_v3_2026-05-18.pdf'. Keep the earlier versions; they are the history.
3
Mark exactly one version current and the rest superseded
Set a status on each attached document. One — and only one — carries the 'Current' status; every earlier file is marked 'Superseded.' If you later issue v4, flip v3 to Superseded and mark v4 Current so there is never ambiguity about which document is live.
4
Record what changed in each version's note
On each version after the first, write a one-line change note: 'v2: corrected hours from 12 to 10' or 'v3: updated bill-to address per client request.' This is the thread that lets anyone read the folder top to bottom and understand the revision trail without opening every PDF.
5
File the record so the current version is easy to reach
Place the record in the relevant client and fiscal-year folder alongside your other invoices. Because the current version is marked, the record drops cleanly into normal filing while still preserving its full history underneath.

Record structure

Fields to record per version

Capture these on the invoice record and on each attached version so the ordered set reads clearly and the current document is never in doubt. Keep the fields factual — this is document organization, not an accounting ledger.

Invoice number: The constant identifier shared by every version in the folder, e.g. 1042. It does not change between revisions; the version marker carries the difference.
Version label: A simple ordered marker per document — v1, v2, v3 — that fixes the sequence so the order of revisions is unambiguous.
Version status: Either 'Current' or 'Superseded.' Exactly one document is Current at any time; all earlier ones are Superseded.
Version date: The date this particular revision was created, e.g. 2026-05-09. Distinguishes the documents and sets their chronological order.
Change note: A one-line description of what differs from the prior version, e.g. 'corrected rate from $95 to $90/hr.' Empty only for v1.
Attached document: The actual PDF for that version, uploaded as its own file so no revision overwrites another.
Client / account: Which client the invoice belongs to, e.g. Brightline Studio, so the record files alongside that client's other invoices.

Example setup

An example version history folder

Here is how a record for one twice-revised invoice looks once the full ordered set is in place. Note that every version is preserved, the change notes form a readable trail, and only the latest document is marked Current.

Clients / Brightline Studio / 2026 / Invoice 1042 (version history)

The single record for invoice 1042, holding all three versions in order with statuses and change notes attached.

Invoice-1042_v1_2026-05-03.pdf — Superseded

Original issued version. Change note: '(original).' Status set to Superseded once v2 was created.

Invoice-1042_v2_2026-05-09.pdf — Superseded

Change note: 'corrected billed hours from 12 to 10; total $1,140 to $950.' Was Current until v3 replaced it.

Invoice-1042_v3_2026-05-18.pdf — Current

Change note: 'updated bill-to address to new registered office per client.' The version the client is paying against now.

Clients / Brightline Studio / 2026 / Invoice 1043 (version history)

A separate invoice's own version folder — kept apart so each invoice number's history stays self-contained.

Common mistakes

Common mistakes to avoid

Overwriting the previous PDF with the corrected one, which destroys the history the folder exists to preserve. Always add the new version as a separate file.
Leaving two documents both marked Current — or none marked at all — so no one can tell which version is live. Keep the rule to exactly one Current at a time.
Using vague filenames like 'final' or 'v2 real' instead of an ordered label plus date, which reintroduces the ambiguity you were trying to remove.
Treating a cancelled invoice as just another version here. A void is a separate event with its own reason; file it under a voided-invoice record, not as a superseded revision.
Skipping the change note, so the documents exist in order but no one can see why each revision happened without opening and comparing every PDF.

How it helps

How Cash Workspace helps

One record holds the whole ordered set

Keep every revision of an invoice as attached documents on a single record, so the full history travels together instead of scattering across drafts and drives.

Clear current-vs-superseded status

Mark one document Current and the rest Superseded so anyone opening the record knows immediately which version is live without guessing from filenames.

Change notes per version

Add a short note to each revision describing what changed, building a readable trail from the original through to the current document.

Files alongside your other invoices

The version record drops into the same client and fiscal-year folders as the rest of your invoices, and you can export the records when you hand them off. It is free.

Voided invoice record

When an invoice is cancelled rather than revised, file it as a void with its reason here — a separate event from keeping ordered versions of a still-valid invoice.

Draft invoice staging folder

Hold tax-invoice drafts that have not been sent yet. Version history begins once an issued invoice gets revised; this covers the earlier not-yet-sent stage.

Invoice resubmission after rejection log

Track invoices a client or AP portal rejected, the reason, and the corrected resubmission — the rejection-driven reason behind some of the versions you file here.

Change order to invoice link

Cross-reference an approved change order to the invoice line it bills, which often explains why a new version of an invoice was issued.

Document version control workflow

The general one-document-many-versions pattern across any file type, when you need version control beyond invoices specifically.

Invoice lifecycle stage map

See where every invoice stage — draft, sent, revised, settled, archived — lives in your workspace, and how version history fits the overall map.

Finance workflows

Browse the full set of invoice, expense, and document organization workflows in one place.

FAQ

Frequently asked questions

Should each revised invoice get a new invoice number?: That is your billing decision, not something this folder dictates. Many people keep the same number across revisions of one invoice and use the version label to distinguish them; others issue a new number. Either way, the version history folder keeps the documents that belong to that one invoice together and marks which is current. This is organizational guidance, not accounting or tax advice.
Is this the same as voiding or cancelling an invoice?: No. A void is cancelling an invoice that should never have stood, and it gets its own record with a void reason. Version history is for an invoice that is still valid but has been corrected one or more times. Keep the two separate — file cancellations under a voided-invoice record.
What if I just re-sent the exact same invoice without changing it?: That is a resend, not a new version, and it belongs in a resend or reissue log rather than here. The version history folder is specifically for documents whose content differs from the prior version. If nothing changed, do not add a new version.
Does Cash Workspace detect the differences between versions for me?: No. Cash Workspace stores and orders the documents you attach and lets you set each one's status and change note. It does not read your PDFs, compare them, or extract what changed — you write the change note yourself. It also does not sync with your bank or any invoicing app.
How many old versions should I keep?: Keep all of them. The whole purpose of the folder is the complete ordered trail, so a superseded version is still part of the record. Mark old ones Superseded rather than deleting them; how long you retain records overall is a separate retention question outside this page's scope.

Organization, not accounting advice

Cash Workspace helps you organize invoice revisions as ordered documents and mark which is current; it is not accounting, bookkeeping, tax, or legal software. It does not read or compare your PDFs, extract what changed, classify documents, or sync with your bank or any invoicing tool — you attach each version and write each change note yourself. Whether to reuse or reissue invoice numbers, and how to treat a correction for accounting or tax purposes, are decisions for you and your accountant.

Start a free workspace for your revised invoices

Set up a version history folder for your most-revised invoice in a few minutes: one record, every version attached in order, the current one clearly marked. Cash Workspace is free — operated by HELPERG LLC. Questions? Reach us at info@helperg.com.