Invoices are the highest-volume coding decision in most companies, and they split cleanly in two: PO-backed invoices, which inherit their coding from the purchase order, and non-PO invoices, which arrive with no coding at all and need a decision on the spot.
The first group is a pipeline problem. The second is where the judgment, the delay, and the errors concentrate.
PO-backed invoices inherit their coding
When the requisition was coded properly, the invoice rides the purchase order's coding straight through. The failure mode is upstream: a requisition coded to a dumping-ground account, or an order amended without touching its accounting block, propagates the error to every invoice that follows. Inheritance is only as good as what gets inherited.
Non-PO invoices are where coding gets hard
A services bill with no order forces the question: whose budget, which account, which project. The answer usually lives with the requester, who answers slowly, or with an AP coder working from memory of similar bills. This is the population where coding time dominates processing time and where most miscoding happens.
Splits and accruals multiply the decisions
One invoice, three cost centers. A repair that is partly maintenance expense and partly capital. A December invoice for January service. Splits, capitalization calls, and period cutoffs turn one coding decision into several, each with its own way to be wrong and its own month-end consequence.
Coding errors surface at month-end, when they cost most
Wrong coding rarely blocks payment, so it travels silently until the close, then shows up as variances to explain and reclasses to book under deadline. The cheapest moment to code correctly is the first one. Every later correction costs more and is done under more pressure.
Precedent should do the coding
Almost every invoice, including the hard non-PO ones, resembles something the company has coded before. A system that reads that history, the supplier's past coding, the requester's cost center, the project's spend pattern, can code the routine cases autonomously and route only the genuinely new ones. Automated GL coding covers what that takes.
Fragment codes invoices from precedent across your ERP and documents, and asks a person only when the case is new. See how it works or request a demo.