Quick answer
Start with the actual notice of assessment or decision, not a generic tax checklist. Preserve the complete downloadable notice, every annexure and the eFiling message showing when it became available. Add the return or declaration that led to the assessment, SARS's stated reasons, the calculation you say is correct and source records that prove each disputed item.
How to use this guide
The strongest working pack has three layers: a procedural record showing what SARS issued and what you submitted; an item-by-item schedule comparing SARS's position with yours; and transaction evidence supporting the proposed grounds. Keep payment and collection material in a separate section because disagreeing with an assessment does not itself suspend the obligation to pay.
First identify exactly what SARS issued
Record the taxpayer or entity, tax type, tax period, assessment number, issue date, date of delivery or eFiling availability, amount assessed, payment date shown and every case reference. Save the original PDF or electronic record in a read-only folder. Screenshots may help explain what appeared on screen, but they should not replace the source notice.
Then classify the document. It may be an original, additional, reduced or jeopardy assessment, a penalty decision, a request for information or another decision. The correct response is not automatically an objection. Depending on the notice and current rules, a taxpayer may need to consider a correction, remission application, request for reasons, objection, appeal or another process. Customs and excise matters also have their own statutory framework and should not be pushed into the ordinary Tax Administration Act dispute workflow without checking scope.
Build an assessment-to-return comparison
Place the submitted return, declaration or reconciliation beside the assessment. Use a table with one row for each affected line, source code or adjustment. Include the value submitted, SARS's value, the difference, SARS's stated reason, your proposed value and the document that supports it. Separate amounts you accept from those you dispute and from items still being investigated.
This prevents a blanket challenge. Under the current SARS objection framework, the objection should identify the disputed part or specific amount, set out the grounds and include substantiating documents not previously delivered. A large upload does not perform that work by itself. The schedule should explain how each attachment answers the reason for the adjustment.
Preserve reasons and all procedural correspondence
Save every letter, verification request, audit notice, request for relevant material, outcome, revised assessment, case note and eFiling communication in date order. If the existing reasons are not sufficient to formulate an objection, a request for reasons may be relevant. That request is a distinct step, is made before the objection and has its own trigger and timing rules.
Do not assume there is one deadline that applies to every document. SARS's current objections page describes an 80-business-day period under the dispute rules, but the starting event differs depending on whether a valid request for reasons was made and how SARS responded. Other processes use other periods. Read the exact notice, record the delivery date and check the current rule for the route actually being used.
Gather evidence by disputed item
Choose records for what they prove, not because they are common tax documents. An employment-income issue may require IRP5 or IT3 certificates, payslips, employment records and bank entries. A business-income issue may need contracts, invoices, ledgers, delivery evidence, statements and a reconciliation to the return. An expense or input-tax dispute may require more than an invoice: connect the supplier, transaction, business purpose, performance or delivery, accounting entry and payment evidence.
For assets, preserve acquisition and disposal agreements, invoices, valuations where relevant, dates, proof of payment and a reproducible base-cost or allowance schedule. For travel or home-office items, keep the contemporaneous log, floor plans, expense allocation and other records applicable to the particular claim. For penalties or interest, collect the filing and payment history, notices, prior remission decisions and facts relied on, while checking whether the merits and penalty issues use different remedies.
Retain original electronic files where possible. Record who supplied each item, what period it covers and whether it is complete. Never recreate a missing invoice, change an original or present a later summary as if it were contemporaneous proof. A missing-record register is more useful than an unexplained gap.
Make calculations reproducible
Prepare the calculation in a clean spreadsheet or schedule that another person can follow. Identify source data, formulas, assumptions, exchange rates, allocation methods and rounding. Reconcile the result to the return, the assessment and the amount you want substituted. Keep a locked copy of the source data and a dated working version.
If an adviser prepared the original return, obtain the exact working papers and data version used. A new calculation that cannot be reconciled to the filed position can create confusion about whether the dispute concerns a factual error, a legal interpretation or incomplete information.
Keep payment, authority and filing proof separate
Add the statement of account, payment references, collection notices and any payment-arrangement material to a payment folder. If payment suspension is being considered, treat the section 164 request and its outcome as a separate file. A request for reasons or objection is not proof that payment or recovery has been suspended, and interest may continue.
If a representative will act, preserve the appointment or authority records without exposing tax credentials or identity documents more widely than necessary. Finally, keep the exact filed form, attachment index, upload confirmation, case number and delivery proof. A saved draft in eFiling does not establish submission.
A practical handover order
Give the reviewer a one-page cover sheet, the original assessment, the return, the reasons and correspondence chronology, the item-to-proof table, indexed evidence, the calculation, the payment-status file, the missing-record list and proof of prior submissions. That structure lets a tax practitioner decide what is proved, what is still missing and which procedural route requires attention.
FAQs
Which SARS document should anchor my assessment evidence pack?
Use the complete assessment or decision actually issued, including its identifier, tax period, delivery record and annexures. Then compare it with the exact return or declaration submitted.
Must every disputed SARS adjustment have its own proof?
Build one row per disputed item showing SARS's value, your proposed value, the ground and the evidence that supports it. An unsorted document upload does not explain that relationship.
What should I do if SARS's reasons are too limited to prepare grounds?
A request for reasons may be relevant before an objection. Its availability, manner and timing depend on the document and current rules, so preserve the delivery date and check the applicable trigger.
Does my assessment document pack prove that payment is suspended?
No. Dispute steps and payment suspension are separate. Keep the account, collection notices, any section 164 request and SARS's outcome in a distinct payment file.
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.