Completed vs billable
The floor marks a job done. Finance asks if it was billable, complete, or awaiting sign-off. Sales already promised a date the system does not reflect. Without a shared state model, you get duplicate entry, month-end arguments, and coordination costs that rival those described in multi-site mess — only at single-site scale with fewer sites to blame.
Ops and accounts are not speaking different languages on purpose. They optimise for different outcomes: throughput, margin, cash. The handoff between them is often implicit, and implicit handoffs fail loudly at month-end.
One status list both teams recognise
Write states in plain English that both teams will actually sign — not ERP jargon only finance understands, and not whiteboard shorthand only the floor uses. Something like: complete awaiting QA, ready to invoice, invoiced, on hold — customer. Each state names who moves it next and which system is the source of truth.
Pick one system of record for customer-facing status. If finance owns the invoiced state, ops must not maintain a parallel "done" list that disagrees with it. Updates should happen as part of the work itself, not in a meeting — the meeting that replaced the system covers what happens when you let that slip.
Weekly fifteen minutes beats a new ERP
A variance sync — ops and finance, same report, same definitions — catches drift before it becomes blame. Focus on exceptions: jobs marked done but not billed, billed but not complete, WIP that has aged past tolerance. When you find one, fix the rule or the field, not the person.
Do not buy another module until this sync has run for six weeks. Often the fix is discipline plus one field, not a platform. Quotes, jobs, and invoices for trades covers UK-shaped examples of how this works in practice.
WIP and margin need the same language
Work in progress arguments happen when ops counts units complete and finance counts cost absorbed. Agree whether percent complete is manual, system-calculated, or not used at all. One method, written down. Without that, margin conversations become moral debates rather than operational ones.
Trades and manufacturers across Teesside and the North East often run job costing in one tool and invoicing in another — that is fine if the state handoff is owned. It breaks when each team maintains a private truth until month-end.
Include site managers in the state list workshop, not only finance. If the floor will not say the words on the list, the list will not survive Tuesday.
Change orders and snagging are where floor-to-finance most often breaks down. Ops marks complete, the customer disputes a line, and finance waits for a paper sign-off. Name the state for "disputed" and "ready to invoice" explicitly. Do not leave a grey zone that becomes email.
If ops live in a job system and finance in a ledger, a thin sync of state and invoice triggers may beat re-key — the integrate before you replace argument applies here. Name an owner for mismatches, and build toward one report the room trusts for WIP and margin.
Start the fix in one room with both teams present — not an email thread that reopens the same argument next month. End with a signed state list posted where both teams work. That list is the contract until software catches up.