5 BAS Data Entry Mistakes That
Trigger ATO Audits

Why BAS Errors Go Unnoticed Until the Letter Arrives

Most Australians do not worry about ATO audits because they assume audits target deliberate fraud — people hiding cash income, fabricating deductions, running two sets of books. But the ATO's compliance engine does not work that way. The ATO runs over 60 separate data-matching programs, and the vast majority of flagged discrepancies are not fraud. They are data entry errors made by people who were trying to lodge correctly and got one label wrong.

Here is what changed in recent years. Single Touch Payroll (STP) now reports every pay run in real time — the ATO knows your W1 and W2 figures before you open the BAS form. The Taxable Payments Annual Report (TPAR) tells the ATO what contractors you paid. Bank data-matching programs pull merchant transaction totals. Industry benchmarks flag businesses whose GST ratios fall outside the norm for their sector. The system is not waiting for a human auditor to notice an anomaly — it cross-references data from four or five external sources against your BAS automatically, and when something does not line up, it generates a discrepancy flag before anyone at the ATO reads your return.

The five mistakes below are the ones that trigger those flags most often — not because they are the most expensive, but because they create a cross-reference mismatch between what you reported on your BAS and what the ATO's other data sources already show. Each one is preventable with a pre-lodgement check that takes less than two minutes and costs nothing more than the discipline to run it before you click submit.

Mistake #1: Recording GST-Free Sales as Taxable (G1 Misclassification)

G1 is the first label on the BAS and the one that feeds into every other GST calculation on the form. The G1 figure — total sales — determines what appears at 1A (GST on sales), and the relationship between G1 and 1A is the single most audited ratio on the BAS. On a cash basis, 1A should approximate G1 multiplied by 1/11, minus the portion of G1 that represents GST-free sales.

The error that breaks this ratio is a GST-free sale coded as a taxable sale in the accounting system. A medical practice bills a patient $220 for a consultation. The consultation is GST-free, but the practice manager is using a default tax code in Xero or MYOB that auto-assigns GST to every invoice line. The invoice gets coded with $20 of GST that should not exist. At the end of the quarter, G1 includes $220 for this sale. If the software treats it as fully taxable, 1A shows $20. But the ATO's data-matching engine looks at the industry code for a medical practice, knows that medical services are overwhelmingly GST-free, and expects a low 1A-to-G1 ratio. When the ratio is higher than the industry benchmark, the system flags it.

This is not a software bug. It is a tax code assignment error that happens at the transaction level — the invoice was entered, the tax code dropdown defaulted to "GST on Income," and nobody checked whether the underlying service was GST-free. The same error occurs with basic food retailers (groceries are GST-free, prepared food is taxable), education providers (tuition is GST-free, course materials may not be), and exporters (GST-free exports coded as domestic sales at G2).

The categories where GST misclassification is most common, based on ATO guidance on BAS corrections, are insurance premiums (input-taxed, not GST-free and not taxable), basic food items (GST-free but prepared food is taxable), medical services and education (GST-free, but ancillary products may carry GST), and financial services (input-taxed, meaning no GST is charged and no input tax credits can be claimed). A single misclassified supplier — say, an insurance broker whose invoices are coded as taxable instead of input-taxed — compounds the error across every transaction in the quarter.

Mistake #2: Forgetting Capital Purchases at G10

G10 is the field where businesses report capital purchases — assets bought for the business where GST was included in the purchase price. Vehicles, equipment, property, IT hardware, office fit-outs. For most small businesses filing a full BAS (not Simpler BAS), G10 feeds into the 1B calculation: 1B should approximate (G10 + G11) × 1/11.

The error is not miscoding a capital purchase as non-capital — that would misclassify the expense category but would not change the total 1B figure, since both G10 and G11 feed the same 1B calculation. The real error is missing the purchase entirely: the business bought a $33,000 vehicle, the invoice came in, it was paid, and the bookkeeper coded the expense to the vehicle asset account but forgot to check the GST box. Or the accountant coded it to a fixed asset account with no GST tax code assigned. Or — most common — the purchase happened late in the quarter, the tax invoice arrived after the BAS was prepared, and nobody went back to update the GST figures before lodgement.

A missed $33,000 capital purchase at G10 means a missed $3,000 GST input tax credit at 1B. The business overpays GST by $3,000 for the quarter. That is money the business is entitled to — not a tax planning strategy, not an aggressive deduction, just the basic operation of the GST system — and it is gone because one checkbox on one transaction was missed.

This error is structurally hard to catch because the Simpler BAS reporting method, which applies to businesses with turnover under $10 million, does not even show G10. On Simpler BAS, the capital/non-capital split is invisible — both feed 1B directly. So a business on Simpler BAS never sees G10 and cannot verify whether a capital purchase was included in the 1B calculation from the form alone. The verification requires a separate report from the accounting software, which means an extra step that most small business owners skip. For the complete label-by-label breakdown of GST, PAYG, and FBT fields, see the complete guide to BAS data extraction.

