Software in January, subscriptions in February
A client's monthly accounting software subscription went to computer costs in January, when one bookkeeper did the month. In February it went to subscriptions, because the holiday cover did it. In March, back to computer costs. Fuel went to motor expenses one month and travel the next. The totals are right; the lines jump about.
The client, reading their monthly pack, asks why subscriptions doubled. Nobody has a good answer, because nobody chose it. It just depended who was at the desk.
Why coding varies across a team
Every bookkeeper has habits learned at their last firm or from their first client. The chart of accounts for each client is different, often inherited, with overlapping accounts that invite different choices. Bank rules help with the regulars but only where someone set them up, and they are not visible to whoever is working on the file unless they go looking.
Firms with freelance or remote bookkeepers see more of this, because there is less day-to-day contact to smooth out habits. Growth makes it worse: every new starter adds another set of instincts.
What inconsistent coding costs
Month-on-month comparisons become unreliable, which undermines the management figures you sell. Year-end adjustments pile up when the accountant reclassifies. VAT treatment can go wrong when a supplier is coded to an account with a different default rate. And reviewers spend time correcting the same patterns again and again.
| Where drift shows up | What the client notices |
|---|---|
| Recurring suppliers moving between accounts | Lines jumping month to month |
| Similar accounts used interchangeably | Budgets that never compare |
| Different VAT rates for one supplier | Queries from their accountant |
| Capital items expensed some months | Surprises at year end |
How we build consistent coding across the firm
- We read each client's transaction history through the Xero or QuickBooks API and work out how each regular supplier and payee has been coded, including where it has varied.
- Where history is consistent, that becomes the draft rule. Where it varies, the reviewer or client manager picks the right treatment once, and that choice is recorded.
- Rules are pushed into the ledger's own bank rules where it helps, and kept in a visible rulebook per client that anyone working on the file can read.
- Each month, before review, a check compares new postings with the rules and flags anything coded differently, with the rule and who set it.
- A firm-wide view shows which clients have the most drift and which staff tend to deviate, framed as a training aid rather than a scoreboard.
- When a new supplier appears, a model suggests an account based on similar suppliers across the client's history and your firm's standards, for the bookkeeper to accept or change.
Rules are yours and can be changed at any time. The check only asks 'is this intended?'; the bookkeeper or reviewer answers.
Clients sometimes cause drift themselves, for example by coding their own card spend in the ledger between your visits. The check treats their postings the same way, so you can see where the client's own habits are the source and have a gentle conversation about it, or lock those accounts down if the ledger allows.
Accounts that read the same every month
Clients see lines that make sense from month to month. Reviewers stop correcting the same things. New starters and cover staff pick up a client's conventions from the rulebook rather than by trial and error. And the firm has a written standard, which makes growth and remote working far less risky for quality.
Sound familiar?
- Clients ask why a cost line jumped when spending did not change.
- The same supplier appears in different accounts across the year.
- Holiday cover changes how a client's books look.
- Reviewers correct the same coding patterns every month.
- Your coding standards are unwritten.