Quick answer
Immediately before submission, verify the latest authentic SARS letter, exact due date and time, any written extension actually granted, the correct taxpayer, tax type and period, closure of every request item, reconciliation and reviewer sign-off, authority to submit, confidentiality or privilege decisions, file readability, the live channel limits, and the final submission action. Freeze the sent set and keep the receipt, case reference and post-submission owner.
How to use this guide
This is a release-control gate for a substantially completed response. It does not calculate a universal SARS deadline, organise the source records or decide the tax position. If the pack is still being built, use the source-document organisation guide. If the notice has not been authenticated and classified, use the audit-letter first-response guide.
Gate 1: confirm the exact procedural fork
Read the current letter again, not a summary in an email or task list. Confirm which release you are making:
- Verification response: the requested supporting material or an authorised, separately considered Request for Correction under the verification letter.
- Audit material response: the records, information or arrangements requested in the Notification of Audit or later audit correspondence.
- Audit Findings response: a response to proposed findings before an assessment; do not call the findings letter an assessment.
- Assessment or eligible decision: stop using this audit-response checklist as the procedural authority and move to the correct reasons or dispute analysis.
Check the taxpayer name or entity, tax reference, case reference, tax type, period and letter date. SARS correspondence on eFiling includes requests, findings and assessment-related notices; retrieving the exact document reduces the risk of applying a deadline or pack to the wrong stage.
Gate 2: prove the controlling deadline
The release record should contain:
- the authentic letter and delivery or retrieval evidence;
- the due date and any stated time or channel cut-off;
- the internal interpretation of how the date was calculated;
- any request for clarification or more time;
- SARS's written response; and
- the latest valid extension or revised instruction, if one exists.
Do not replace the letter's date with a generic number of business days from an article, call-centre discussion or past case. Do not treat an extension request, complaint or appointment as an extension. Unless a valid change is confirmed, manage the response against the active stated date.
Work backwards. Set earlier internal cut-offs for evidence completion, technical review, legal review where needed, authorisation and upload testing. The final day should not be the first time the team discovers that a file is unreadable, the user lacks access or the upload set exceeds the live channel controls.
Gate 3: close every request item
Compare the final bundle with the request-to-evidence matrix. For every row, require one of these controlled outcomes:
- evidence supplied and cross-referenced;
- an approved explanation supplied;
- alternative evidence supplied with the limitation recorded;
- written clarification or agreed later delivery recorded; or
- a deliberate escalation decision that stops submission.
Blank rows, unowned gaps and “to follow” notes without authority are not closed. Make sure a covering letter does not claim full compliance if the matrix shows unresolved items. Conversely, do not add irrelevant records merely to make the bundle appear substantial.
Gate 4: test the evidence and narrative together
Confirm that:
- the response text uses the same taxpayer, period, population and terminology as the schedules;
- every material number can be traced to the filed position, computation, ledger and source record where applicable;
- reconciling items are quantified and explained;
- document dates and tax periods are consistent;
- reconstructed, converted, redacted or annotated records are clearly identified;
- missing evidence and conflicts are disclosed to the reviewer;
- factual statements are supported; and
- draft legal conclusions or unnecessary admissions have been removed or approved.
Ask a reviewer who did not assemble the pack to follow a sample of important figures from response text to source evidence and back again. A schedule total that cannot be reproduced should remain a no-go item.
Gate 5: verify authority and sign-off
The release record should identify:
- the taxpayer or authorised decision-maker;
- the owner of factual accuracy;
- the accounting or tax-technical reviewer;
- any legal reviewer and the exact issues reviewed;
- the person authorised to use the submission profile; and
- the person responsible for monitoring the case afterward.
Check that the eFiling or other profile is linked to the correct taxpayer and tax type. Do not use a colleague's credentials or share a password or OTP. SARS's scam guidance says it will not request passwords, OTPs, banking PINs or eFiling login credentials through informal communications.
Sign-off should identify the frozen pack version. Approval of an earlier draft does not cover a later file added after review. Any change after sign-off should reopen the relevant factual, technical, legal or owner approval.
Gate 6: resolve confidentiality, third-party and privilege decisions
Before release, confirm that the bundle contains no uncontrolled mailbox export, unrelated personal data, hidden spreadsheet content or legal file added by convenience. For each redaction or withheld item, record the request affected, decision-maker, reason and whether the remaining evidence still answers the request.
Do not claim that POPIA, commercial sensitivity, possession by an accountant or copying a lawyer automatically prevents disclosure. Do not assume involving a lawyer makes ordinary source records privileged. If the question is material and unresolved, stop the release and obtain advice rather than improvising a label in the covering response.
Gate 7: perform a technical dry run
Use the actual intended channel and current work page where possible. Check:
- supported file type;
- file-size and count limits shown for the route;
- password protection or encryption that could prevent SARS from opening a file;
- corrupted, blank, rotated or illegible pages;
- spreadsheet print areas, hidden rows, columns, sheets, formulas and external links;
- unique, understandable filenames;
- correct ordering and cross-references;
- whether the barcode or case letter must accompany another channel; and
- whether a stable connection and authorised user are available.
SARS's public verification page currently describes formats, per-file size and upload-count controls for that process. PAYE audit guidance shows its own work-page sequence. Check the live route and letter because technical controls can differ or change; do not force a generic limit onto every tax type.
Open every final file from the frozen submission folder, not from the preparer's working directory. Calculate checksums where proportionate and compare the upload list with the final manifest.
Gate 8: complete submission and preserve proof
Distinguish “selected,” “uploaded” and “submitted.” SARS tells verification users to click submit and warns that the link may close afterward. The PAYE audit example also has separate upload and submit steps.
After the final action:
- save the acknowledgement, receipt or available confirmation;
- record the date, time, channel, user and case reference;
- archive the exact files and manifest;
- confirm that no file was omitted or duplicated;
- record any error message and corrective action; and
- notify the post-submission owner.
If the channel fails near the deadline, preserve evidence of the failure and use the available official support or alternative route specified by SARS. Do not state that an attempted upload equals a valid response without evidence.
Gate 9: assign the next watch point
Submission does not close the matter. The case owner should monitor official correspondence for:
- an acknowledgement or finalisation;
- a request for additional material;
- audit progress communication where applicable;
- an Audit Findings Letter;
- a revised or additional assessment; or
- another procedural instruction.
Set a dated review point and store later correspondence in a new response cycle. Do not overwrite the first submission bundle. If an assessment is issued, move to the correct post-assessment route rather than reusing this pre-assessment checklist. The post-assessment deadline guide owns that later boundary.
Stop the submission if any no-go condition remains
Do not release merely because the clock is close if:
- the letter or due date is not authenticated;
- the wrong taxpayer, period, tax type or case is selected;
- a material request has no controlled response;
- figures do not reconcile;
- a high-impact contradiction is unexplained;
- provenance of a key record is uncertain;
- authority to submit is missing;
- a material privilege or legal-exposure issue is unresolved;
- final files fail the technical dry run; or
- no method exists to preserve submission proof.
Escalation does not guarantee more time. It means the authorised decision-maker receives the actual risk, available options and evidence before the deadline action is chosen.
For a separate red-team pass before release, test the completed pack against the SARS response mistakes guide.
FAQs
Is there one standard deadline for every SARS audit response?
No. Use the exact authentic letter and any valid written change. Do not replace its date with a generic online timeframe or assume a request for more time pauses it.
What should close each item in the SARS request?
Require reviewed evidence, an approved explanation, accepted alternative treatment or a deliberate escalation decision. An unowned blank, informal promise or unexplained omission is not closure.
What technical checks should I run before submission?
Open every final file, verify readability, taxpayer and period, current format and size controls, filenames, hidden spreadsheet content, ordering and the final manifest on the actual intended channel.
Is uploading the files the same as submitting them?
Not always. SARS guidance shows separate upload and submit steps on relevant work pages. Complete the final action and preserve the acknowledgement or other proof.
Related Lexuno paths
Related articles
Source notes
Legal note
This article is general legal information for South African readers. It is not legal advice. Speak to a qualified legal professional about your specific facts before taking action.