Mistake #3: W1 and W2 Figures That Do Not Match Single Touch Payroll

This is the field pair that generates more ATO discrepancy notices than any other BAS section. W1 (total salary and wages) and W2 (amount withheld from those wages) are reported to the ATO through two separate systems: your payroll software reports them in real time through STP with every pay run, and your BAS reports them quarterly as a summary. The ATO's system compares the two. When they do not match, the system does not send a polite email asking if you might want to double-check — it generates an automatic discrepancy flag.

The most common causes of the mismatch are mundane but persistent. A payroll officer processes a pay run in the wrong period — the pay date is 31 December but the software dates it 2 January, pushing the W1/W2 into Q3 instead of Q2. A manual adjustment is made in the payroll system to correct an earlier error, but the adjustment updates the STP report without updating the BAS pre-fill. A termination payment is processed and the payroll system splits it into multiple payment types, some of which flow to W1 and some of which do not, creating a gap between what the BAS expects and what STP delivered.

The structural problem is that STP update events do not modify BAS pre-fill figures. As the ATO's own STP guidance page states: "update events do not modify your BAS figures." If a payroll administrator corrects an employee's YTD entitlements through an update event, the STP records are corrected, but the pre-filled W1 and W2 numbers on the BAS remain frozen at the original submission. The BAS operator needs to manually edit the W1 and W2 fields to match the corrected STP totals. If they do not — if they trust the pre-fill and move on — the BAS gets lodged with the wrong figures.

This exact scenario plays out in accounting firm forums regularly. On Reckon's community forum, a payroll administrator described discovering that their STP-submitted gross earnings and PAYG tax amounts did not match the payroll summary report for a week's pay run. The cause was an update event that corrected employee data without changing the employer pre-fill totals. The ATO's response, quoted by a Reckon representative: "update event-type submissions only amend employee-data. It doesn't change or affect prefill-employer data. If you notice the ATO's prefill balances are incorrect, it's recommended that you edit the W1 & W2 fields to correct them to what they should be."

If a payroll administrator who works with STP daily had to ask the forum why the numbers did not match, the mechanism is clearly not intuitive. And the mismatch persists until someone manually compares the BAS pre-fill against the payroll report — the exact step that gets skipped when the BAS is being prepared under time pressure. For the wider problem of why manual BAS preparation is prone to these errors, see why BAS lodgement week is the hardest week in small business.

Mistake #4: FBT Instalment Variance from the Prior Year

The FBT instalment label F1 does not appear on every BAS. It only appears when your business is registered for Fringe Benefits Tax — meaning you provide employee benefits such as company cars, expense payment benefits, or entertainment. For the businesses that do report F1, the label carries an ATO-calculated instalment amount based on your most recently lodged FBT return. Because the amount is pre-calculated, most businesses assume it is correct and copy it without checking. That assumption is the mistake.

F1 becomes an audit trigger when the quarterly instalment is significantly higher or lower than the previous year's equivalent quarter without a corresponding change in the number of employees receiving fringe benefits. If your business had 12 employees with company cars last year and 15 this year, the FBT liability is higher — but the ATO's pre-calculated F1 does not know this yet because it is based on last year's FBT return. Varying the instalment downwards without a documented reason risks a shortfall interest charge. Not varying it upwards when benefits have increased means the business is underpaying FBT, and the year-end reconciliation will produce a catch-up payment plus interest.

The error is not in the calculation — it is in failing to recognise that F1 needs active review, not passive acceptance. A business that treats F1 as a pre-filled field that "the ATO already knew" is betting that last year's fringe benefits profile exactly matches this year's. For businesses with seasonal headcount changes, international assignments, or benefit policy changes mid-year, that bet is almost always wrong.

This error survives because FBT is the tax obligation that most small business owners understand the least. GST is part of every transaction. PAYG withholding is part of every pay run. FBT is a once-a-year reconciliation with quarterly instalments that feel detached from daily operations. A business owner who reviews the GST and PAYG sections of their BAS carefully may glance at F1, see a number the ATO put there, and move on. That glance is where the error lives.

Mistake #5: Fuel Tax Credits at the Wrong Rate, for the Wrong Fuel

