CARF & regulatory
Prepare the report, expose the exception, preserve the correction.
Build reviewable CARF data from reconciled events, validate it against a pinned schema and retain immutable release and correction lineage.
Final filing acceptance pending
- Prepare
- User, wallet and transaction categories.
- Validate
- Schema and business-rule findings.
- Correct
- Superseding version and reason lineage.
Reporting is an evidence workflow
- Separate new-data, correction and no-data messages.
- Trace report totals to canonical events and evidence.
- Require named preparation and independent release approval.
- Keep submitted versions immutable and corrections explicit.
- Orchestrate specialist KYT and Travel Rule providers without replacing them.
South African implementation boundary
SARS states that applicable reporting CASPs—not individual taxpayers—carry CARF reporting obligations. ChainClose currently provides preparation and validation foundations; it does not claim to be a reporting CASP or to have filed a return.
Official sources
External references used for the factual and regulatory context on this page.