Tax Knowledge Centre

Introduction

Condonation is one of the most important procedural gateways in South African tax dispute resolution. It is commonly used to describe SARS's power to extend the time period within which a taxpayer may lodge an objection. If an objection is not lodged in time, and no valid extension is granted, the assessment or decision may become final and the taxpayer may be shut out of the objection-and-appeal process.

Practitioners therefore need to understand two issues clearly. The first is the legal framework governing condonation. The second is what to do when SARS refuses condonation, particularly where SARS fails to provide proper reasons. A refusal is not necessarily the end of the matter. Properly analysed, it may itself be challengeable.

The legal framework

The starting point is section 104 of the Tax Administration Act 28 of 2011 (TAA), read with the dispute resolution rules and SARS Interpretation Note 15 dealing with the extension of time to lodge an objection or appeal.

Section 104(1) gives a taxpayer the right to object to an assessment or decision that is subject to objection and appeal. That right, however, must be exercised in the prescribed manner and within the prescribed time period.

Section 104(4) gives a senior SARS official the power to extend the period for lodging an objection:

• by up to 30 business days if reasonable grounds exist for the delay; or
• by more than 30 business days if exceptional circumstances exist that gave rise to the delay.

This discretion is limited by section 104(5), which prohibits an extension:

• beyond three years from the date of the assessment or decision; and
• where the objection is based wholly or mainly on a change in a practice generally prevailing at the relevant time.

These limits are crucial. Once the three-year period has expired, the issue is generally no longer one of discretion. The matter is then barred by law unless SARS has simply miscalculated the applicable time period.

When is an objection late?

The rules generally require an objection to be delivered within 80 business days from the date of assessment. Where reasons were requested under the rules, the period is calculated from the delivery of those reasons or from the notice that adequate reasons had already been provided.

For these purposes, "day" means a business day. Saturdays, Sundays, public holidays, and the period from 16 December to 15 January are excluded. Practitioners who miscalculate this period often create avoidable disputes.

In practical terms, a delay of up to 30 business days beyond the original 80-business-day period usually falls to be considered under the "reasonable grounds" test. A longer delay generally requires "exceptional circumstances", subject always to the three-year outer limit.

Reasonable grounds and exceptional circumstances

The distinction between reasonable grounds and exceptional circumstances is fundamental.

Reasonable grounds generally involve circumstances beyond the taxpayer's control that explain the delay. Illness, absence from the country, delay in obtaining material documents, or similar practical impediments may qualify, depending on the facts.

Exceptional circumstances impose a higher threshold. They are not exhaustively defined, but may include severe illness, serious disruption in services, disaster, or other unusual events that genuinely caused the delay. The mere existence of a difficulty is not enough. The taxpayer must show that it actually caused the objection to be late.

That causation requirement is central. Condonation is not obtained by general explanation or sympathy. It must be supported by a chronology, documentation, and a clear link between the event relied upon and the delay itself.

Late objection versus invalid objection

A recurring problem in practice is the failure to distinguish between a late objection and an invalid objection.

A late objection is one delivered outside the prescribed time period.

An invalid objection, by contrast, may have been delivered on time but fails to comply with the rules. This may happen where the objection does not properly identify the disputed amount, does not set out sufficient grounds, or fails to include required supporting material.

The distinction matters because the consequences differ. An invalid objection lodged within time may sometimes be corrected and resubmitted within the period allowed by the rules. But once that opportunity is lost, the taxpayer may require condonation for the new objection. Practitioners must therefore treat formal compliance as part of the gateway to the merits, not as a technical afterthought.

What SARS expects in a condonation application

A proper condonation application should do more than ask for indulgence. It should:

• calculate the correct due date;
• explain the delay chronologically;
• attach supporting proof;
• show why the circumstance relied on caused the delay;
• explain the length of the delay; and
• briefly indicate that the objection has prospects of success.

Prospects of success are relevant, but they do not replace the need for an adequate explanation. Strong merits will not necessarily save a poorly motivated condonation application, and a good explanation will not rescue a hopeless objection.

What happens when SARS refuses condonation?

Many taxpayers treat a refusal of condonation as the end of the road. That is often wrong.

A refusal of condonation is itself a decision and must be approached as such. The first step is to identify what kind of refusal SARS has made.

The first possibility is a discretionary refusal. In that case SARS has considered the taxpayer's explanation and decided that the requirements for extension have not been met.

The second possibility is a refusal by operation of law, typically because the three-year limit has expired. In that case SARS has no discretion. The only real issue is whether SARS is legally and factually correct, for example in its calculation of the relevant period.

Where SARS has exercised a discretion, the practitioner should not merely repeat the original condonation request. The proper question becomes whether SARS exercised its discretion lawfully, rationally, and on the correct facts.

The importance of reasons

A critical question in every refusal case is whether SARS has provided adequate reasons.

A refusal of condonation is administrative action and must comply with the requirements of lawful, reasonable, and procedurally fair decision-making. If SARS simply states that condonation is refused, without explaining why, that creates an immediate difficulty.

Without reasons, the taxpayer does not know whether SARS considered the evidence, applied the correct legal standard, misunderstood the chronology, or ignored relevant material altogether. A refusal without reasons is therefore not merely unhelpful. It is often procedurally defective and vulnerable to challenge.

In practice, the absence of reasons may become one of the strongest available grounds of attack.

How practitioners should respond

The first mistake is to re-argue the original condonation application. That rarely resolves the issue. The better approach is to challenge the refusal as a decision.

The issue is no longer simply whether the taxpayer had a good reason for the delay. It is whether SARS made a lawful decision.

Depending on the facts, the challenge may be based on one or more of the following:

• failure to provide adequate reasons;
• failure to consider relevant evidence;
• application of the wrong legal test;
• reliance on irrelevant factors; or
• irrational or arbitrary decision-making.

Where SARS has not given proper reasons, it is also prudent to request them formally. This may clarify the basis of refusal, and if SARS still fails to respond adequately, it strengthens the taxpayer's position in any later challenge.

A refusal of condonation may itself be taken on objection. If SARS disallows that objection, the matter may be escalated to the Tax Board or Tax Court, depending on the case. In appropriate circumstances, administrative-law review may also be considered where the refusal is procedurally unfair, irrational, or unsupported by reasons.

Finality and legality

Tax administration requires finality. Time limits exist for good reason, and condonation is not intended to undermine the orderly resolution of disputes. That is why the statutory framework is strict and why poorly motivated applications fail.

However, finality does not excuse unlawful decision-making. SARS is entitled to insist on compliance with the rules, but it must still act lawfully, rationally, and fairly. A refusal based on no reasons, wrong reasons, or ignored evidence is not saved merely by the principle of finality.

Conclusion

Condonation is a critical procedural safeguard in tax dispute resolution. Practitioners must understand the time limits, the distinction between reasonable grounds and exceptional circumstances, and the difference between a late objection and an invalid one.

Equally important is understanding how to deal with refusal. A refusal of condonation is not necessarily the end of the dispute. It may itself be challengeable, especially where SARS fails to provide adequate reasons. The practical lesson is clear: success in condonation matters does not lie in asking SARS for sympathy. It lies in correct time computation, disciplined preparation, proper evidence, and, where necessary, a focused challenge to the legality of SARS's decision.

The use by SARS of AA88 third-party appointments remains one of the more invasive debt-collection mechanisms encountered in practice. Although many practitioners first encounter these appointments in the payroll environment through e@syFile Employer, the legal basis for the process lies in section 179 of the Tax Administration Act 28 of 2011 (TAA). That distinction is important. What appears administratively to be a payroll instruction is, in law, a statutory recovery step with defined preconditions and significant consequences.

In practice, the AA88 process often creates tension between operational efficiency and procedural fairness. Employers are required to act quickly, yet they usually do not have access to the underlying tax documents or communications necessary to verify whether the appointment is legally and factually justified. Taxpayers, in turn, may find that deductions commence before they have a meaningful opportunity to test the underlying debt or SARS's compliance with the statutory safeguards.

This article considers the legal framework of AA88 appointments, the safeguards contained in section 179, and the practical problems that arise when the appointment is implemented through employer systems.

What is an AA88 appointment?

An AA88 is commonly described as a Third Party Appointment Notification issued by SARS to a person who holds or owes money to a taxpayer. In the employment context, SARS appoints the employer to withhold and pay over amounts from the employee's remuneration in satisfaction of an alleged tax debt.

From an operational perspective, the instruction is often delivered and managed through e@syFile Employer. The employer is expected to deduct the stated amount and pay it to SARS by the due date. If the employer cannot comply, the employer must communicate that position through the relevant response process.

The fact that the appointment is processed through a payroll system should not obscure its legal nature. It is not merely an administrative payroll instruction; it is an exercise of a statutory debt-collection power under the TAA.

The statutory foundation: section 179 of the TAA

Section 179 empowers SARS to require a third party to pay money to SARS where that third party holds or owes money to the taxpayer. In payroll situations, this power translates into the appointment of the employer to deduct from salary or wages.

However, section 179 is not an unrestricted collection tool. It contains important safeguards aimed at balancing SARS's collection powers with procedural fairness to the taxpayer. Chief among these is the requirement in section 179(5) that SARS may only issue a third-party appointment after delivering a compliant final demand to the taxpayer at least 10 business days before issuing the notice.

This safeguard is central to the fairness of the process. It gives the taxpayer notice of the debt, notice of the intended recovery steps, and an opportunity to consider the mechanisms available for debt relief or engagement with SARS before a third party is instructed to intercept funds.

The importance of the section 179(5) final demand

Section 179(5) is not a trivial procedural step. It is a material statutory protection. The final demand must be delivered to the taxpayer and must contain the prescribed information, including the recovery steps SARS may take and the debt-relief options available to the taxpayer. These mechanisms include arrangements that may relate to hardship, including the taxpayer's ability to maintain basic living expenses.

In practice, one of the most contentious issues is whether SARS can prove that this final demand was in fact delivered. This issue has become particularly important where disputes arise over what was, or was not, reflected on the taxpayer's eFiling profile, or whether the taxpayer had actual access to the communication allegedly relied upon by SARS.

This difficulty becomes even more pronounced in the AA88 context. The third-party appointment is issued to the employer, but the employer has no access to the taxpayer's eFiling correspondence. As a result, the employer cannot verify whether SARS complied with section 179(5), yet is expected to implement deductions immediately.

