Manaz Afzal

Accounting & Finance · Growing businesses

The right account on every bill, including suppliers who sell more than one thing

Bill coding for accounting practices on Xero and MYOB, tested on 59,886 real supplier payments against the supplier default bookkeepers correct today.

79%coded right; supplier default 67%
63%of bills posted without review at 91% accuracy
25%right for brand-new suppliers, which have no default

Executive summary

A learned coder sets the right account on 79% of supplier bills, against 67% for the supplier default, and posts 63% without review at 91% accuracy.

79%of bills coded right; supplier default 67%
63%posted without review at 91% accuracy
25%right for new suppliers, which have no default

Situation

An accounting practice’s bookkeepers check and correct the account on every captured bill; the supplier default misses whenever a supplier sells more than one thing.

Approach

A coder from supplier name, history, amount and cost centre, fitted on 187,269 real payments and tested on 59,886 later ones against the supplier default.

Result

79% coded right against 67%; a 0.8 confidence bar posts 63% of bills without review at 91%.

The problem

In a bookkeeping practice the supplier, date and amount on a bill are now read reliably by Dext, Hubdoc or Xero’s own capture, and supplier rules post the simple ones automatically. The time that is left is the account code. Xero and MYOB suggest the account the supplier was coded to last time, a bookkeeper checks it, and the suppliers that sell several kinds of thing get corrected by hand, bill after bill. Practices that remove that step say it is what lets one bookkeeper look after two or three times as many client files.

I wanted to measure how often the supplier default is right on a large real ledger, how much a coder that also reads the description and amount adds, and how many bills could post without a review at an accuracy a practice principal would sign off.

Team
Practice principal, client managers, bookkeepers
Scale
Hundreds to thousands of bills a month across many client files
Systems
Xero or MYOB Business, Dext or Hubdoc, Xero Practice Manager or FYI
Measure
Bills posted without an account edit; bookkeeper minutes per bill

What I built

A coder that proposes the account for each captured bill from the supplier name, the supplier’s coding history, the amount and, where known, the client’s cost centre or tracking category, with a confidence score. Confident bills go to Xero or MYOB as drafts with the account set; the rest arrive in the bookkeeper’s queue with the top suggestions ranked.

Bill capturedDext, Hubdoc orXero bill inboxCoderAccount andconfidence scoreDraft billConfident bills postedwith the account setBookkeeperThe rest, with rankedsuggestions
Every correction becomes training data, so the coder learns each client’s chart of accounts.

Results

I tested on real supplier payments from a public ledger: 247,155 payments with the account chosen by the finance team across 131 expense accounts, fitted on payments before October 2025 and tested on the 59,886 that followed. The supplier default coded 67% of bills correctly. The learned coder reached 75% from the supplier and amount alone, and 79% when the cost centre was known.

Most common account for every bill21%Supplier default: last account usedhow Xero and MYOB pre-fill a bill67%Supplier’s most common account72%Learned coder: supplier, amountname patterns and supplier history75%Learned coder plus cost centrewhen the client or tracking category is known79%
62% of suppliers with five or more bills were coded to more than one account, which is why the supplier default misses. Data: London Borough of Camden, payments over £500

Posting without review

At a confidence bar of 0.8 the coder posts 63% of bills with the account set, and 91% of those match the finance team’s choice. The bookkeeper reviews the rest. A practice sets the bar per client: tighter for a client with GST-sensitive coding, looser for a simple file.

60%70%80%90%100%20%40%60%80%100%Accuracy on auto-coded billsBar at 0.8: 63% of billsat 91% accuracyShare of bills posted as drafts without a bookkeeper editing the account
Confidence barBills auto-codedAccuracy on those bills
0.6078%83.7%
0.8063%90.8%
0.9053%93.2%
0.9546%96.3%

Repeat and new suppliers

Repeat suppliers carried 94% of bills in the test year. For them the coder adds about seven points over the supplier default. For new suppliers there is no default at all; the coder still gets 25% right from the name alone, and 33% with the cost centre, which turns a blank field into a ranked shortlist.

