Messy Books, Where to Start A Bookkeeping Cleanup Triage, and When to Catch Up or Start Fresh

Last reviewed: October 2026

Where do you start when the books are a mess?

Start with the lodgment list, not the transactions. Before touching a single bank line, write down every activity statement, tax return, payroll report and super obligation that is overdue or due in the next eight weeks. That list decides the order of everything else, because a late BAS carries penalty and interest risk that a messy chart of accounts does not.

Then go to the bank statements. They are the only record in a messy file that is complete and was not created by the client. Download them from the bank directly for every account and card, including the ones the owner "doesn't really use", and confirm the closing balance of each month. Every later step is measured against those balances.

Only after that do you open the old accounting file and judge it. The question is not whether it looks untidy. It is whether its bank balances agree with the statements, and if not, from which date they stopped agreeing. That date is usually where the real cleanup begins.

Should you catch up the old books or start fresh?

Catch up when the old file reconciles for most of its history; start fresh when it does not and the lodged periods are not in doubt. That is the practical test. "Starting fresh" only ever means a new accounting file with checked opening balances. It never means walking away from periods that were not lodged, or were lodged wrongly.

The ATO's overview of record-keeping rules for business sets the boundary. It says you need to be able to reconstruct your original data if your record-keeping system changes over time, that you need to keep most records for 5 years, and that ASIC requires companies to keep records for 7 years. A fresh file that cannot explain where its opening balances came from does not meet that standard. Keep the old file, archived and read-only, even when you stop working in it.

What records does the ATO actually require?

The ATO requires records of all transactions relating to a business's tax, super and registration affairs. Its overview page says the minimum information on a record is generally the date, the amount and a description, the relevant GST information, the purpose of the transaction, and the relationship between the parties where that is relevant.

That list is a good test for a catch-up. A bank line with a payee name gives you the date and amount. It does not give you the purpose or the GST treatment. Those have to come from an invoice, a receipt or the owner's answer, which is why the questions, not the data entry, set the pace of a cleanup. The same page adds that where expenses relate to both business and personal use, you need clear documents showing the business portion. If the mess includes the owner's private spending, our guide to owner expenses with no receipts covers the drawings and loan account side.

The ATO's page on when to do record-keeping and reporting tasks is also worth sending to the owner once the cleanup is done. It lists recording income, expenses and drawings daily, doing the bank reconciliation monthly, and cross-referencing payments with invoice numbers. Most messy files are simply those three habits stopping.

What happens if BAS and returns are already overdue?

Overdue lodgments can attract a failure to lodge penalty, but the ATO usually warns first and often waives it for refund or nil results. The ATO's page on the failure to lodge on time penalty says the base penalty is one penalty unit for every 28 days, or part of 28 days, that a document is overdue, up to a maximum of 5 penalty units. The base amount is multiplied by 2 for a medium withholder and by 5 for a large withholder.

The same page has three points that matter for a catch-up. First, the ATO says it will warn you by phone or in writing, and issue a notice to lodge, before it applies the penalty. Second, it says it generally will not issue a penalty notice for a late activity statement or tax return that results in a refund or a nil result, with exceptions, including where the penalty was applied before lodgment and where the entity is a large withholder. Third, you can ask for a remission, but you are expected to lodge your outstanding documents first.

Ignoring the problem is the expensive path. The ATO's page on what happens if you don't lodge says it can issue a default assessment, which attracts a 75% penalty of the tax-related liability, so for every $100 owed, an additional $75 is payable. Its guidance for businesses that can't lodge and pay on time is to contact the ATO before the due date, says a payment plan may be available, and notes that a general interest charge applies to any amount not paid by the due date.

The practical rule: lodge the oldest outstanding period first, with correct figures, and talk to the ATO early if the client cannot pay. A quick estimate lodged to beat a deadline usually means a revision and a second round of work later.

How do you fix GST errors found during the cleanup?

Many can go on a later BAS instead of revising every earlier one. The ATO's page on types of GST errors splits them into two kinds.

A credit error is one where too much GST was reported or paid, such as a sale reported twice. The ATO says a credit error can be corrected on a later BAS lodged within the period of review for the period in which the error was made, which runs for 4 years and one day from the day the BAS was lodged, and that credit errors have no value limit. There is an extra limit where the correction claims additional GST credits whose own 4-year time limit has expired.

