Records guide

Crypto tax records in Australia: what to track before you estimate

The estimator is intentionally manual, so the quality of the result depends on the quality of the transaction data you put into it. If your records are weak, the app will still return numbers, but the estimate will not deserve trust.

Track the date and AUD value

Those two fields drive both income timing and cost-base logic. If either one is vague, the estimate becomes weak fast. This matters for both staking receipts and CGT disposals.

Track fees separately

Fees change both acquisition cost and disposal economics. This version allows you to enter the fee in AUD on each event. If you fold fees into rough total values instead of tracking them clearly, the cost base can drift.

Track what asset came out and what came in

For swaps, you need both sides of the transaction. The outgoing token drives the CGT event and the incoming token becomes a new parcel. If either side is missing, the year-end holding picture will be wrong.

Track source context when the event type is not obvious

Some wallet activity is easy to misread after the fact. A short note like “staking reward”, “rebalance swap”, or “sell to AUD” can make later manual entry much easier, especially if multiple transfers happened on the same day.

A practical minimum record set

For this app, the practical minimum is: date, disposed or acquired asset, quantity, AUD value, fee in AUD, and enough notes to tell a buy, sale, swap, or staking receipt apart. That is enough to get value from the current estimator even before you build a more complete tax ledger.