This creates a practical and legal dilemma. The employer is required to act on a statutory instruction without being able to confirm whether one of the most important procedural safeguards in the TAA has been satisfied.

The exception in section 179(6)

Section 179(6) creates an exception to the prior final-demand requirement. SARS may dispense with the requirement if a senior SARS official is satisfied that giving the final demand would prejudice the collection of the tax debt.

While this exception may be necessary in appropriate circumstances, it introduces another layer of uncertainty for employers and taxpayers. When an AA88 is received by an employer, the employer generally has no way of knowing whether SARS first delivered the section 179(5) final demand or whether SARS instead relies on section 179(6). If SARS relies on section 179(6), the employer likewise has no means of verifying whether the decision was taken by the requisite senior official or whether the statutory threshold for prejudice to collection was properly met.

The result is a lack of transparency. The person compelled to deduct and pay over funds is unable to determine whether the legal preconditions for the appointment have been met.

The proof-of-debt problem

A further practical weakness in the AA88 system is that the employer is usually not given access to the documents that establish the alleged debt. The appointment assumes that the employer must deduct and pay over funds, yet the employer will generally not have access to:

• the assessment or assessments on which the tax debt is based; or
• the statement of account showing the outstanding balance and the allocation of payments.

This is a serious defect from an administrative-justice perspective. An employer may be required to interfere with an employee's salary without being given the foundational documents necessary to verify the debt. In many cases, the employer is simply expected to trust the instruction without any visibility into whether the debt is correctly stated, whether payments have already been made, whether allocations have been done properly, or whether the balance is based on outdated or incorrect SARS records.

Practitioners will recognise that these are not remote possibilities. Tax disputes often arise because SARS statements of account do not accurately reflect the true position, because payments have been misallocated, because assessments are under dispute, or because historical balances have not been corrected.

Where this occurs, the risk is that deductions are made on a debt that is not properly established or is no longer payable in the amount asserted.

Compliance pressure on employers

The employer's position is further complicated by the compliance consequences of failing to act. SARS guidance has historically indicated that a third party who fails to comply with an appointment may face personal liability and possible offence consequences. The consolidated TAA also contains offence provisions addressing wilful or negligent failure to comply with sections 179 to 182 after notice by SARS.

The practical effect is that the employer is placed under considerable pressure. If the employer deducts and pays over the amount, it may be acting on an instruction whose legal basis cannot be independently verified. If the employer refuses or delays, it may face adverse consequences for non-compliance.

This is one of the structural tensions inherent in the AA88 process. The employer is exposed to legal risk, but lacks the information necessary to assess the validity of the instruction with confidence.

Inability to comply: a common payroll reality

In many cases, an employer may simply be unable to comply fully with an AA88 appointment. The employee may have left employment. The remuneration may be insufficient. The employer may not hold or owe the full amount contemplated in the notice. Alternatively, the payroll position may be such that only part of the amount can be deducted.

These are commonplace realities in payroll administration. Section 179 does not operate in a vacuum and cannot compel payment of amounts that are not held or owed. Where compliance is not possible, the employer must respond appropriately and place the relevant facts before SARS through the prescribed e@syFile process.

This is an important practical point. Employers should not assume that receipt of an AA88 automatically means that full compliance is always possible. Equally, they should not ignore the notice. A structured response is necessary where compliance is impossible or only partially possible.

The risk of unlawful or unjustified deductions

The combination of limited visibility and immediate compliance pressure creates a real risk of unlawful or unjustified deductions. This may occur where:

• the underlying debt is incorrect;
• payments have already been made but not properly allocated;
• the balance relied upon by SARS is outdated;
• an assessment has been challenged or suspended; or
• the statutory prerequisites for the appointment have not been met.

Where deductions are made in such circumstances, the prejudice to the taxpayer can be immediate and significant. Salary is attached before the underlying dispute is resolved, and the taxpayer may then be forced into a reactive process to obtain supporting documentation, challenge the appointment, and seek reversal or refund of amounts collected.

This is one reason why practitioners should approach AA88 appointments with care. The fact that an instruction has been issued through an official SARS process does not mean that it is immune from challenge.

A practical response framework

Where an AA88 is issued, a careful and structured response is required. From a practical perspective, the following steps are usually relevant.

The first is to require SARS to substantiate the debt by providing the relevant assessment or assessments, the statement of account, and confirmation of the authority of the SARS official who issued the appointment. Without these documents, the factual and legal basis for the instruction remains uncertain.

The second is to consider whether SARS complied with section 179(5). If there was no compliant final demand delivered to the taxpayer at least 10 business days before the appointment, this should be raised directly and the validity of the appointment should be challenged.

The third is to respond promptly where the employer cannot comply, whether because the employee has left employment, insufficient funds are available, or the employer does not owe or hold the amount contemplated.

The fourth is to challenge deductions that have already occurred where the debt is not substantiated or the withholding appears unjustified. In such cases, corrective action, including reversal or refund, may need to be demanded.

The structural problem in the AA88 system

The deeper issue is that the AA88 system, particularly as implemented through employer platforms, is structurally skewed in favour of collection efficiency. The employer is required to act quickly and faces consequences for non-compliance, yet is not given the means to verify whether SARS has complied with the procedural safeguards in the TAA or whether the debt is correctly reflected.

The employer does not have access to the taxpayer's eFiling notices and cannot test delivery of the section 179(5) final demand. The employer also usually does not have the assessments or statement of account necessary to confirm the debt. The taxpayer, meanwhile, may suffer deductions before the statutory safeguards have been properly interrogated.

This is not merely an administrative inconvenience. It raises important questions of legality, procedural fairness, and proportionality in the implementation of SARS's collection powers.

Conclusion

AA88 third-party appointments are powerful collection mechanisms, but they are not beyond legal scrutiny. Section 179 of the TAA contains safeguards that must be respected. SARS may have a strong interest in efficient recovery of tax debts, but that efficiency must operate within the statutory framework.

For practitioners, the key lesson is that an AA88 must be approached as a legal process, not simply as a payroll instruction. The validity of the underlying debt, proof of the assessments, delivery of the final demand under section 179(5), and the possible application of section 179(6) all require careful consideration.

For employers, the challenge is equally significant. They are often expected to act under legal pressure while lacking access to the information needed to verify the appointment. That imbalance is at the heart of many disputes involving AA88 deductions.

The prudent approach is therefore one of structured engagement: insist on substantiation, test compliance with the statutory safeguards, respond promptly where compliance is impossible, and challenge deductions where the legal basis for the appointment is defective. In the AA88 environment, both taxpayers and employers need to remember that administrative delivery through e@syFile does not displace the rule of law.

Tax practitioners are increasingly encountering situations where SARS requests bank statements shortly after the submission of a tax return. On the surface, these requests are often labelled as "verifications." However, in the field, there is growing concern that SARS is using these seemingly routine requests as an entry point to conduct audits — without following the correct legal procedures required under the Tax Administration Act (TAA).

Understanding the Legal Distinction

A critical starting point is to recognise that the TAA does not contain a formal definition of either "verification" or "audit." Instead, SARS operationalises these terms through practice notes and administrative conduct.

Based on SARS's own guides and interpretation:

• A verification is understood as a basic check of a taxpayer's return against third-party data or supporting documentation. It is administrative in nature and usually occurs shortly after a return is filed.
• An audit, by contrast, is a more in-depth inquiry that involves the examination of books, records, and underlying transactions to determine the accuracy of the return or the taxpayer's compliance with tax laws.

Critically, Section 42 of the TAA lays out the procedural obligations for audits, which include:

• A notice of commencement of the audit;
• Progress reports throughout the process; and
• A letter of audit findings before finalisation.

If these steps are not followed, the audit may be procedurally defective.

This distinction has been tested in case law such as Forge Packaging (Pty) Ltd v Commissioner for SARS, where the court ruled that SARS had not initiated an audit because it failed to follow the procedural requirements under Section 42 — even though the information requested was extensive.

My Professional View: When Does a Verification Become an Audit?

Based on experience in the field, I am of the opinion that the complexity of the bank statement and the depth of SARS's engagement with the data are what determine whether the process remains a verification or becomes an audit.

When It Is a Verification

• The bank statement is simple, with limited transactions.
• SARS does not interrogate individual transactions.
• SARS does not request general ledgers or supporting documents.
• No additional correspondence or inquiries are made beyond the initial submission.

In such cases, the process falls within the realm of a verification.

When It Becomes an Audit

However, when the bank statement is complex, the situation changes:

• SARS cannot properly assess tax compliance without further documents — specifically the general ledger, which is necessary to interpret the transactions.
• If the taxpayer is part of a group of companies, SARS would logically need all related bank statements across the group, and general ledgers showing intercompany entries and reconciliations.

Furthermore, if SARS begins to:

• Interrogate the bank data (e.g., asking detailed questions or requesting source documents for individual transactions),
• Run the data through internal analytical systems, or
• Augment the data with information from third parties or other tax years,

then SARS is no longer verifying — it is auditing, in substance if not in name. This escalation triggers the procedural requirements of Section 42, and SARS cannot avoid those obligations by continuing to call the process a "verification."

What Happens in Practice: Procedural Breaches

On the ground, practitioners are finding that SARS often begins with a verification request — such as for 3–6 months of bank statements — and then quietly expands the scope into a full audit without:

• Issuing a formal audit notice;
• Providing progress reports; or
• Issuing a letter of findings.

In many instances, SARS:

• Rejects objections or verifications even where supporting documents are provided;
• Demands explanations for every bank transaction;
• Requests general ledgers, trial balances, or supporting contracts;
• And electronically processes or interrogates the data.

Yet these cases remain labelled as "verifications," despite clearly meeting the threshold of an audit. This conduct is problematic and potentially challengeable in law. SARS cannot ignore its statutory duties simply by calling an audit a verification.

Why This Matters

The distinction between a verification and an audit is not academic — it carries significant legal and practical implications:

• Taxpayers subjected to audits have a right to transparency, including audit notifications and findings, which can be critical for objections or litigation.
• Failure by SARS to comply with Section 42 can render the process procedurally unfair and provide grounds for a legal challenge or Tax Ombud complaint.
• Practitioners must be alert to signs of escalation and challenge SARS where due process is ignored.

