Digital Asset and Crypto Tax: Common Questions

Trading one coin into another means you have disposed of what you held, so the value in baht at that moment is measured against the cost you already carried. The frequent misunderstanding is to wait for a bank withdrawal before counting anything, which is exactly why heavy trading years with no withdrawal end up with the thinnest records.

Paying with tokens works as two legs at once: the coin is disposed of at its value that day, and the proceeds settle the bill. You therefore need both the value at the moment of payment and the cost of the specific batch spent. A merchant receipt alone does not do the job, because it says nothing about the payer's cost side.

Shifting coins between wallets you own does not create income, but it must be flagged as such. Otherwise the calculation tool reads the outgoing leg as a sale and the incoming leg as a fresh purchase, and phantom gains appear on holdings you never let go of. Matching those transfer pairs is where most of the data work actually goes.

Tokens received at no cost are a benefit measured on the day you can actually use or transfer them, and that same figure becomes the cost base when the batch is later sold. The recurring complication is that the receipt date and the unlock date differ, so record both while they are still visible on-chain.

Use a price you can point back to from the venue where the trade actually happened, and stay with the same source for the whole year. Hopping between sources transaction by transaction makes the figures hard to defend when someone asks. Keep the timestamped export or capture alongside them, not just a number typed into a spreadsheet.

Pick a matching convention and hold to it for the full year rather than choosing per trade whichever lot flatters the result. Most people order by acquisition sequence simply because it is the easiest to retrace. What matters more than the choice itself is documenting which convention you adopted and applying it identically across every account.

Charges tied directly to acquiring or disposing of a position generally belong in the calculation, provided they are separated from general account charges that attach to no particular trade. The step most often missed is a fee deducted in tokens, because that deduction itself has to be valued.

Whether an offset is available depends on the channel the trades ran through and on whether you act as an individual or through a company, so no single answer fits everyone. What you can do straight away is keep the data separated by source, because once everything is merged into one pile no later claim can be evidenced.

It counts when the reward lands under your control, valued at that day's price rather than waiting for a sale. Related costs such as electricity and equipment depreciation need evidence that separates them from household spending, so anyone mining at home should either meter the rigs separately or keep an allocation method they can explain.

Both hand you additional tokens, but the underlying arrangement is not the same, so the classification can differ and with it both the rate and the way it is reported. Keep the programme terms you accepted, the lock-up period, and the per-period receipts — those three are what a classification argument rests on.

Remuneration settled in tokens is still remuneration: convert it to baht on the payment date and run it through the same channel as a cash payment. The paying side carries its usual obligations too, so ask for a payment record that already states the baht value rather than reconstructing it yourself months later.

It depends on volume, regularity, and whether there are real expenses you want recognised. A company adds annual obligations and fixed costs, which rarely pays off for modest activity. We look at a full year of transactions before giving a view, because unwinding a structure later is not free.

The base set is a transaction export from every venue used, the bank movements connected to them, a list of wallet addresses you control, and a note of which transfer legs pair with which. Together those four let you narrate the route of the money end to end, which is what a reviewer wants far more than a summary figure.

Rebuild from whatever survived: confirmation emails, on-chain transfer history, and the bank's record of money in and out — then write down precisely how you reconstructed it. A reconstructed set whose origin you can explain is in a far better position than a gap left blank.

Start by sizing what is outstanding before deciding anything: gather the data year by year and see which years actually move the needle, rather than filing everything at once without knowing the numbers. Coming forward voluntarily generally lands better than waiting for a query, and we sequence the years by risk.

Read carefully which year and which group of transactions is being asked about, then answer exactly that scope with evidence that ties item to item. Handing over an unsorted pile tends to widen the enquiry. We can assemble the response set and attend the explanation, quoting once we have seen the volume involved.

Send the raw exports each venue gives you, plus the list of wallet addresses you control; that is enough to scope the work. Please do not tidy the tables first — reformatting is what usually drops the timestamp and fee columns, and those are the two we lean on most.

The clock is driven less by line count than by how many venues are involved and how complete the files are. Complete data from a handful of venues usually wraps within a few weeks; anything needing reconstruction runs materially longer. We give a timeframe after reviewing the first batch of files.

We quote case by case once the real scope is visible: how many venues, how many years, and how much has to be rebuilt. There is no packaged price on the site because two cases with identical transaction counts can differ several times over in effort.

Pull the exports quarterly into one place and log every new wallet address the day it is created. That alone removes most of the year-end crunch. We hand over the filing structure we used so you can keep running it without staying tied to us.