Quick answer
Avoid treating every SARS assessment problem as the same objection. The most damaging errors are using a stale generic deadline, challenging the whole assessment without identifying the disputed part, filing grounds that do not answer SARS's reasons, attaching records without explaining what they prove, and assuming that disagreement stops payment or collection.
How to use this guide
Preserve the notice first. Then classify the route, calculate time from the correct trigger, map each proposed ground to an amount and source record, and keep proof of valid delivery. If any of those controls is missing, pause before making an unsupported statement or filing the wrong form.
Mistake 1: starting from a remembered deadline
Do not calculate from the date you happened to open eFiling, the date an adviser forwarded the assessment or an old online article. Record the actual assessment or decision date, the legally relevant delivery event and any later notice concerning reasons. Identify the current rule for the chosen process.
SARS's current objection guidance reflects an 80-business-day objection period, with different starting points depending on whether a valid request for reasons was made and whether adequate reasons were supplied. That does not create an 80-day answer for every SARS communication. Requests for reasons, appeals, requests for material, payments and other actions have their own triggers. Stale pages referring broadly to 30 business days for all objections can produce the wrong calculation.
Mistake 2: assuming an objection is always the next form
An assessment disagreement may involve a correction request, a remission application, a request for reasons, an objection or another procedure. An objection outcome may move the matter to appeal. A complaint deals with service or administration, not necessarily the merits of an assessment. Customs and excise matters are not automatically governed by the ordinary Tax Administration Act dispute rules.
Opening whatever option appears in eFiling does not prove that it is legally available or appropriate. Read the document, identify the decision, tax type and stage, and confirm the prescribed channel. Do not use one process in the hope that it will silently protect another.
Mistake 3: disputing everything in general terms
Avoid statements such as “SARS is wrong” or “all deductions should be allowed.” Identify the precise adjustment, source code, penalty, tax treatment or amount. State the value SARS used, the value requested and the ground supporting the change. Separate accepted, disputed and unresolved items.
The current objection framework requires the disputed part or specific amount, detailed grounds and substantiating documents. A broad narrative can hide the actual issue and make it difficult to tell whether each ground is supported.
Mistake 4: ignoring the reasons SARS has given
Read the assessment, audit outcome and correspondence together. If SARS disallowed an amount because a transaction was not proved, a response about general business hardship does not answer that reason. If the issue is a legal interpretation, a pile of bank statements may not address it.
Where reasons are genuinely inadequate to formulate an objection, consider whether a request for reasons is available. Do not use it automatically, repeat it after an objection to try to gain time, or assume any request changes the objection period. Validity, sequence and the response from SARS matter.
Mistake 5: uploading evidence without an item-to-proof explanation
More pages are not necessarily better evidence. Build an index that identifies each file, date, source and the fact it supports. Reconcile invoices, contracts, ledgers, certificates and bank entries to the return and the disputed assessment line. Keep calculations reproducible.
Do not alter originals, recreate missing documents or remove inconvenient pages. Preserve the source version and explain any later reconstruction honestly. If a record is unavailable, place it on a gap register and assess what can still be proved.
Mistake 6: overlooking penalties, interest and separate remedies
An assessment can contain several decisions. The tax adjustment, understatement penalty, administrative penalty, interest and account balance may not all be challenged through the same grounds or process. Check which component is disputed and whether remission or another remedy applies.
Avoid treating inability to pay as proof that an assessment is wrong. Likewise, do not treat a good merits case as proof that penalties will disappear. Preserve filing history, payment history, notices and the particular facts relied on for each issue.
Mistake 7: assuming the dispute freezes the debt
The Tax Administration Act generally requires payment despite a dispute unless payment is suspended under the applicable process. A request for reasons or an objection does not itself prove suspension. Keep the statement of account, payment date, collection notices and any section 164 application and outcome in a separate control file.
Interest may continue, and a partial suspension or later revocation may have consequences. Check the status rather than describing a submitted request as approved. Do not ignore an undisputed amount merely because another item is contested.
Mistake 8: losing evidence of what was filed
A draft saved in eFiling is not a submission. Preserve the final form, every attachment actually delivered, upload confirmation, case number, recipient, channel and date. Compare the attachment index with the submission receipt and record any system error immediately.
Do not wait passively after filing. Monitor for invalidity notices, requests for supporting material, objection outcomes and revised assessments. An appeal has a separate trigger after the objection decision. A complaint or telephone call should not be assumed to pause that process.
Mistake 9: making outcome or timing promises
No taxpayer or adviser can safely guarantee acceptance, condonation, payment suspension or completion by a fixed date. SARS must apply the legislation and rules to the particular facts. Use a current action calendar and describe uncertainty directly.
A controlled file should end with the next procedural step, its trigger, the person responsible, the evidence still missing and a separate payment action. That is a stronger safeguard than repeatedly rewriting a general explanation.
FAQs
Is using a 30-business-day SARS objection deadline still safe?
Not as a generic current statement. SARS's current objection framework uses 80 business days, but the starting event depends on the assessment and any valid reasons process. Check the current rule and actual trigger.
Can I object to the whole assessment without listing individual errors?
A safe objection identifies the disputed part or amount, the requested result, detailed grounds and substantiating documents. General disagreement does not perform that work.
Is a large SARS upload enough if the evidence is all included?
Not necessarily. Index each record and explain which disputed item and ground it supports. Preserve originals and a reproducible calculation.
What proof should I keep after filing with SARS?
Keep the final form, exact attachment set, upload or delivery confirmation, case reference and any system error record. A saved draft is not proof of submission.
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.