Coding invoices in accounts payable means assigning each one to an account and usually a cost centre, and it is one of those tasks that looks trivial and quietly determines whether your management accounts mean anything. The difficulty is rarely that somebody does not know which account to use. It is that two people use different accounts for the same thing, or the same person codes differently in January and June, and the comparison everybody relies on is between two differently constructed numbers. This page argues that consistency matters more than accuracy in the abstract, and sets out how to get it in a team small enough that the rule lives in one person's head.
Consistency beats accuracy, and here is why
A cost coded to a slightly imperfect account every single time still produces a usable trend. The same cost coded three different ways produces a management account that moves for reasons nobody can explain. Trends are what small businesses actually use their accounts for.
Code at entry, with the document in front of you
Coding later, from a list, is guessing from a supplier name. Coding at entry, while the invoice is open, is reading. It also puts the decision with the person best placed to see the description, which is where it belongs.
Write the awkward cases down as they happen
Not a chart of accounts, which nobody reads, but a short list of the decisions that were hard: which account software subscriptions go to, how mixed invoices are split, where an annual licence is spread. That list is what makes a new starter code the way you do.
Questions people ask about coding invoices accounts payable
Should approvers code invoices?
They are often best placed to and rarely willing. A workable compromise is that payables codes and the approver corrects, which puts the knowledge and the accountability in the right places.
How do we handle an invoice covering several cost centres?
Split it, and write down the basis. The temptation is to code the whole thing to the largest, which is fine until somebody asks why one department's costs jumped.
Does coding affect the close?
Directly: a miscoded invoice is found during review, which is rework at the worst possible moment. On the worked example on this site, 40 tasks at 45 minutes plus 6 reviews at 30 is 33 hours, which is 2.75 working days across two people at six hours a day.