Keep staking rewards, airdrops and mining receipts as separate event types. They can have different facts about entitlement, control, restrictions and value. A single “free crypto” label loses information needed to establish the nature and timing of the receipt.
SARS's general guidance applies ordinary income-tax principles to crypto assets, but that does not settle every new reward arrangement. This article provides a record structure, not a blanket rule that all rewards become taxable at the same moment or carry the same cost treatment.
Record entitlement and access separately
For each event, note when the reward was announced, when an entitlement arose, when it was credited and when it could be transferred or sold. Those may be different dates. Do not assume a displayed dashboard number proves receipt or accrual for tax purposes.
Save the programme terms and any vesting, lock-up, withdrawal or clawback conditions. If those terms change, keep the version applying to your event. A current web page may not explain a reward credited months earlier.
Three records, three factual questions
| Activity | Evidence to retain | Tax question to resolve |
|---|---|---|
| Staking | Stake or delegation record, reward statement, lock-up terms and fees | When did the entitlement or receipt arise, and what is its nature? |
| Airdrop | Distribution terms, eligibility, claim action, restrictions and token identity | Was there an enforceable entitlement or usable receipt, and how is it valued? |
| Mining | Pool statements, blocks or payout records, operating costs and equipment records | What income and expense treatment applies to the activity? |
Do not call a lending reward “staking” merely because an app groups both under Earn. Preserve the actual arrangement and counterparty. The stablecoin guide explains why a token and a separate yield product should not be treated as the same thing.
An unsolicited token appearing in a wallet is also not an invitation to interact with it. Do not visit an unknown claim site or sign a transaction just to establish a value for a spreadsheet. Record the observation and ask your reviewer how to handle it safely.
A hypothetical rewards ledger
These examples demonstrate multiplication and evidence fields. None establishes the legally correct recognition date, a market quote or an approved tax conclusion.
| Candidate event | Quantity | Assumed rand unit value | Candidate value for review |
|---|---|---|---|
| Staking reward credited | 0.5 token A | R200 | R100 |
| Airdrop allocation, restrictions unresolved | 40 token B | Not reliably established | Unresolved, not automatically zero |
| Mining pool payout | 0.001 BTC | R1,200,000 | R1,200 |
The airdrop row remains incomplete because the facts do not support a reliable value or timing conclusion. Entering R0 simply to make software accept the file would conceal that issue. Add the token contract, network, available market evidence and restriction details to the review file.
For the mining row, keep expenses separate. An electricity bill for your entire household is not automatically a deductible mining cost. A reviewer needs a defensible allocation and the applicable rules before an expense is claimed.
Keep later disposals connected
Suppose token A is later sold for R140 with a R2 fee. Assuming a R100 allowable cost and an allowable fee solely for this arithmetic illustration, the illustrative later difference is R140 - R2 - R100 = R38.
Do not use that assumption until the initial receipt's treatment and later cost are settled. Otherwise you risk counting the same value twice or omitting part of the taxable history. Preserve the original reward ID so the sale can be linked back to its source.
If rewards are pooled with purchased tokens, maintain sufficient detail for the applicable cost-allocation method. A single current wallet balance cannot reconstruct which events created it.
Prepare an annual review pack
Export reward statements, transaction history, fees and disposals before platform access changes. Record time zones consistently. Reconcile opening units plus receipts and purchases, less transfers and disposals, to closing units, with explanations for any differences.
Attach a list of unresolved events rather than presenting them as completed tax calculations. The SARS guide and wallet hub provide adjacent context. SARS’s general crypto guidance does not provide a universal recognition rule for every staking or airdrop arrangement. The ledger therefore records the facts without assigning a tax date or cost to an uncertain event. Resolve those points before using it to file a return.
Sources and verification
Primary SARS guidance read on 20 September 2026. The linked FAQ was reviewed by SARS in 2021. The examples are original arithmetic illustrations; they do not determine the tax treatment of an individual transaction.