The Evidence You Will Need Later
If an invoice is ever questioned, the argument is settled by what was recorded at the time. Six things to keep, none of which takes effort.
Sharedwho controls this stretch
If an invoice is questioned six months later, the question is settled by what was recorded at the time: what was agreed, what was delivered, when, and who acknowledged it.
The delay in “The Evidence You Will Need Later” needs separate timestamps for work, approval, invoicing and settlement. Teams reviewing read the current software summary for how Monitask works can strengthen the work-record part of that chain without pretending to explain what happened inside the customer’s accounts-payable process.
Six things, all of them a by-product of ordinary work, all of them worth keeping deliberately rather than by accident.
The questions raised in “The Evidence You Will Need Later” can also be checked against FSB small-business resources. Use the outside resource to identify what evidence and ownership the next action requires.
The agreement
The email with the six lines, and anything that amended it. The single most important document and the one most often spread across a thread.
The four items that carry most of the weight, per job:
- What was agreed, and when.
- The order reference and its value.
- Evidence the work was delivered.
- The invoice as sent, with the date and address.
Pull it into one place when it is written, not when it is needed.
The order
The document itself, each version, with dates. Not just the number.
An amended or superseded order a year later is otherwise impossible to reconstruct.
The delivery record
What was sent or done, when, and to whom. A dated email attaching the work is sufficient for most service businesses.
For goods, a signed note. For site work, a dated photograph.
The acknowledgement
Any reply confirming receipt. "Thanks, got it" is worth more in a dispute than any amount of internal record.
Where no reply comes, a short follow-up creates one.
The changes
Every addition or reduction, with its price and date, in the running list described in the scope note here.
This is the file that is always missing and always decisive.
The invoice trail
When it was sent, to what address, through what route, and any confirmation of receipt.
"We never received it" is answered by this and by nothing else.
Where it should live
One folder per job, or one thread per job, kept as the job runs. Not assembled afterwards.
Reconstruction takes hours and produces gaps; keeping takes seconds and produces a file.
What not to keep
Everything. A folder with four hundred emails is as unusable as none.
The six items above, plus anything unusual, is the whole of it.
The photograph
For physical work, dated images of what was done are worth more than any description. They settle quantity and condition arguments immediately.
They cost nothing and almost nobody takes them.
The timesheet
Where work is charged by time, a contemporaneous record of hours is the only defensible basis.
Reconstructed later, it is a reasonable estimate and is treated as one.
What this is not for
Litigation, usually. Most of this file is used to answer an administrative query in one email rather than four.
Its value is in the queries it closes, not the cases it wins.
Who the file is actually for
Nothing in this list is for your own recollection. Each item exists so that some specific third party can answer a question without taking your word for it: an approver confirming the work happened, a new contact reconstructing an arrangement their predecessor made, a collection agent deciding whether the debt is clean enough to pursue, an insolvency office-holder admitting your claim, a court.
All of them are reading, not listening.
That is what sets the standard for what to keep. A file that would satisfy a stranger with no stake in the outcome is sufficient; a file that depends on you being there to explain it is not a file. The test is whether somebody else could pick it up and establish what was agreed, what was delivered, when, and what remains unpaid.
Why it has to be built as you go
A reconstructed file is visibly reconstructed. Messages found and forwarded months later, dates established by inference, a delivery confirmed from memory — all of it is weaker than the same facts recorded at the time, and all of it takes much longer to assemble.
The documents also stop being available. Contacts leave, portals revoke access, message threads are archived, and a delivery confirmation that was a two-line reply becomes impossible to find.
This is why the habit at the end of this note is a habit rather than a procedure. Putting the order, the confirmation and the sent invoice into one place as each arrives costs seconds and happens while the material is still in front of you. Assembling the same file in month four costs an afternoon and produces something incomplete, and it is needed precisely in the cases where incompleteness is expensive.
The smallest version that still works
If none of the rest is realistic, four things carry most of the weight: what was agreed and when, the order reference, evidence that the work was delivered, and the invoice as sent.
Four items per job, in one folder, named after the job.
That is enough to answer the questions a stranger will ask, enough for an agent to take the case, and enough to survive a change of contact at the buyer. Everything else in this note improves the file; these four are the difference between having one and not.
The ten-second habit
When anything is agreed, delivered or changed, the message that records it goes in the job folder immediately.
Ten seconds, at the moment it happens, and the file builds itself.