What should I check if a return appears outstanding after my accountant submitted it?

Identify the exact outstanding item

Start with the official message or account view, including its date, taxpayer reference, tax type and period. An owner may describe everything as a tax return, while the warning refers to a specific VAT period, employer reconciliation or company income tax year. Write down the precise item before asking the accountant to investigate.

Confirm that the view belongs to the correct legal taxpayer. A director’s personal profile, a company profile and another company with a similar trading name can be confused during a handover. Also check that the screen is current and not an old downloaded report. A stale document can accurately describe a past problem that has since been resolved.

Ask for evidence beyond a completion message

Request the filed return, submission acknowledgement or official status evidence, the submission date and any relevant assessment or response. An email saying completed may mean prepared, reviewed, saved, submitted or assessed. Agree which stage was actually reached. The accountant’s explanation is useful, but the official record should support the claimed filing outcome.

If the return was submitted through another authorised profile or channel, ask for the evidence from that process. Do not assume that the absence of a document in one local folder means no filing occurred. The related article on proof of tax return submission explains the evidence pack to retain for future queries.

Match the identifiers one by one

Work through the list before making assumptions about a system delay. Many apparent technical problems are differences in identity, period or stage that can be established from the records.

Check whether the return was saved or actually filed

A prepared return can remain saved in the system without being submitted. A tax calculation can also be generated before filing. SARS individual return guidance distinguishes saved and filed versions; use the current guidance for the particular return type rather than assuming identical labels across all forms. Check the actual response after the submission attempt.

If a validation error occurred, identify the field or requirement that failed and whether it was corrected. If the connection timed out, establish whether the return reached SARS before repeating the action. Preserve the error message and time. Clicking a submission control is evidence of an attempt, not proof of successful completion.

Illustrative example: the wrong VAT period was checked

A fictional company’s owner sees an outstanding VAT period and asks why the accountant has not filed. The accountant supplies a valid acknowledgement, but it relates to the following period. The accountant had completed the recent return while the earlier one still required missing purchase records. Both people were referring to VAT, yet they were discussing different obligations.

The team records the completed period as filed and keeps the earlier period open with a named evidence request. It does not resubmit the completed period or assume the acknowledgement clears both. The example shows why period-level records matter more than a general statement that VAT is up to date.

A different business might find that the correct return was successfully submitted but a status view has not reflected it. That requires a different response, supported by the correct acknowledgement and any processing correspondence. The same warning can therefore have different causes; the evidence should determine the next step.

Look for later requests or changed assessments

Review correspondence issued after the original submission. SARS may request supporting documents or undertake verification. A filing acknowledgement does not establish that those later tasks are complete. Record the case reference, requested information and the actual response deadline from the notice. Ask whether the accountant’s engagement includes monitoring and responding to this correspondence.

Also distinguish a return filing issue from disagreement with an assessment. If the return was filed and an assessment issued, the relevant remedy may involve a correction, reduced assessment request, objection or another applicable process, depending on the facts. Obtain advice before choosing the route. Refiling indiscriminately can create conflicting versions without resolving the real issue.

Separate debt from missing returns

An account or compliance view may show a payment problem even though the return is filed. Match the liability to the tax type and period, then compare payments and allocations. A bank payment made with an incorrect reference may need follow-up. A payment instruction awaiting approval may not have left the bank at all. These are different from an unsubmitted return.

Do not mark the issue closed merely because the business paid an estimated amount. Payment does not necessarily satisfy the filing obligation, and filing does not necessarily settle the account. Keep the two statuses separate in the return register so the accountant and owner can identify the actual remaining task.

Check access and representative changes

A change of accountant, registered representative or eFiling access can affect who can see and act on a tax type. Confirm the current authorised arrangement and whether a tax type transfer or access request is complete. Use official processes and avoid sharing personal login credentials as a shortcut. The owner should retain appropriate visibility and records even when a practitioner performs the work.

Ask the outgoing preparer for historical submission evidence and unresolved correspondence. Do not treat a provider handover as a fresh start that removes earlier obligations. A new accountant may need both the current portal position and the old filing records to explain the mismatch accurately. Record who is responsible for the query after the handover.

Raise a focused query when the evidence still conflicts

Prepare a concise case summary with the taxpayer, tax type, period, submission date, acknowledgement and the current conflicting status. Use the appropriate SARS channel and retain the reference. Include the documents needed to establish the issue without sending unrelated confidential records. A clear comparison is more useful than a large unlabelled bundle of screenshots.

Record the response, requested next step and follow-up responsibility. A query reference proves that a query exists, not that the return status has been corrected. After SARS or the preparer acts, check the relevant record again and retain the updated evidence. Avoid promising a customer a compliance outcome before the official position supports it.

Handle genuine missing records or filing failures openly

If the investigation shows that the return was not filed, identify the reason and prepare an accurate recovery plan. Recover missing documents, complete the calculation and review the relevant requirements. Do not submit unsupported nil figures merely to make the warning disappear. Where a deadline or notice has already been missed, obtain advice about the consequences and the appropriate next steps.

Use the overdue return recovery article if several periods or tax types are affected. It helps separate source-record reconstruction, filing, debt and queries. One failed return can sometimes reveal a wider handover or record keeping problem that needs a more complete inventory.

Close the issue with a clear evidence record

The final record should state the cause, action taken, current official status and any remaining payment or verification task. Keep the original acknowledgement and the evidence that resolved the mismatch. Agree a future completion standard with the accountant so prepared, filed and paid are not used interchangeably.

Vatco’s tax returns submission service can help review the relevant return records and organise the next step. Bring the outstanding notice, correct tax references and the evidence supplied by the previous preparer. Start with the exact discrepancy so the response addresses the real obligation.