Conclusion

The simple act of requesting a bank statement may start as a verification, but if the data is complex, or if SARS begins to interrogate or augment that data, it becomes an audit in everything but name.

In these cases, SARS must issue a formal audit notice and follow the procedures set out in the Tax Administration Act. Where this does not happen, taxpayers and practitioners should assert their rights and, where necessary, demand that SARS reclassify the process and comply with the law.

This issue is not theoretical. It is unfolding in the field, daily. As practitioners, we must hold SARS accountable to the law and ensure our clients are afforded the procedural fairness that the TAA requires.

In South African tax administration, the right to object and appeal is one of the taxpayer's most important protections. That right, however, only works properly if the taxpayer can understand what SARS decided, why it decided it, and how it arrived at the amount or conclusion in question. Where SARS provides no reasons, vague reasons, or formulaic reasons, the taxpayer is often forced to object "in the dark". That is not merely inconvenient. It can undermine the fairness of the entire dispute process.

The importance of reasons is therefore not procedural trivia. It goes to the heart of whether a taxpayer can formulate a proper objection, determine whether the objection is timeous, and assess whether further remedies are available. In practice, poor reasons from SARS are one of the most common causes of unnecessary dispute, delay, and prejudice.

Why reasons matter in the tax dispute process

A taxpayer cannot object effectively unless the real basis of the assessment or decision is known. It is not enough for SARS simply to communicate an outcome. A proper objection requires the taxpayer to identify the factual issue in dispute, the legal rule relied upon, and the respect in which SARS is alleged to have erred. If those matters are unclear, the taxpayer is placed at an immediate disadvantage.

This is particularly important because an objection must be detailed and specific. A bare denial is not enough. The taxpayer must engage with the actual grounds of assessment or decision. If SARS has not explained those grounds properly, the taxpayer's objection may become speculative, incomplete, or too general. That, in turn, may expose the objection to disallowance or procedural attack.

Reasons also matter because dispute time periods are affected by them. Under the dispute framework, the date from which the objection period runs may depend on whether reasons were requested and when they were provided. This means that inadequate or disputed reasons are not only relevant to the merits. They can also affect whether SARS later alleges that the objection was out of time.

The legal framework

The duty to provide meaningful reasons does not arise from one source alone. It sits at the intersection of the Tax Administration Act 28 of 2011, the dispute resolution rules, SARS guidance, and broader administrative-law principles.

The TAA establishes the formal structure for assessments, objections, appeals, and certain procedural decisions. The dispute rules then provide the machinery through which a taxpayer may request reasons where the basis of an assessment or decision is not apparent. These rules are critical because they recognise a practical reality: a taxpayer cannot be expected to formulate a proper objection where the assessment or decision is not properly intelligible.

Interpretation Note 15 is also important because it explains how the timing of objections and appeals may be influenced by requests for reasons and the delivery of reasons. It further addresses SARS's discretion to extend time periods in appropriate cases. Although an interpretation note does not have the force of legislation, it is important in practice because it reveals how SARS approaches the issue and how timelines are intended to operate administratively.

Over and above this lies the broader principle of just administrative action. SARS is a public authority exercising statutory power. Its decisions must therefore be lawful, reasonable, and procedurally fair. Fairness includes the giving of intelligible and responsive reasons, especially where the decision has a direct impact on a taxpayer's rights. In this sense, adequate reasons are not merely a matter of convenience. They are part of the procedural fairness that must accompany the exercise of public power.

What counts as "adequate reasons"?

The real issue is not whether SARS has sent some response, but whether the response is good enough to enable the taxpayer to understand the case that must be met. That is the true standard.

Adequate reasons should ordinarily disclose at least four things. First, they should identify the material facts on which SARS relies. Second, they should identify the legal basis for the conclusion reached. Third, they should explain the methodology or calculation used, where an amount has been adjusted or imposed. Fourth, they should show the connection between the facts and the conclusion. Unless these features are present, the taxpayer may still not know what SARS is actually saying.

This is where many SARS communications fall short. In practice, the problem is often not complete silence, but rather reasons that are vague, generic, or non-responsive. A response is unlikely to be adequate where SARS merely states a conclusion without explaining the factual basis for it. It is also inadequate where SARS recites sections of legislation in the abstract but does not explain how those provisions apply to the taxpayer's specific facts. Equally problematic is the situation where SARS provides information that is broadly related to the matter, but does not actually answer the question raised by the taxpayer.

A formulaic response does not become adequate merely because it is dressed in official language. If the taxpayer still cannot identify the factual dispute, the legal premise, or the basis of the computation, the reasons remain deficient.

The importance of issue-specific reasons

One of the key principles emerging from the authorities is that reasons must be responsive to the issue actually raised. This is a critical practical point. A taxpayer may ask why a deduction was denied, why an objection was treated as invalid, or why an extension of time was refused. If SARS replies in broad and general language without addressing the specific complaint, the taxpayer has still not been given proper reasons.

The law is concerned with substance, not form. Calling something "reasons" does not make it adequate. The question is whether the taxpayer now knows enough to formulate a meaningful response. If the answer is no, the requirement has not truly been met.

Reasons are important beyond assessments

The problem does not arise only with substantive assessments. It also arises in a range of procedural decisions that can materially affect a taxpayer's rights.

A common example is a refusal to extend the time for lodging an objection or an appeal. Such a refusal can be decisive because it may shut the taxpayer out of the dispute system altogether. For that reason, the refusal must be supported by proper reasons. If SARS simply states that the request is refused, without explaining the basis upon which its discretion was exercised, the taxpayer may be unable to challenge the refusal meaningfully.

Another example is where SARS treats an objection as invalid. In that situation, SARS must communicate the grounds of invalidity clearly enough to enable the taxpayer to correct the problem if it can be corrected. A vague statement such as "non-compliant" or "does not meet the rules" is often not enough. Without proper particulars, the taxpayer is denied a fair opportunity to cure the defect.

In this way, the adequacy of reasons affects the entire dispute chain, not merely the first assessment.

Why inadequate reasons are so prejudicial

Poor reasons create prejudice at several levels. First, they impair the taxpayer's ability to prepare a focused objection supported by appropriate documents and legal argument. Second, they create uncertainty around time limits, particularly where the running of the objection period depends on the delivery of reasons. Third, they may undermine an application for condonation or extension, because the taxpayer may struggle to demonstrate prospects of success if the true basis of SARS's case is still unclear.

This is especially serious in South African tax practice, where procedural deadlines are strictly applied and where SARS often places heavy emphasis on formal compliance with the rules. It is unjust for SARS to expect precision from taxpayers while itself providing reasons that are imprecise, generic, or evasive.

What should taxpayers do in practice?

Where an assessment or decision is unclear, the first step is to request reasons promptly under the dispute rules and retain proof of delivery. Dates, case numbers, screenshots, correspondence logs, and acknowledgements should all be preserved carefully. Good recordkeeping is essential because disputes about reasons often become disputes about timing as well.

The second step is to assess the response critically. The taxpayer or practitioner should ask: does this response explain the facts relied on, the legal basis, the method of calculation, and the link between the facts and the conclusion? If not, SARS should be told clearly and specifically why the reasons are inadequate.

The third step is to avoid accepting labels at face value. A communication from SARS may be styled as reasons, but that does not settle the matter. The practical question is whether it truly enables a proper objection or response.

The fourth step is to consider what procedural remedy is appropriate if SARS persists in giving poor reasons. Depending on the circumstances, this may include challenging a related procedural decision, raising the inadequacy directly in the objection process, or relying on broader fairness principles where the taxpayer has been prejudiced.

At the same time, taxpayers must be careful not to assume that delay will always be excused simply because SARS's conduct has been poor. Time periods should be monitored rigorously, and a protective approach should be adopted where there is any uncertainty.

Conclusion

Adequate reasons are not a courtesy. They are a procedural necessity. Without them, the taxpayer cannot understand the assessment or decision, cannot formulate proper grounds of objection, and may be unfairly prejudiced in relation to deadlines and condonation. The real question is not whether SARS provided some form of response, but whether SARS provided reasons that genuinely explain the decision in a way that enables the taxpayer to exercise dispute rights effectively.

For tax practitioners, this is the critical practical point: whenever SARS gives vague, generic, or non-responsive reasons, the issue should be confronted directly and methodically. The fairness of the dispute process depends on it.

Introduction

SARS is increasingly issuing verification letters requesting "relevant material" and warning taxpayers that, if the material is not submitted, SARS may raise an estimated assessment under section 95(1)(c) of the Tax Administration Act.

This warning is serious. In VAT matters, SARS may reverse input tax. In income tax matters, SARS may disallow deductions or estimate taxable income. The result can be a substantial assessment, even where the underlying transaction is genuine and the taxpayer can ultimately prove the claim.

The issue is not whether SARS may request documents. SARS clearly has that power. The issue is whether SARS may rely on section 95(1)(c) where the request is vague, excessive, impractical, not properly received, or where SARS treats a minor defect as a basis for reversing the claim.

In my view, this is where the process may become procedurally unfair and, in appropriate cases, unlawful.

What section 95(1)(c) does

Section 95(1)(c) permits SARS to raise an assessment based on an estimate where the taxpayer does not respond to a request for relevant material under section 46 after more than one request has been delivered.

This power must be used carefully. Section 95(1)(c) is not a penalty provision. It is an estimating mechanism. SARS may use it where it cannot finalise the assessment because the taxpayer has failed to provide material that SARS properly required.

That does not mean SARS can make any request, however wide, and then raise an estimated assessment if the taxpayer does not comply perfectly. SARS must still act lawfully, reasonably and procedurally fairly. The estimate must also be rational and based on information available to SARS.

The purpose of relevant material in a verification

The key phrase is "relevant material". In a verification, SARS should be checking a specific item, claim, amount or risk in the return. Relevant material is material that helps SARS verify that specific issue.

A verification is not supposed to be an open-ended inspection of the taxpayer's entire accounting system. If SARS wants to verify VAT inputs, it may ask for selected invoices and proof of payment. If SARS wants to verify expenses, it should identify the expense category or claim. If SARS wants to verify turnover, it should identify the information needed to test turnover.

A proper request should therefore identify: what SARS is verifying; which documents are required; why those documents are relevant; how they must be submitted; and a reasonable time for compliance. If the taxpayer is left guessing what SARS wants, the request is defective.

