Preparing workspace
Loading the latest tax workspace context
We're checking your organization, active taxpayer, and operational state so the next screen arrives in a clean, trustworthy state.
We're checking your organization, active taxpayer, and operational state so the next screen arrives in a clean, trustworthy state.
Use the on-site assistant for access help, simple next-step guidance, exchange setup basics, and basic tax-flow questions.
Use this for access help, next-step guidance, exchange setup basics, and simple tax-flow questions.
Browse the most useful answers by topic, or ask a question in plain language.
Follow the main flow in order: choose where the crypto activity is held, add a read-only API connection or upload CSV files, import the activity, review anything flagged, generate the report, then download it and submit through SARS eFiling.
Use Connect accounts to save the exchange or source first. For custodial exchanges, the normal path is read-only API access or CSV upload. You can save the source now and finish the setup later if needed.
Yes. The access flow supports both Google sign-in and standard email plus password access, so users can choose the simplest path for them.
Use the forgot password flow from the sign-in page. Enter your email, open the secure reset link, and choose a new password before signing back in.
Open the invitation link you received, sign in or create your account if needed, then accept the workspace invitation to land inside the correct organization.
Use Import activity to upload raw CSV files or import from a saved read-only exchange connection. CSV is usually the quickest first step, while API-ready sources are better for ongoing updates.
This is where you fix anything blocking a clean report, like missing values, unmatched transfers, or classifications that need a decision before the report is generated.
Use Generate report once imports are clean. From there you can create the tax-year snapshot, generate the taxpayer PDF, and download the files you need.
After downloading the taxpayer PDF, open SARS eFiling and complete the return there. The app prepares the report and supporting files, but the final submission still happens inside SARS.
Use CSV upload when you want the fastest first estimate or you already have export files ready. Use read-only API access when a supported exchange should keep pulling activity over time. Self-custody wallet imports are a separate path and are not the same as exchange account setup.
Exchange imports are for custodial platforms like Binance, Luno, VALR, or Bybit, where activity comes in through read-only API access or CSV exports. Self-custody wallet imports can use EVM, Avalanche C-Chain, Solana, or Bitcoin public addresses, or wallet CSV, and must never include seed phrases, private keys, or wallet passwords.
The product currently supports Luno, VALR, Binance, and Bybit with validated API or CSV paths, plus EVM, Avalanche C-Chain, Solana, and Bitcoin public wallet addresses, wallet CSV, Coinbase, Kraken, and a manual CSV fallback for lighter imports.
No. The source name is your own internal label so you can recognize the account later. Keep it simple and clear, like 'Russell Binance account' or '2025 Luno CSV'.
The app helps separate disposal gains from revenue-style income, but this is still a guidance layer rather than legal advice. If something looks unclear, review the treatment carefully or ask a practitioner before filing.
It can explain how the product works and answer basic tax-flow questions, but it should not replace practitioner advice or official SARS guidance for complex filing decisions.