SARS Request for Reasons vs Notice of Objection: Which Comes First?

Key takeaways

The two procedures at a glance

This comparison describes the general Tax Administration Act dispute process. Customs and excise disputes are excluded from the ordinary Chapter 9 framework and must be classified under their own legislation. Particular penalty, interest, correction, remission and account workflows may also have a required sequence.

Start with the exact SARS record, not the balance

Download the complete notice and its supporting correspondence. A statement of account or eFiling balance may show what is payable without identifying the objectable assessment, decision or grounds. Build a control sheet with:

• taxpayer or entity name and tax reference number;
• tax type and period or year of assessment;
• notice type, assessment number, case number and transaction identifiers;
• the notice date and available delivery or eFiling history;
• the return, declaration or request to which SARS responded;
• the original amount, SARS's adjustment and the amount the taxpayer says is correct;
• every audit finding, verification outcome, penalty, interest item or other decision in dispute;
• the documents in which SARS says it gave reasons;
• any correction, remission, reasons, objection, condonation, appeal or payment-suspension step already taken; and
• the person authorised to file and verify the receipt.

Read the notice for its dispute wording and channel. Section 104 of the Tax Administration Act governs objections to assessments and specified decisions under a tax Act, but not every communication, account entry, service failure or exercise of power is automatically objectable. A follow-up on a delayed refund, a complaint about service and a correction of the taxpayer's own return are not converted into objections merely by calling them disputes.

The classification should happen before drafting. Otherwise a taxpayer can prepare detailed objection grounds against the wrong record, or use a reasons request when SARS's published process directs the issue to correction, remission, a contact-centre query or another route.

When a Request for Reasons is the right first step

Rule 6 allows an aggrieved taxpayer, before lodging an objection, to ask SARS for the reasons required to formulate that objection. The question is therefore functional: do the existing notice, audit findings, verification correspondence and attachments explain the factual and legal basis well enough to identify the disputed assessment grounds and respond to them?

A reasons request may be justified where, for example:

• the assessment shows an adjustment but the accompanying records do not identify why SARS made it;
• an audit outcome gives a conclusion without enough factual or legal basis to understand the case to answer;
• several items were adjusted and the supplied explanation does not map the reasons to the affected items or amounts;
• SARS says the taxpayer did not discharge an evidential burden but does not identify the material gap sufficiently for objection grounds to be formulated; or
• the current SARS workflow permits a reasons request following a partially allowed or disallowed remission request for an account item.

The request should not ask SARS to advise the taxpayer how to object, disclose every document it holds, reconsider the merits or calculate the taxpayer's case. It should identify the precise assessment or permitted account item, point to the reasons already given, explain why those reasons do not enable a properly framed objection and state what further explanation is required.

Reasons that are brief are not necessarily inadequate

Do not equate length with adequacy. A short notice may incorporate an audit-findings letter or another document that states the basis clearly. Rule 6 allows SARS to notify the taxpayer that adequate reasons have already been provided and to identify the documents containing them. The review must therefore cover the full assessment chain, not only the face of the notice.

Use an issue map before requesting more:

Do not put substantive objection grounds into this map merely to create a longer reasons request. Its purpose is to show the connection between an identified assessment and the explanation needed to formulate the later objection.

When a reasons request is the wrong tool

SARS's current reasons page limits the workflow to specified assessment and account items. It expressly directs correction of an error on an original assessment to the Request for Correction functionality and directs advice requests, service complaints and outstanding-refund follow-ups elsewhere. The current eFiling guide also states that a reasons request must precede the objection and can be made only once for the relevant assessment or account item.

Pause before using Rule 6 where:

• the taxpayer entered information incorrectly and a Request for Correction remains available;
• the issue is a penalty or interest item for which a Request for Remission is the prescribed first step;
• the existing assessment, audit outcome and attachments already give enough reasons to formulate detailed grounds;
• an objection has already been submitted;
• the communication is not an assessment or a decision subject to objection and appeal;
• the issue is an eFiling access problem, service complaint, refund delay or account allocation query;
• the dispute falls under a separate customs or excise process; or
• the taxpayer wants documents rather than reasons and has not identified the correct lawful disclosure process.

A reasons request is not a placeholder for an objection. It is also not proof that SARS accepted the request as valid. Preserve the submitted form or letter, case number, delivery confirmation and SARS response, then keep monitoring the objection position.

The Request for Reasons clock

Under the current dispute-resolution rules, a Rule 6 request must be delivered within 30 business days from the date of assessment. SARS may extend that request period by no more than 45 business days if a SARS official is satisfied that reasonable grounds exist for the delay. A late-request field or application still needs a fact-specific explanation and does not guarantee an extension.

If SARS considers adequate reasons already provided, Rule 6 requires notice within 30 business days after delivery of the request, identifying the documents containing those reasons. If SARS considers that the necessary reasons were not provided, the rule requires reasons within 45 business days. SARS may extend its period for exceptional circumstances, complexity, principle or amount, subject to the rule's notice and limit.