VAT, sole proprietors and professional practices

The practical problem differs depending on the tax type and the taxpayer.

In VAT verifications, SARS does not necessarily request all input tax invoices. It often asks for a selection of the larger or higher-risk input invoices, together with proof of payment and supporting documents. That can be a legitimate verification process if the request is targeted and proportionate.

The problem arises where SARS reverses input tax mechanically because a selected invoice was not uploaded in time, was only partially provided, or contains a minor or curable defect. A vendor may have made a genuine taxable supply, paid the supplier, and hold records proving the transaction. In those circumstances, SARS should not treat a late upload, partial response or technical invoice defect as automatic proof that the input tax does not exist.

SARS should identify the defect, explain why it is material, and allow the taxpayer a fair opportunity to correct or explain it where possible.

In the case of sole proprietors and professional practices, the verification can be even more burdensome. SARS may request extensive documents relating to income, expenses, bank deposits, vouchers, proof of payment and supporting schedules. Depending on the wording and scope of the request, SARS may effectively be asking for the full accounting record of the practice.

That may no longer be a simple verification. It may be an audit in substance. A professional practice may have hundreds or thousands of transactions, client deposits, recoveries, disbursements, mixed business and personal payments, and several expense categories. A request for substantially all vouchers and supporting documents can therefore be extremely onerous.

The key point is that SARS must identify what it is verifying. A targeted request for selected VAT invoices may remain a verification. A broad request for substantially all records of a sole proprietor or professional practice may cross the line into audit. SARS should not use section 95(1)(c) to punish a taxpayer for failing to comply with a request that is unclear, excessive or impractical.

Verification versus audit

The label used by SARS is not decisive. The substance of the process matters.

A verification is a limited check. An audit is a wider examination of the taxpayer's records, accounting treatment and tax position. If SARS requests selected VAT invoices, that may remain a verification. But if SARS requests substantially all records, all vouchers, all bank statements and all supporting documents, the process may have moved into audit territory.

This matters because an audit carries procedural safeguards. SARS should provide proper notice, communicate the basis of the audit, and give the taxpayer a fair opportunity to respond to proposed adjustments. SARS should not avoid those safeguards simply by calling the process a verification.

The section 95(1)(c) warning: notice or threat?

SARS verification letters often include a warning that failure to submit the requested material may result in an estimated assessment under section 95(1)(c).

SARS may say this is merely a statutory warning. In principle, taxpayers should be told the consequences of non-compliance. However, the warning becomes problematic where it is attached to a request that is vague, excessive or impossible to satisfy in the time allowed. In that context, the warning operates as a threat: comply with an unreasonable request or face an estimated assessment.

That is not fair administration. SARS should only rely on section 95(1)(c) where the underlying request was clear, relevant, proportionate and capable of being complied with.

Non-receipt and practical difficulties

Another common problem is that taxpayers do not always receive SARS notices. A request may be placed on eFiling, sent to the wrong profile, missed by the taxpayer, or not brought to the attention of the person responsible for compliance.

Section 95(1)(c) refers to delivery of more than one request. But delivery is not always the same as actual knowledge. Where the taxpayer genuinely did not receive the request, SARS should be slow to impose the severe consequence of an estimated assessment. The real question is whether the taxpayer was given a fair opportunity to comply.

The same applies where the taxpayer receives the request but cannot comply because of the volume of documents, system limitations or the need to obtain records from third parties.

What the taxpayer should do

The taxpayer should not ignore the request.

If the SARS request is unclear, too wide or impossible to comply with in the time allowed, the taxpayer should respond before the deadline. The response should state that the taxpayer is willing to comply, but that SARS must identify the specific issue being verified, narrow the request if necessary, grant an extension, or accept documents in batches.

If SARS has already raised an estimated assessment, the taxpayer should act immediately. The taxpayer should submit the outstanding material and request a reduced or additional assessment under section 95(6). In VAT estimated-assessment cases, this must be done urgently, as SARS refers to a 40-business-day period from the VAT217 notice.

The taxpayer should also consider a suspension of payment request under section 164 where the estimated assessment creates an immediate debt.

Conclusion

SARS may verify. SARS may request relevant material. SARS may estimate in proper cases. But SARS must act fairly.

Relevant material must be relevant to a specific verification purpose. A verification should not become an open-ended demand for everything. If SARS is effectively examining the taxpayer's full accounting records, the process may be an audit, and the audit safeguards should apply.

In VAT cases, SARS should not mechanically reverse input tax for late submission, partial submission or minor invoice defects where the underlying transaction is genuine and can be proved.

The warning of section 95(1)(c) should also not be used as a threat to force compliance with an unreasonable request. Section 95(1)(c) should be used as an estimating mechanism where SARS genuinely cannot assess because relevant material has not been provided. It should not be used as a punitive shortcut where the taxpayer was not given a fair, clear and reasonable opportunity to comply.

Introduction

Prescription is one of the most important protections available to taxpayers in the South African tax administration system. It prevents tax affairs from remaining open indefinitely and creates finality once the statutory period has expired. The practical question often arises where SARS, during the verification or audit of a later year, identifies a problem that may also have existed in an earlier year. A common example is rent expenditure that SARS believes should have been apportioned between deductible and non-deductible use. SARS may then request documents for an earlier year that has already prescribed. The taxpayer must then decide how to respond.

The issue is not whether SARS may ever request information. SARS has wide powers to request relevant material. The issue is whether SARS may use a document request after prescription to reopen a year that is already closed. The taxpayer's response must be careful. A flat refusal may create unnecessary risk. Full compliance without reservation may also create risk, because SARS may attempt to use the documents to support an additional assessment. The correct approach is usually a qualified response that records prescription, reserves the taxpayer's rights, and requires SARS to identify the legal basis for requesting documents relating to a prescribed year.

The purpose of prescription

Prescription under section 99 of the Tax Administration Act exists to provide certainty. Once the prescribed period has passed, SARS is generally barred from issuing a further assessment for that year. Section 99 establishes the limitation period for SARS to issue assessments and the default period is three years after the original assessment, subject to specified exceptions.

For most income tax assessments, the ordinary prescription period is three years from the date of the original assessment. For self-assessment taxes, such as VAT and PAYE, the period is generally five years. This distinction is important. In an income tax rent-apportionment matter, the first question is whether SARS is within three years from the date of the original assessment. If SARS is outside that period, SARS must identify an exception before it can raise an additional assessment. For VAT or PAYE matters, the question is usually whether SARS is within five years.

The rent apportionment example

Assume a taxpayer claimed rent expenses in an earlier income tax year. The taxpayer used the premises partly for trade and partly for another purpose, or SARS later forms the view that the rent was not fully deductible. SARS then audits a later year, still within prescription, and discovers that the rent expense in that later year should have been apportioned.

SARS may be entitled to examine and adjust the later year if it is still within prescription. The taxpayer must engage with SARS on the merits of that open year. The taxpayer may have to provide the lease agreement, floor plan, usage schedule, management accounts, general ledger, and calculation of the deductible portion of the rent.

However, the later-year finding does not automatically reopen an earlier prescribed year. SARS cannot simply say: "We found the apportionment was wrong in 2024, therefore we will reopen 2020." Prescription still applies to the earlier year. SARS must show why the earlier year falls within one of the statutory exceptions.

The section 99 exceptions

Section 99(2) is the key provision. Prescription does not apply where the full amount of tax was not assessed due to fraud, misrepresentation, or non-disclosure of material facts. In the case of an assessment by SARS, prescription may be displaced where the failure to assess the full amount was due to fraud, misrepresentation, or non-disclosure of material facts.

For self-assessment, the exceptions are expressed more specifically. They include fraud, intentional or negligent misrepresentation, intentional or negligent non-disclosure of material facts, or failure to submit a return or make the required payment.

The distinction matters. SARS must do more than identify an error. SARS must identify the statutory exception. In a rent case, SARS must show that the non-apportionment was not merely an incorrect tax treatment, but was caused by fraud, misrepresentation, or non-disclosure of material facts.

Error versus non-disclosure

A disagreement about rent apportionment is not automatically non-disclosure. Many tax disputes arise because SARS and the taxpayer disagree on the application of the law to disclosed facts. That is different from the taxpayer hiding facts.

For example, if the taxpayer disclosed rental expenditure in the tax return, financial statements, tax computation, or accounting records, and SARS could have requested supporting documents within the prescription period but failed to do so, the taxpayer has a strong prescription argument. SARS may say the rent should have been apportioned. The taxpayer may say the rent was fully deductible, or that any apportionment adopted was reasonable. That is a merits dispute. It does not automatically become a prescription exception.

Non-disclosure requires a material fact that was not disclosed. In a rent case, a material fact might be that part of the premises was used privately, or by another entity, or for exempt activities, and that this fact was not disclosed or could not be identified from the return or supporting records. Even then, SARS must connect the non-disclosure to the failure to assess the full amount of tax within the ordinary prescription period.

The taxpayer should therefore insist that SARS identify the specific material fact allegedly not disclosed. It is not enough for SARS to state generally that the rent was incorrectly claimed. SARS must explain what was not disclosed, why it was material, and how it caused the under-assessment.

SARS' power to request relevant material

Section 46 of the Tax Administration Act gives SARS power to request relevant material for the purposes of the administration of a tax Act. SARS may require a taxpayer or another person to submit relevant material within a reasonable period.

The same provision requires that the taxpayer submit relevant material at the place, in the format, and within the time specified in the request. It also allows SARS to extend the period if reasonable grounds for an extension are submitted by the taxpayer. Importantly, section 46(6) provides that relevant material required by SARS must be referred to in the request with reasonable specificity.

This means that SARS cannot make an unlimited or vague demand. A request for "all documents relating to rent for the past ten years" may require challenge or clarification. SARS must identify the material required with reasonable specificity. The taxpayer may ask SARS to specify the year, tax type, issue, document category, and relevance.

However, the existence of section 46 does not mean SARS may revive a prescribed year merely by requesting documents. SARS' information-gathering power must be considered together with section 99. Where a year has prescribed, the taxpayer should not ignore SARS, but should require SARS to explain the statutory basis for requesting documents in relation to a closed year.

The danger of a flat refusal

