VAT Refund Supporting Documents Checklist
Prepare SARS VAT refund packs with valid tax invoices, VAT201 support, ledgers, bank evidence, and clear refund explanations.
- VAT refund support should explain why input VAT exceeded output VAT for the period.
- The pack should include valid tax invoices, VAT schedules, ledgers, bank evidence, and notes for large or unusual claims.
- Refund delays often come from missing documents, profile issues, outstanding returns, bank-detail problems, or VAT control differences.
A VAT refund is not only a number on the VAT201. It is a claim that SARS may ask the vendor to prove.
The supporting file should show why the refund exists and why the input VAT claimed is valid. That matters for cash flow, because a weak refund pack can delay money the business may already be planning to use.
VAT refund pack
Prepare:
- submitted VAT201 return
- VAT calculation
- input VAT schedule
- output VAT schedule
- valid supplier tax invoices
- bank statements or payment evidence where useful
- import or export documents where relevant
- VAT control reconciliation
- refund explanation note
- proof of submission and SARS correspondence
This supports VAT refund support and VAT audit support.
Explain the reason for the refund
The file should name the commercial reason for the refund. Common reasons include:
- large equipment or asset purchases
- export or zero-rated sales
- project setup costs
- seasonal low sales
- supplier catch-up invoices
- capital expenditure before revenue starts
If management cannot explain why the period is a refund period, SARS may also struggle to follow the claim.
Input VAT checks
Review every material input claim for:
- valid supplier VAT number
- buyer details where required
- invoice date and period
- description of goods or services
- VAT amount
- duplicate claims
- denied or restricted expenses
- private or mixed-use items
This is where VAT201 return checks and VAT reconciliation overlap.
Refund delay controls
| Control | Why it matters |
|---|---|
| Bank details checked | Refunds can stall where profile details are weak |
| Other returns reviewed | Outstanding tax returns can affect compliance status |
| VAT control reconciled | The ledger should support the claimed refund |
| Large claims explained | Unusual input VAT should have clear notes |
| SARS correspondence saved | Follow-up depends on knowing what was requested |
These controls help the business distinguish a SARS processing delay from a weak file.
Refund reason table
| Refund driver | Documents to prepare | Review note |
|---|---|---|
| Capital equipment purchase | Tax invoice, payment support, asset record | Explain the purchase and business use |
| Export or zero-rated sales | Export documents and sales support | Prove why output VAT is low or zero-rated |
| Project setup costs | Supplier invoices and project budget | Explain timing before revenue starts |
| Seasonal low sales | Sales trend and prior-period comparison | Show why input VAT exceeded output VAT |
| Supplier catch-up invoices | Invoice list and period review | Check that claims were not duplicated |
| Import VAT | Customs and clearing documents | Link import VAT to the claim period |
This table helps the reviewer explain the refund before SARS asks. A refund with a clear commercial reason is easier to support than a refund that appears only as a negative amount on the return.
Vendor profile checks
A strong document pack can still be delayed if the vendor profile has problems. Check banking details, registered particulars, eFiling access, representative authority, address details, and outstanding returns before relying on the refund date.
Also review broader tax compliance. Outstanding VAT, PAYE, income tax, or administrative issues can affect how quickly the matter is resolved. The refund pack should therefore include a quick compliance status check, not only invoices.
If SARS has requested bank-detail confirmation or profile verification before, keep those records available. Refund follow-up is slower when the team has to search for representative and banking documents after the case has already started.
Input claim support
Refunds are often driven by input VAT. That means the supplier invoice file should be stronger than usual. Review each large invoice for supplier VAT number, buyer details, date, description, VAT amount, and whether the expense was incurred for taxable supplies.
Where supplier documents are weak, request corrected invoices before submitting a verification response. If a document cannot be corrected, decide whether to exclude the claim or keep a clear risk note. Do not bury weak documents inside a large upload and hope they are missed.
For capital assets, connect the invoice to the asset register and business use. For project costs, connect invoices to the project or cost centre. For import VAT, keep customs and clearing documents with the claim. The aim is to show why the input VAT belongs to the vendor and the period.
Output VAT and refund logic
The refund explanation should not focus only on expenses. It should also explain output VAT. If output VAT is low because sales were seasonal, delayed, zero-rated, or below normal, say so and support it with sales records.
If zero-rated sales are involved, prepare the evidence before submitting the pack. SARS may need to see why the zero rate was applied. Export documentation, customer records, transport support, contracts, and sales invoices should be organised by transaction where relevant.
Credit notes can also create refund periods. If the refund is caused by credit notes, link each credit note to the original sale and explain why it was issued.
Cash-flow link
If the business depends on the refund to pay suppliers, wages, or project costs, the refund timeline should be visible in the cash-flow forecast. Treat the refund as uncertain until the verification is final.
That is why VAT refund work should link to cash-flow management, not only tax filing.
Follow-up and allocation
After the refund is submitted or verified, monitor SARS correspondence and the statement of account. If the refund is released, match the bank receipt and clear the VAT control balance. If the refund is offset against another tax debt, record the allocation so the accounting records agree.
If SARS disallows part of the refund, review the reason against the support pack. The business may need to object, correct a return, obtain missing invoices, or accept the adjustment. The decision should be documented because it affects future VAT periods and possibly income tax or annual financial statements.
Refund follow-up should also feed into process improvement. If missing invoices caused the delay, improve supplier collection. If profile details caused the delay, clean the SARS profile. If the refund reason was hard to explain, improve VAT review notes before the next submission.
Refund approval review
Before management relies on a VAT refund, the finance team should classify the refund as expected, under verification, released, offset, delayed, or disputed. Each status has a different cash-flow meaning. A refund that is expected but not yet released should not be treated the same as cash in the bank.
The approval review should confirm the refund amount, the VAT period, the commercial reason, the strongest supporting documents, open SARS requests, and the likely next action. This gives owners a more realistic view than simply saying SARS owes the business money.
If the refund is large compared with normal turnover, attach a short explanation for management as well as SARS. The explanation should say what changed in the period, why input VAT exceeded output VAT, and what evidence supports the claim.
Repeated refund periods
Repeated refund periods need extra attention. They may be normal for exporters, project-based businesses, start-up phases, or businesses making large capital purchases. They can also signal weak output VAT, delayed sales capture, duplicated input claims, or poor VAT coding.
Review refund trends over several periods. Compare refunds to sales, purchases, asset additions, exports, and cash movements. If the pattern is commercial and supported, keep the explanation. If the pattern is not clear, perform a deeper VAT reconciliation before the next claim.
This trend review helps avoid treating every refund as an isolated event. It also gives the business better cash-flow expectations and stronger support if SARS asks why refunds keep arising.
Owner approval note
Before the pack is submitted, the owner or finance lead should approve the refund explanation. That approval confirms that the tax file matches the commercial reality of the period and that management understands the cash-flow risk if SARS delays or adjusts the refund.
Keep that approval with the submitted VAT records.
Practical takeaway
A VAT refund pack should make the refund easy to understand. If the refund depends on invoices or assumptions that cannot be supported, the file needs review before submission or response.