Received a SARS verification request? What to check before uploading documents

Do not upload documents reflexively. Start with the actual SARS verification letter. Identify the return or declaration being checked, the tax type and period, what SARS has requested, and the response date stated in the letter. Then reconcile the submitted position to the underlying records, organise a complete response that SARS can follow, check the electronic submission, and retain an exact record of what was sent.

This is practical preparation, not a rule that every verification needs the same documents or the same response. The letter and the facts of the return remain the starting point.

What a SARS verification is

The South African Revenue Service (SARS) describes verification as a check of information supplied in a return or declaration. It may compare that information with third-party data, financial or accounting records, and other supporting documents. SARS says verification and audit are separate processes; an audit is a broader examination of records and the declared tax position. See SARS’s current verification and audit guidance for its full explanation.

That distinction matters, but the label alone does not answer what to submit. Read the correspondence issued for the matter. A verification request does not by itself show that the return is wrong, and a well-organised response does not guarantee that SARS will accept the position, finalise the matter, or make a refund.

Start with the verification letter, not the upload button

SARS says it notifies a taxpayer of verification by official letter and that the letter shows the due date or time frame and the information to be supplied. It also says the material requested can depend on the tax type. A generic online checklist should therefore not replace the letter in front of you.

Confirm the return, period and request

Before collecting files, record:

• the taxpayer or entity named in the letter;
• the tax type and period;
• the return or declaration under verification;
• any case or reference number shown;
• every item or issue for which material is requested;
• the response date stated in the letter; and
• the submission channel described or available for the matter.

Read the request alongside the return or declaration that was actually submitted. A request about one period or figure should not be answered from a different version, a later working paper, or a record belonging to another taxpayer.

Keep the original letter and delivery record

Save the original letter in the working file. Keep the related eFiling correspondence or other delivery record with it. If the matter later changes stage, this provides a reliable starting point for the chronology and helps identify precisely what SARS asked for at that time.

If you use the SARS Online Query System or a branch rather than eFiling, current SARS guidance says the verification letter should accompany the documents because its barcode connects the material to the tax record. Follow the instructions for the actual channel being used.

Reconstruct what was actually submitted

The next task is not simply to locate documents. It is to understand the reported position those documents are meant to support.

Compare the return with the source records

Obtain the filed return or declaration and the calculation or schedule behind the relevant amount. Then trace that amount to the source records. Depending on the matter, those records might include certificates, statements, invoices, contracts, ledgers, payroll records, calculations, or other documents connected to the item SARS has asked about.

The appropriate evidence depends on the tax type, the transaction, and the particular request. There is no universal verification pack. The useful question for each document is: what reported figure or factual statement does this support?

Identify differences before explaining them

Check whether the return, calculation, third-party information, and source records agree. Note any missing document, duplicate amount, different date, changed figure, or unexplained reconciliation item before preparing the upload.

An evidence gap and an error in the submitted return are different problems. A polished document pack cannot make an incorrect position correct. Equally, a figure that is supportable should not be abandoned merely because the records are initially disorganised. SARS’s general verification guidance identifies a Request for Correction as one possible response where a taxpayer wants to change the original declaration. Whether it is available or appropriate must still be checked against the tax type, return, workpage, and procedural stage. A Tax Review may be appropriate before a procedural choice is made.

Build a response SARS can follow

Organise the response around the request, not around the folders in which the records happened to be stored. For a short request, clear file names may be enough. For a larger response, a concise index or covering schedule can show how the requested item, reported amount, explanation, and file relate to one another.

Working field	What to record
Request item	The item or issue described in the verification letter
Filed position	The amount or statement in the submitted return or declaration
Reconciliation	How the filed position connects to the source records
Supporting file	The file name and the point that document supports
Gap or explanation	Any missing record or difference requiring attention before submission

This table is an organisational method, not a prescribed SARS form. Keep any explanation factual and proportionate. Relevant, clearly indexed evidence is generally more useful than an unstructured document dump, but do not withhold material that the letter requires or that is necessary to explain the reported position.

