A naming and merging convention for contracts and invoices
The archive problem is not storage - it is retrieval five years later, by someone who does not remember what the file was called. A workable convention has three parts: a folder per counterparty, a file name that begins with an ISO date and a document type, and one merged bundle per transaction so a single file answers "what happened here". The convention only earns its keep if it is cheap to apply, so everything below is designed to be typed in a few seconds.
The name pattern
YYYY-MM-DD_cparty_type_status_version.pdf, all lowercase, hyphens inside a field and underscores between fields. ISO dates sort correctly as text and are never ambiguous. Underscores between fields give you something to split on when a script needs to parse the name; hyphens inside a field keep the field readable.
| File name | What it says |
|---|---|
2026-11-19_acme_supply-agreement_signed_v1.pdf | Signed supply agreement with Acme, first version, dated 19 Nov 2026 |
2026-11-19_acme_invoice-4471_paid.pdf | Invoice 4471 from Acme, marked as paid |
2026-11-19_acme_delivery-note_signed.pdf | Delivery note, signed on receipt |
2026-11-19_acme_bundle.pdf | A bundle named only by counterparty and date - no type, no version, do not use |
The fourth row is the failure mode: a bundle named only by counterparty and date. Six months later it is one of eleven files with the same shape, and opening each one is the only way to know which is which.
Folders: counterparty first, year second
Two levels are enough for most small businesses: acme/2026/. Counterparty first because that is how people search ("what do we have with Acme"), year second because it bounds the listing. For a company with thousands of counterparties, add a first letter level (a/acme/2026/) to keep folder listings short; for a handful, the year level alone is fine.
Resist the urge to organise by document type first. Type is already in the file name, and a type-first tree splits one relationship across five folders, which is exactly the wrong shape for due diligence, audits and disputes - all of which ask for "everything about this counterparty".
One bundle per transaction, and the originals still kept
Keep both. The individual documents stay in the folder under their own names; the bundle is an additional file that collects them in reading order. The bundle is what you send to an auditor, a lawyer or a new accountant, because it answers the whole question in one attachment. The originals are what you keep for the cases where the bundle is not enough - a signature that needs to be verified on its own, an invoice that must be submitted to a tax portal as a separate file.
This is the point where merging has a real cost, and it should be stated plainly: a merged bundle has no bookmarks, and links that pointed between the original files do not survive. A bundle is a reading copy. If navigation matters, put a manifest page first - see below - rather than relying on an outline that will be dropped.
The manifest page
A one-page summary at the front of the bundle is the single highest-value thing in this whole convention. It costs two minutes and it turns a stack of pages into a document. It should hold:
- Counterparty, transaction reference, and the total value with currency.
- A list of the documents inside, with their page ranges in the bundle: Invoice 4471 - pages 2-3.
- What is missing, if anything: delivery note not yet received. Writing down the gap is more useful than a bundle that silently lacks a document.
- The date the bundle was assembled and by whom.
Build the manifest as a one-page PDF from a word processor, then merge it as the first file. The page ranges are easy to fill in if you add the documents in a known order and note their page counts as you go - the merge tool shows the running total while you build the list, which is the cheapest way to get the ranges right.
Order inside the bundle
Order answers the reader's first question - "what am I looking at?" - before they have to open anything else. A workable sequence for a purchase transaction:
- Manifest page.
- Signed contract or order confirmation, if there is one.
- Purchase order or the buyer's instruction.
- Invoice.
- Delivery note, signed.
- Payment evidence (remittance, bank confirmation).
- Correspondence that changes the interpretation - a variation, a credit note, an agreed discount.
Two rules keep this sane: money documents follow the contract they depend on, and anything that amends an earlier document goes at the end, never between a document and its evidence. A credit note filed before the invoice it corrects makes the bundle read as if the invoice were never issued.
Versions that sort and still make sense
Version suffixes are where discipline collapses. Three rules prevent most of it:
- Numbers, not adjectives.
_v1,_v2,_v3. "final", "final2" and "FINAL-actual" sort arbitrarily and mean nothing to a reader a year later. - Never overwrite a version. If the counterparty sends a revised contract, it becomes
_v2with its own date. Overwriting destroys the history that a dispute may depend on. - Mark state separately from version.
_draft,_signed,_countersigned,_paid. State changes without a new version, and the file name should show it; otherwise you cannot tell a signed copy from a draft that happens to be v2.
The exception to the no-overwrite rule is a correction that is not a new version - a mis-scan of the same signed page. Replace it, but note the correction in the manifest rather than pretending the first attempt never existed.
Assembling a bundle in practice
The mechanics are the same as any merge and take about a minute once the files are prepared:
- Rotate anything scanned sideways. Fixing orientation after merging means redoing the merge, because the result is a new document.
- Confirm every file opens and is the version you think it is. A password-protected invoice that fails to merge is a problem worth finding before the bundle exists.
- Merge in the order above. Check the page count against the sum of the parts before you download.
- Number the bundle pages if it will be printed or referenced: bottom centre, plain numbers, starting at 1, cover page unnumbered if you have a separate cover.
- Name it
YYYY-MM-DD_cparty_bundle.pdfand store it alongside the originals, not instead of them.
The merge and numbering steps are described in more detail in merging: order and bookmarks and page number layout. If a bundle has to be sent to a portal with a size limit, splitting at a document boundary is better than compressing the scans.
Retention, encryption and the boring parts
Signed contracts and invoices are the documents most likely to be needed years later and most likely to contain personal data. Two habits pay off: keep the archive in a location that is backed up and access-controlled rather than in a shared drive with open permissions, and keep encrypted originals encrypted - a password-protected copy that has been "unlocked" and stored in the clear is a different document with a different risk profile. If a bundle must be shared outside the company, share the bundle and keep the encrypted originals in the archive.
Retention periods are set by tax and contract law in your jurisdiction, not by what fits on a disk. The practical rule: do not delete anything that has a signature or a payment attached until the statutory period has passed, and do not delete the originals just because a bundle exists.
Frequently asked
Should the bundle include the unsigned draft?
Only if the history matters - a negotiation, a dispute about what was agreed. Otherwise it doubles the size and invites confusion about which version was executed. Keep the draft in the folder, out of the bundle.
What if the counterparty sends one PDF containing all the documents?
Split it at the document boundaries first, name the parts, then reassemble in the order above. Splitting before naming is the reliable sequence, because a 40-page scan named scan.pdf gives you no clue where the boundaries are until you have looked at every page.
Is a merged bundle acceptable as evidence?
Sometimes, but originals are stronger. Many jurisdictions treat a re-written PDF as a copy rather than an original record, and a digital signature on any source document is broken by the merge. Keep the originals and treat the bundle as a reading aid.
Related reading: password-protected PDFs and shrinking scans.
Written by the PDFNest team. Last updated November 19, 2026.