A taxpayer should be cautious before simply refusing to provide documents. A refusal may be used by SARS to allege non-cooperation. It may also escalate the matter unnecessarily. In some cases, SARS may contend that the documents are relevant to an open year, even if they relate historically to a prior year. For example, SARS may request the original lease agreement signed in an earlier year to verify the rent deduction in a later year that is still open. In that case, the document may be relevant to an open year, even though the document was created in a prescribed year.

The correct question is therefore not merely whether the document is old. The correct question is whether SARS is using the document request to administer an open year or to reopen a prescribed year.

A flat refusal may be risky where the document is relevant to an open year. But where SARS expressly requests documents for the purpose of adjusting a prescribed year, the taxpayer should raise prescription immediately.

The better response: qualified engagement

The safest response is usually to engage, but under reservation of rights. The taxpayer should respond within the SARS deadline and say: the year has prescribed; the taxpayer does not waive prescription; the taxpayer does not accept that SARS may reopen the year; SARS must identify the legal basis for the request; SARS must confirm whether it relies on section 99(2); SARS must identify the alleged fraud, misrepresentation, or non-disclosure; SARS must confirm that any documents supplied will not constitute a waiver of prescription; and SARS must confirm that no additional assessment will be issued unless SARS establishes a valid section 99(2) exception.

This approach avoids non-compliance while protecting the taxpayer's legal position.

SARS cannot extend prescription after it has expired

A further important point concerns extensions of prescription. The Commissioner may extend a prescription period by prior notice of at least 30 days to the taxpayer, before the expiry of the period, by a period approximate to a delay arising from the taxpayer's failure to provide relevant material requested under section 46 or from resolving an information entitlement dispute.

The words "before the expiry" are critical. If the year has already prescribed, SARS cannot normally revive it by issuing a fresh document request after expiry and then saying the taxpayer's delay extends prescription. Section 99(3) operates before the prescription period expires. It does not convert an already prescribed year into an open year.

Any agreement to extend prescription must be made before the expiry of the original period. This supports the taxpayer's argument that SARS must act timeously if it wants to preserve its ability to assess.

Where SARS never requested documents during prescription

The taxpayer's position is stronger where SARS never requested documents during the prescription period. SARS had the statutory power to verify, audit, and request relevant material before prescription expired. If SARS did not exercise those powers, it cannot later convert its own inaction into taxpayer non-disclosure.

This is particularly important in the rent apportionment example. If the rent expense was disclosed in the financial statements or tax computation, and SARS never asked for the lease, floor plan, or allocation schedule before prescription expired, the taxpayer can argue that SARS had the opportunity to investigate the issue and did not do so.

The taxpayer should not say only: "SARS never asked." The stronger formulation is: SARS had the right to request documents before prescription; the taxpayer submitted the return; the rent expense was disclosed; no documents were withheld because no request was made; SARS did not extend prescription before expiry; SARS has not identified fraud, misrepresentation, or non-disclosure; therefore, the year remains prescribed.

Later-year findings do not automatically prove earlier-year non-disclosure

SARS may argue that a later-year rent apportionment adjustment reveals a pattern. That may be factually relevant, but it does not by itself override prescription. A later-year finding may cause SARS to suspect that the same issue existed earlier. Suspicion is not enough. SARS still has to identify the section 99(2) exception for the prescribed year.

The taxpayer should separate the years. For the later year that is within prescription, the taxpayer should deal with the merits of the apportionment. For the earlier prescribed year, the taxpayer should raise prescription and require SARS to prove the exception.

This separation is essential. If the taxpayer mixes the two years together, SARS may try to treat the merits of the later year as an admission for the earlier year. The taxpayer should avoid making unnecessary admissions. A concession that apportionment may be appropriate in the later year should not be framed as an admission that the earlier year was incorrectly or dishonestly filed.

Practical wording for the taxpayer's position

A suitable position is:

"The taxpayer records that the year of assessment concerned has prescribed under section 99(1) of the Tax Administration Act. The taxpayer does not waive reliance on prescription. SARS did not request the relevant material during the prescription period and did not issue any notice extending prescription before expiry. The rent expense was disclosed in the taxpayer's return, financial statements, tax computation, or accounting records. There was no fraud, misrepresentation, or non-disclosure of material facts. SARS is requested to identify the specific section 99(2) exception relied upon and the material facts allegedly not disclosed before requiring documents for a prescribed year."

This wording does three things. It responds to SARS. It preserves prescription. It shifts the focus to SARS' burden to identify the exception.

Documents supplied under reservation of rights

Where the taxpayer decides to provide documents, the submission should be expressly qualified. The covering letter should state that the documents are provided under reservation of rights, without waiver of prescription, and only to avoid any allegation of non-cooperation.

The taxpayer should also state that the documents may not be used to contend that the taxpayer agreed to reopen the year. If SARS wants to assess the prescribed year, SARS must first identify a valid statutory exception.

A reservation of rights is not a magic formula, but it is important evidence of the taxpayer's position. It prevents SARS from arguing that the taxpayer voluntarily accepted that the year was open.

Conclusion

Where SARS requests documents for a year that is already out of prescription, especially in relation to rent apportionment, the taxpayer should not ignore SARS and should not issue a reckless refusal. The proper approach is a controlled and qualified response.

Prescription is a substantive protection. SARS generally has three years for income tax and five years for self-assessment taxes. Once that period has expired, SARS must rely on a section 99(2) exception such as fraud, misrepresentation, or non-disclosure of material facts. A disagreement about rent apportionment is not, by itself, proof of any of those exceptions.

SARS may request relevant material under section 46, but the request must be reasonably specific and must be connected to a valid tax administration purpose. If the request concerns a prescribed year, SARS should be asked to identify the statutory basis for the request and whether it relies on section 99(2). If SARS did not request documents before prescription and did not extend prescription before expiry, it cannot usually revive the year by making a late request.

The taxpayer's best position is to respond promptly, reserve all rights, refuse to waive prescription, ask SARS to identify the exception relied upon, and provide documents only where appropriate and strictly under reservation. This approach protects the taxpayer while avoiding the risks that come with outright non-compliance.

Introduction

Lump sums are taxed using separate tax tables, not the ordinary income tax tables. They are intended to be taxed once, in the year received. By law, prior and current lump sums are aggregated when a taxpayer receives multiple lump sums over time. The issue is how the credit for prior tax is calculated.

Aggregation itself is accepted and not in dispute. The distortion arises from re-calculating prior lump sums using current tables rather than crediting the actual tax already paid. This creates a hidden double taxation that many taxpayers and practitioners do not immediately recognise.

The 2014 lump sum — taxed in 2014

Consider a taxpayer who received a lump sum of R1 000 000 in 2014. The tax was calculated using the 2014 lump sum table. The actual tax paid in 2014 was R161 550. This is the real tax that SARS collected and that the taxpayer has already paid.

The 2014 table applied progressive rates: 0% on the first R315 000, 18% on the band up to R630 000, 27% on the band up to R945 000, and 36% on the balance up to R1 000 000. The total tax of R161 550 was correct at the time and has been paid.

SARS approach — aggregate and apply the 2025 table

When the taxpayer later receives another lump sum — say R1 200 000 in 2025 — SARS aggregates the two amounts. The total aggregated amount is R2 200 000. SARS then applies the 2025 lump sum table to the aggregated amount. The tax on R2 200 000 under the 2025 table is R500 400.

The problem arises in the credit for the prior 2014 lump sum. SARS recalculates the tax on the 2014 R1 000 000 using the 2025 table, not the 2014 table. This produces a notional credit of R90 900 — substantially less than the R161 550 actually paid in 2014.

The SARS method then calculates tax payable as R500 400 minus the notional credit of R90 900, giving R409 500. But this is not the correct outcome.

Proof of double tax

The double tax becomes clear when the actual tax paid is compared with the notional credit allowed. The actual tax paid in 2014 was R161 550. The notional credit allowed by SARS under the 2025 recalculation is only R90 900. The difference — R70 650 — is the extra tax paid because of the notional re-calculation.

This R70 650 represents the portion of the 2014 lump sum that has been taxed again. It is not a new tax on the 2025 lump sum. It is a second layer of tax on the 2014 lump sum that arises solely because SARS used a current table to recalculate historical tax rather than crediting the tax that was actually paid.

Summary of the impact

The distortion can be summarised in four steps. First, SARS calculates tax on the aggregated amount using the 2025 table: R500 400. Second, SARS allows a notional credit for the 2014 lump sum recalculated using the 2025 table: R90 900. Third, the tax payable under the SARS method is R409 500.

Fourth, and most important, the fair tax payable — if the actual tax paid in 2014 was properly credited — is R338 850. The extra tax paid, the double tax, is R70 650. This is the amount that should not have been charged.

The solution

The correct approach is straightforward. Aggregation must remain because the law requires it and it ensures cumulative taxation. The credit, however, must be fixed. The taxpayer should deduct the actual tax paid on the prior lump sum — R161 550 in this example — not the notional amount of R90 900.

Applying this correction: R500 400 minus R161 550 equals R338 850. This correctly recognises the prior tax already paid and removes the double tax. It ensures fairness, consistency and the correct application of the law.

Key takeaway

Aggregation is accepted and ensures cumulative taxation. The problem is using a notional credit on the aggregated amount instead of the actual tax already paid in the earlier year. SARS already has the real tax paid on record. The taxpayer and practitioner should insist on crediting the actual tax paid to ensure fairness, consistency and the correct application of the law.

Introduction

SARS is increasingly using automation, data analytics and AI in tax administration. That much is clear. But an important legal question arises when the Tax Administration Act (TAA) requires a senior SARS official to make a decision. Can AI effectively make that decision, with a human merely approving it? In my view, that is where the problem begins.

The TAA is not anti-technology, but it is not AI-native legislation. It is drafted around identifiable human functionaries, written authority, designated posts and clear lines of accountability. The Act contemplates decisions being made by the Commissioner, a senior SARS official, or another SARS official with proper authority. That structure is built for human decision-making, not for a machine to become the real decision-maker behind the outcome.

This distinction is critical. There is nothing inherently unlawful about SARS using AI to assist with administration. AI may help with case selection, risk profiling, anomaly detection, data matching and even pre-population of returns. But assistance is one thing; substitution is another. If AI becomes the substantive decision-maker, and the official merely rubber-stamps the result, the decision becomes legally vulnerable.