Fuel tax credits (FTC) are the most rate-sensitive labels on the BAS. The ATO publishes different credit rates for different fuel types — liquid fuels (diesel, petrol) at different rates from gaseous fuels (LPG, LNG, CNG) — and different rates depending on whether the fuel is used in heavy vehicles on public roads or in off-road machinery. The road user charge, which reduces the credit for on-road heavy vehicle use, increases by 6% every year, so the rate you used in last year's Q2 BAS is not the rate for this year's Q2. And from 1 April to 30 June 2026, the road user charge was temporarily set to zero for three months — meaning the FTC rate for on-road heavy vehicle diesel jumped from 18.4 cents per litre to 50.8 cents per litre for that single quarter. A business that applied the standard rate from the first nine months of the financial year to the April–June quarter underclaimed by 32.4 cents per litre on every eligible litre of diesel.

The ATO has specifically identified fuel tax credits as a compliance focus area. A Tax Alert issued by the ATO flagged concerns about misuse of GPS and telematics data to inflate FTC claims — specifically, organisations claiming the full off-road rate for fuel used partially on public roads. The ATO's concern is not limited to deliberate inflation. It extends to businesses using the wrong apportionment method: a transport company that estimates 20% of fuel use is off-road but does not maintain fuel logs to substantiate the split. When the ATO reviews the claim and finds no evidence for the split, the entire claim is at risk.

The FTC scheme returns over $7.5 billion annually across roughly 300,000 claimants. With compliance funding increased in the latest federal budget, the ATO's FTC audit activity is expanding, not contracting. For the step-by-step extraction workflow that captures BAS labels into a verifiable spreadsheet, see how to extract Australian BAS data to Excel.

Common FTC rate errors include applying a single rate to an entire quarter when fuel was purchased before and after a rate change date, using the on-road rate for fuel consumed by auxiliary equipment (which qualifies for the higher off-road rate), and claiming credits for fuel types that are not eligible — such as fuel used in light vehicles on public roads or fuel used for private purposes. The ATO's FTC business page includes a calculator that cross-references fuel type, usage, and date to produce the correct rate — but a business owner who does not know the rate changed will not know to use the calculator.

What Happens When the ATO Flags a BAS Discrepancy

An ATO discrepancy flag does not mean the auditor is at your door. It means the system has identified a data mismatch and the return enters a review queue. The first step is typically a risk review — the ATO examines the specific discrepancy and may request additional information by letter, phone, or through your myGov account. You have 28 days to respond. If the response resolves the discrepancy, the review closes. If it does not, the review escalates to a formal audit.

The penalty framework for BAS errors depends on whether the ATO determines the error was a failure to take reasonable care, recklessness, or intentional disregard. A false or misleading statement that results in a tax shortfall attracts a base penalty amount (BPA) of 25% of the shortfall for failure to take reasonable care, 50% for recklessness, and 75% for intentional disregard. A BAS error of $15,000 — the amount from the LinkedIn case that opened this article — carries a penalty of $3,750 at the lowest tier, plus the general interest charge (GIC) applied daily from the original due date of the BAS.

Since July 2025, GIC and shortfall interest charges are no longer tax-deductible. A GIC rate of 10.65% per annum compounding daily on a $15,000 shortfall over 12 months adds approximately $1,680 in non-deductible interest on top of the penalty. And repeated BAS errors can trigger a shift from quarterly to monthly GST reporting — the ATO can move your business to 12 BAS lodgements per year instead of four, increasing compliance overhead by a factor of three. That decision is not appealable.

The practical reality, visible in accounting forums and professional networks, is that most flagged BAS errors are not fraud. They are data entry oversights that could have been caught by a pre-lodgement review. The ATO's own GST gap analysis shows that the net GST gap — the difference between what the ATO expects to collect and what it actually collects — was approximately $385 million in 2024–25, and around 75% of that came from voluntary disclosures made during ATO reviews, not from audits uncovering deliberate evasion.

For a similar pattern in UK payroll tax documents, see the five P60 data entry mistakes that put payroll reconciliation at risk and the P45 errors that cause incorrect tax coding at the next job.

Pre-Lodgement Checks That Catch These Five Errors

Every error described above has a corresponding check that takes less than two minutes and can be performed without leaving the spreadsheet where your BAS data is compiled. The checks are not complicated — they are just specific.

None of these checks requires accounting expertise beyond what a BAS-lodging business owner already has. What they require is a structured pre-lodgement routine that runs before the submit button is clicked — not after the quarter has closed and the next BAS is already being prepared. For a comprehensive checklist that covers the full quarter-end preparation process, see the BAS quarter-end checklist.

How Extraction Prevents BAS Errors Before They Reach the ATO

The five errors described above share a common root cause: they happen when a number is typed into a BAS field manually, without an automated cross-reference against the source data that generated it. Extraction removes the typing step — but more importantly, it creates a structured record where cross-validation is automatic.

