VAT Audit Verification Response Checklist
Prepare SARS VAT audit and verification responses with VAT201 returns, ledgers, tax invoices, bank support, and clear review notes.
- A VAT audit pack should show how the VAT201 connects to the ledger and source documents.
- The response should separate clean evidence, exceptions, missing support, and items needing correction.
- Refund periods, large input claims, and unusual VAT treatment need stronger notes before documents are sent to SARS.
A SARS VAT verification response should not be a loose folder of invoices. It should be a structured pack that explains the return.
The goal is to show how the VAT201 was built, which documents support the input claims, where output VAT came from, and why any unusual treatment is valid for the period.
Response sequence
- Read the SARS request and identify the exact period and documents requested.
- Pull the submitted VAT201 and the supporting calculation.
- Reconcile the VAT201 to the ledger and VAT control account.
- Match input claims to valid tax invoices.
- Match output VAT to sales, credit notes, and relevant schedules.
- Add notes for exceptions, zero-rated items, imports, exports, and corrections.
- Submit a clean pack and keep a copy of the response.
This supports VAT audit support and VAT compliance support.
Evidence table
| Evidence | What it proves |
|---|---|
| VAT201 return | What was declared |
| VAT calculation | How the return was built |
| General ledger | Where the accounting entries sit |
| VAT control account | Whether the return agrees to the books |
| Supplier tax invoices | Whether input VAT was supported |
| Sales reports and invoices | Whether output VAT was complete |
| Bank statements | Whether payments and receipts support the period |
| Review notes | Why exceptions were accepted |
The table is useful because SARS may ask for documents, but the business still needs to prove the logic behind them.
Build the response index
Before sending documents, create an index. The index should list each document, the period it relates to, the VAT201 line or schedule it supports, and any explanation SARS will need to understand it. This prevents the response from becoming a bulk upload with no clear story.
For input VAT, group invoices in the same order as the input schedule. For output VAT, group sales reports, invoices, credit notes, and zero-rated support in the same order as the output schedule. If bank statements are included, mark the pages or transactions that support the VAT period.
The index should also show exceptions. If an invoice was corrected, if a credit note was posted late, if an import document supports the VAT instead of a supplier invoice, or if a transaction was excluded, note it clearly. Hiding exceptions usually creates more follow-up.
Input VAT evidence review
Input VAT is often the focus of verification because it reduces the amount payable or creates a refund. Review each material claim before it is sent. Confirm supplier details, VAT number, invoice date, invoice number, buyer details where required, description, VAT amount, and whether the expense is allowed.
The response should not include weak invoices without review notes. If a document is incomplete, decide whether to obtain a corrected invoice, exclude the claim, or explain why the support is still valid. The decision should be visible in the working file.
Also check duplicate claims. The same supplier invoice may appear twice if it was uploaded, captured manually, or processed through a creditor statement. Duplicate input claims are easier to catch before SARS does.
For imports, support usually sits outside normal supplier invoices. Keep customs documents, clearing documentation, proof of payment, and import VAT schedules together. The response should make it clear why the import VAT belongs in the period claimed.
Output VAT evidence review
Output VAT support should prove that sales were declared completely and correctly. Gather sales reports, invoices, credit notes, cash-sale records, POS exports, ecommerce reports, bank receipts, and zero-rated or exempt support where relevant.
The reviewer should compare sales per VAT201 to sales per ledger and management accounts. If there is a difference, explain it. Timing differences, deposits, exempt income, zero-rated supplies, or accounting cut-off entries can be valid, but they should not be left unexplained.
Zero-rated and exempt items need particular care. A zero rate should have supporting evidence. Exempt income should be separated from taxable sales. If the treatment is uncertain, the response should be reviewed before documents are sent.
Credit notes should link back to original sales. If large credit notes drive the VAT result, include the commercial reason and supporting documents.
Common weak points
- invoices without required VAT details
- input VAT claimed in the wrong period
- credit notes posted late
- mixed-use expenses without notes
- imports without customs support
- zero-rated sales without supporting evidence
- VAT control balances that do not agree to returns
- bank movements that do not match the declared activity
These items should be isolated before submission so management understands the risk.
Refund-sensitive periods
VAT refunds often attract closer review. If a refund is driven by a large asset purchase, export activity, a slow sales period, or a catch-up of supplier invoices, the file should name that reason clearly.
The refund response should also tie to VAT refund supporting documents and cash-flow management, because delayed refunds can affect operations.
SARS correspondence control
Keep every SARS notice, request, upload confirmation, case number, and response note together. A VAT verification can move through several steps, and the team needs to know what was requested, what was submitted, and when.
Deadlines should be tracked immediately. If the business needs more documents from suppliers, banks, clearing agents, or internal staff, assign responsibility early. Waiting until the final day usually leads to weak uploads or missed evidence.
After submission, check whether SARS asks for more documents, finalises the case, disallows a claim, or raises an assessment. The outcome should be compared to the response pack so the business knows whether a correction, objection, or process change is needed.
When to consider correction or dispute routes
If the review finds an error, the next step depends on the facts. The business may need a revised return, a correction, a voluntary disclosure route, an objection, or a clearer response to the current case.
Do not force a weak file through as if all items are clean. A clear separation between supported amounts and problem items usually produces a better decision.
After the case closes
Once SARS finalises the verification, update the VAT control account and the compliance file. If a claim was disallowed, the accounting records may need a journal. If a refund was released, the bank receipt should be matched. If an assessment was raised, the objection or payment decision should be documented.
The review should also feed back into monthly VAT controls. If missing invoices caused the problem, improve supplier document collection. If zero-rated support was weak, create a standard evidence pack. If the VAT control account did not agree, reconcile it before the next return.
The point of an audit response is not only to close the SARS case. It should also reduce the chance that the same weakness appears in the next VAT period.
Internal review before upload
Before anything is uploaded, the response should be reviewed by someone who did not compile the pack. That reviewer should check whether the SARS request has been answered exactly, whether the period is correct, whether the documents are readable, and whether each large amount can be traced to the schedule.
The reviewer should also look for contradictions. A VAT schedule may show one amount while the ledger shows another. An invoice date may fall outside the period. A bank payment may not match the supplier invoice. A sales report may exclude one branch or online channel. These issues should be resolved or explained before SARS receives the file.
Name the final response clearly. Keep the submitted pack, the working pack, and the review notes separate. If the business later needs to object or respond to a follow-up, it must know exactly what SARS has already seen.
What not to send blindly
Do not send every invoice, bank statement, and ledger export without a review index. Large unstructured uploads make it harder for SARS to follow the response and harder for the business to prove that the right documents were submitted.
Do not send private or irrelevant records where a focused extract would answer the request. Also avoid sending documents that undermine the submitted VAT201 unless the response explains the issue and the chosen correction path.
If support is missing, record that fact and decide on the next step. The business may need to request documents, reverse a claim, submit a correction, or prepare for a dispute. A clean decision trail is better than a rushed upload with unexplained gaps.
Practical takeaway
A VAT audit response should make the return easy to follow. If the pack does not explain the VAT201 from source document to ledger to submission, it is not ready.