Reading a VAT pack before lodgement
A controller’s walk-through of what we open first when a monthly VAT reporting application arrives for review.
When a VAT reporting application lands on our desk, we do not start with the signature block. We start with the control account.
Control account first
The VAT control account should tell the same story as the draft return. If output tax in the ledger and box totals diverge by more than a rounding band, we stop and ask for the bridge. Many “form errors” are actually posting cut-offs from the last two days of the month.
Sample with a reason
Random samples waste everyone’s time. We bias toward cash-heavy days, new suppliers, and invoices just under approval thresholds. For each sample we want the tax invoice, not a delivery note or pro-forma. If the claim rests on a document that is not a tax invoice, it goes into the findings list even when the arithmetic looks neat.
Cut-off questions worth asking
- Were credit notes for returned goods dated inside the period?
- Did branch transfers create double output recordings?
- Are advance receipts coded consistently with your accounting policy?
Closing the read
A short memo beats a long essay. Controllers need a list they can assign: fix now, fix next month, or accept and document. That is the tone we use in VAT return reviews and in the VAT chapter of a fuller tax reporting application audit.