End of day reconciliation has a particular kind of dread attached to it in a van sales operation: the vans are back, the cash tin is out, and somewhere between the doorstep and the depot the numbers have stopped agreeing — a few pounds short here, three cases unaccounted for there. The variance is rarely one big leak. It is many small, boring gaps, each created hours earlier by something that was never written down at the moment it happened. This article lays out the three checks a day-end has to close — stock, today’s sales, today’s payments — the nine places the variance hides, and the discipline (and tooling) that turns a two-hour argument into a routine.
The three checks the day must close
Strip away the paperwork and a van sales day is a closed system that has to pass three checks: the stock must reconcile, today’s sales must reconcile, and today’s collected payments must reconcile. If any check fails, something happened that was not recorded:
Day-end variance is simply the difference between what these checks predict and what the count and the cash tin actually show. That reframing matters, because it turns “the money’s short” — an accusation — into “which recorded number is wrong?” — a traceable question.
The nine places the variance hides
Work through these common sources when a day won’t balance — each one names the record that was missed:
| # | Leak | What actually happened | Which equation it breaks |
|---|---|---|---|
| 1 | Unrecorded giveaways | A free case to smooth over a complaint, samples for a new line — goods left the van with no document | Stock |
| 2 | Returns taken, not booked | Product came back over the doorstep — van stock physically rose — but no return document was raised | Stock (and cash, if a refund was given) |
| 3 | Doorstep price overrides | The driver honoured a price the system did not know about; invoice and expectation diverge | Cash |
| 4 | Part-payments misallocated | £40 against a £55 invoice recorded as settled, or against the wrong invoice | Cash |
| 5 | Missed or handwritten invoices | A sale completed on a promise or a pad — the system never saw it | Both |
| 6 | Load list ≠ what was loaded | The van left with more or less than the paperwork says; the day starts pre-broken | Stock |
| 7 | Damage and expiry untagged | Written off in reality, still “good stock” on paper | Stock |
| 8 | Credits raised days later | The adjustment lands in Thursday’s numbers for Tuesday’s problem | Cash (timing) |
| 9 | Cash handling gaps | Float errors, change mistakes, notes in the wrong envelope | Cash |
Notice what the list has in common: almost every leak is a recording failure at the moment of the event, not a counting failure at the end of the day. Counting harder at 6pm cannot recover a fact that was never captured at 11am. That is why the fix lives on the doorstep, not in the depot.
A worked day-end: finding two variances in one van
Van 3 comes back. First, the stock equation:
| Stock movement | Units |
|---|---|
| Opening van stock | 84 |
| + Loaded at depot | 240 |
| + Customer returns received | 6 |
| − Sold / delivered | 262 |
| − Damage written off | 4 |
| − Unloaded back to depot | 30 |
| Expected closing stock | 34 |
| Counted on the van | 31 |
| Stock variance | −3 |
Then the money. Today’s invoices came to £1,842 with £36 of credits, of which £610 was left on account — so payments applied to today’s invoices should total £1,196. The driver also collected £75 against last week’s outstanding invoices, reconciled separately under (b). Expected across recorded payment methods: £1,271. Counted: £1,256.40. Money variance: −£14.60.
Now the trace, and this is where recording-at-source pays. The £14.60 resolves in minutes: one invoice for £54.60 shows a payment recorded as settled while the terminal shows £40 taken — a part-payment keyed as full (leak 4), fixed by re-posting £14.60 to the customer’s account balance, no money missing at all. The three units take one question at tomorrow’s brief: a replacement handed over at a complaint stop with no free-of-charge document raised (leak 1). Neither was theft; both were unrecorded events — and both now carry a reason code instead of a suspicion.
Give the residue a reason code
Whatever variance survives the trace should be logged per van, per day, against a short fixed list: price override · unrecorded return · unrecorded FOC/replacement · damage · cash handling error · loading variance · credit timing · part-payment misposting · unexplained. The list matters more than tonight’s zero: a fortnight of coded residue tells you which leak to fix structurally (one van always “loading variance”; one round always “price override”), and it keeps “unexplained” honest — a category that should shrink month by month, and stand out sharply when it does not.
End of day reconciliation that traces instead of argues
The discipline has three parts, and each maps to a leak cluster:
- Start from a true zero. The load against a system load order, checked on, so leak 6 cannot pre-break the day. Periodic blind van counts keep the opening figure honest.
- Record every event where it happens. Sales invoiced at the doorstep; returns, damages and giveaways captured as their own documented types the moment goods change state; payments taken against the specific invoice, with part-payments recorded as part-payments. This closes leaks 1–5 and 7 at the source.
- Run all three checks daily, and log the residue. Whatever variance survives gets a reason code, per van, per day. Patterns identify themselves quickly once variance is a dataset instead of an argument.
This is exactly the shape of RouteMagic’s van sales workflow. The driver app invoices on the spot and takes cash, card, cheque and bank-transfer payments against the invoice, offline-first, which reduces the opportunity for leaks 3, 4 and 5; returns (leak 2), free-of-charge samples and replacements (leak 1) and stock-condition changes for damage and expiry (leak 7) are each captured as their own documented event at the moment they happen; loads go on against system load orders and van stock is counted in-app, including blind counts, which pins down 6; and electronic proof of delivery settles the disputes that used to become late credits. Payments against older invoices are recorded against the specific outstanding invoice, so old-debt collections reconcile under their own heading instead of muddying today’s takings. None of this guarantees a zero — software cannot stop a case walking off a tailgate — but it changes what the variance is: every doorstep event posts timestamped to the same live inventory and ledger, so the checks arrive at the depot with far less left to explain, and what remains can be traced against records rather than memories. That is the basis of the 15-minute end-of-day reconciliation published on RouteMagic’s van sales page — a published platform positioning, and a fair description of what day-end becomes when the day is recorded as it happens.
Conclusion
Day-end variance is rarely a counting problem — it is an event-capture problem wearing one. A day that will not balance is a day where something changed hands without being recorded at the moment it happened, and no amount of harder counting at 6pm recovers a fact that was never written down at 11am. Hold the day to its three checks — the stock movements, today’s sales settlement, and every payment collected today reconciled by method against the ledger — and record each event at source: the return as it comes over the doorstep, the replacement as it leaves the van, the part-payment as a part-payment. Then give whatever residue survives a reason code instead of a shrug. A practical way to start this week: run the reason-code log per van for a fortnight before changing anything else. The pattern that emerges will tell you which leak to fix structurally — and it usually is not the one everyone suspected.
