South Africa crypto reporting in 2026: CARF records for CASPs

South Africa crypto reporting in 2026: CARF records for CASPs

South Africa crypto reporting 2026 includes CARF obligations for relevant providers. This guide outlines recordkeeping checks using SARS guidance and explains why tax reporting and FSCA licensing are separate questions.

Understand the reporting framework

South Africa’s Crypto-Asset Reporting Framework, or CARF, sets tax information reporting requirements relevant to reporting crypto-asset service providers. SARS says the framework took effect on 1 March 2026. A provider should distinguish these reporting duties from its separate licensing and conduct obligations. The article is a practical recordkeeping overview, not a statement that every crypto product is treated identically for tax purposes.

Keep the original source, the date checked and a short note explaining what the evidence supports. This makes later review quicker and helps distinguish a verified fact from an interpretation. If an item cannot be confirmed, record that limitation clearly and assign a follow-up instead of filling the gap with a guess. Apply the same process consistently so that readers can understand the basis and limits of the information.

Identify whether a business falls in scope

SARS describes reporting providers as businesses with a South African nexus that facilitate crypto-asset transactions for customers. The scope depends on the legal entity, its services and the applicable definitions. A brand name alone may not identify the reporting business. Providers should review the official guidance and determine which entities, accounts and transaction flows are covered before designing collection processes.

Keep the original source, the date checked and a short note explaining what the evidence supports. This makes later review quicker and helps distinguish a verified fact from an interpretation. If an item cannot be confirmed, record that limitation clearly and assign a follow-up instead of filling the gap with a guess. Apply the same process consistently so that readers can understand the basis and limits of the information.

Collect records systematically

A defensible process begins with clear customer and account records, transaction identifiers, timestamps, asset type, transaction amount and relevant exchange or transfer details. Keep original source data and a traceable record of corrections. Reconcile internal ledgers with external platform and wallet records on a scheduled basis. Missing or inconsistent data should be routed for review rather than silently filled with an estimate.

Keep the original source, the date checked and a short note explaining what the evidence supports. This makes later review quicker and helps distinguish a verified fact from an interpretation. If an item cannot be confirmed, record that limitation clearly and assign a follow-up instead of filling the gap with a guess. Apply the same process consistently so that readers can understand the basis and limits of the information.

Separate due diligence from trading records

Customer due diligence and transaction records serve different purposes. Keep the evidence used to identify a customer separate from transaction-level data while linking them through controlled identifiers. Limit access to staff who need it, log changes and document retention decisions. A privacy-conscious data flow reduces accidental exposure while preserving an audit trail for reporting and compliance review.

Keep the original source, the date checked and a short note explaining what the evidence supports. This makes later review quicker and helps distinguish a verified fact from an interpretation. If an item cannot be confirmed, record that limitation clearly and assign a follow-up instead of filling the gap with a guess. Apply the same process consistently so that readers can understand the basis and limits of the information.

Check exceptions and source definitions

Do not assume every transfer is a taxable disposal or every wallet interaction is reportable in the same way. The CARF definitions and SARS implementation guidance determine what information must be collected and reported. Flag edge cases such as transfers between a customer’s own wallets, missing acquisition details or transactions routed through another provider for qualified review.

Keep the original source, the date checked and a short note explaining what the evidence supports. This makes later review quicker and helps distinguish a verified fact from an interpretation. If an item cannot be confirmed, record that limitation clearly and assign a follow-up instead of filling the gap with a guess. Apply the same process consistently so that readers can understand the basis and limits of the information.

Build a repeatable review cycle

Assign an owner for the reporting calendar, data validation, exception handling and sign-off. Test a sample of records against source statements and document reconciliation differences. Keep the version of the rules used for each reporting period, and update procedures when SARS releases new technical guidance. A review log makes it easier to explain how a report was prepared.

Keep the original source, the date checked and a short note explaining what the evidence supports. This makes later review quicker and helps distinguish a verified fact from an interpretation. If an item cannot be confirmed, record that limitation clearly and assign a follow-up instead of filling the gap with a guess. Apply the same process consistently so that readers can understand the basis and limits of the information.

Practical checklist for South African CASPs

Map the reporting entity and services, verify the current SARS CARF guidance, document customer and transaction data fields, retain source records, reconcile exceptions and assign review responsibility. Confirm licensing questions separately with the FSCA because tax reporting does not replace financial-sector authorisation. South Africa crypto reporting 2026 should be approached through official sources and qualified tax advice for individual cases.

Keep the original source, the date checked and a short note explaining what the evidence supports. This makes later review quicker and helps distinguish a verified fact from an interpretation. If an item cannot be confirmed, record that limitation clearly and assign a follow-up instead of filling the gap with a guess. Apply the same process consistently so that readers can understand the basis and limits of the information.

Source: https://www.sars.gov.za/businesses-and-employers/third-party-data/crypto-asset-reporting-framework-carf/. See also Crypto Compliance and Risk and the South African English blog. Check current official guidance.