When BAS data is extracted into a spreadsheet using Custom Column Extraction — defining columns like Total Sales (G1), GST on Sales (1A), GST on Purchases (1B), Total Wages (W1), and Tax Withheld (W2) — the output is a single row per quarter with every BAS label in its own column. In the row below, you add validation formulas: =ROUND(G1_cell/11, 0) next to 1A, =W2_cell + W3_cell + W4_cell next to W5, =1A_cell - 1B_cell for net GST. If a validation formula returns a value that differs from the extracted value by more than a few dollars, you investigate before lodging. The formula catches the misclassification. The extraction eliminates the typing error. Together, they turn a five-error minefield into a single verification pass.

The quarterly ledger approach — four extraction runs, four rows in a spreadsheet, one sum row at the bottom — takes this further. When Q1 through Q4 are in the same workbook, you can compare quarter-to-quarter ratios. A W1 figure that dropped 40% from Q2 to Q3 without a corresponding reduction in employee headcount is visible before the ATO's data-matching engine sees it. A 1A-to-G1 ratio that jumps from 0.088 to 0.095 between quarters suggests a classification change that needs investigation, not a rounding anomaly.

These are not advanced forensic accounting techniques. They are spreadsheet formulas that take thirty seconds to add. The barrier has never been complexity — it has been the fact that manually typing 12 label values per quarter across four quarters produces 48 opportunities for a transcription error, and adding 6 validation formulas to each row adds 24 more numbers to manage. Extraction replaces the manual typing with one processing run, one row of output, and one verification pass per quarter. The validation formulas are populated from extracted values that were read from the BAS, not typed from memory. For the complete batch workflow that merges four quarters of extracted BAS data into a single annual ledger, see how to batch-process quarterly BAS statements into one annual tax ledger.

FAQ

How do I know if the ATO has already flagged my BAS?

If the ATO has flagged a discrepancy, you will receive a letter or electronic communication through myGov or your tax agent. The letter will specify the period under review and the nature of the discrepancy. The ATO generally gives 28 days to respond. If you have not received a letter, your BAS has not been flagged — but that does not mean previous errors are resolved. The ATO has up to four years from the original BAS due date to initiate a review.

Can I fix a past BAS error without triggering an audit?

Yes. The ATO encourages voluntary disclosure. If you discover an error in a previously lodged BAS, you can correct it by lodging a revised BAS or by adjusting the figure in your next BAS, depending on the size and type of the error. GST errors under a certain threshold can be corrected in the next BAS without needing a formal revision. However, if the ATO has already commenced a compliance activity — you have received a letter notifying you of a review — you cannot correct the error in a later BAS and must address it through the review process. Voluntarily disclosing an error before the ATO finds it reduces penalties and signals good faith.

Does the Simpler BAS format make these errors more or less likely?

Simpler BAS reduces the number of fields you report — G1, 1A, and 1B instead of seven GST labels — which means fewer fields to get wrong. But it also reduces visibility. On a full BAS, a G10 omission is visible because G10 is a separate label. On Simpler BAS, G10 is invisible; the error still affects 1B, but you cannot see it from the form alone. Simpler BAS makes data entry easier but pre-lodgement verification harder. If you are on Simpler BAS, the pre-lodgement checks listed above still apply — you just need to pull the underlying transaction data from your accounting software to perform them.

What if I do not have employees — do W1 and W2 still apply?

If you do not employ anyone and do not withhold PAYG from any payments, leave W1 and W2 blank. Do not enter zero unless the form requires a value. The W1–W2 labels only appear on your BAS if you are registered for PAYG withholding. If you are not registered and the labels appear, contact the ATO — the registration status may be incorrect and lodging a blank W1 could trigger an unexpected compliance notice.

How often do FTC rates change, and how do I stay current?

Fuel tax credit rates change at least twice per financial year — once on 1 July with the new financial year, and once when the road user charge increases (currently 6% per year). Rates can also change mid-quarter due to government measures, as happened from 1 April 2026 when the road user charge was temporarily set to zero. The ATO publishes updated rates on its FTC rates page. Check the page at the beginning of every BAS period before calculating your claim.

Are there any BAS fields where an error has no consequence?

No. Every field on the BAS feeds into either the amount payable or the ATO's cross-reference checks. Labels that appear informational — like G2 (export sales) and G3 (other GST-free sales) — are used by the ATO to validate the 1A-to-G1 ratio. Leaving them blank when they should contain a value is itself a discrepancy. The only safe rule is to report every label that applies to your business, and verify every label against source data before lodging.

The five errors described in this article are not exotic. They do not require complex tax planning to trigger, and they are not limited to businesses with poor record-keeping. They happen when a number is typed into the wrong label, a pre-filled field is trusted without verification, or a rate change is missed because the last quarter's rate was copied forward. Each one has a pre-lodgement check that catches it. And each check takes less time than the ATO correspondence that follows when it is not caught.