A debit error is one where too little GST was reported, such as a GST credit claimed twice. For a business with GST turnover under $20 million, the ATO says it can be corrected on a later BAS lodged within 18 months of the due date of the BAS in which the error was made, provided the net sum of the debit errors is less than $12,500 and the error was not the result of recklessness or intentional disregard of GST law. Anything over the limit, or out of time, means revising the original period. Catch-up work finds a lot of duplicated GST credits, so check these limits before you plan the corrections.

What is the right order for a bookkeeping catch-up?

Risk first, then the bank, then the detail. This is the order we would run for a typical small business file that is several quarters behind:

1. Build the lodgment list. Every overdue or near-due BAS, return, payroll and super obligation, with dates, from the ATO portal rather than the client's memory.
2. Get every statement. All bank, card and loan accounts, straight from the institutions, for the whole period you are working on.
3. Find the last good date. Compare the file's bank balances to the statements month by month and mark where they stop agreeing.
4. Decide catch-up or fresh. Use the table above. Write the decision and the reason into the file notes, so the next person knows why.
5. Reconcile the oldest unlodged period. Match every line, send anything you cannot explain to a clearing account, and do not guess.
6. Send one question list. Date, amount, payee and a plain question for each unexplained item, with a way to upload documents. One list per period, not fifty emails.
7. Fix coding and GST, then lodge. Post the answers, check GST codes, correct earlier errors within ATO limits, and lodge that period before moving to the next.
8. Set the monthly rhythm. Once current, agree a monthly reconciliation date and a monthly question list, so the file does not drift again.

Steps 3, 5 and 6 are where the hours go. Our walkthrough on speeding up bank reconciliation with AI shows how matching rules fit into step 5, and our piece on whether AI can be trusted to categorise transactions sets out where automated coding is reliable and where it is not.

What does a catch-up look like in practice?

Here is a clearly labelled illustration, not an Agentive client. A small trades company arrives in late October. Its June and September quarter BAS are unlodged. The accounting file reconciles to the bank statement up to the end of February, then nothing: about 1,400 bank and card lines sit uncoded.

The bookkeeper keeps the file, because everything before March agrees with the bank. They reconcile March to June first and send the owner one list of 60 unexplained items. While waiting, they find a supplier bill entered twice in an earlier lodged quarter, so a GST credit was claimed twice. That is a debit error well under $12,500 and inside 18 months, so it can be corrected on the June BAS rather than revising the old quarter. The June BAS is lodged, then September follows the same pattern. Only then does the bookkeeper tidy the chart of accounts, because at that point it is a convenience, not a risk.

What do BAS agents owe a client with messy books?

Reasonable care, which means checking the facts rather than lodging whatever the file says. The Tax Practitioners Board's Code of Professional Conduct says registered agents must take reasonable care in ascertaining a client's state of affairs, to the extent it is relevant to a statement they are making, and must take reasonable care to ensure taxation laws are applied correctly.

For a catch-up, that has three plain consequences. Do not lodge a BAS from an unreconciled file. Do not code an unexplained transaction as a business expense to make a deadline. And keep the question list and the owner's answers on file, because they show the care that was taken. Our article on automating BAS preparation in Australia covers the checks that should sit before every lodgment.

Where does AI help with a catch-up, and where should it stop?

AI is well suited to the bulk of a catch-up and poorly suited to the decisions in it. Matching 1,400 bank lines to bills, suggesting codes from past patterns, spotting duplicate bills, building the question list and chasing the owner for answers are repetitive and rules-based. That is the work an AI bookkeeper can carry, and our bank reconciliation AI page explains how it runs in practice.

Agentive's view, from building this for Australian bookkeepers and BAS agents, is that a catch-up is where a human sign-off matters most. The file has no track record, so there is nothing to calibrate against. The AI should propose and the bookkeeper should approve, period by period, before anything is lodged. Our guide to review checkpoints for AI bookkeeping sets out where those sign-offs belong.

Where the AI runs matters too, because a catch-up hands over years of a client's financial history in one go. Agentive's AI Employee runs on a dedicated single-tenant server on AWS Sydney, with client data stored onshore and never used to train models. Our article on data governance for AI in Australia explains why that design matters, and the Agentive AI Employee overview covers the rest.

Order beats effort

Messy books feel like one big problem. They are really a queue: overdue lodgments, then bank balances, then coding, then tidiness. Work the queue in that order and the ATO risk falls fastest. Start a fresh file only when the old periods are settled, keep the old one archived, and correct GST errors within the ATO's limits rather than reopening everything. Then set a monthly rhythm, because the cheapest catch-up is the one you never need to do again.