Automated Line-Item Coding for Xero & MYOB

How it works

Why per-supplier coding history beats generic rules

A rules-based coding system asks you to define what each account code applies to - "all invoices from freight companies go to account 6200." That works when suppliers are simple and consistent. It breaks the moment a freight supplier adds a fuel surcharge, a storage fee, and a handling charge to the same invoice. The rule codes the whole thing to 6200. The correct treatment splits the lines across freight, storage, and handling - each with potentially different GST treatment.

History-based coding looks at how that specific supplier's invoices have been coded in the past. If the freight supplier's "Fuel Levy" line has been coded to account 6210 in the last 14 invoices, the next one goes to 6210 automatically with high confidence. If the same supplier adds a new charge type that hasn't appeared before, the system flags it for review rather than guessing. The coding builds on real decisions, not rules that have to be maintained manually as suppliers change.

GST treatment at the line level

Most Australian businesses handle GST at the invoice level - the whole invoice is either taxable or it isn't. Mixed invoices, where some lines include GST and others are GST-free, get coded to one treatment or the other with a manual override somewhere in the process. That override is where GST errors concentrate, particularly at the end of a busy month when the AP officer is processing 30 invoices and running out of attention.

Line-level coding applies the correct GST treatment to each line independently. A supplier invoice covering freight (10% GST), health and safety levies (GST-free under certain conditions), and exported goods (zero-rated) gets each line treated correctly, not forced into a single invoice-level treatment that's wrong for two of the three categories. For BAS preparation, the difference between getting mixed invoice GST right in the coding and fixing it in the accounting system at quarter-end is significant - both in time and in the risk of carrying incorrect input tax credits.

What re-entry at month-end actually costs

Coding errors discovered at month-end require journal entries to correct them in Xero or MYOB. Each journal entry is a documented manual correction - a record that something was wrong the first time. For businesses that go through external audit or prepare management accounts for investors or lenders, a ledger full of correcting journals is a signal that the front-end process isn't working. Automated line-item coding doesn't eliminate the possibility of errors, but it reduces them to genuine exceptions - cases where the system's confidence was low enough to flag the invoice for review before it was posted, not surprises discovered after the fact.

Frequently asked questions

Related glossary terms