These are procedural rules, not a safe filing calendar for every case. Record:

1. the assessment date and delivery history;
2. the ordinary reasons-request date;
3. any lateness and extension request;
4. the exact request submitted and proof of delivery;
5. whether SARS accepted it as a valid Request for Reasons;
6. any notice identifying earlier reasons;
7. the date reasons or further reasons were delivered; and
8. the recalculated objection date and an earlier internal filing target.

Do not rely on an old article or a tax-type webpage that still displays the former objection period. The March 2023 rules changed the general objection period to 80 business days. The operative notice, current rules, current SARS guidance and actual procedural history must be reconciled for the case.

What a Notice of Objection must do

A Notice of Objection is the formal challenge. Section 104 provides the statutory right to object to an assessment or a decision described in the applicable framework. Rule 7 then prescribes the notice requirements.

The current rule requires the taxpayer to:

• complete the prescribed form in full;
• specify the part or specific amount of the assessment disputed;
• specify which grounds of assessment are disputed;
• set out the grounds of objection in detail;
• submit the documents required to substantiate those grounds that were not previously delivered for the disputed assessment;
• provide the required delivery address and signature; and
• deliver the completed notice through the prescribed channel within the applicable period.

An objection is not complete merely because it says that SARS is wrong or attaches a large file. Each ground should connect five things: the assessed item, SARS's reason, the material fact the taxpayer relies on, the legal basis for the challenge and the exact alteration sought.

The Constitutional Court's 2025 United Manganese judgment describes the objection and appeal framework as the default route for substantive challenges to assessments and records the rule that a later appeal may not introduce a new ground of objection against a part or amount not objected to under Rule 7. The practical lesson is to define the disputed scope accurately at objection stage. It is not a reason to add speculative grounds or challenge unaffected amounts.

The objection clock after a reasons decision

SARS's current objections page and Rule 7 state the general objection period as 80 business days. Without a reasons request, the trigger is the date of assessment or applicable SARS decision. Where a valid Rule 6 request was made, the trigger is linked to delivery of SARS's notice that adequate reasons were already provided or delivery of the requested reasons or further reasons.

Do not calculate the date from the day the taxpayer happens to open an email unless that is the legally relevant delivery event. Do not assume that a saved eFiling draft, ordinary query, complaint, request for correction or invalid reasons request changed the trigger. Use the actual assessment, rule, correspondence, submission receipt and eFiling history.

If the objection is late, section 104 and the rules provide a constrained extension process. SARS's objections page explains that the grounds for lateness must be given and that different tests and outer limits apply. Do not treat condonation as routine. A taxpayer facing a disputed or expired date should obtain advice before submitting a generic explanation or abandoning the underlying merits.

A route decision for common situations

The assessment contains clear itemised reasons

If the complete record identifies the adjustments, facts and legal basis sufficiently, prepare the objection. Do not request reasons merely because the taxpayer disagrees with them. Disagreement is the subject of the Notice of Objection.

The notice shows an unexplained adjustment

Check whether an audit or verification letter supplies the explanation. If the full chain still does not permit detailed objection grounds, prepare a focused Rule 6 request before objecting and preserve the timing evidence.

The taxpayer entered the wrong figure

Check whether the relevant return and tax type allow a Request for Correction. A taxpayer error is not automatically an assessment dispute. If correction is unavailable or SARS has made a separate adjustment, classify the resulting record afresh.

A remission request was partly allowed or disallowed

Follow the current account-item workflow. SARS's 2026 eFiling guide permits a reasons request against qualifying remission outcomes and explains the sequence to objection. Record the specific penalty or interest transaction rather than treating the entire account balance as the disputed item.

An objection has already been filed

Do not attempt to lodge a Rule 6 reasons request afterward. Retrieve the filed objection, its grounds, attachments and receipt. If the grounds are defective, the objection was invalidated or SARS's later case differs materially, obtain procedural advice on the remedies that remain available.

SARS has not responded to the reasons request

Keep the Rule 6 response period, any notified extension and the objection date under active control. Preserve proof of delivery and follow the current SARS channel. Delay does not justify assuming that the objection deadline disappeared, that payment stopped or that a court remedy is immediately available.

The taxpayer needs urgent collection protection

Treat payment and collection as a parallel workstream. Section 164 says that an objection or appeal does not by itself suspend the duty to pay or SARS's recovery powers. A request to suspend payment has separate statutory factors, evidence and status. Neither a reasons request nor an objection receipt is a suspension decision.

Build a controlled sequence file

Keep the reasons request and objection in separate folders inside one dispute file. A simple register should show:

• document name and version;
• date created, issued, received or delivered;
• tax type, period and assessment or case number;
• process type: assessment, correction, remission, reasons, objection, condonation, appeal or suspension;
• sender and recipient;
• eFiling location or prescribed delivery channel;
• submission receipt and case number;
• response date and effect on the next step; and
• reviewer and next action.

For the reasons folder, keep the full assessment chain, the issue map, the final request, proof of delivery, any extension request, SARS's notice and the reasons supplied. For the objection folder, keep the approved grounds, item schedule, calculations, indexed supporting material, completed form, final upload set and receipt.