Supplier defaultLearned coderRepeat suppliers78%New suppliers25%
A new supplier has no default in Xero or MYOB, so the bookkeeper starts from a blank account field.
Supplier defaultLearned coder£500 to £1k77%£1k to £2.5k76%£2.5k to £10k74%£10k to £50k72%Over £50k63%
Larger bills are harder to code and matter more, so the confidence bar is set higher above a value threshold agreed with the client manager.

Data and method

Data
London Borough of Camden, payments to suppliers over £500, Camden Open Data (Open Government Licence): 247,155 payments from April 2022 to October 2026 with supplier, expense account, cost centre, amount and date. Payments to individuals and redacted names were removed, and no supplier is named here.
Target
The expense account recorded by the finance team; accounts with fewer than 50 bills grouped
Split
Fitted on payments before October 2025; tested on October 2025 to October 2026
Methods
Supplier last-used account; supplier most common account; logistic regression on supplier-name character patterns, supplier history, amount band and, in a second version, cost centre
Measures
Share coded to the recorded account, by supplier history and amount band; accuracy and coverage at confidence bars

Limitations

  • A council ledger stands in for a practice’s many client files. Its chart of accounts is larger than most small businesses’, which makes coding harder, and a practice’s per-client histories are shorter, which makes it harder in a different way. The coder is tested on the practice’s own files before use.
  • The data has no line descriptions. Bills captured by Dext or Hubdoc carry line text, which adds signal.
  • The recorded account is the finance team’s choice, which is sometimes inconsistent; part of the remaining error is disagreement rather than mistakes.
  • GST treatment is checked separately; the coder sets the account only.

How I would take it live

  • Export two years of coded bills for a pilot group of clients from Xero or MYOB
  • Fit the coder per client with a shared supplier-name model, and agree confidence bars with each client manager
  • Run in shadow for a month: the coder suggests, bookkeepers decide, and the edit rate is tracked
  • Post confident bills as drafts with the account set; review the edit rate monthly in Xero Practice Manager or FYI

Financial impact

About 565 bookkeeper hours a year back in the practice

The gain is the account check on bills the coder posts with confidence. Bill counts, minutes per check and the hourly cost are assumptions.

InputValueSource
Bills a month across clients3,000 growing practice
Minutes to check and code the account1.5
Share posted without review63%Measured confidence bar 0.8
Accuracy on those bills91%Measured
Loaded bookkeeper cost an hourA$65

Calculation

  1. Bills a year posted without review22,612
  2. Bookkeeper hours returned565
  3. Value of those hoursA$36,744

Annual valueA$36,744

Faster month-end and fewer reclassification journals are further gains and are not counted here.

Implementation and rollout

Four weeks from export to drafts with the account set

  1. Week 1

    Export

    Two years of coded bills for a pilot group of clients from Xero or MYOB.

    Practice principal, Manaz

  2. Week 2

    Fit and set bars

    Coder fitted per client with a shared supplier-name model; confidence bars agreed with client managers.

    Client managers, Manaz

  3. Week 3

    Shadow month begins

    Coder suggests, bookkeepers decide; edit rate tracked per client.

    Bookkeepers

  4. Week 4 onward

    Live drafts

    Confident bills posted as drafts with the account set; monthly edit-rate review.

    Practice, Manaz on support

Tools

Xero or MYOB Business, Dext, Hubdoc or Xero bill capture, Xero Practice Manager or FYI, Python, scikit-learn

Team

  • Practice principal owns the rollout and the client list
  • Client managers set confidence bars per client
  • Bookkeepers review low-confidence bills and correct codes
  • Manaz coder, Xero or MYOB integration and monthly review

The timeline is a plan for a typical engagement; it depends on data access and how many systems are involved.

Risks and mitigations

What could go wrong in production, and the control for each

RiskMitigation
A client changes its chart of accountsNew accounts mapped on the day; corrections retrain the coder.
GST-sensitive codingHigher bar for those clients; GST treatment checked separately.
Large billsHigher confidence bar above an agreed value.
Inconsistent past codingShadow month surfaces disagreements for the client manager to settle.

Key takeaways

Key takeaways

  • The supplier default is right 67% of the time on a real ledger.
  • A learned coder lifts that to 79% and handles new suppliers.
  • A confidence bar per client turns accuracy into review time saved.
  • Corrections feed back, so each client file improves month by month.