Quick answer
Organise the file around the assessment's disputed items, not around a loose pile of document types. Keep untouched originals in one controlled location. Create a working copy with a cover sheet, chronology, assessment-to-evidence matrix, tax-period folders, reproducible calculations, correspondence register and separate payment folder. Every attachment should have a short filename and an index entry explaining what it proves.
How to use this guide
The goal is traceability: a reviewer should be able to move from SARS's adjustment to your proposed ground, then to the calculation and source record, without guessing. Document selection is a separate task; organisation begins after you have identified the records that may matter.
Create a read-only original record
Download the full notice of assessment or decision, annexures, submitted return, SARS letters, eFiling messages and every original source file. Save them without renaming or editing their internal content. Where possible, retain native electronic records as well as any PDF used for review. Record who supplied each file and when.
Use an originals folder that is not used for annotations. If a scan is needed, keep the physical original safely and note where it is held. If metadata or an email chain may matter, preserve the original message rather than copying only its text into a new document. Never overwrite a source record with a highlighted version.
Start with one control sheet
The cover sheet should identify the taxpayer, tax type, period, assessment or decision number, issue and delivery dates, amount, payment date, case references and responsible reviewer. Add a route field showing whether the current task is classification, reasons, objection, appeal, remission or another process. A route field marked “not yet confirmed” is safer than an assumed label.
Below it, keep a deadline register. For each date, name the triggering document, delivery evidence, applicable current rule, calculation method, due date and owner. Do not create a single generic “SARS deadline” cell. SARS's current ordinary objection period is expressed as 80 business days, but its start is affected by the reasons process; other steps use other periods and triggers.
Build the assessment-to-evidence matrix
Use one row per adjustment, source code, penalty or disputed amount. Suggested columns are:
- assessment page and line;
- value declared;
- value assessed;
- difference;
- SARS reason;
- accepted, disputed or unresolved status;
- requested value;
- proposed ground;
- calculation reference;
- supporting file and page;
- what that file proves; and
- missing evidence or follow-up.
This matrix is the spine of the file. The current objection framework expects the disputed part or amount, the grounds and substantiating documents. A folder called “invoices” does not show how a particular invoice answers SARS's reason or reconciles to the requested value.
Use a tax-period and issue folder structure
Keep each taxpayer, tax type and period separate. Within the active period, use folders such as 01Assessment, 02Returnasfiled, 03SARSreasons, 04Issuematrix, 05Sourceevidence, 06Calculations, 07Correspondence, 08Filingsandreceipts and 09Paymentstatus. If there are several disputed issues, create subfolders that use the same issue numbers as the matrix.
Avoid organising only by sender, such as “from accountant” or “from SARS.” That can scatter one transaction across multiple places. Also avoid mixing personal-income, VAT, payroll or company-income periods merely because a document appears relevant to more than one. Use a controlled cross-reference instead of duplicating or silently moving the original.
Name and index each source file
A concise convention might include the issue number, date, counterparty and document type: I032025-02-14SupplierAinvoice.pdf. Do not put conclusions such as “proof SARS is wrong” into filenames. Record the file's source, date range, page count and integrity note in the index.
For compound evidence, show the chain. An expense may involve a contract, invoice, delivery record, ledger entry and bank payment. Link all five to the same matrix row and state the distinct fact proved by each. If an item contains confidential information unrelated to the issue, obtain advice before redacting it; preserve an unaltered original and identify any review copy as redacted.
Keep calculations transparent and versioned
Store raw source data separately from working calculations. A calculation cover note should identify the input files, formulas, allocation method, assumptions, rates and the result requested. Reconcile the total to the return and assessment. Protect formula cells where useful, but do not create a locked workbook that the reviewer cannot inspect.
Use dated version names and a short change log. Do not circulate several files called final, final2 and finalrevised. Once a filing version is approved, freeze an exact copy beside its attachment bundle so later working changes do not alter the record of what SARS received.
Separate procedural, payment and authority records
Keep all SARS communications in chronological order with sender, recipient, channel, date and case reference. Store the final form, attachment manifest, successful submission confirmation and any system-error evidence together. An eFiling draft belongs in working papers, not the filed record.
Keep statements of account, payment references, collection notices and any section 164 suspension request and outcome in the payment folder. The merits file should not imply that payment is suspended. Store representative authority securely and avoid placing tax credentials or unnecessary identity documents in a broadly shared evidence bundle.
Run a pre-filing integrity check
Compare the attachment manifest with the matrix. Check that page references open, periods match, totals reconcile and every proposed ground has evidence or an explicitly recorded gap. Remove accidental duplicates but keep different versions where their difference matters. Confirm file sizes and permitted delivery channel under the current SARS process.
After submission, save the exact bundle and receipt as an immutable snapshot. Continue the chronology with later SARS requests, outcomes and revised assessments. Good organisation is not a promise of success; it makes the evidence, omissions and procedural history capable of being reviewed.
FAQs
Should I organise SARS records by document type or disputed issue?
Use the disputed issue as the main organising key, while preserving originals by taxpayer, tax type and period. Cross-reference each source record through an assessment-to-evidence matrix.
How should I preserve original SARS source documents?
Keep an untouched read-only copy of each original file and use separate annotated working copies. Record the source and date, and never overwrite an original with highlights or redactions.
What should a SARS evidence index say about each file?
Record its filename, source, date range, pages, related assessment line and the fact it is offered to prove. Note any integrity issue or missing part directly.
How do I prove which attachments were actually filed with SARS?
Freeze the final form and exact attachment bundle, then keep the manifest, upload or delivery receipt, case number and any error evidence together as one submission snapshot.
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.