You Delivered the Fuel. Where the Hell's the Invoice?

The truck got home. The revenue is still somewhere in a folder.

EDITOR'S NOTE: All quantities, prices, IDs, scenarios, and estimated exposure in this issue are synthetic. They are examples, not client financial results or an accounting or compliance conclusion.

DIRECTION DROP | Congratulations. You own an expensive receipt.

The truck loaded. The driver delivered. The customer got the fuel. And three days later, accounting is still asking whether the bill of lading belongs to Tuesday or Thursday.

Everybody did a job. Somehow, the company still hasn't finished the job.

A delivery is physical work. An invoice is a financial record. They need to agree, but they're not the same thing. Your delivery-to-invoice gap is where missing paperwork, wrong product codes, split loads, and wishful thinking hold hands and wander off with the money.

Mission: Find every completed delivery that is not yet ready to bill, give each exception an owner, and never turn a missing document into an invisible problem.

COMMAND DROP | Four pieces. One chain of evidence.

Treat order-to-cash as four connected records, with the ERP or accounting system remaining the financial system of record.

1. ORDER: Who ordered which product, for which location, under which pricing and delivery terms? This creates the commercial instruction; it does not prove delivery.

2. LOAD / BOL: What product and quantity were loaded at the source? A bill of lading (BOL) is a movement record. One BOL can support more than one delivery, so don't pretend the BOL number alone identifies a customer drop.

3. DELIVERY EVIDENCE: What quantity reached the destination, when, and under which delivery ID? Record the proof required by the contract and operating procedure. Confirm whether the agreement bills on gross, net, metered, or another defined quantity basis.

4. INVOICE: Which customer, product, quantity, price, tax treatment, and invoice number ended up in the finance system? Record the link back to the actual delivery and approved price source.

The chain is ORDER -> LOAD -> DELIVERY -> MATCHED -> INVOICED. A mismatch diverts to EXCEPTION with a reason, owner, timestamp, and next action. No disappearing into a "miscellaneous" tab where problems go to retire.

The reconciliation controls that earn their keep

Do not automatically delete, replace, or generate a final invoice because one spreadsheet row happens to match. Your ERP controls posting. Human approval and proper segregation of duties remain in place where required by policy.

FIELD BUILD | The money isn't gone. Yet.

Synthetic example only: A distributor completes 150 deliveries in a week. Three completed delivery records have no matched invoice. If the average intended invoice value for those three is $2,200, the unbilled amount under review is $6,600 (3 x $2,200). That is not automatically lost revenue or net profit. It is a billing and cash-flow exposure until somebody reconciles it.

Now give each unmatched record a cause. One is missing delivery evidence. One was a split load where the system reused the wrong reference. One has a product-code mismatch. A good reconciliation board shows all three, their age, and their owners. A useless dashboard celebrates "150 deliveries completed" while pretending the last three never happened.

Acceptance test: A reviewer can list all deliveries completed but not invoiced, reproduce the matching logic, identify duplicates, and explain every manual override with a timestamp and accountable user.

SIGNAL CHECK | Three ways the cracks widen

• You reconcile on names instead of IDs. The same customer may have more than one tank, site, or account. Use stable identifiers for orders, stops, and invoicing.
• You overwrite the original source. Preserve raw imports and record corrections separately. Otherwise nobody can explain why Tuesday's gallons changed after Friday's invoice run.
• You never age exceptions. A two-hour missing ticket and a two-week missing ticket are not the same emergency. Set internal escalation windows and review them daily. Those windows are business controls, not legal deadlines.

For applicable hazardous-material highway transport, separate statutory shipping-paper retention and accessibility requirements from your commercial delivery-to-invoice reconciliation. Do not treat a customer signature or accounting attachment as a blanket substitute. See 49 CFR 177.817.

TOOL OF THE WEEK | Reconciliation before expensive software

For a small operator, start with read-only exports from dispatch and the ERP. Load them into a controlled spreadsheet or database view. Join by approved keys, flag unmatched items, and publish only exception counts to general dashboards. Keep customer details and financial records behind least-privilege permissions.

For larger volume, use a database with unique IDs and a versioned import contract. Make imports idempotent: retrying the same file must not create a second load or invoice candidate. Log job IDs, counts, errors, and checksums, not customer names, account numbers, or sensitive delivery details. The raw source stays in approved storage.

If a vendor sells you an "autonomous revenue intelligence platform" that can't explain how it handles split deliveries, save your money. Buy the dispatcher coffee and ask for the actual failure cases.

FREE DROP | The five-point unbilled load hunt

1. Export completed deliveries for a defined business day.
2. Export posted or approved invoices for the same operating window.
3. Match using stable delivery IDs and documented split-load rules.
4. Review unmatched deliveries, duplicates, quantity variances, and price conflicts; assign owners.
5. Re-run after corrections, and retain an exception log with evidence of closure.

STOP POINT: If the source records or pricing basis cannot be verified, route to review. Never invent the missing gallon, price, signature, or timestamp just to make a cell turn green.

THE LAST WORD

Moving fuel without billing it is just an expensive field trip. Finish the chain. Pay the people. Keep the receipts. And stop making accounting perform a forensic investigation every damn Friday.

WORKS CITED / CHECK THE RECEIPTS

• PHMSA highway shipping-paper requirements and retention, 49 CFR 177.817
• PHMSA interpretation on shipping-paper duties and responsibilities (2026)
• Google Apps Script quotas and limits
• OWASP Logging Cheat Sheet (avoid sensitive data in application logs)

Pipeline Punks is the workshop side of True North Data Strategies LLC. Editorial and training only. Verify current regulations, accounting policies, customer agreements, and pricing terms before operational use. No client data is included.

Jacob Johnston | 719-204-6365 | jacob@truenorthstrategyops.com

Back to top