8 Common GST Coding Mistakes to Fix in Xero

A BAS that does not look right is rarely caused by one dramatic error. More often, it is the result of small coding decisions repeated across dozens of bank-feed transactions. Common GST coding mistakes can overstate what you owe, leave legitimate GST credits unclaimed, and turn BAS time into a stressful search through old receipts.

For a busy small business, the goal is not to memorise every GST rule. It is to set up sensible accounts, use the right tax rates consistently, and know which transactions deserve a second look before the BAS is lodged. Xero can make this process much easier, but only when the coding behind the bank feed is sound.

Why GST coding needs more attention than it gets

GST coding is more than choosing a category such as fuel, materials or subscriptions. Each transaction also needs the right tax treatment. That treatment flows through to your BAS, your profit and loss report, and the amount of GST you pay or claim.

A transaction can be a genuine business expense but still have no GST to claim. Equally, an expense with GST included can be coded incorrectly as GST-free, leaving money on the table. The distinction matters because the BAS is based on the data in your accounts, not on what you intended to enter.

The good news is that most issues are predictable. Once you know where they occur, a regular review becomes straightforward.

1. Using GST on every business expense

One of the most common GST coding mistakes is assuming that every business purchase includes claimable GST. Many expenses do, but not all of them.

Bank charges, some insurance premiums, interest, loan repayments and certain government charges may not include GST. If you apply GST on expenses automatically, your BAS can claim more input tax credits than you are entitled to.

Check the supplier invoice or receipt rather than relying on the transaction description in the bank feed. If GST is included, the document should normally show the GST amount or state that the price includes GST. For purchases of more than $82.50 including GST, you generally need a valid tax invoice to support your claim.

This is also where a clean chart of accounts helps. Separate accounts for bank fees, finance costs and insurance make it easier to apply the correct default tax rate and spot exceptions.

2. Treating GST-free, input-taxed and out-of-scope as the same thing

A zero GST result can mean different things. That is why using a single no-GST tax rate for every exception creates problems over time.

GST-free purchases and sales are part of the GST system but have GST applied at zero. Input-taxed items are treated differently again, while out-of-scope transactions sit outside the normal GST calculation. Wages, transfers between your own bank accounts, loan principal repayments and owner contributions are common examples that may be out of scope.

The right code depends on the transaction, not simply whether GST appears on the receipt. For example, a loan repayment needs to be split between principal and interest. The principal is not an expense and does not carry GST, while the interest component may have its own treatment.

If this sounds overly detailed, that is because it can be. The practical approach is to identify the transaction types your business sees regularly, set sensible rules for those, and review anything unusual instead of forcing it into the nearest category.

3. Letting bank rules repeat an old error

Bank rules save time, particularly for trades, hospitality venues and service businesses with frequent supplier payments. But a rule is only useful when it is based on a correct original transaction.

A rule created for a software subscription, fuel supplier or regular wholesaler can keep applying the same account and GST rate long after the supplier changes what it is charging you. It can also code a personal purchase made at a familiar merchant as a business expense without anyone noticing.

Review your bank rules at least once a year, and whenever there is a change in your business. Check the account, GST rate, tracking category if used, and rule conditions. Do not allow a rule to auto-approve transactions you have not reviewed if the supplier’s charges vary significantly.

For example, a hardware store may supply materials for a job one week and a personal item the next. A broad rule may be convenient, but it is not a substitute for checking the receipt.

4. Claiming full GST on mixed business and private costs

Mobile bills, vehicle costs, home internet, and some travel expenses often have both business and private use. Coding the entire amount as a business purchase with full GST is an easy mistake, especially when the payment comes from the business bank account.

The correct treatment depends on the facts. You may need to apportion the cost between business and private use, then claim GST only on the business portion where GST is included. The same principle applies when a sole trader pays a business expense from a personal account. The expense may still be deductible and eligible for a GST credit, but it should be recorded properly rather than ignored because it did not appear in the bank feed.

Keep a reasonable basis for your split. A consistent percentage supported by usage records is more useful than a guess made at BAS time. Vehicle claims can require particular care, so do not assume that every fuel, registration or repair transaction should receive the same treatment.

5. Coding sales without checking whether GST was charged

GST coding errors are not limited to purchases. Sales invoices need just as much care because they determine the GST you collect.

If your business is registered for GST, most taxable sales will have GST added. However, some income may be GST-free, outside the scope of GST, or treated differently because of the nature of the service or customer. Applying GST automatically to every income account can result in charging incorrectly or reporting the wrong amount at 1A on the BAS.

Set up your standard sales items in Xero with the appropriate tax rate, then check one-off invoices before sending them. This is particularly useful for businesses with deposits, reimbursements, grants, overseas customers or different service lines.

A deposit is a good example. It is not automatically GST-free simply because the work has not been completed. The GST treatment will depend on what the payment is for and how it is invoiced. Recording it correctly from the start is far easier than untangling it after the money has been spent.

6. Posting GST-inclusive amounts as GST-exclusive, or the other way around

A receipt showing $110 including GST contains $10 of GST, not $11. Small input errors around tax-inclusive and tax-exclusive settings quickly add up, especially where invoices are entered manually.

This often happens when an invoice total is typed into a line that Xero treats as tax-exclusive, causing GST to be added again. The reverse can happen when a tax-exclusive supplier amount is entered as GST-inclusive, understating the expense and GST credit.

Before approving bills, check that the line total and invoice total agree with the supplier document. If an invoice has several lines with different tax treatments, do not simplify it into one line just to save time. Split the transaction so the GST calculation reflects what was actually purchased.

7. Forgetting adjustments, refunds and merchant fees

Refunds and credit notes should reverse the original transaction correctly. If a supplier refund lands in the bank feed and is coded as ordinary income, it can inflate sales and distort GST. If a customer refund is treated as a general expense rather than a credit against the sale, the same issue arises in reverse.

Merchant settlements need attention too. A customer may pay $1,100, but the bank deposit could be $1,078 after card fees. The full customer payment should be recorded as sales, with the merchant fee posted separately using the tax treatment shown on the provider’s statement. Coding only the net deposit as income understates both revenue and GST collected.

This is a worthwhile monthly check for retailers, cafés and any operator taking regular card payments. Reconcile the payment provider clearing account to the statements, not just to the bank deposits.

8. Leaving GST corrections until the end of the year

Waiting until the annual accounts are prepared to fix GST errors is costly. By then, receipts are harder to find, staff may not remember the transaction, and several BAS periods may need consideration.

A better habit is a short review before each BAS. Look through large or unusual expenses, transactions with no tax rate, accounts that should rarely have GST, and income entries that were coded manually. Compare the current BAS to prior periods and ask sensible questions when a figure moves sharply. A jump may be completely valid, but it should be explainable.

For businesses reporting GST on a cash basis, timing also matters. GST is generally reported when you receive payment from customers or pay suppliers, rather than simply when an invoice is raised or a bill is entered. Your Xero organisation settings and reconciliation process need to match the basis you use for GST reporting.

Build a process that catches errors early

Good GST coding is less about perfection on every transaction and more about having controls that catch the exceptions. Keep source documents, reconcile bank accounts regularly, use bank rules carefully, and make the BAS review a planned task rather than a last-minute job.

If you are repeatedly unsure about the GST treatment of the same types of transactions, that is a sign your Xero setup needs attention. A few clear coding rules and properly configured accounts can give you tidier records, cleaner BAS figures and reporting you can actually use. That leaves more of your time for running the business, with fewer surprises when the next BAS is due.