Categorise a Bank Statement Before It Goes Into Xero

The gap this fills

A live bank feed is the right tool when it's set up from the start of a financial year and the account stays open. That's not most of the messy cases bookkeepers actually deal with. You take on a new client partway through the year and need the first eight months backfilled. A sole trader hands over a folder of PDFs because they never connected a feed. An account gets closed and the historical statements are the only record left. In every one of those, you're looking at a stack of PDF statements and a spreadsheet, not a feed.

Xero can still import a CSV manually through Accounting → Bank Accounts → the account → Statements → Import a Statement, but a plain export just gives you date, description, and amount. Every row still needs to be manually coded to an account before it's useful for tax time or reporting. On a full year of business transactions that's not a five minute job.

Where this sits in the Xero workflow

This doesn't touch Xero directly and doesn't claim to be a bank feed replacement. It's a step before Xero: convert the PDF, get a CSV with a Category column already filled in for most transactions, then import that into Xero the normal way. You're still doing the import and the reconciliation in Xero itself. What changes is that most rows already have a sensible category sitting next to them, so coding becomes a spot-check instead of a read-every-line exercise.

Xero's own bank rules do something similar once they exist, matching a merchant name to an account code automatically. The catch is you have to build each rule manually, which means coding that merchant by hand the first time. On a batch of historical statements you've never processed before, none of those rules exist yet. This gives you a starting category on the first pass, before any rule has been written.