- A connected order-to-invoice flow keeps shipments and billing tied together, so work cannot leave the building and quietly stay unbilled.
- A building-products distributor recovered roughly $200K of shipped, installed work that had never been invoiced, surfaced during a year-end review rather than by any system flag.
- The gap was in the tooling, not the team: QuickBooks has no required field, validation, or alert to flag an order that shipped but was never billed.
- Business Central ties posted shipments to invoicing and offers delivered-but-uninvoiced views, so a monthly review becomes a real control instead of a year-end surprise.
Work can leave the building before it is invoiced, and if nothing links the shipment to the billing, the two can drift apart without anyone seeing it. It is one of the more common gaps we find in growing distributors and contractors, and it is exactly the kind of thing an ERP (enterprise resource planning) system is built to close.
We saw a clear example of it recently. A multi-division building-products distributor told us they had recovered close to two hundred thousand dollars of work they had shipped, installed, and never invoiced. What stood out was how they found it: by chance, during a year-end review, rather than from anything in their system flagging it.
How an order ships without an invoice
The pattern is ordinary, which is what makes it easy to miss. Materials go onto a sales order. They are purchased, shipped, and installed. The sales order is simply never turned into an invoice, and nothing in the system is set up to notice, so the order looks settled while the billing step quietly goes undone.
At roughly three million dollars in annual revenue, that uninvoiced work was close to ten percent of the top line. Once it surfaced, part of it was hard to collect: an invoice that arrives months after a job wrapped up is a difficult conversation, and some customers are reluctant to pay it.
A careful team can still miss this, because the tool has no checkpoint for it. QuickBooks has no required field, no validation, and no alert to say an order shipped but was never billed. The step depends entirely on someone remembering it, every time.
How Business Central keeps it connected
This is the kind of gap an ERP system is designed to close. In Business Central, Microsoft's cloud ERP, the order-to-invoice flow is connected on purpose:
- Posted shipments are tied to invoicing, so the system knows what shipped and what has been billed.
- You can run open sales orders with aging, and pull views of what has been delivered but not invoiced.
- A monthly review of open and undelivered-but-uninvoiced orders becomes a real control, not a year-end surprise.
None of that is advanced. It is the difference between a system that records what you enter and one that surfaces what was missed.
The simplest habit to adopt, whatever system you are on: once a month, someone runs the list of orders that shipped but were never invoiced, and clears it. In Business Central that is a standard view. In a tool without one, it is a manual spreadsheet kept up by hand.
Why the connected flow matters
The two hundred thousand dollars is the figure that gets attention, but the real point is quieter: when a system has no guardrails, invoicing depends on everyone remembering every step, every time. That holds up until it doesn't, and the shortfall surfaces at year-end instead of the same week. A connected order-to-invoice process moves the safeguard from memory into the system, where a routine monthly check can catch what slipped before it ages.
If you suspect work is going out without being billed, a review of your open orders usually surfaces it quickly. We are glad to help you run that review. Let's talk it through.