What records should I keep to show a tax return was submitted and accepted?

Define what you need to prove

The phrase submitted and accepted can mean several things. You may need evidence that a return reached SARS, that it passed a processing stage, that an assessment was issued or that an amount was paid. Ask which question the record must answer. One screenshot or email rarely proves all of them, and different tax types use different workflows.

Start with the taxpayer’s legal identity, tax reference, return type and exact period. A receipt for a director’s personal income tax return does not establish that the company’s return was filed. A VAT return for one period does not clear a different outstanding period. These identifiers are the foundation of a useful evidence pack.

Retain the version actually filed

Save a readable copy of the return that was submitted, with its period and version information where available. Keep the calculations and supporting schedules that explain the figures. A working spreadsheet or unsigned draft may differ from the final return and cannot establish what SARS received. If an accountant filed it, request the filed copy rather than only a summary of the expected result.

Where a correction creates another version, preserve the earlier return and identify which version is current. Record the reason for the change and the submission evidence for the replacement. Do not overwrite the old file so that the business can no longer explain an earlier assessment, query or payment. Version control matters when several people work on the same tax period.

Keep official submission evidence

Use the current official workflow for the return type. Do not invent a universal accepted certificate or assume every return produces the same notice as an individual income tax return.

What is the difference between saving a tax return and submitting it?

Saving preserves work in progress within the relevant system. Submitting sends the completed declaration through the filing process, subject to the system’s validation and response. The SARS individual return guidance distinguishes saved and filed versions, and its MobiApp guide states that an issued or saved ITR12 has not been submitted. That specific guidance should not be converted into an invented status label for every tax type.

A saved return can contain all the intended figures and still remain unfiled. Likewise, a calculation result is not a submission receipt. Before closing the task, inspect the return history or official response for the correct taxpayer, period and version. If the system reports a validation failure, timeout or unresolved error, retain that evidence and establish whether a successful submission occurred rather than assuming the click was enough.

There is an important individual income tax exception to a blanket instruction to submit everything: SARS may issue an auto-assessment. Follow the current auto-assessment guidance and review its correctness; an accurate auto-assessment can require no return submission. Distinguish that official assessment from a draft you have saved yourself. If changes are required, follow the applicable process and deadline rather than treating the saved correction as filed.

An internal checklist should therefore record the actual outcome: draft saved, successfully filed, auto-assessed with the relevant review, or unresolved. Do not use one completed checkbox for all four. The distinction helps the owner and accountant agree what remains to be done without relying on ambiguous messages.

Illustrative example: the accountant says the return is done

A fictional owner receives an email saying the annual return work is complete. The attachment is a calculation and a PDF of a prepared income tax return. The owner asks for the official filing evidence and discovers the return was saved pending approval rather than submitted. The work may be prepared correctly, but the filing task is still open under those facts.

The owner reviews and authorises the appropriate next step. After submission, the accountant supplies the filed version, acknowledgement and any assessment issued. The business records the tax type and period and assigns responsibility for checking later correspondence. This example is not a statement about any actual accountant; it shows why the meaning of done should be agreed in advance.

Track supporting-document requests separately

SARS can select a submitted return for verification or audit. The official guidance explains that further documents may be requested after filing. Keep the request, its date, the relevant case reference and the response deadline stated in the actual notice. A return submission receipt does not prove that the later supporting-document task has been completed.

Retain an inventory of what was supplied and evidence of the upload or submission outcome. Check whether files were merely attached or whether the required submission step was completed. If a file was rejected, unreadable or missing, record the correction. Avoid claiming that verification is complete until the relevant official response supports that conclusion.

Connect the assessment with payment and account allocation

Where an assessment or account shows an amount payable, review the actual due date and payment reference. Keep payment evidence alongside the return record but identify it as a separate stage. A return can be filed while the resulting payment remains outstanding. A payment can also be made with an incorrect reference and require allocation follow-up.

Compare the account position after payment where appropriate and investigate differences. Do not make a second payment solely because a recent transfer has not yet appeared without checking the details. Likewise, do not assume that a bank confirmation resolves a penalty, interest charge or another period’s debt. Record the exact obligation the payment was intended to settle.

Create a compact index for each return

Use a folder or register entry showing the legal entity, reference, return type, period, version, preparer, reviewer, submission date and current follow-up status. Link the filed copy, acknowledgement, assessment, correspondence and payment evidence. Keep sensitive tax records in a controlled location rather than posting them to a broadly accessible shared drive.

The index should be understandable when the accountant or administrator changes. Avoid filenames such as final-final that do not identify the period or version. Retain the source evidence under the applicable record keeping requirements, including longer retention where relevant to unresolved returns, disputes, audits or investigations. Do not delete everything merely because a standard calendar interval has passed.

Investigate an outstanding status using the evidence

If the return still appears outstanding, compare the official reference, type, period and version with the receipt. Check whether the return was submitted through a different authorised profile or channel and whether the current view is showing the correct entity. Review any rejection or later request before concluding that SARS lost the return.

Ask the preparer for the actual response and raise a focused query through the appropriate SARS process if the mismatch remains. Preserve the case reference and follow-up. Avoid filing a second, potentially inconsistent return merely to remove a warning. Establish the existing status and the correct next action first.

Agree the completion standard with your preparer

A practical handover should say what was filed, for whom, for which period and what remains open. Vatco’s tax returns submission service can help organise the filing and evidence record. Bring the relevant tax references, current status and any prior submission documents.

Use the tax compliance status workflow when the separate goal is to review or share compliance status. A compliance result and a particular return’s evidence pack answer different questions. Keeping both clear makes later enquiries and handovers more reliable.