How to Spot Bookkeeping Problems Before VAT Submission

How to spot bookkeeping problems before vat submission becomes expensive when the business only notices the weakness under deadline pressure. In South Africa that usually means a problem with balance sheet review, management reporting, and clean schedules shows up just as SARS questions, management decisions, or month-end sign-off need a clean answer.

VAT deadlines expose bookkeeping problems that have usually been building for weeks or months already.

So businesses should look for the warning signs before the filing date starts driving every decision.

The four bookkeeping warning signs to check first

1. The bank is still not fully reconciled

If the bank is unclear, the filing process is already sitting on a weak base.

2. Major items still need explanation

Unusual transfers, corrections, and reclasses should be explainable before the return is treated as ready.

3. Source support is not easy to locate

If the business still has to search inboxes and folders for key support, the process is too fragile.

4. Old balances are still being rolled forward

That usually means the monthly close is not strong enough yet.

A quick pre-VAT review table

The mistake SMEs make most often

They treat VAT pressure as if it begins at the filing deadline.

In reality, the stress usually started earlier:

• month-end drift
• poor document submission
• unresolved balances
• weak review of unusual items

So bookkeeping red flags before VAT filing is useful. It moves the review earlier.

What the business should do before the deadline window

1. confirm the bank is current
2. review major balances and exceptions
3. gather missing support early
4. escalate unclear items before the filing pack is assembled

Those four steps reduce more VAT pressure than most last-minute fixes.

Why the VAT return is only as strong as the books behind it

A VAT submission may look like a tax task, but the return is built from bookkeeping detail. If sales, purchases, bank allocations, supplier invoices, debit notes, credit notes, imports, and owner payments are not captured correctly, the VAT return inherits those weaknesses.

That is why the pre-submission review should start inside the bookkeeping file. The question is not only whether the VAT201 can be submitted. The question is whether the records behind the VAT201 are current, supported, and explainable if SARS or management asks for detail later.

For South African SMEs, this matters because VAT pressure often arrives at the same time as ordinary month-end pressure. The owner wants a number, the tax practitioner wants support, and the bookkeeper is still chasing documents. That sequence creates avoidable risk.

The input VAT checks owners usually miss

Input VAT is often where small errors repeat. Businesses claim VAT based on supplier documents that are incomplete, invoices that do not match the entity, duplicated bills, expenses paid from personal accounts, or transactions that were coded from the bank without enough source support.

Before submission, the business should check whether larger input VAT claims can be supported quickly. If the file includes high-value supplier invoices, equipment purchases, imports, unusual once-off expenses, or credit notes, those items should be easy to trace. If they require a long inbox search, the file is not yet ready enough.

The review should also separate normal timing from real problems. A supplier invoice may be valid but captured in the wrong period. A payment may appear in the bank while the invoice is still missing. A personal card payment may relate to the business but still need proper evidence before it supports a VAT claim.

The output VAT checks that protect sales reporting

Output VAT depends on the sales record being complete. Retailers, service firms, contractors, and online sellers can all run into different sales-side problems. The common issue is that the sales system, invoice file, receipts, and bank do not tell the same story.

A business should look for gaps between issued invoices and customer receipts, sales reports and bank deposits, credit notes and original invoices, and cash or card collections and the records behind them. If those gaps are not reviewed before filing, the return may be submitted from a file that still has open sales questions.

This is especially important where the owner uses more than one system. A POS tool, ecommerce platform, payment gateway, bank account, and accounting system can each show a different version of the same trading activity. The bookkeeping process has to reconcile the versions before the VAT return is treated as final.

A practical pre-submission evidence pack

The business should be able to produce a basic pack for the VAT period without starting from scratch.

The pack does not need to be complicated. It needs to be complete enough that a reviewer can see why the VAT number is reasonable.

What to fix before submitting

Some issues should be fixed before submission rather than explained afterward. These include unreconciled bank accounts, missing high-value invoices, duplicate supplier bills, old VAT control differences, unexplained journals, and sales reports that do not agree with the accounting file.

Other items can be listed as known timing differences if they are real, documented, and expected to clear in the next cycle. The discipline is to name them clearly. Unnamed differences become future confusion.

The owner should ask for a short open-item list before the return is approved. That list should show what was resolved, what remains open, who owns it, and whether it affects the current submission. If the provider cannot produce that view, the business may be relying on trust without enough control.

The safer monthly rhythm

The safest VAT process is not a two-month panic. It is a monthly bookkeeping rhythm that keeps the file close to ready all the time. Bank reconciliations should be current, documents should be submitted regularly, and unusual transactions should be questioned while the memory is fresh.

That rhythm lowers the risk of last-minute corrections and makes VAT less dependent on one urgent review. It also helps management because the same clean records used for VAT support better cash flow decisions and month-end reporting.

When to pause before approval

The owner should pause before approving a VAT submission when the bank is not reconciled, large input claims are unsupported, sales reports do not agree to the accounting file, or the open-item list contains items that affect the VAT number. Submitting first and explaining later can create more work than resolving the issue before filing.

This does not mean every small timing difference must hold up the process. It means the business should know which differences are harmless, which are documented, and which still affect the return.

Use this page with

• bookkeeping red flags before VAT filing
• VAT registration and returns
• bookkeeping
• month-end bookkeeping checklist

The stronger the books are before VAT season, the less likely the business is to treat every submission as a finance emergency.

Separate timing differences from filing errors

Not every difference in the VAT review is a filing error. Some differences are timing items that can be explained and carried into the next period. Others change the VAT201 result and should be fixed before submission. The business needs a way to separate the two.

Examples of timing differences include supplier invoices received after the cutoff, customer credits processed after month-end, or bank receipts that relate to invoices already declared in the correct period. Filing errors are different. They include unsupported input VAT, sales that were not captured, VAT codes applied to non-deductible expenses, duplicated supplier documents, or output VAT that does not agree to the sales evidence.

That distinction helps the owner make better decisions. If the difference is documented timing, the return may still be supportable. If the difference changes the return, filing before correction only moves the problem into a SARS query or a future adjustment.

Make approval a control point, not a rubber stamp

Before a VAT return is approved, someone should confirm that the bank reconciliation is complete, input VAT support is available, output VAT ties back to sales, and material exceptions are listed. This approval does not need to be a long meeting, but it should be more than clicking submit because the deadline is close.

For SMEs with outsourced bookkeeping, the approval step should also define who owns each unresolved item after submission. If the bookkeeper flags an exception and management ignores it, the business should not treat that as a bookkeeping failure later. If the bookkeeper does not flag the exception, the provider's review process needs attention.

Good VAT control is therefore shared. The bookkeeper prepares the evidence, management confirms business context, and the final submission reflects a file that can be explained.

Review old VAT habits after submission

After the return is filed, the business should look at the issues that nearly delayed it. If the same supplier invoices are always late, if sales reports always need manual repair, or if VAT codes are corrected every period, the problem is not the latest submission. It is the monthly bookkeeping habit that feeds the submission.

This review should produce one or two process changes before the next period. That might mean changing document cutoffs, reviewing VAT codes earlier, separating mixed-use expenses, or checking sales reports before month-end. Small changes made every period reduce the chance that VAT control depends on a last-minute rescue.