Decentralised News · Guides · Decision research
By Heath Muchena · Source review 2026-11-14 · Instrument version 1.0.0
What Matters
An agent can organize transaction facts, source records and unresolved questions. It should not turn a transaction label into a universal tax treatment. This South Africa-scoped preparation record separates evidence, proposed classification and reviewer status, while preserving missing information. It calculates no tax and issues no filing verdict.
The hardest part of an automated crypto-tax workflow may be identifying what its neat output leaves unresolved: an old acquisition, a missing valuation, two records of one movement, or a proposed classification that nobody has reviewed.
This article prepares the evidence for a South African individual review. It does not replace a jurisdiction-specific tax analysis or treat every swap, bridge, reward or failed transaction as automatically taxable. The original DN tool works with redacted reference labels, so the review queue can be shared without pasting personal tax data into it.
DN Evidence Block
Sources reviewed: 2026-11-14 · Evidence type: Current SARS guidance and an original evidence-preparation/handoff method; sources checked on 13 November 2026 UTC.
Scope: Preparation for a South African individual’s crypto-tax review. Residence, entity scope, tax treatment, deductions, filing obligations and authorized submission remain separate decisions.
- SARS applies ordinary tax principles to crypto assets and distinguishes revenue/capital treatment according to facts and circumstances.
- SARS guidance supports retaining transaction evidence and records; a generated summary is not a substitute for the underlying source.
- CARF provider reporting does not replace an individual’s ordinary income-tax declaration.
Not established by this work: No taxpayer records, return, assessment, tax calculation, filing software or live SARS account were reviewed. All examples are synthetic. No event is classified as taxable or exempt by the tool.
Original DN instrument · version 1.0.0
DN Crypto Tax Preparation Record — South Africa
Check a redacted event-evidence queue for missing references, unresolved treatment and unsupported reviewed flags. Preserve source-population gaps and export a local handoff record. No tax calculation, classification or filing verdict is produced.
Enter your assumptions or load a labelled example. Required blank numbers stay missing; unknown evidence remains unknown. Use nonpersonal labels only. This instrument makes no network requests and uses no persistent browser storage.
Use your own inputs
No current result. Complete inputs or load an illustrative example.
A preparation checklist for South African individual review, not tax advice, a filing system, a residency decision or a taxability classifier. Counts do not prove complete source coverage. Treatment and review flags are user-entered. Only redacted references belong in the tool; it does not need amounts, names, tax numbers, wallet addresses or credentials. Retention and storage requirements must be assessed separately. No external requests or filing action.
1. Fix the taxpayer and review-period scope
Start with the person and period whose evidence is being prepared. A South African individual, a company and a person with unresolved tax residence do not automatically share the same filing analysis. An agent should record the confirmed scope and refer an unresolved scope question for review before assigning treatment.
SARS’s crypto-asset guidance applies ordinary tax principles and places responsibility for declaring relevant taxable income on the taxpayer. It distinguishes possible revenue and capital treatment according to the facts. The presence of an automated trading bot does not settle that distinction.
Prepare: the review-period boundaries, a nonpersonal taxpayer-scope label and a list of unresolved residence or entity questions. DN’s instrument is limited to preparation for a South African individual review. It does not decide residence, determine whether a return is required or calculate tax.
2. Build a complete source inventory before classifying rows
An agent can confidently classify the records it receives while missing an entire exchange, wallet or imported history. Start with the population of sources: platform exports, wallet activity, fiat records and prior acquisition evidence relevant to the review period.
Prepare: a source inventory with coverage dates, export version, missing periods and a controlled location for originals. Use stable aliases in the public worksheet rather than account identifiers or wallet addresses. A label such as exchange-A is enough to connect a review question to the privately retained evidence.
The tool compares the number of entered event rows with a declared event population, when one is known. That is a reconciliation check, not proof of completeness. Equal counts can still conceal duplicated imports, misgrouped transactions or an omitted source. Preserve the method used to produce the population and investigate count differences instead of adjusting the number until it matches.
3. Record what happened before deciding what it means for tax
Use factual event labels such as sale, swap, receipt for services, reward, bridge, wrapping operation, transfer, fee or failed attempt. Keep the observed asset movements and status separate from the proposed tax classification.
SARS’s crypto FAQs make treatment dependent on facts and circumstances, and address examples such as payment for services and mining. They do not provide a universal automated classification for every modern DeFi operation.
Prepare: the event evidence and the question a reviewer must answer. A bridge or wrap label does not itself establish a taxable disposal, and a failed transaction does not establish that no fee or other relevant event occurred. The tool never converts its event-kind dropdown into a tax verdict.
4. Preserve the valuation evidence and its timing
A token amount alone is not a reviewable value record. Preserve the transaction time, asset and quantity, the amount paid or received, and the valuation or conversion evidence used in the preparation. A reviewer must be able to identify why a particular rand amount was assigned to an event.
The SARS FAQs identify receipts and invoices as acceptable evidence of purchase and sale prices. That supports retaining the transaction basis rather than replacing it with a model-generated estimate.
Prepare: a valuation reference with source, timestamp, currency and method. If the needed price or conversion cannot be established, mark it missing. Do not silently substitute a daily close, current spot price or neighboring asset. DN’s record stores a reference to the valuation work; it does not prescribe a universally valid conversion method or calculate a taxable amount.
5. Keep acquisition history and fees attached to the event
A disposal record can be complete on one platform while its acquisition evidence sits elsewhere or predates the current review period. Retain the chain of evidence needed to understand the holding and any costs claimed in the proposed treatment.
SARS’s crypto guidance discusses expense deductions and base-cost adjustments within the applicable tax framework. These are conditional concepts, not permission to deduct every fee an agent sees.
Prepare: the acquisition or cost record, the fee evidence and a reasoned explanation when a category is not applicable. Keep gross amounts and fees distinguishable so the same charge is not counted twice. Do not pick a favorable cost method or deduction merely because it produces a lower result. The local tool accepts a reference such as “not applicable: reviewer memo A” where the rationale is retained; an unexplained N/A remains missing.
6. Reconcile ownership and movement across accounts
A withdrawal from one service and a deposit into another can be two records of one movement. Conversely, two similar quantities can be unrelated events. An agent should preserve ownership and movement evidence before merging entries or removing an apparent duplicate.
Prepare: the privately retained mapping of source and destination, transfer evidence, fees and any change in beneficial ownership or contractual rights. Use reference labels in the worksheet rather than publishing addresses, names or tax identifiers.
This record does not declare all self-transfers tax-free or all protocol transformations taxable. It makes the factual question inspectable. For a bridge, wrap, liquidity position or reward, describe the rights and assets before and after the operation and leave the treatment unresolved where the evidence or applicable analysis is incomplete.
7. Separate a proposed classification from reviewed treatment
An agent’s proposed answer is a draft. Keep its supporting facts, sources and unresolved assumptions beside the classification so a reviewer can accept, revise or reject it without reconstructing the entire process.
The SARS crypto FAQs say that normal tax or capital-gains treatment depends on the facts and circumstances. A high transaction count, long holding period or product label should not be turned by this worksheet into an automatic classification.
Prepare: one of three statuses: unresolved, proposed, or reviewed. A reviewed status needs a retained review reference and a responsible role. It remains a user-entered assertion; DN has not verified the reviewer’s qualifications or conclusion. This distinction is why the instrument can show a tidy evidence pack while still refusing to call it ready for filing.
8. Keep originals and a retention plan beyond the agent’s working memory
A chat summary or generated CSV should not become the only surviving evidence. Retain original records and the transformations used to prepare the review, including corrections and any changed classification.
SARS’s recordkeeping guidance calls for records to be kept in an orderly, safe and inspectable form. Its retention guidance includes a five-year period measured from return submission for submitted returns, with other circumstances requiring separate attention. It also addresses prescribed electronic formats and authorization for certain storage arrangements.
Prepare: a retention and access plan that accounts for the actual return, audit, dispute and storage situation. Do not use this worksheet to calculate an automatic destruction date. A backup copy and an export are useful operational measures; neither by itself establishes compliance with the applicable recordkeeping rules.
9. Hand off unresolved items without confusing provider reporting with the return
A provider may report information that helps SARS identify activity, but that does not assemble the taxpayer’s full factual record or decide its tax treatment.
The current SARS CARF page places reporting obligations under that framework on the relevant crypto-asset service providers and says individuals continue declaring transactions through their ordinary income-tax returns. CARF reporting is not a substitute for the individual’s preparation and review process.
Prepare: a handoff list of missing sources, valuations, acquisition evidence, ownership questions and proposed classifications. Confirm the authorized filing process separately. This article does not assert that AI tools are universally prohibited from filing; it separates preparation from the accountable decision to submit a return.
The local JSON export carries the period, reference labels, entered statuses, open issues and creation timestamp. It sends nothing to SARS or a tax platform. A complete record means the entered handoff fields are assembled, not that the taxpayer owes zero, a particular event is exempt, or a return is legally correct.
Methodology, limitations and corrections
DN’s method separates event facts, evidence references and treatment status. The instrument checks for five reference categories per event: original source, rand valuation work, acquisition/cost history, fees and ownership/movement evidence. A reference may point to a reasoned non-applicability decision, but a bare N/A or unknown remains a gap. These are preparation categories, not a claim that each event has the same tax consequence.
The event population is supplied independently by the user. Entered rows above that population are rejected as inconsistent; fewer rows expose a gap, and an unknown population stays null. Unique event IDs prevent simple duplicate counting but do not establish that two distinct IDs represent distinct economic events. The operator must preserve its grouping and reconciliation method.
Unresolved and proposed treatment remain open. A reviewed flag without a retained review reference or responsible role is a contradiction. Even a fully populated record returns only an assembled handoff status, never a tax or filing conclusion. Empty records likewise do not establish an exemption or absence of obligations.
The JSON export contains the review scope, redacted references, input statuses, open issues and creation timestamp. Keep underlying documents and sensitive personal information in the taxpayer’s controlled records. Version 1.0.0, 14 November 2026: original preparation instrument and synthetic fixtures, based on SARS sources checked on 13 November UTC. The article does not rely on the inconsistent CARF effective dates found across two SARS pages; only the provider-reporting versus individual-return distinction is used.
For corrections, identify the claim, source and date when contacting Decentralised News. A new record-creation timestamp does not refresh its underlying evidence.
Change log: version 1.0.0, 2026-11-14. Initial documentation review, original instrument and labelled examples.
Frequently asked questions
Does using an agent change whether crypto income is revenue or capital?
The tool does not make that decision. SARS describes treatment as dependent on the applicable ordinary principles and the facts and circumstances. Automation alone does not settle the classification.
Are all swaps, bridges and rewards taxable events?
Do not apply one universal label. Preserve the factual operation, rights and evidence, then obtain the appropriate South African analysis for that event.
Can I enter N/A for missing acquisition evidence?
An unexplained N/A remains missing. A non-applicability conclusion should point to a retained reasoned review record rather than conceal an unavailable document.
Does CARF reporting replace my tax return?
No. SARS distinguishes reporting by relevant service providers from the individual’s continuing income-tax declaration process.
Does the completed worksheet mean I can file?
No. It means the entered preparation fields have been assembled. The actual tax position, return, authorizations and submission remain separate decisions.
Should I paste tax numbers, account records or wallet addresses here?
No. Use redacted labels that point to your own controlled documents. The tool needs no personal identifiers or credentials and sends nothing to SARS.
Primary sources
- SARS: Crypto Assets & Tax. Ordinary tax principles, taxpayer responsibility, conditional revenue/capital treatment, costs and base-cost concepts. Historical exchange-control remarks are not adopted. Reviewed 2026-11-13.
- SARS: crypto-asset FAQs, reviewed June 2021. Fact-dependent treatment, service/mining examples, purchase/sale evidence and conditional expense treatment; no universal DeFi classification. Reviewed 2026-11-13.
- SARS: recordkeeping. Record integrity, submitted-return retention baseline and storage/authorization considerations; no automated destruction-date rule. Reviewed 2026-11-13.
- SARS: supporting-document retention FAQ. Five-year submitted-return supporting-document baseline, subject to the wider applicable circumstances. Reviewed 2026-11-13.
- SARS: Crypto-Asset Reporting Framework. Relevant service-provider reporting versus individual income-tax declarations; no effective-date claim is used. Reviewed 2026-11-13.
- SARS: CARF implementation announcement. Individuals continue ordinary income-tax declarations; no change-of-tax-treatment inference. Reviewed 2026-11-13.
Turn the finding into a decision
If records are fragmented, first define the missing evidence and the South African review question. The DN Research Desk can discuss a source-based preparation brief with redacted inputs and an agreed scope. That is not a tax opinion or filing service. Any software considered for imports should be assessed for the actual exchanges, event types and jurisdiction; an affiliate relationship would not establish correct treatment.
Related DN research
Disclosure: Analysis and instrument results are editorial. Where labelled affiliate links appear, DN may receive compensation when you sign up or buy through them. Commercial relationships do not determine findings. No tested integration or guaranteed outcome is implied.
