Every practice has one. It might be called Suspense, Uncategorised, Ask My Accountant, or a number nobody remembers choosing. Whatever it is called, it does the same job: it holds the transactions where somebody hit a question they could not answer and needed to keep moving.
That is a perfectly reasonable thing to do. The problem is what happens next, which is usually nothing, until the week of lodgement.
Why it matters for the BAS specifically
G1 and the rest of the activity statement fields are built from coded transactions. A transaction sitting in suspense has, in effect, been given a coding decision — just not the right one.
That produces one of two errors, and which one you get depends on how suspense is configured:
- The transaction is excluded from G1, understating reported sales or purchases.
- The transaction is included at whatever GST treatment the suspense account carries, which is nobody's intended answer.
Neither is defensible if the lodgement is examined later. And because suspense is invisible on the face of a P&L that most people skim, it survives right up until someone deliberately runs the report.
The method
The instinct is to work through suspense chronologically, from the top. That is the slowest possible order, because it treats every line as an independent question. Most of them are not.
Step 1 — Sort by absolute value, descending
Look at the largest items first. Not because they are more likely to be wrong, but because they are the ones where a wrong answer changes the BAS materially, and the ones most likely to need a conversation with the client rather than a decision from you.
Start those conversations first. They have the longest turnaround.
Step 2 — Sort by repetition, and look for rules
Now re-sort the same listing by description or vendor. What usually appears is a handful of names repeating ten or twenty times.
That is not twenty questions. It is one question and nineteen consequences. Answer it once, then apply it to the whole group.
This is where most of the time is recovered. A suspense account with 60 lines in it is very often eight genuine questions and 52 repeats, and a chronological pass hides that structure completely.
Step 3 — Separate "unknown" from "unanswered"
The remainder splits into two piles that need different handling:
Unknown to you, knowable by you. A vendor you do not recognise but could identify in two minutes — a quick search, an invoice already in the file, a look at what the same client did last quarter. Do these yourself. Sending them to the client is slower and makes you look like you are not paying attention.
Genuinely unanswerable without the client. A transfer that might be a loan, a drawing, or equipment. A payment whose business purpose you cannot infer. Batch these into a single request per client rather than sending them one at a time — three separate emails in a week trains a client to ignore you.
Step 4 — Attach the answer to the transaction
When the answer arrives, record it against the transaction, not in an email thread.
This is the step people skip, and the cost lands later. Six weeks after lodgement, a client asks why a payment was treated the way it was. If the answer lives in an inbox, reconstructing it takes longer than the original decision did. If it lives on the line, it takes seconds.
Step 5 — Empty it, then check it stays empty
Suspense should be zero at lodgement. Not small. Zero.
Then check it again a week later. If it has refilled, that is information: something in the process is routing transactions there faster than anyone is clearing them, and that is a rules problem rather than a diligence problem.
The failure that looks like a coding problem but is not
One case is worth calling out because it wastes hours if it is misdiagnosed.
If an entire import has landed in suspense — every row, not a scatter — that is usually not a coding issue at all. It generally means the import was never attached to a bank account, so there was no account for the bank side of each transaction to post to.
The tell is the pattern. Genuine suspense is scattered and irregular: a few lines here, a repeating vendor there. A whole statement in suspense, in date order, is structural.
Coding will not clear it. You can code every line correctly and the balancing side still has nowhere to go. The fix is to attach the import to the right bank account, not to re-code the transactions — and doing it the other way around means doing the work twice.
Do it at the start of the quarter
Everything above is easier in week one than in the last week.
The client conversations have time to complete. The rules you create apply to the rest of the quarter instead of being applied retrospectively. And the discovery that a whole import went to suspense happens when it is an errand rather than an emergency.
The habit worth building is not "clear suspense before lodging". It is "run the suspense report on the first Monday of the quarter" — at which point clearing it before lodging takes care of itself.
Where software helps
The reason suspense fills is that a question arrived and could not be answered on the spot. Software cannot answer the question, but it can shorten the loop.
ReconLink chases your clients for statements, receipts, and answers on specific transactions, and the reply comes back attached to the transaction it belongs to — so step 4 happens by default rather than by discipline. It codes around 99% of lines before you look at them, which means the residue that needs a human is genuinely the residue. And every coded line shows the rule it used, so a repeating vendor is visibly one rule rather than twenty separate decisions.
What it does not do is decide. The judgement, and the signature on the lodgement, stays with the registered agent.
$99 a month, ex GST. Unlimited clients, unlimited seats. Thirty days free, no card.
Frequently asked questions
Should a suspense account ever have a balance at lodgement?
No. Anything in suspense is an unanswered question, and G1 is built from coded transactions — so a balance there means the BAS is either missing the transaction or carrying it at an unintended GST treatment.
What is the fastest way to work through a large suspense listing?
Sort by value first to start the slow client conversations early, then re-sort by vendor or description. Most large listings are a small number of real questions plus a long tail of repeats of those same questions.
Why did an entire bank statement land in suspense?
Usually because the import was not attached to a bank account, so the balancing side of every transaction had nowhere to post. It looks like a coding failure and is not — re-coding the lines will not clear it. Attach the import to the correct bank account instead.
Is it better to ask the client about suspense items one at a time or in a batch?
In a batch, per client. Separate messages across a week train a client to deprioritise them. One consolidated request, with the specific transactions attached, gets a better response rate and a faster one.
How often should suspense be reviewed?
At the start of every quarter, and again before lodgement. Reviewing only at lodgement is what converts routine questions into a lodgement-week emergency.
The short version
Suspense is a queue of unanswered questions wearing an account's clothing.
Work it by value, then by repetition — most listings are a handful of real questions and a long tail of repeats. Record answers on the transaction rather than in an inbox. And if a whole import is sitting there in date order, stop coding: it is not attached to a bank account.
Run it on the first Monday of the quarter and the last week takes care of itself.