Tax and SARS knowledge base
What is the difference between a SARS complaint and a tax dispute?
What is the difference between a SARS complaint and a tax dispute?
Last reviewed:
Direct answer
A SARS complaint is for dissatisfaction with a SARS process or service that has not been adequately resolved. A tax dispute is for a disagreement with an assessment or decision, and it must follow the process and deadline that apply to that assessment or decision. SARS's 2025 general guide says an objection must be submitted within 80 business days from the date of assessment, or from the date written reasons were provided in the stated circumstance. Do not file a service complaint in the expectation that it replaces an objection, appeal or another formal tax remedy.
The practical first step is to read the latest SARS notice closely. If it identifies an assessment, a decision, an amount, a due date or a formal right to object, preserve it and identify the specific remedy before taking another step. If the problem is a missing document, an unresolved request, a technical channel problem or poor service, a complaint may be relevant. The same case can sometimes contain both a service problem and a tax issue, but they remain separate questions.
What this means in practice
SARS describes a complaint as a grievance or dissatisfaction with a process, including a query, return or service request, that has not been adequately resolved. Its eFiling guide lists categories such as unresolved service or operational matter, missing or lost documentation, employee behaviour or competence, channel or technical issues, and quality or speed of service. Those are process-focused categories. They do not decide whether a tax assessment is correct.
For example, a taxpayer may have supplied supporting documents but SARS cannot locate them. That may justify a complaint about missing documentation after the taxpayer has kept the submission evidence and case number. By contrast, if SARS has issued an assessment and the taxpayer disputes the amount or basis of assessment, the current assessment notice and dispute information must be considered. Calling the issue a complaint does not change its legal character.
Create a dated case file before selecting a route. Save the original notice, return, assessment, statement of account, case reference, proof of upload and a brief chronology. Separate the facts into two columns: operational problem and tax disagreement. This simple distinction helps prevent a complaint form from becoming a vague explanation that does not address either route properly.
Step-by-step
- Read the most recent SARS correspondence and identify whether it refers to a service request, a tax assessment, a decision, a verification, an audit or a formal deadline.
- Write down the tax type, period, SARS case number, assessment number if any, date issued and response date. Do not rely on a recollection of an earlier call.
- If the problem is service or process dissatisfaction, use eFiling's Services, Complaints and New Complaint path. SARS says representatives must select the correct taxpayer before lodging a taxpayer-related complaint.
- Select a category that matches the process problem and provide the required reference. For some complaint categories, SARS requires a case number.
- If you disagree with an assessment or decision, stop and review the route and deadline stated in the notice. Obtain advice promptly if there is uncertainty or the amount is material.
- Keep proof of every submission and check the complaint work page or correspondence for status messages. Do not submit duplicate forms just because the underlying tax question is still unresolved.
- Deal separately with any payment, return, document request or formal dispute step shown in the current SARS notice.
Documents and records to keep
- The assessment, decision or notice that triggered the concern.
- The latest Statement of Account, relevant return and supporting documents.
- Case numbers, submission receipts, screenshots and correspondence.
- A dated chronology distinguishing service events from tax issues.
Keep original records in a secure folder and use clear file names. A complaint about service can benefit from screenshots and prior case references, while a tax disagreement usually needs the relevant assessment, return and evidence. Do not alter documents to fit a desired explanation. If a record is unclear, preserve the original and prepare a short factual note identifying the date, amount or reference that matters.
Important limits and exceptions
A service complaint does not itself amend a return, cancel a debt, suspend a due date, reverse an assessment or guarantee a turnaround time. SARS may validate the complaint form and can show a validation failure if a complaint or case number is invalid. The complaint process therefore needs accurate taxpayer and case details, but accuracy alone does not convert a dispute into a complaint.
Likewise, a formal tax remedy does not necessarily correct a service problem such as missing correspondence or a technical eFiling failure. The safest approach where both appear is to preserve the evidence, follow any stated deadline and get tailored help before a remedy is lost. A complaint, upload or online query should never be assumed to replace a statutory step because the results of using the wrong route can be serious.
When to get tailored advice
Get tailored advice promptly where a SARS notice gives a formal deadline, a final demand, an estimated assessment, an audit or verification request, a large balance, enforcement risk or a matter that could affect more than one tax period. Seek help if you cannot tell whether the concern is operational, substantive, or both.
TaxProof can help organise the chronology, reconcile documents and identify questions for a tax specialist. It cannot decide a SARS dispute or extend a deadline. Use the current SARS correspondence as the controlling document for your case.