The Constitution strengthens this point

The Constitution strengthens this point. Section 33 requires administrative action to be lawful, reasonable and procedurally fair, and it gives a right to written reasons. Section 195 requires public administration to be accountable, transparent and fair. Those principles require more than a name at the bottom of a notice. They require that the lawful decision-maker actually apply an independent mind to the taxpayer's facts.

PAJA takes the matter further

PAJA takes the matter further. Administrative action may be reviewed if the decision-maker was not authorised, if there was no proper procedure, if the process was unfair, if relevant facts were ignored, if the decision was arbitrary or irrational, or if adequate reasons were not given. Those review grounds fit squarely into the AI debate. A machine-driven outcome, adopted without real human evaluation, may amount to no proper application of mind at all.

POPIA also matters

POPIA also matters. Section 71 places limits on decisions with legal or substantial effects where they are based solely on automated processing intended to profile a person. That provision reinforces the broader concern that fully automated adverse decisions sit uneasily with South African administrative law.

Warning signs for practitioners

For practitioners, the warning signs are practical. Does the SARS decision engage properly with the taxpayer's actual facts? Does it explain why submissions were rejected? Or does it read like a generic, formulaic response? If the reasons are standardised and disconnected from the case, one must ask whether there was a real human decision at all.

The better argument

The better argument is therefore not that SARS may never use AI. It is that the TAA allows AI support, but it is not AI-friendly where Parliament requires a human official to decide. The issue is not modernisation. The issue is legality. Where the law says a senior SARS official must decide, the final judgment must remain human, accountable and properly reasoned.

The bottom line

The bottom line is simple: AI may help SARS administer, but it cannot lawfully replace the human decision-maker where the TAA requires human authority.

Introduction

Tax practitioners have become accustomed to strong language in SARS correspondence. Audits are framed robustly, findings are often expressed confidently, and letters sometimes carry an unmistakable tone of finality even where important facts remain disputed. That is not, by itself, the problem. SARS is entitled to audit, to question return positions, and to raise additional assessments where it believes the fiscus has been prejudiced. The real problem begins when SARS moves too quickly from a disputed adjustment to a behavioural finding, and from that behavioural finding to a severe understatement penalty.

That pattern deserves careful attention because it can distort the dispute process. A deduction may be disallowed. An allowance may be recalculated. A VAT figure may be reconstructed. But none of those outcomes automatically means the taxpayer acted negligently, grossly negligently, or intentionally. Those are separate enquiries and should always be treated as such.

The distinction is well illustrated by two recent types of SARS correspondence. In one corporate income tax audit findings letter, SARS proposed finance cost and depreciation adjustments for the 2023 and 2024 years of assessment and then proposed understatement penalties of 100% for gross negligence and, in relation to one depreciation item, 150% for alleged intentional tax evasion. In a separate VAT finalisation letter, SARS reconstructed output tax from bank deposits, revised its view after receiving further explanations and loan-account material, but still imposed a 25% understatement penalty on the basis of "reasonable care not taken". Together, those letters show how SARS overreach can develop in practice.

The first mistake practitioners must avoid

One of the easiest traps in practice is to accept SARS's structure of argument. SARS will often present matters in a sequence that feels natural: the return was wrong, therefore there was an understatement, therefore a penalty follows, therefore the behaviour fits into a serious category. If the practitioner accepts that structure without breaking it apart, the case becomes far harder to defend.

The correct approach is to separate every issue.

The first question is whether the tax treatment was in fact wrong. The second is whether SARS has properly explained why it says the treatment was wrong. The third is whether the factual material relied upon by SARS is complete and properly particularised. Only then should one ask whether the conduct was blameworthy, and if so at what level. In other words, the tax issue and the penalty issue are related, but they are not the same.

This distinction is essential because SARS sometimes writes as if an adjustment is already proof of culpability. That is simply not so. A tax adjustment is about the correct tax outcome. An understatement penalty is about the taxpayer's behaviour. Those are different legal and practical enquiries, and practitioners should resist any attempt to merge them into one.

A good example of overreach: documentation disputes turned into behavioural findings

The corporate income tax audit findings letter provides a useful illustration. SARS proposed disallowing finance costs and depreciation, recording total proposed adjustments of more than R10 million. In relation to depreciation, SARS stated that only limited invoices had been provided and that depreciation would be allowed only to the extent supported by the asset register and invoices. It then linked that dispute to a penalty narrative based on gross negligence.

This is a familiar move. A documentation problem becomes a tax problem, and then, almost immediately, a behavioural problem.

But incomplete documentation does not automatically prove culpable conduct. It may weaken the taxpayer's evidential position, but that is not the same thing as proving that the taxpayer acted with serious fault. In practice, the existence, ownership and use of an asset may often be supported by more than just one class of document. Asset registers, finance agreements, bank records, insurance schedules, registration documents, maintenance records and internal working papers may all become relevant. SARS is entitled to test the evidence, but it is not entitled to assume that any documentary gap automatically converts the matter into gross negligence.

That is a practical lesson practitioners should remember: weak proof is not the same thing as bad faith. SARS often compresses those ideas together, and advisers need to unpack them again.

The danger of treating absence of receipts as proof of no trade

The most striking feature of the income tax letter is SARS's treatment of the 2024 depreciation claim. SARS stated that there was no trading during the year of assessment and that bank statements reflected no business receipts. On that basis, it concluded that depreciation had to be disallowed because the assets were not used in the production of income. It then went much further and proposed a 150% understatement penalty on the basis of alleged intentional tax evasion.

This is precisely the kind of analytical leap practitioners should challenge.

A year with no business receipts does not always mean there was no trade in the relevant tax sense. Businesses may experience temporary inactivity. Assets may be held ready for use. Vehicles may be under repair, off the road for regulatory reasons, standing idle in a weak market, or retained as part of a business structure awaiting contracts. The absence of visible revenue may be relevant, but it is not self-proving. Much depends on the broader factual context.

Even more importantly, the step from "no receipts" to "intentional tax evasion" is simply too large unless SARS can point to proper facts supporting intention. Intentional tax evasion is an extremely serious allegation. One would ordinarily expect concealment, falsification, fabricated records, knowingly false statements, or some similar conduct demonstrating conscious evasion. Yet the letter, as framed, moves from a dispute about depreciation to a conclusion of intent without setting out the sort of factual foundation that such a conclusion would ordinarily require.

Practitioners should therefore be alert to a crucial point: a wrong allowance, even if it is wrong, is not automatically tax evasion. SARS must prove intention separately. A disputed deduction and a moral accusation are not the same thing.

Estimated assessments and behavioural conclusions

The VAT finalisation letter illustrates a different but equally important form of overreach. SARS explained that it reviewed the annual financial statements and the vendor's bank statements, identified deposits over the audit period, later removed some deposits after the vendor explained that they were intercompany flows, and then retained four deposits as taxable supplies. On that basis, SARS finalised an output tax adjustment and imposed a 25% understatement penalty for reasonable care not taken.

This raises a different set of concerns.

Where SARS reconstructs VAT from bank deposits, it is working by inference. A bank deposit is not automatically output tax. It may be a loan, a capital movement, an intercompany transfer, a non-taxable receipt, or the proceeds of a transaction whose VAT character still needs to be examined properly. In the letter itself, SARS acknowledged that some of its initial assumptions had to be revised once the vendor provided a further explanation and loan-account support. That is important because it shows that the reconstructed position was not self-evident from the start.

Practitioners should use that fact carefully. If SARS's own view changed once fuller information was supplied, that is a strong indication that the matter was fact-sensitive rather than obvious. It becomes much harder, in those circumstances, to treat the reconstructed liability as automatic proof that the vendor failed to take reasonable care. Estimation may justify further enquiry or even adjustment, but estimation is not the same as behavioural proof.

That point matters well beyond VAT. Whenever SARS is working from approximation, inference, or reconstruction, advisers should be cautious about allowing those techniques to become the basis for strong behavioural language.

What practitioners should do when SARS overreaches

The best response is not outrage. It is discipline.

When a SARS letter shows signs of overreach, practitioners should structure their response in layers. First, identify exactly what SARS is alleging. Secondly, test whether SARS has actually proved the facts it relies on. Has it identified the precise assets, entries, invoices, deposits or schedules in dispute? Has it explained its calculations? Thirdly, test whether the legal conclusion really follows from those facts. Fourthly, and separately, deal with behaviour. Even if the adjustment survives in whole or in part, why does that not justify gross negligence, reasonable care not taken, or intentional tax evasion?

This last stage is where many cases are won or lost. Practitioners often spend all their energy on the underlying tax position and leave the penalty issue underdeveloped. That is a mistake. Even where a taxpayer does not succeed entirely on the merits, it may still succeed on penalty. In many matters, that can make a very substantial difference to the eventual outcome.

The wider lesson for the profession

The broader lesson is straightforward. SARS letters must be read critically, not reverently. Strong wording is not the same as strong reasoning. A formal conclusion is not always a fully demonstrated conclusion. The letters discussed here show how easily SARS can move from adjustment to behaviour, and from behaviour to severe penalty language, even where the factual foundation is thinner than the tone suggests.

Practitioners therefore need to hold on to one central discipline: do not let SARS turn every tax disagreement into a moral accusation.

Mistakes happen. Misallocations happen. Documentation gaps happen. Estimated reconstructions happen. None of those situations automatically proves blameworthy conduct. If advisers consistently separate the adjustment from the penalty, and the penalty from the behavioural category, they will often find that SARS's most aggressive conclusions are much weaker than they first appear.

Why this matters

Tax practitioners are increasingly seeing SARS verification requests to sole proprietors demanding every invoice/receipt and proof of payment (POP) for every expense reflected in the income statement — often across hundreds or thousands of transactions. While SARS is empowered to verify returns and request relevant material, blanket population-wide demands can create an unreasonable compliance burden, especially where low-value, high-volume transactions are common.

Practitioners also report scenarios where taxpayers upload extensive documentation and the matter is finalised very quickly thereafter, raising legitimate concerns about whether submissions were meaningfully considered. Even where SARS uses internal tools and risk rules to accelerate case handling, the credibility of the process depends on SARS being able to show that requests are properly targeted and outcomes properly reasoned.

