ERP
Sales orders and order lines, delivery notes, invoices and invoice lines, credit notes, agreed pricing and customer terms.
Revenue
The work you already paid for, but never charged
Nothing about this is dramatic. A trip is driven and the invoice run misses it. Extra hours are booked on a job and the order is invoiced at its original scope. A delivery goes out in two shipments and only one is billed. Each is small enough that nobody escalates it, and the operational system that recorded the work is not the system that produces the invoice. Coheed reconciles the two every morning and puts the gap in front of you while the evidence is still fresh enough to charge. It works from what your systems recorded, so work that was agreed verbally and never booked anywhere stays invisible here too.
- Systems combined
- ERPSCMTMS
- Runs
- Daily at 6am
Sound familiar?
Teams bring us this use case when one or more of these is true.
- You are fairly sure some work goes out unbilled, and you cannot say how much.
- Credit notes and late invoices are found by whoever happens to look, not by a process.
- Extra hours and material booked on a job depend on somebody remembering them at month-end.
- The month closes and the revenue figure never quite matches what the operation actually did.
How it works
Coheed runs this as a scheduled insight over your connected systems, then hands the result to an agent.
- 1
Completed work is collected from the systems that record it
Delivered order lines from the ERP and warehouse, completed trips from the TMS, and closed work orders with their booked hours and material from planning: everything that represents work actually done.
- 2
It is matched against what was invoiced
Each item is matched to the invoice lines that followed it, using the cross-system order and customer links the integration layer maintains, so a delivery split across two shipments or an order invoiced in parts still reconciles correctly.
- 3
The gaps are classified, not just counted
What is left over is separated into work that was never invoiced, work invoiced below what the order or agreement covers, and work still legitimately open, so nobody chases items that are simply waiting for the next invoice run.
- 4
The insight becomes an action
Confirmed gaps go to an agent that prepares the invoice or the correction with the underlying evidence attached, and routes anything touching a customer relationship through human approval.
Which data it uses
Only the fields this use case needs are read. Nothing is copied that the insight does not use.
SCM
Shipments, receipts, and the delivery registration that shows what physically left the building and when.
TMS
Completed trips with their customer, route, and completion date, for transport work that is billed per trip.
Coheed
The cross-system order and customer links, and the reconciliation history that shows whether a gap is new or recurring.
What changes
What a team notices once this runs. No invented percentages: the effect depends on your data and your process.
- Unbilled work is found in days rather than at year-end, when it is still defensible to a customer.
- The size of the leak becomes a number instead of a suspicion.
- Recurring causes surface: one route, one customer, one order type that keeps slipping through.
- Invoice corrections are prepared with evidence attached, so the conversation with the customer is short.
From insight to action
Unbilled Work Agent
Available as an agent
Runs after the daily reconciliation, drafts the missing invoice or correction with the delivery, trip, or work order it is based on attached, and holds it for approval. Nothing reaches a customer without a human releasing it.
Mode: Human-in-the-loop
Every insight can stay read-only, run with human approval, or run autonomously. You decide per action type, and you can change it later.
FAQ
Frequently asked questions
Isn't this what our accountant already checks?
An accountant reconciles what was booked against what was invoiced, both inside finance. This reconciles what physically happened, in the warehouse, on the road, or on the floor, against what was invoiced. Work that never became a booking at all is invisible in the first check and is exactly what this one finds.
Will it flag everything that is simply waiting to be invoiced?
No. Items still inside your normal invoicing window are classified as open rather than missing, and only start counting once they pass the cadence you set per order type.
Does it invoice the customer automatically?
Not unless you decide it should. By default the agent prepares the invoice or correction and holds it for approval, because a late charge is a customer conversation, not a bookkeeping entry.
Which systems does it need?
One ERP is the minimum, because that holds both the orders and the invoices. Adding the system that registers the physical work, your WMS, TMS, or production planning, is what makes it catch the work that never reached the ERP in the first place.
Built on these maturity levels
Most relevant for
Logistics & Transport
Combine your TMS, telematics, fleet, and finance systems into insights no single tool can produce.
B2B Commerce
Unify your webshop, ERP, and CRM so pricing, stock, and accounts stay in sync, and turn insight into agents.
B2B Wholesale
Close the gaps between CRM, ERP, and SCM so promises, stock, and margin hold across the whole order chain.
Manufacturing
Connect the quote, the shop floor, and purchasing so promised dates, real cost price, and margin per order finally agree.
Other use cases
Predictive Customer Lifetime Value
Score churn risk and future value per account by combining CRM engagement decline with ERP order frequency and value trends.
Lead-to-Quote Readiness
Surface correct ERP pricing, live stock, discounts, and customer agreements on every new CRM lead so sales can quote immediately.
Order Exception Monitoring
Catch stock gaps, unrealistic delivery dates, pricing errors, and missed agreements after the order, before the customer notices.
See this on your own data
Tell us your ERP, CRM, and SCM stack and we will show what this use case looks like on your systems.