Tax and SARS knowledge base
What is the difference between SARS verification and an audit?
What is the difference between SARS verification and an audit?
Last reviewed:
Direct answer
Verification usually asks you to support information declared on a return with documents. A SARS tax audit is broader. SARS says a tax audit aims to determine whether the taxpayer has correctly declared their tax position and that selection can be risk or random based. In either case, read the notice closely, preserve your records and respond to the exact request.
Treat the notice, account screen or correspondence for your own case as the operational starting point. SARS processes depend on tax type, period, service and the information on SARS's system. Keep every source record and avoid assuming that a general explanation confirms an outcome for your account.
What this means in practice
The terms are often used interchangeably, but they describe different types of review. A verification request is commonly focused on evidence behind particular income, deductions, credits or declarations. The SARS supporting-documents FAQ describes the documents and channels that may be relevant to this kind of request. A tax audit can examine a wider tax position, including the relationship between returns, financial statements and other records.
The label does not tell you whether the tax result is right or wrong. A verification or audit selection is not proof of an error. What matters is the scope of the SARS communication: tax type, years or periods, case number, documents required and the specific action requested. Avoid treating an initial document request as a final assessment, but do not ignore it because it may affect what SARS can decide next.
A useful way to manage a SARS matter is to create a dated evidence folder. Save the original message, list the tax reference and period, keep the return or assessment, and note every action you take. Save a PDF or screenshot of submissions. This record trail helps you distinguish a technical problem, a document request, a service complaint and a formal tax disagreement.
Step-by-step
- Save the SARS letter or eFiling message and identify whether it uses the language of verification, audit, additional supporting documents or another process.
- Record the taxpayer, tax type, return or period, case number and deadline. These details prevent evidence from being sent to the wrong matter.
- For verification, make an item-by-item list of requested evidence and the return amount it supports. Use the particular document list in the notice.
- For an audit, gather the return, financial statements, reconciliations, ledgers, invoices, bank records and correspondence relevant to the scope. Do not send unrelated material without considering the request.
- Prepare complete and readable records. Where calculations link many records, create a factual schedule that lets the reviewer trace an amount to its evidence.
- Submit through the channel SARS specifies and retain proof. Respond to follow-up requests by addressing the precise missing issue.
- Get tailored advice if the request is broad, the records include confidential or third-party information, an assertion is disputed, or a material assessment could follow.
Before submitting anything, reread the selected option and the reference number. Compare your proposed action with the original SARS communication, the latest Statement of Account and your supporting records. Keep the acknowledgement and check the account or case status afterwards. If the screen gives a validation failure or SARS asks for more information, deal with the identified issue rather than sending a duplicate request without checking the facts.
Documents and records to keep
- SARS correspondence and current case status.
- Return, assessments and calculation schedules.
- Certificates, invoices, bank records, financial statements and ledgers relevant to the stated scope.
- Upload confirmation and a chronology of responses.
Keep a copy of the return, assessment, declaration or correspondence to which the matter relates. Store source records with meaningful file names and retain proof of submission. Do not alter a document to make it fit an expectation. If a record needs explanation, provide a brief factual schedule pointing to the relevant date, amount or return entry.
Important limits and exceptions
The SARS audit-file guide cited here is directed to access to audit files and does not establish every taxpayer right or disclosure obligation. Verification can lead to further review, and an audit can have a focused scope. Do not make conclusions about confidentiality, relevance, legal privilege or assessment consequences without tailored advice and the current legal position.
A general guide cannot choose the correct legal remedy where facts are disputed, a formal deadline is short, a material sum is involved, or another person has acted on your behalf. An upload, query, complaint or request may not replace an objection, appeal, payment arrangement, statutory disclosure or other tax-specific process. Use the current SARS notice to assess whether a separate step is required.
When to get tailored advice
Seek advice where SARS requests audit working papers, the case covers several years, the matter involves a business or trust, the taxpayer cannot reconcile the requested evidence, or the request might affect a material assessment or dispute.
TaxProof can help organise a chronology, reconcile records and identify the questions requiring specialist review. It cannot make a SARS decision. Obtain prompt tax or legal advice for a final demand, audit request, estimated assessment, large balance, enforcement risk, confidentiality concern or formal deadline.