One Duplicate Buys an Audit

Say ticket 4417 came off the scale on a Tuesday morning: 22.4 tons of 3/4 minus, Hartline Excavating, $9.50 a ton. The yellow copy rode back across the pit on a clipboard in an open cab, through forty minutes of rain. By the time it reached the office tray, the tonnage was a gray smear.

The driver did the sensible thing. He copied everything onto a fresh ticket, turned the clean one in Wednesday, and tossed the wet original on the dash to deal with later.

It dried out. Two weeks on, it slid from behind the visor during a cab cleanout and landed in the tray with that day's paper, looking exactly like what it was: a ticket nobody had keyed. So the clerk keyed it. The month-end invoice to Hartline carried the same load twice, $212.80 each time.

Hartline's AP clerk found the pair in about four minutes, because matching tickets to invoice lines is her job. Same serial number, same truck, same minute on the clock. One phone call, one credit memo. On your books, the whole episode nets to zero.

That's the paper math. The real transaction happened inside the clerk's head.

What the clerk learned for $212.80

Before the duplicate, your invoices got the treatment every long-standing vendor earns: a glance at the total and a stamp. You were a vendor whose paper could be trusted.

After the duplicate, you're a vendor who has billed twice for one load. Not in her opinion. In her documentation.

So the next invoice gets matched line by line. And the one after that. An email arrives: "Going forward, please attach signed scale tickets for all invoice lines." Payment that used to land in 30 days starts landing in 45 or 50, because full matching happens when she gets to it. Questions that used to be waved through now get raised, and every question is twenty minutes of your office's time. And when she finds a line she doesn't like, she doesn't call anymore. She deducts it from the check and lets you chase the difference, because the duplicate taught her that your invoices contain errors and her deductions are probably right.

Say Hartline runs $35,000 a month with you. Twenty extra days of payment float parks roughly $23,000 of your money in your receivables for as long as she keeps matching. Borrow against your line at 9% and that's about $2,100 a year in interest, bought by one wet ticket. The deductions and the office hours ride on top.

The claim your bookkeeper will argue with

Here's the part worth disputing: a caught duplicate costs you more than a missing ticket of the same size.

The missing ticket is the error everybody fears, and it should be. It costs face value, $212.80, quietly and forever. But it costs it once, and nobody thinks less of you, because nobody knows.

The duplicate is the error everybody shrugs at, because the credit memo makes the customer whole and the ledger closes clean. But it's the only ticket error your customer is guaranteed to see, and it changes how your invoices are read for years. Every other leak in your operation drains once, at the rate of the error. This one keeps charging you every month the audit stays on.

If that's wrong, it's wrong in a checkable direction. Pull the file on any customer who ticket-matches you today and look for the incident that started it. There usually is one.

Where the pairs come from

It's tempting to file ticket 4417 under careless driver, but that's the wrong lesson. Duplicates aren't made by people. They're made by lanes in your process that legitimately print two papers for one load.

The rewrite of a smeared or torn ticket. The reprint when the carbon strikes light. The DOT job where the load crosses a certified public scale and picks up a second weight document that travels with the first. The ticket turned in late, keyed from the driver's radio call, then turned in again as paper. Run an operation long enough and these lanes produce pairs on schedule, whatever you tell the drivers.

flowchart TD
    A["Smeared ticket gets rewritten"] --> E["Two papers, one load"]
    B["Light carbon gets reprinted"] --> E
    C["DOT load adds a certified scale ticket"] --> E
    D["Radio call keyed, paper arrives later"] --> E
    E --> F["Your keying desk finds the pair"]
    E --> G["Their AP clerk finds it first"]
    F --> H["Costs a staple"]
    G --> I["Costs the audit"]

Which means the question was never whether two papers will exist for one load. The question is who finds the pair first, your keying desk or their AP clerk. That's a race.

Winning the race

The serial number is the dedupe key, and your carbon books already have it. Three habits close most of the gap:

• A rewrite carries its ancestry. A recopied ticket gets the original's serial written across it ("REWRITE OF 4417"), and the damaged original is stapled to the book stub, not left in a truck.
• The keyed list gets sorted by serial once a month. Five minutes in the workbook. Any serial that appears twice is a pair you caught before the customer did.
• A second weight document never becomes a second line. The certified scale ticket gets stapled to the pit ticket at the window, the day it arrives.

This check is mechanical, which is also why it suits software. Termco reads the tickets your operation already produces, carbon rewrites and coffee rings included, and flags a serial it has seen before, at intake, while the invoice is still unbuilt. Nobody at the scale changes anything. The paper stays paper. If you want to know whether pairs are already slipping through your tray, send 10-20 sample tickets to hi@termco.ai and you'll have findings within 48 hours.

Either way, run the serial sort this month. The duplicate you catch at the keying desk costs you a staple. The one your customer catches costs you the benefit of the doubt, and you don't buy that back with a credit memo.