What it means
An invoice may contain several types of cost: a supplier might bill equipment, installation and a service plan together. If a clerk charges everything to repairs, the fixed-asset record, current expense and maintenance forecast can all be wrong.
Build clear coding rules for frequent purchases, with a usable chart of accounts that has descriptions and examples, and give project codes and cost centres named owners and active dates. A default code copied from a past invoice can save time but also repeat a mistake when a supplier's work changes.
For mixed invoices, allow allocation across lines with evidence of how the split was determined. Design the review sample carefully.
If reviewers inspect only large invoices, they may miss a common small-item error; if they count every line equally, one complex invoice can dominate the rate. State whether the denominator is invoices, invoice lines or monetary value, and categorise errors by account, cost centre, project, tax code or missing evidence.
Tax coding can have separate consequences, because the presence of a tax amount on an invoice does not by itself establish that input tax is recoverable; the business needs the correct documentation and applicable rule. Where a local requirement is material or uncertain, the tax owner should review it.
Automation and supplier templates help, but they need oversight: optical recognition may misread a cost centre or carry an outdated code, and a purchasing system may pass the code from a purchase order, which is useful only if the order was coded correctly. Check both the invoice and the source order on a sample basis.
Set approval paths for unusual expenses and changes to project allocation. Use errors to improve upstream work: if a whole department repeatedly enters the wrong project code, fix the order form or training rather than only sending corrections back to accounts payable, and if a supplier sends vague invoices, ask for clearer line descriptions.
For owners, the aim is a report that can be used to decide. A high accuracy rate is useful, but look at the financial size and type of the remaining errors, because one wrongly capitalised purchase can matter more than many minor department miscodes.
In practice
Real-world examples.
Example
A contractor invoice covers repairs and new equipment. The finance team separates the lines under its policy rather than posting the total to maintenance. The equipment is capitalised, and only the repair labour reaches the expense report.
Example
A marketing invoice is charged to the wrong client project. The project manager catches it before the monthly margin report is issued. Finance reposts it with a note, and the client margin is restated before anyone sees the wrong figure.
Example
An automated system assigns a familiar supplier's new training service to the old software subscription code. A reviewer checks the invoice description and corrects the code. The supplier's default is then updated so the error does not recur.
Formula
Calculation
Invoice coding accuracy = Correctly coded invoices in the reviewed population / Invoices reviewed x 100
Worked example. An invented company reviews 200 posted invoices and finds 184 with the correct account, cost centre and project coding under its stated rules.
- Invoice coding accuracy = 184 / 200 x 100 = 92%.
- It then reviews the amount and type of the 16 errors before setting a remedy; the percentage alone does not show their financial effect.
If one invoice can contain several codes, a line-level metric may better reflect the work. Use a consistent sampling method across periods.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Blue Cedar Installations, an invented company working on several building projects. Its monthly reports showed one project losing money while another appeared unusually profitable. A project lead found that a supplier's installation invoices had been coded to the wrong project because the system copied a code from the supplier's first job. Finance reviewed the affected invoices, purchase orders and site confirmations. It corrected the allocation using its documented adjustment process and explained the revised reports to both project leads.
The team then made project code a required field on new purchase orders and sampled recurring suppliers' invoices each month. Complex shared costs required an approved allocation basis rather than a guess by the clerk. The next reports were not perfect, but the source of errors became visible. The owner could compare project margins with greater confidence, while the finance team spent less time undoing mistakes after the close.
Watch out
Common mistakes.
- Measuring only how quickly invoices are entered while ignoring account and project errors.
- Relying on a supplier's historical default code when the purpose of its work changes.
- Treating all errors as equal without considering amount, tax effect and whether reports were already issued.
Questions
People also ask.
Should accuracy be measured per invoice or per line?
Choose a consistent unit that fits invoice complexity; mixed invoices often need line-level review.
Can automated coding replace review?
It can reduce manual work, but samples and exception checks are still needed for changed services and poor source data.
What happens after a coding error is found?
Correct it with an audit trail, assess any affected report or tax filing, and fix the upstream cause where possible.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%