The SARS Verification & Supporting Packs service page explains Anchor’s evidence-led approach in more detail. The verification section of the frequently asked questions also addresses document selection and the role of a supporting pack.

Check every document before submission

Perform a page-by-page quality check rather than assuming that a file which opens is ready to send. Confirm that:

• the document is legible and complete;
• all pages are present and in a sensible order;
• the taxpayer, entity, tax period, and dates are correct;
• totals agree with the relevant schedule and filed amount;
• file names are clear, distinct, and connected to the index where one is used;
• duplicate pages and irrelevant working versions have been removed; and
• any missing or contradictory record has been identified rather than hidden in the pack.

Also check the current technical requirements for the channel. SARS publishes separate eFiling document standards covering accepted formats, file sizes, file counts, naming problems, and protected or encrypted documents. These are operational requirements and may change. Check the live guidance instead of relying on an old screenshot or a number copied into a generic checklist.

Check the electronic submission itself

Uploading a file and sending the completed response are not necessarily the same action. SARS’s current eFiling upload guidance instructs the user to upload the selected files and then use Submit to SARS to send the supporting material.

SARS also warns that the supporting-document link will no longer be available after the final submission action. It says a further link would need to be opened through another request from a verifier or auditor. Before selecting the final action:

1. compare the uploaded file list with the verification letter and your index;
2. open or preview the uploaded files where the channel permits;
3. confirm that the correct versions are attached;
4. check that each upload shows a successful status; and
5. submit only when the response is complete for the request, subject to the stated response date.

Use the applicable SARS channel and its current instructions. This article deliberately does not reproduce a screen-by-screen process, because labels and channel requirements can change.

Preserve the exact submission record

Retain a clean final record containing:

• the verification letter and related correspondence;
• the filed return or declaration reviewed;
• the final calculation or reconciliation;
• the index or covering schedule;
• an exact copy of every file submitted;
• the submission acknowledgement, status, or timestamp available from the channel; and
• later requests or correspondence from SARS.

Store the final submitted versions separately from working drafts. If SARS asks for further material, this makes it possible to see what was already provided and prevents a later response from being built on an uncertain file history.

This article does not state a universal statutory retention period. Retention obligations can depend on the tax type, record, and circumstances, and need separate consideration.

Common mistakes before pressing Submit

Avoid these recurring preparation problems:

• answering from memory instead of reading the current letter;
• uploading before checking the filed return and calculation;
• treating every document on file as equally relevant;
• sending unexplained totals that do not reconcile to the return;
• assuming a neat pack can cure a weak or incorrect tax position;
• attaching incomplete, illegible, duplicated, or protected files;
• confusing an upload action with the final submission action; and
• failing to retain the final files and proof of submission.

The objective is not to manufacture volume or certainty. It is to provide a complete, intelligible response to the request actually made, supported by the records that exist.

When professional help may be appropriate

Consider obtaining a review before submission where:

• the return or declaration does not reconcile to the source records;
• the filed position may contain an error;
• SARS requests evidence that does not exist or cannot be obtained;
• several tax types, entities, or periods are involved;
• the amount or potential consequence is material;
• it is unclear what a document proves or how it relates to the reported amount; or
• the correspondence suggests that the matter may be moving beyond verification.

If you request a case assessment, keep the initial enquiry high level. Do not send tax returns, identity documents, tax numbers, passwords, banking credentials, or other sensitive records through the initial contact form. Supporting documents can be requested separately where appropriate.

Final pre-submission checklist

Before using the final submission action, confirm that you have:

1. read and retained the verification letter;
2. identified the taxpayer, tax type, period, return, request, and stated response date;
3. reconciled the filed position to the underlying records;
4. addressed unexplained differences and evidence gaps;
5. organised each requested item with the relevant explanation and support;
6. checked every file for accuracy, completeness, legibility, naming, and current channel rules;
7. compared the uploaded list with the final response pack; and
8. prepared to retain the exact submission and its acknowledgement.

That sequence will not determine SARS’s outcome. It does, however, reduce the risk of submitting a response before the position and evidence have been properly understood.