The better starting point: review the financials first

In most proprietor income tax cases, there should already be a coherent set of financial information underpinning the return — typically annual financial statements (AFS) or, at minimum, a structured income statement, balance sheet, and supporting schedules (or accounting reports from the accounting system).

A reasonable and efficient approach is:

1. SARS reviews the financials (AFS or equivalent) and the return to identify the specific risk drivers (e.g., unusual margins, large year-on-year movements, atypical expense ratios, or mismatches to third-party data).
2. SARS then issues a targeted request aligned to the risk identified — rather than defaulting to "every invoice and POP for all expenses."

This approach aligns with the principle that information requests should be foreseeably relevant and reasonable (rather than limitless). It also reduces noise, speeds up resolution, and improves decision quality.

Verification is not audit: document expectations must differ

A key practical problem is that many "verification" requests are framed like audit requests. That is not just semantics — scope and process matter.

• A verification should ordinarily test specific declarations in the return, usually focusing on identified risk items.
• An audit is typically broader in scope and depth and triggers greater process expectations (including communication and outcome requirements reflected in the audit framework).

Where SARS requests resemble audit-level population testing (everything, everywhere, all at once), practitioners should consider asking SARS to clarify whether the matter has escalated to audit, and to apply the appropriate procedural approach.

What SARS should request for a verification (proportionate and workable)

For verification, the emphasis should be on targeted substantiation, starting from the financials and then drilling down only where needed. A practitioner-friendly, SARS-friendly verification model is:

1) Foundational documents

• AFS / financial statements (or equivalent) that reconcile to the return
• General ledger or expense schedule only for the specific categories under query
• Selected bank statements only where they are necessary to test the queried items

2) Focused substantiation

• Invoices/receipts and POP for the specific expenses or categories flagged
• A sample approach for high-volume, low-value items (where appropriate), rather than 100% testing

3) Clear issue framing

• SARS identifies the risk driver (e.g., "repairs increased 300%," "motor vehicle claim appears excessive," "subcontractor costs inconsistent with turnover"), enabling the taxpayer to respond precisely.

This is materially different from an "audit file." It is a verification response built around financials first, then specific proof where warranted.

What SARS should request for an audit (when the matter truly requires it)

Where SARS has escalated to an audit (or the scope is clearly audit-like), deeper documentation can be appropriate — but it should still be structured and linked to audit objectives. In an audit context, SARS may reasonably request wider accounting records, reconciliations, and fuller populations — provided the requests remain connected to audit issues and are administered fairly.

The key point for practitioners and SARS alike is sequencing and proportionality:

• Start with financials and risk drivers.
• Then request documents relevant to those drivers.
• Escalate depth only if the verification response indicates a need for audit-level enquiry.

Addressing the "AI data harvesting" concern — professionally and without speculation

Clients are increasingly asking whether SARS is collecting "everything" to build future analytics or AI models, especially where outcomes appear to be finalised without meaningful engagement. Practitioners should avoid unprovable allegations, but it is entirely appropriate to ask SARS — neutrality intact — to confirm that requests are limited to what is reasonable and foreseeably relevant to tax administration, and that decisions reflect consideration of what was submitted.

The credibility of SARS processes depends not only on lawful powers, but on demonstrable fairness: targeted requests, sensible volumes, and reasons that show the decision-maker applied their mind.

Practical guidance for practitioners: how to respond without building an audit pack

When faced with a blanket "every invoice + POP" verification request, a defensible and efficient approach is:

1. Submit the financials first (AFS or equivalent) and ensure they reconcile to the return.
2. Ask SARS to specify the risk items or categories driving the request.
3. Provide substantiation only for those items/categories, using sampling for genuinely high-volume, low-value lines where appropriate.
4. If SARS insists on population-wide proof, request clarity on whether the matter is now an audit and ask for the appropriate audit process to be followed.

Conclusion

Sole proprietors must substantiate deductions, and SARS is entitled to verify returns. But a workable, credible system starts with the financials, identifies risk, and then requests specific supporting documents appropriate to either a verification or an audit. Blanket "everything" requests in verification cases are costly, often unproductive, and can undermine confidence when outcomes appear too rapid to reflect genuine review.

A "financials-first, risk-based" approach better serves SARS, practitioners, and taxpayers: fewer unnecessary uploads, faster resolution, and outcomes that are easier to justify and defend.

Why tax practitioners should expect greater pressure on estimates

Provisional tax has traditionally been viewed by many taxpayers as a routine compliance obligation. Twice a year, the taxpayer or tax practitioner calculates an estimate, submits the IRP6, arranges payment, and moves on to the next deadline.

That view is becoming increasingly dangerous.

In the current fiscal environment, provisional tax is far more than an administrative process. It is one of SARS's most powerful early collection mechanisms. It enables SARS to collect tax before the final assessment is issued and before the normal income tax liability has been finally determined.

From SARS's perspective, the attraction is obvious. Provisional tax accelerates cash collection. It reduces the delay between the earning of income and the payment of tax. It gives SARS a basis to monitor current-year taxable income. It also gives SARS a mechanism to challenge taxpayers who submit low estimates.

For this reason, tax practitioners should expect SARS to pay closer attention to provisional tax estimates, especially where the taxpayer has used the basic amount, submitted a reduced estimate, traded better than expected, or failed to retain proper evidence supporting the calculation.

The collection numbers show why provisional tax matters

The SARS Tax Statistics demonstrate the significance of provisional tax as a revenue collection tool. For the 2024 tax year, company provisional tax payments amounted to approximately R306.5 billion.

• First provisional period — R129.9 billion
• Second provisional period — R167.8 billion
• Third provisional period / top-up — R8.8 billion
• Total company provisional tax — R306.5 billion

Total SARS tax revenue for 2024/25 was approximately R1.855 trillion. Company provisional tax alone therefore represents roughly 16.5% of total SARS tax revenue — about one-sixth of SARS's total tax collection.

The cash-flow impact of even a small increase is significant: a 5% increase would collect roughly R15.3 billion earlier, and a 10% increase would collect roughly R30.6 billion earlier. SARS does not need to increase tax rates to improve early collections — it can achieve a major cash-flow benefit simply by applying pressure to provisional tax estimates.

Provisional tax is not a separate tax

Provisional tax is not a separate tax. It is an advance payment system. The taxpayer is required to estimate taxable income for the year and pay normal tax in advance. The final liability is still determined when the annual income tax return is assessed.

The practical risk is that taxpayers often treat provisional tax as a cash-flow decision rather than a tax calculation. They ask, "How much can I afford to pay?" The correct question is, "What is my estimated taxable income for the year, and can I justify that estimate if SARS asks?"

Who is a provisional taxpayer?

A provisional taxpayer is not only a company. It includes:

• a company;
• a person, other than a company, who earns income that is not remuneration;
• a person who earns remuneration from an employer that is not registered for employees' tax;
• a person notified by the Commissioner that he or she is a provisional taxpayer;
• and a labour broker with an exemption certificate.

Most ordinary salary earners are therefore not provisional taxpayers if their only income is salary and PAYE is properly deducted. However, the position changes where the individual earns income outside the PAYE system.

The individual trader trap

An individual who trades in his or her own name is generally within the provisional tax system. This includes a sole proprietor, consultant, freelancer, independent contractor, commission earner, professional person in private practice, or any person who carries on a business outside the normal PAYE system — accountants, bookkeepers, IT consultants, plumbers, electricians, doctors, advocates, architects, online businesses, commission earners, landlords and individuals with business income alongside a salary.

The practical mistake is to assume that the R30,000 rule protects all individuals. It does not. The R30,000 exclusion applies only to an individual who does not carry on any business and whose taxable income from specified passive-type sources does not exceed R30,000 for the tax year. It is not a general exemption for individual traders.

The individual trader is particularly vulnerable because taxable income can change quickly during the year. A few profitable months can make the first or second provisional tax estimate too low, and SARS can then challenge the basis of the estimate.

Why SARS is likely to challenge estimates

Where a taxpayer submits a low estimate, SARS may ask whether that estimate is reasonable. SARS may compare the estimate to prior-year taxable income, VAT turnover, PAYE information, third-party data, bank information, assessed income, investment income and other information available to SARS.

Common risk areas include using an outdated basic amount, reducing the estimate without proper support, submitting an estimate below current-year trading results, ignoring management accounts or VAT turnover, failing to adjust for once-off income or capital gains, using cash flow as the basis for the estimate, or simply submitting a low number because the client does not want to pay.

Paragraph 19(3): SARS's pressure mechanism

Paragraph 19(3) of the Fourth Schedule is central. SARS may call upon a provisional taxpayer to justify any estimate made and require particulars of income and expenditure. If SARS is dissatisfied with the estimate, SARS may increase the estimate to an amount it considers reasonable.

The most important practical point is that SARS's increase of the estimate is not subject to objection and appeal. This is a powerful collection tool, and the taxpayer must deal with the SARS request properly and immediately. A weak response may result in SARS increasing the estimate, which then directly affects the provisional tax liability.

The basic amount is not always a safe harbour

Many taxpayers believe the basic amount gives automatic protection. It does not. If the taxpayer's current-year trading position shows that taxable income is likely to be higher, SARS may question why the estimate was not increased. This is particularly important where taxable income exceeds R1 million, where the second provisional tax estimate rules are stricter.

The better question is not whether the basic amount can be used, but whether the estimate can be defended if SARS asks for justification.

Practical evidence required

The main defence against SARS pressure is evidence. A provisional tax calculation should be supported by a proper working paper and retained on the taxpayer file.

For companies, the file should include the prior-year assessment, basic amount calculation, management accounts, year-to-date turnover and profit, projected income for the rest of the year, tax adjustments, capital gains or once-off receipts, assumptions used, client instructions, the tax calculation, proof of IRP6 submission, proof of payment, and the SARS receipt.

For individual traders, the file should include year-to-date income and expenses, projected income and expenses, other taxable income, PAYE already deducted, rebates and medical credits, capital gains, retirement contributions, the estimated taxable income calculation, the tax payable, reasons for any reduction, and confirmation of client instructions.

The client instruction problem

A common practical problem arises where the client instructs the practitioner to reduce the provisional tax payment because of cash-flow pressure. The client must be warned that provisional tax is based on estimated taxable income, not affordability. If the client insists on a lower estimate, the practitioner should retain the instruction in writing and record the advice given. This protects both the taxpayer and the practitioner if SARS later raises penalties, interest or an increased estimate.

