Business

Keeping a versioned categories and tax codes file (Australia)

Categories change, and so does what your accountant needs. Keep a dated categories and tax codes file with a change log. A-dollar example and a template.

Editorial illustration for Keeping a versioned categories and tax codes file (Australia)

Keep your categories and tax codes file versioned, because it is only useful while current: a dated copy, a column for the code your accountant gave you, and a short change log. When a category is split, merged or renamed, the log tells your accountant exactly what changed and when, and your totals stay explainable.

Why version a file this small?

Because categories drift. A landscaping sole trader starts the year with "Materials" and by September has split it into "Plants", "Soil and mulch" and "Hardware". If the file simply replaces the old one, last year's totals under "Materials" cannot be matched to anything. A version label and a log keep the old and new schemes both readable.

What does the file need?

  • A version label and date at the top, for example "Categories v3, 1 October".
  • The category list, one per row, with a one-line description.
  • A column for the accountant's code, copied exactly as they provided it.
  • A notes column for mixed-use or unusual items.
  • A change log on a second tab: date, what changed, why.

What does a change log look like?

DateChangeReason
1 JulAdded 'Plants'Large purchases needed their own line
1 JulSplit 'Materials' into 'Soil and mulch' and 'Hardware'Different suppliers and treatment
1 OctMerged 'Misc' into 'Hardware' and 'Sundries'Misc was hiding detail

Three rows are enough. What matters is that each change has a date, so totals before and after can be compared without confusion.

How do I handle old transactions after a split?

Decide whether to re-label them or leave them. Suppose July to September had A$4,860.00 under Materials, and you now know A$1,720.00 of it was plants, A$1,140.00 was soil and mulch and the rest hardware. Hardware is then 4,860.00 - 1,720.00 - 1,140.00 = A$2,000.00. If you re-label, say so in the log; if you leave them, say so as well. Either is fine as long as the accountant knows. The numbers are made up.

How can I check the file against my transactions?

  1. List the distinct categories in the transactions: =UNIQUE($D$2:$D$2000) in Excel 365 or Google Sheets.
  2. Compare against the file. Any category in the transactions but not in the file is missing a code.
  3. For each category in the file, check =COUNTIF($D$2:$D$2000, A2) is above zero. A zero means a retired category, which is worth noting in the log.
  4. Confirm the sum of all category totals equals the sum of all transactions.

Can an app keep this file for me?

An app can keep the category setup in one place, which removes some of the version juggling. SpendixAI lets you create categories and sub-categories with an accounting code and tax-related settings, and its export centre includes a categories and tax codes file. It is built around India and INR, so those settings follow Indian GST and we do not claim Australian support. As a model: keep the setup somewhere exportable.

Naming versions so you can find them

Use a plain pattern such as categories-v3-2026-10-01 in the file name, so the order is obvious in a folder. Keep older versions rather than overwriting them, even though they take almost no space. When your accountant refers to the October list, you can open exactly that one. If you share the file through a cloud folder, add the version number inside the sheet too, since file names can change while the contents travel on.

Year-end tidy

  • Freeze the final version and save it with the year's records.
  • Start next year's file as a copy, with a fresh log.
  • Send your accountant the file and the log together.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports