Accounting for Crypto Payments Received

What is the basic treatment?

Crypto received in exchange for goods or services is revenue, valued in your reporting currency at the point of receipt. That much is consistent across most jurisdictions and is not the difficult part.

The difficulty starts if you keep it. Holding the asset means its value moves, and disposing of it later is generally a separate event with its own gain or loss. Now you are tracking a position as well as running a business.

Why converting on receipt matters

It removes the second event. If the provider converts as the payment settles, the amount you booked as revenue is the amount you received, and there is no holding period to account for.

That is the real reason most merchants choose fiat settlement, and it is worth more to a finance team than the spread costs. A treasurer weighing a 1% conversion cost against maintaining a crypto position across a reporting boundary will usually take the 1%.

What should you ask a provider for?

A settlement report, per transaction, containing the gross amount, the fee, the conversion rate applied, and the net received. Exportable in a format a spreadsheet can read.

This sounds obvious and providers vary enormously. Some give a clean report, some give a dashboard that cannot be exported usefully, and some give a chain explorer link and leave the reconstruction to you. Ask to see a real export before signing rather than after your first quarter end.

Also ask how long history remains available after an account closes. Reconstructing a year of settlements from chain data is expensive, and the switching pages treat exporting history as the first step of any migration for that reason.

Where does the fee actually appear?

Often nowhere useful. The processing fee is usually itemised. The conversion spread frequently is not, because it is embedded in the rate rather than charged as a line.

For a finance function that wants to know the cost of accepting crypto, an unpublished spread means the number cannot be produced from the reports. That is worth raising during selection, since a provider that shows the rate applied alongside the market rate at that moment is giving you something most competitors do not.

What about VAT and sales tax?

Unchanged by the rail. A sale is a sale regardless of what the customer paid with, and the tax treatment of the underlying transaction does not move because the settlement asset did. Confirm the specifics locally, since the interaction with settlement timing differs by jurisdiction.

What a usable settlement report contains

Per transaction: the date, the asset received, the quantity, the market value at receipt in your reporting currency, the provider fee, the conversion rate applied, and the net amount settled. Exportable as CSV.

Providers vary enormously here. Some produce exactly that. Some produce a dashboard that cannot be exported usefully. Some produce a chain explorer link and leave the reconstruction to you. Ask to see a real export before signing rather than at your first quarter end.

The two events, restated

Receipt is income at the value on the day. Disposal is a separate event with its own gain or loss. Converting on receipt collapses them into one because the holding period is effectively zero.

That is the whole of the simplification, and it is why most merchants settle to bank currency despite paying a spread for it. The spread is a known cost; a tracked position is an ongoing obligation on somebody’s time.

What changes if you hold

You need cost basis tracking per lot, a policy on which lots are disposed first, and a valuation at each reporting boundary. None of that is exotic and all of it is work that did not exist before.

If the business genuinely wants the exposure, that work is the price of it. If the exposure arrived because settling in crypto was the default, the work is pure overhead and converting removes it.

What does not change

The tax treatment of the underlying sale. VAT, sales tax and revenue recognition follow what you sold, not what the customer paid with. That is worth stating plainly because it is a common source of hesitation with a simple answer.

Where to go next

The settlement entry covers the terms that decide when revenue actually lands. The volatility guide covers the conversion decision that determines whether you have one taxable event or two, and the country pages cover jurisdiction-specific treatment.

Getting finance involved early

Before choosing a provider rather than after, because the settlement report format is effectively unchangeable once you have integrated, and it is the artefact your finance function lives with.

Show them a real export from two candidates and ask which they can work with. That takes an hour and it prevents the most common post-integration complaint in this category, which is that the numbers are all there and none of them are usable.

Reconciliation as an accounting control

The scheduled comparison between your records and the provider’s is a payments safeguard and an accounting one. It is what lets you assert that recorded revenue matches settled funds, which is the assertion an auditor will eventually ask you to support.

Run it on a schedule, keep the output, and alert on discrepancies rather than logging them quietly. A discrepancy found the same week is a question; the same discrepancy found at year end is an investigation.

The cost is a scheduled job and somewhere for it to report. The alternative is trusting a callback path that is delivered over a network which loses things.

If you take one action from this guide, ask two shortlisted providers for a sample settlement export and show both to whoever closes your books. That single hour prevents the most common complaint in this category, which is that all the numbers exist and none of them are in a usable shape.