Your first CARF return is due 31 May 2027.
Be ready long before that.
Since 1 March 2026, every FSCA-licensed crypto-asset service provider must collect tax-residency self-certifications from every user and file a full transaction report with SARS. CarfReady handles both — collection, validation, and a return that passes SARS's own schema before you submit it.
From user list to filed return, in three steps
Collect self-certifications
Send each user a hosted link under your name. The form captures exactly what the OECD standard requires and rejects incomplete answers on the spot — SA ID check digits included. Your dashboard shows the re-papering burn-down.
Upload your transaction log
Drop in your back-office export — common exchange formats are recognised and converted automatically. Every gap becomes a punch-list item with a row-level reference, not a rejection letter from SARS.
Download the return
One click aggregates per user, asset and transaction category, validates against SARS's published schema, and names the file per the eFiling convention. Corrections after filing are one upload away.
Built for the whole obligation, not just the form
Due-diligence punch list
Missing residencies, malformed TINs, users you must halt — every problem listed with its source row, ordered for your compliance officer.
Schema-valid by construction
Every return is validated against the official SARS XSD bundle before you ever see a download link. If it downloads, it parses.
Corrections that follow the BRS
CARF702 correction messages with proper DocRefID lineage, generated from the manifest of your original filing.
Deadline telemetry
Re-papering and filing countdowns on every screen. The regulation has two dates that matter; you'll never lose sight of either.
Pricing
Portal
- Hosted self-certification portal under your name
- Unlimited invite links & submissions
- SA ID / TIN validation at the point of capture
- Re-papering burn-down dashboard
- users.csv export, yours anytime
Complete
- Everything in Portal
- Transaction-log ingestion with exchange-format adapters
- Due-diligence punch list across users and transactions
- Schema-valid CARF returns, BRS-named for eFiling
- CARF702 corrections with DocRefID lineage
- Filing-season support
Questions CASPs actually ask
We already have a compliance officer. Why do we need software?
Your compliance officer is exactly who this is for. CARF is an annual, schema-validated XML filing plus a standing due-diligence duty across your whole user base. CarfReady does the mechanical work — collection, validation, aggregation, XML — so your officer spends their time on judgement calls, not spreadsheets.
What happens if a user never completes their self-certification?
The regulations require you to halt transactions for new users without a valid self-certification, and to re-paper existing users within 12 months of 1 March 2026. CarfReady's dashboard shows exactly who is outstanding so you can chase, restrict, or escalate before the deadline.
Our transaction data lives in our own back office. How does it get in?
Export it as CSV. Canonical columns work directly; common exchange export shapes (side/pair/volume/total) are recognised and converted automatically. Anything ambiguous is flagged by row — nothing is guessed silently.
What if we discover an error after we've filed?
Every CarfReady return ships with a manifest recording its MessageRefID and per-user DocRefIDs. Rebuild with only the corrected users and CarfReady produces a BRS-compliant CARF702 correction referencing the original records.
Is CarfReady itself regulated? Do you see our users' data?
CarfReady is software tooling; the reporting obligation stays with you as the RCASP. Your workspace data is yours — export it at any time. We are not a tax practitioner and nothing here is tax or legal advice.
The clock started on 1 March 2026.
Early-access workspaces are onboarding now. Bring your user list; leave with a live self-certification portal and a dry-run return the same week.
Request early access