Do not overwrite the original notice or alter source documents. Redact working copies where appropriate, but keep an access-controlled original. Do not place unredacted taxpayer information in a public article, generic collaboration channel or visual asset.

Draft a focused Request for Reasons

Where the current eFiling workflow applies, use the available Request for Reasons process. For specified manual exceptions, SARS's current page and the August 2024 delivery notice describe a letter route and required channel. Check the latest public notice before sending because delivery details can change.

A controlled draft should identify:

1. the taxpayer and authorised representative;
2. the tax reference number, tax type and period;
3. the assessment, decision, case and transaction identifiers;
4. the assessment date and the request's timing position;
5. the part or amount with which the taxpayer is dissatisfied;
6. the documents reviewed as existing reasons;
7. the specific factual or legal explanation still required;
8. why that explanation is needed to formulate an objection;
9. the address or eFiling profile for delivery; and
10. every attachment and submission receipt.

Avoid accusatory narrative and broad discovery demands. Do not state that there were “no reasons” if an audit or verification letter exists. Describe what was provided and the precise gap.

Move from reasons to objection without losing the issue map

When SARS responds, update each issue rather than starting again. For every disputed part, record:

• SARS's assessment ground, including the later reasons;
• what the taxpayer accepts and disputes;
• the facts and source records supporting the taxpayer's position;
• the legal ground relied on;
• the assessed value, requested value and reconciled difference;
• any material uncertainty or missing evidence; and
• the alteration requested.

If SARS says adequate reasons were already contained in specified documents, review those documents against the issue map. The response may resolve the explanation problem without resolving the merits. If reasons remain arguably inadequate, obtain advice on the procedural options while protecting the objection date. Do not let a dispute about the quality of reasons become an unmonitored substitute for the substantive challenge.

Filing channel and proof matter

SARS's current eFiling guide covers reasons, objections, appeals, condonation and suspension for supported tax types. Public Notice 5114 of 2024 prescribes eFiling for ordinary dispute delivery and an email or branch route for listed exceptions such as estate duty, donations tax, imported services supplied to non-vendors, rejection of a VAT-registration application and specified First Schedule decisions.

The channel is part of validity. Before the deadline:

• confirm that the representative has active authority and the correct tax product access;
• check that the relevant assessment and period appear in the workflow;
• resolve unavailable menu options early and preserve screenshots of genuine errors;
• keep the exact files submitted, not only a folder of intended attachments;
• save the submission confirmation, timestamp and case number; and
• retrieve and store the issued correspondence from the correct eFiling location.

A screenshot of a draft screen is not proof that SARS received a valid request or objection. A case number without the submitted document is not proof of its contents.

Questions to resolve before choosing the route

Ask the taxpayer, representative or adviser:

1. What exact assessment or decision is being challenged?
2. Is it subject to objection and appeal under section 104 and the applicable tax Act?
3. Which tax type, period, part and amount are affected?
4. What is the assessment date and what delivery evidence exists?
5. Which audit, verification, findings or remission documents came before it?
6. What reasons has SARS already provided, and where?
7. Do those reasons identify the factual and legal basis sufficiently to formulate grounds?
8. What precise explanation is still missing?
9. Is correction, remission, a service query or another process the required first step?
10. Has any objection already been filed for the same assessment or item?
11. Was a reasons request made, and was it accepted as valid?
12. What response or notice did SARS deliver and when?
13. What is the documented objection deadline under each possible trigger?
14. Are extension or condonation grounds required?
15. What part or amount will the objection specify?
16. Which source record substantiates each proposed ground?
17. Is payment or collection active, and has a separate suspension request been decided?
18. Who will approve, file and verify the final submission?

When a tax lawyer or specialist review is proportionate

Obtain prompt advice where the assessment date or delivery is disputed; the reasons request or objection may be late; SARS rejected a reasons request; the notice's objectability is uncertain; the adjustment is material; a complex interpretation or valuation is central; fraud, avoidance or understatement penalties are alleged; source records are incomplete; active collection threatens the business; or the dispute may proceed to appeal, alternative dispute resolution, the tax board, tax court or High Court.

A registered tax practitioner may handle many return, calculation and eFiling issues. Legal advice becomes more important where statutory interpretation, procedural validity, contested evidence, privilege, jurisdiction or litigation strategy is central. The roles can be complementary. Confirm the scope, responsible filer, deadline owner and review record in writing.

Related Lexuno resources

• Use the Tax Law hub to place the assessment inside the wider tax process.
• Review the tax lawyer glossary entry when deciding whether legal review is proportionate.
• Check the income-tax glossary for the general framework behind an income-tax assessment.
• Check the VAT glossary where the disputed record concerns value-added tax.
• Build the item and evidence record with the SARS objection document pack.
• Reconcile the sequence and dates with the tax dispute checklist.
• Use the tax attorneys directory where provider selection is required.

FAQs

Related Lexuno paths