Every figure on a GST or VAT return already exists in the accounts before filing starts. What decides how long the return takes is whether each transaction carries its tax treatment, or whether that treatment has to be worked out again from documents.
What a return is actually made of
A GST or VAT return summarises transactions that have already been entered. Output tax on sales, input tax on purchases, zero-rated and exempt supplies, amounts outside the scope of the tax. None of it is new information at filing time. Every figure on the form is sitting somewhere in the accounts weeks before the deadline.
Preparing a return is therefore a grouping exercise rather than a calculation one. Transactions have to be sorted into the categories the form asks for, and the business has to be able to show which transactions made up each total if the tax authority asks a year later. How long that takes comes down to a single structural question. Was the tax treatment recorded on each transaction when it was entered, or does it have to be established again, from invoices and memory, at the point of filing?
The spreadsheet between the ledger and the return
In most growing businesses the process runs the same way each quarter. Sales and purchase listings are exported for the period. The listings go into a spreadsheet, rows are filtered by tax code, a handful of known exceptions are adjusted by hand, the columns are totalled, and the totals are typed into the filing portal.
That spreadsheet holds real accounting decisions. Which supplier invoices were left out and why. Which sales were treated as zero-rated. How a partial input tax claim was apportioned. None of those decisions travel back into the ledger, so the file becomes the only record of them. Next quarter the adjustments are recreated by copying the previous file forward, which works well enough until the person who built it is on leave, or has left.
Transactions that arrive without a tax treatment
Not everything that affects a return comes in through a sales or purchase document. Journals posted directly to the ledger for accruals, prepayments and year-end adjustments usually land on revenue and expense accounts with no tax coding attached. An expense claim entered as one reimbursement line can cover several receipts with different treatments. Purchases from overseas suppliers may need to be reported differently from local ones. A credit note raised against an invoice from an earlier period sits in one period for the accounts and a different one for the filing.
Each of these is handled correctly once, by whoever prepared the return that quarter. The handling is rarely written down anywhere the next preparer can find it, so the same judgment gets made again from scratch, sometimes differently.
A return is quick when the tax treatment was recorded at the moment of entry, and slow when it has to be reconstructed from documents afterwards.
Corrections that land after a return is filed
An invoice from a filed period gets corrected. Two versions of that period now exist: the one that was submitted, and the one the accounts show. If the original entry is edited in place with nothing to mark the change, the difference stays invisible until someone reconciles the filed returns against the annual accounts, which usually happens at audit. At that point the work is separating the differences that were already reported in a later return from the ones nobody picked up.
The mechanical alternative is that corrections are posted rather than edited, under a transaction type that identifies them, with their own numbering and their own printed document. The reconciliation between what was filed and what the ledger holds then becomes a report someone runs, instead of an investigation someone starts.
What changes when the treatment sits on the transaction
AOC holds AP, AR and GL in a combined ledger, so sales, purchases and the journals that adjust them are read from a single set of records. There is no step where two exports have to be matched before the totals can be trusted.
Analysis dimensions carry the detail a return needs on the transaction itself. AOC supports up to 10 dimensions per function, so tax treatment can sit alongside entity, branch or product on the same record, and the return can be read by any of them without the data being re-tagged first.
Journal types are defined by the business rather than fixed by the vendor. A quarterly tax adjustment can be set up as its own transaction type, with its own sequence, its own document and an automatic reversal in the following period, so every adjustment made for filing purposes stays identifiable afterwards by the type it was posted under.
Reports are available immediately, which matters most after the return has gone in. When a query arrives about a figure filed eight months ago, the listing behind that figure is produced from the ledger at the moment it is asked for.
What an accounting system does not settle
No system decides tax treatment. Whether a supply is zero-rated, whether input tax on a particular cost is claimable, how a partly exempt business apportions its claim: those are judgments made by the business and its tax adviser. A system records the decision and applies it consistently afterwards. It does not make it, and a wrong treatment applied consistently is still a wrong treatment applied to more transactions.
Nor does a new system repair coding that was loose in the past. Transactions already posted without tax detail come across as they are, and any period before the move stays as difficult to reconstruct as it was. The improvement starts from the cutover date, which is one of the arguments for moving before the next audit rather than after it.
A test to run before the next filing
Take the last return that was filed and pick one box on it. The total of standard-rated purchases works well. Then try to produce the list of transactions behind that figure from the accounting system alone, without opening the spreadsheet used at the time.
What the answer tells you
- The list comes out and agrees to the filed figure. The tax treatment is genuinely held in the accounts, and filing is a reporting task.
- It comes out but does not agree. The gap is the volume of manual adjustment happening every quarter. That number is worth writing down, because it grows with transaction volume rather than staying where it is.
- The list cannot be produced without the spreadsheet. The spreadsheet is the accounting record for tax purposes, and whoever maintains it is the only person who can answer a query about it.
The same test is a short and answerable thing to put to a vendor during a demo. Hand over one filed period, and ask to see the transaction listing behind a single box produced from inside the system.
Bring one filed period to a walkthrough
Pick a single box on a return you have already submitted, and see the transaction listing behind it produced from the ledger with no spreadsheet in between.
