The job nobody logged: finding work that never entered the system
Last updated November 16, 2026 · 6 min read
Short answer
You cannot cross-check a work order that was never created — but the supplier statement remembers. A part bought for the van, matched to no job and no invoice, is the fingerprint of unlogged work. The check finds parts with no job, and that is where forgotten jobs surface.
The data reality
Where to export: Supplier purchase statement (parts purchased in the period) crossed against work-order parts lists and invoice lines; the check finds purchased parts no job claims.
Columns that matter: Part number · Purchase date · Quantity · Cost · Linked job number
Supplier statements list purchases, not usage. Truck-stock withdrawals blur the trail unless the office records which job consumed each part — that link is what the check needs.
Why this system leaks
A neighbor calls the technician directly — a capacitor dies, the tech is nearby after hours, the job is done in forty minutes with a part from the van and cash or a promise to pay later. No work order is created, no invoice raised, and the van stock is replenished next supplier run. The job exists in reality, in the supplier statement's replenishment rows, and nowhere in the system.
Every report in the shop is built on records, and this job has none. The FSM shows nothing, QuickBooks shows nothing, the income report is accurate about what it was told. The only trace is a part purchase that no job ever claimed — which is precisely the orphan the supplier-statement cross-check finds.
Why this leak is invisible to every record-based report
FSM reports show logged work; QuickBooks shows invoiced work. An unlogged job exists in neither. The only system that recorded anything is the supplier — the part purchase. That is why the cross-check runs the supplier statement against job and invoice lines: the paper trail of the part is the paper trail of the job.
The side-call is where trust and leaks meet
Neighbors, relatives, after-hours favors — most unlogged work starts as a favor or a shortcut. The fix is not suspicion; it is a rule that removes the decision: every part that leaves the van is attached to a job number, and every job number becomes an invoice. Favor pricing is fine; logging is not optional.
The count tells you the size of the hole
Shops are often surprised by how many orphan parts a month produces. Each orphan is either replenished stock or unlogged work — and the ratio, once measured, tells the owner exactly how much work is escaping the system. Measurement alone usually ends it.
A worked example
Supplier statement shows a 45/5 µF dual-run capacitor purchased in the period. No work order lists it and no invoice bills it. The technician confirms a Saturday call that was never logged — capacitor $68 plus 40 minutes of labor at $95/hour, invoiced only as a verbal promise.
- Recorded work
- $245.00
- Invoiced
- $0.00
- Residual
- $245.00
The orphan part anchored a real job: $68 part plus $177 labor under the log-it-now rule the shop adopted afterward. Residual = $245. The supplier row was the only evidence the work ever happened.
What the data cannot show
- Van-stock purchases are legitimate inventory, not leaks — the check flags parts with no job only after the shop confirms its stock-replenishment rhythm; the conversation, not the algorithm, separates stock from unlogged work.
- Unlogged jobs are found by inference (orphan parts, customer callbacks), not directly — no record exists to reconcile. The check surfaces the fingerprint; the office confirms the job.
Questions shops ask
How do you find a job that was never logged?
Indirectly. The system flags supplier purchases that no work order and no invoice claim — orphan parts. Each orphan is either van stock being replenished or a job that was never logged; the office confirms which, and the unlogged ones become billable immediately.
What should we do when we find an unlogged job?
Log it now, invoice it now. The customer received the work and in most cases expects the invoice. The pattern to fix is the missing rule: parts leave the van only against a job number.
Does this mean our technicians are stealing?
Almost never. Unlogged work is overwhelmingly shortcuts and favors, not theft. The fix is process — a part-to-job rule — not suspicion. The report gives you the count; the conversation gives you the cause.
Run the free check on your files
Run the free check on your files