Technology and control

The provisional tax process must be controlled properly. The practitioner should be able to show how the estimate was calculated, what information was used, what SARS data was available, what the client instructed, what was submitted, what SARS accepted, what was paid, and what documents support the position. This is where proper workflow, document retention, sticky notes, statuses, SARS receipts and calculation records become essential.

AI Taxman can assist by identifying the legal issue, helping draft responses to SARS, highlighting paragraph 19(3) risks, and suggesting practical remedies where SARS places improper or excessive pressure on the taxpayer. However, AI does not replace professional judgment.

Conclusion

Provisional tax has become one of SARS's most important early collection mechanisms. Company provisional tax alone amounted to approximately R306.5 billion for the 2024 tax year — roughly one-sixth of total SARS revenue. A 5% increase could move more than R15 billion forward; a 10% increase could move more than R30 billion forward. That is why SARS is likely to place increasing pressure on provisional tax estimates.

The risk is not limited to companies — individual traders, sole proprietors, consultants, freelancers and professionals in private practice are also exposed. In the new SARS environment, the taxpayer who cannot justify the estimate is vulnerable, and the practitioner who cannot produce the working paper is exposed. Provisional tax is no longer just a deadline. It is a major SARS collection weapon.

Introduction

Provisional tax is a system that requires a taxpayer to estimate taxable income before the final taxable income for the year has been determined.

That point is important. A provisional tax estimate is not an income tax return. It is not a final tax computation. It is not a completed set of annual financial statements.

This distinction matters most where SARS challenges a provisional tax estimate, calls for justification, increases an estimate under paragraph 19(3) of the Fourth Schedule to the Income Tax Act, or imposes an underestimation penalty under paragraph 20.

The law does not allow SARS to treat every difference between estimated taxable income and final taxable income as proof of negligence, understatement, or non-compliance. SARS may also not use hindsight, incomplete statutory reasoning, or automated processes to create provisional-tax liabilities outside the proper limits of the Fourth Schedule and the Tax Administration Act.

P1: The first provisional tax estimate

For a company, paragraph 19(1)(b) requires the taxpayer to submit an estimate of total taxable income during the relevant provisional-tax period. Paragraph 19(1)(c) deals with the first estimate. It provides that the first estimate may not be less than the basic amount, unless the circumstances justify a lower estimate.

The first provisional tax estimate is therefore made early in the year. At that point, the taxpayer does not yet know the final taxable income for the year. The taxpayer may not yet have final branch results, year-end journals, tax add-backs, capital allowance calculations, stock adjustments, capital-gains computations, provisions, bad-debt assessments, or other final tax adjustments.

SARS is not entitled to pretend that this information already exists.

SARS may call for justification under paragraph 19(3)

Paragraph 19(3) allows SARS to call on a provisional taxpayer to justify an estimate. SARS may also require particulars of income and expenditure, or other required particulars. If SARS is dissatisfied with the estimate, it may increase the estimate to an amount that it considers reasonable. That increase is not subject to objection and appeal.

That is a powerful SARS provision, but it is not unlimited. SARS must still exercise the paragraph 19(3) power lawfully, rationally, and for the proper administration of a tax Act. SARS cannot use paragraph 19(3) as a shortcut to cash collection. SARS also cannot use the provision to demand a premature income tax return.

A lawful paragraph 19(3) increase may not be subject to objection and appeal. But an unlawful abuse of paragraph 19(3) is a different matter. SARS cannot place itself beyond legality merely by labelling its conduct as paragraph 19(3) action.

SARS may not use hindsight at P1 stage

The central P1 principle is simple: SARS must judge the taxpayer's estimate by reference to the information available when the estimate was made.

A taxpayer cannot be required to look into the future. It cannot be expected to take later trading results, later management accounts, later accounting adjustments, later capital transactions, or later tax computations and import them backwards into the P1 estimate.

Where SARS uses later information to attack a P1 estimate, the problem is not necessarily the taxpayer's estimate. The problem may be SARS's method. The correct question is not "what was the final taxable income?" but "what information was available to the taxpayer when the P1 estimate was submitted, and was the estimate properly made on that information?"

SARS information requests must remain within section 46

If SARS requests information under section 46 of the Tax Administration Act, the information must be required for the administration of a tax Act. SARS may not request information without reasonable cause.

This is important in provisional tax disputes. SARS may not use section 46, read with paragraph 19(3), to demand final-year information that does not yet exist. SARS may also not use section 46 to force the taxpayer to prepare a premature annual tax return.

A taxpayer is entitled to require SARS to identify:

• the statutory provision relied upon;
• why each item of information is required;
• why the information is necessary for the administration of a tax Act;
• whether SARS is relying on paragraph 19(3), section 46, or both;
• whether the information existed or was reasonably available when the estimate was made.

SARS should not be allowed to shift the burden by issuing broad, unexplained, impossible, or premature information demands.

P1 conclusion

For P1, the taxpayer's strongest position is that the first estimate must be tested at the time it was made. SARS cannot use hindsight, later figures, later profits, or later adjustments to convert a genuine first provisional estimate into an alleged understatement.

Where SARS increases or threatens to increase a P1 estimate under paragraph 19(3), the taxpayer should insist that SARS act within the provision. SARS should identify the facts relied upon, provide the calculation, and explain why the original estimate was unacceptable based on the information available at the time.

P2: The second provisional tax estimate

P2 is different. The second provisional tax estimate is still an estimate — it is not a final income tax return. However, by P2 stage the taxpayer is much closer to year-end, and paragraph 20 of the Fourth Schedule becomes the main risk.

For taxpayers with taxable income exceeding R1 million, paragraph 20(1)(a) applies. If the final or last estimate is less than 80% of actual taxable income, SARS must impose the underestimation penalty. For taxpayers with taxable income of R1 million or less, paragraph 20(1)(b) applies the 90% test and also refers to the basic amount.

This means that, for larger taxpayers, the basic amount is not the answer at P2 stage. The taxpayer must focus on the 80% test and, more importantly, the remission defence under paragraph 20(2).

P2 is still not a final tax return

Large taxpayers often face real practical constraints at P2 stage. A taxpayer with multiple branches, divisions, accounting systems, stock locations, debtors, creditors, tax adjustments, capital allowance schedules, and intercompany charges may not have a final taxable income figure before the year has ended.

That does not mean the taxpayer may guess. It does mean SARS may not pretend that the taxpayer had final information when it did not. The proper P2 enquiry is whether the taxpayer made a serious estimate on the information reasonably available at the time.

Paragraph 20(2): the real P2 defence

Paragraph 20(2) provides the key defence. The penalty may be remitted where the estimate was seriously calculated with due regard to the factors having a bearing on it, and was not deliberately or negligently understated.

For P1, the argument is: SARS cannot use hindsight against an early estimate. For P2, the argument becomes: even if the final taxable income later exceeded the estimate, the P2 estimate was seriously calculated on the information then available, with due regard to the relevant factors, and was not deliberately or negligently understated. That is the correct legal battleground.

SARS may not impose P2 penalties mechanically

SARS should not impose paragraph 20 penalties by rote. It is not enough for SARS simply to compare the final taxable income with the P2 estimate, find that the estimate was below 80%, and leave the penalty standing without considering remission.

Paragraph 20(1) may trigger the penalty. But paragraph 20(2) requires SARS to consider whether the taxpayer's estimate was seriously calculated and whether the understatement was deliberate or negligent. A mechanical penalty process is legally vulnerable.

SARS must engage with the taxpayer's actual calculation, the information available at the time, the taxpayer's assumptions, and the reasons why the final taxable income later differed from the estimate. A taxpayer should resist any SARS approach that treats the penalty as automatic and the taxpayer's explanation as irrelevant.

Practical evidence for P2

For P2, evidence is everything. The taxpayer should be able to show:

• the management accounts used;
• the trial balance used;
• the branch results available at the calculation date;
• which branches or divisions had not yet reported final figures;
• the tax add-backs considered;
• the deductions considered;
• the capital allowances considered;
• the stock, bad debt, provision, capital gain, or other adjustments considered;
• the assumptions used;
• who prepared the calculation;
• who reviewed it;
• why the final taxable income later differed from the estimate.

Where the taxpayer can show that the estimate was prepared from accounting records, adjusted for known tax issues, reviewed by an accountant or tax practitioner, and based on the best available information, the taxpayer has a proper paragraph 20(2) defence.

SARS must separate error from negligence

A later difference between estimated taxable income and final taxable income does not automatically prove negligence. A taxpayer may be wrong without being negligent. A taxpayer may underestimate without deliberately understating.

A taxpayer may miss the 80% mark because of later branch results, late accounting entries, unexpected income, reversed provisions, disallowed deductions, capital gains, exchange movements, or year-end tax adjustments that were not reasonably ascertainable at P2 stage. SARS must not collapse these categories into one another.

The legal question is not merely whether the estimate was low. The legal question is whether the estimate was seriously calculated and whether the shortfall arose from deliberate or negligent understatement.

The proper approach for SARS

A lawful SARS approach should be to:

• identify the estimate submitted;
• identify the final taxable income;
• identify whether paragraph 20(1)(a) or paragraph 20(1)(b) applies;
• calculate the alleged penalty correctly;
• consider the taxpayer's paragraph 20(2) explanation;
• decide whether the estimate was seriously calculated;
• decide whether there was deliberate or negligent understatement;
• give reasons for refusing remission, if remission is refused.

Anything less is vulnerable to challenge.

Conclusion

P1 and P2 are both provisional tax estimates, but they raise different legal issues. For P1, SARS may not use paragraph 19(3) to demand a premature income tax return, rely on hindsight, or increase an estimate by reference to information unavailable when the estimate was made.

For P2, the taxpayer faces the paragraph 20 underestimation-penalty regime, especially the 80% test for taxpayers above R1 million. But SARS still may not treat final taxable income as proof of negligence. The taxpayer's protection lies in paragraph 20(2): the estimate was seriously calculated, with due regard to the relevant factors, and was not deliberately or negligently understated.

SARS is entitled to enforce the law. It is not entitled to rewrite the provisional tax system into a hindsight-driven penalty machine.