Setting up Xero properly the first time

What does setting up Xero actually involve?

Creating the file is the part that takes an hour. Setting it up is the part that decides whether the numbers mean anything afterwards.

Four decisions shape everything that follows: how the accounts are structured, what the opening balances are, when you change over, and what the file assumes about tax by default. Each is quick to make and slow to unpick, because every transaction entered afterwards inherits it. A file that has run for two quarters on the wrong defaults is not a settings problem any more. It is a data problem.

Order matters too. Opening balances before the chart of accounts means entering the balances twice. Payroll before the calendars and superannuation settings are right means the first pay run has to be reversed rather than edited.

Why the default chart of accounts rarely fits

Xero's default chart is generic by necessity. It has to suit a cafe and a consultancy, which means it suits neither of them especially well.

The useful question is not what accounts exist, but what you want to be able to see. If you run two locations, or three service lines, or a mix of grant funded and fee for service work, the chart is where that either becomes visible or stays invisible for the next five years. Rebuilding it around how the business actually reports, before there are transactions in it, costs about an hour. Doing it afterwards means remapping history, and the history is where your comparatives live.

Three things are worth settling at the same time:

1. Whether a split belongs in the chart or in tracking categories. Xero allows two active tracking categories. If you need more dimensions than that, the chart has to carry some of them, and that is much easier to decide before there is anything to move.
2. How specific to be. A chart with four hundred accounts is as unreadable as one with twelve. The test is whether you would ever make a different decision because of the split.
3. Account codes. They order your reports. Setting them deliberately once beats renumbering later.

What should opening balances agree with?

Your last finalised financial statements, to the cent.

Close enough is not a standard that survives an audit, a lender's review or a due diligence process, and a variance introduced at setup does not sit still. It compounds quietly through every reconciliation that follows, and it tends to surface at the worst moment, which is when somebody outside the business is reading the numbers.

If the previous set of statements is itself unreliable, that is worth knowing before you carry it forward rather than after. Carrying a wrong balance into a clean file produces a clean file with a wrong balance in it, which is harder to spot than an obviously messy one.

When should you change over?

At the start of a period, not partway through one.

A changeover date in the middle of a BAS quarter means preparing that quarter from two systems and reconciling the join. It is avoidable work, it is the kind of work that gets rushed, and rushed BAS periods are where errors enter files that otherwise look tidy.

The start of a financial year is ideal. The start of a quarter is usually fine. Mid quarter is workable when there is a reason for it, but the reason should be better than impatience.

The settings to fix before the first transaction

Five settings decide how the file behaves, and every one of them is faster to set than to change:

1. GST registration status and reporting frequency. These drive the activity statement and the tax defaults on every account.
2. Financial year end. It is not June for every entity type, and the file will happily assume otherwise.
3. Tax rate defaults on income and expense accounts. Profit and loss items generally code to GST or GST Free. The exceptions are wages, superannuation, bank revaluation and foreign exchange gains and losses. BAS Excluded is for non business items and for balance sheet items that are not fixed assets. It is not a supply based definition, and treating it as one is among the most common coding errors we are asked to correct.
4. Payroll calendars and superannuation settings. Wrong here means the first pay run has to be reversed rather than corrected, and single touch payroll reports whatever you send it.
5. User roles. A file that is one shared login has no audit trail, which matters most at the moment something is disputed.

What the setup tools will not do for you

Xero's own setup flow, and the conversion tools that bring a file across from another system, do a great deal and do it well. It is worth being precise about where they stop.

They will not decide what your chart of accounts should look like, because that is a question about your business rather than about the software. They will not tell you that an opening balance disagrees with your last statements, because they have nothing to compare it against. They will not know that your financial year ends in a different month, that two of your income accounts should be coded differently, or that the split you actually manage the business by needs a third dimension that does not exist.

None of that is a criticism of the tools. It is the shape of the problem. Software configures what it is told to configure, and the deciding is the work. The same applies to asking an assistant how to set Xero up: you get a good general answer about setting Xero up, and it knows nothing about your file, your entity type, or the statements you are carrying forward.

What it looks like when setup gets rushed

The pattern is consistent enough to describe.

The file looks fine. Reports run, invoices go out, the bank feed connects. Then a BAS comes back different from what the owner expected, or a lender asks for something the reports cannot produce, or a year end review finds the comparatives do not line up with last year's statements. By then the fix is not a setting, because two quarters of transactions have already inherited the assumption. It is a remapping exercise, and it is usually charged by the hour.

The cheapest hour anyone spends on a Xero file is the one before the first transaction goes into it.

The short version

Build the chart of accounts around how you report rather than around the default. Match opening balances to your last finalised statements exactly. Change over at the start of a period. Fix the five settings above before entering anything. If the file is being converted from another system, decide what you are carrying and check it against the source rather than assuming it arrived intact.

If a file already exists and you are not certain any of that was done, that is a reasonable thing to have checked rather than assumed.