Published on: Aug 5, 2026
Last modified on: Aug 5, 2026
Crypto payment accounting is where digital transactions meet everyday finance. This guide shows how businesses can keep crypto payments clear, consistent, and ready for reporting.
Accepting cryptocurrency introduces accounting considerations that do not arise in exactly the same way with conventional payment methods. Finance teams therefore need a consistent framework that allows crypto transactions to move through the company’s existing accounting processes without creating unnecessary manual work or uncertainty.
Defining that method before transaction volumes increase supports a more controlled close and allows unusual transactions to be resolved without creating a new accounting approach each time.
A customer paying in crypto does not necessarily mean that the business receives or holds crypto. Under a fiat-settlement model, the payment provider receives the customer’s crypto, converts it, and settles the merchant in euros, dollars, or another fiat currency. If the business never obtains control of the crypto, it does not recognize that crypto as an asset. Instead, it records the amount due from or received through the provider in its functional currency. Subsequent movements in the crypto asset’s market price therefore do not affect the company’s accounts.
Transacta is one example of this approach, where crypto payments are converted into fiat and settled to the merchant’s corporate IBAN. The platform-generated invoice and settlement information allow finance teams to record the transaction using much the same process as for a conventional fiat payment.
If the business receives and retains the crypto, the asset enters its books and must be valued when received and accounted for at period-end. The settlement model therefore determines which of the accounting requirements discussed below apply.
Once the settlement model has been established, the company should create a repeatable policy that identifies:
the company’s functional currency
the event that constitutes receipt
the approved valuation source and timestamp
the relevant ledger accounts
materiality thresholds for minor discrepancies
the people responsible for review and approval
Digital assets may show different prices across exchanges, providers, and timestamps. If one accountant uses the checkout quote, another uses the blockchain-confirmation time and a third relies on a later conversion rate, economically similar transactions may enter the books at different values.
IAS 8 requires companies applying IFRS to use judgement when no specific standard directly addresses a transaction and to select policies that produce relevant and reliable information. The policy should therefore specify which source takes priority when records conflict, when an exception must be escalated, and how the selected method will be applied consistently.
The payment method should not determine when revenue is recognized. Rather, revenue should follow the customer contract and the transfer of the promised goods or services. IFRS 15 states that revenue is recognized to depict that transfer in the amount of consideration to which the company expects to be entitled.
Suppose a business issues a €10,000 invoice and the customer pays in USDC. The records should still show a €10,000 sale under the company’s normal revenue-recognition policy. The payment then clears the receivable and creates the appropriate digital-asset, cash, or payment-provider receivable entry.
This distinction is important when payment and delivery occur at different times. A customer may prepay or settle an invoice after completion. Others can make several partial payments. Treating the payment itself as revenue may distort cut-off and place income in the wrong reporting period. The invoice, revenue-recognition event, and crypto transaction should therefore remain linked but be recorded as separate accounting events where appropriate.
Where the business receives crypto, the asset must be recorded in the company’s functional currency. The accounting policy should define both the valuation event and the approved pricing source. Possible valuation events include:
payment initiation
network confirmation
payment-provider acceptance
the point at which the company obtains control of the asset or an enforceable right to payment
For U.S. tax purposes, the IRS states that digital assets received for services are measured at fair market value when received. Businesses in other jurisdictions must apply their own accounting and tax rules. The transaction record should capture:
the invoice or order ID and customer reference
the invoiced currency and amount
the crypto asset, network and quantity received
the transaction timestamp and blockchain identifier
the payment status
the fiat rate, valuation source and recorded fiat value
any applicable fees
Stablecoins may reduce short-term price volatility, but they must still be valued in euros, dollars, or another functional currency. Capturing this information when the payment is received reduces reconstruction work during reconciliation and the period-end close.
The amount credited to the business may be lower than the invoice value because of:
payment-processing fees
blockchain network charges
conversion costs
withdrawal and payout fees
Recording only the net amount may understate both revenue and expenses, so each identifiable deduction should be recorded separately. Assume a customer settles a €5,000 invoice and the payment report shows net proceeds of €4,950 after a €50 processing fee. Subject to the company’s policy, the records would normally preserve the €5,000 commercial value and recognize the €50 separately as an expense.
U.S. digital-asset guidance similarly distinguishes the value of property or services from qualifying transaction costs in relevant transactions. The precise treatment depends on the facts and jurisdiction. Regardless of that treatment, the gross payment, identifiable deductions, and resulting balance should remain visible.
Crypto payments become more difficult to account for when the amount received does not match the amount expected. Businesses should define procedures for:
underpayments
overpayments
duplicate payments
expired quotes
refunds
An underpayment may remain as an open receivable or be written off when it falls below an approved materiality threshold. It can also trigger a request for the outstanding balance. On the other hand, an overpayment may create a customer liability until the excess is refunded or applied to another amount owed. Similarly, a payment received after a quote expires may need to be valued using the rate required by the company’s policy rather than the original checkout quote.
Refunds should be recorded as new accounting events rather than by deleting or reversing transaction history without explanation. The refund record should:
link to the original sale
identify the asset and quantity returned
explain whether the refund is based on the original crypto quantity or a stated fiat-value policy
record any additional fee or price difference
Stripe notes that businesses accepting crypto need a formal refund policy and commonly return the original coin amount unless their policy provides for fiat conversion. An exception matrix can clarify which differences may be resolved automatically, which require commercial approval and which need accounting, legal, or tax review. Further guidance on crypto payment exception handling is available in the related article by Coman (2026).
Crypto payment reconciliation should compare:
the sales ledger
the payment transaction
the resulting account or balance movement
The finance team should confirm that:
each sale has the correct payment status
each incoming payment has a valid commercial explanation
the recorded fiat value agrees with the invoice after accounting for identifiable fees or approved differences
An on-chain transaction alone may not establish that the process is complete. Provider acceptance, settlement conditions, or internal control requirements may still be outstanding. Duplicate receipts should not be recognized as additional revenue, and every outgoing transfer should have a documented accounting explanation.
Structured payment data can automate routine matching and direct finance staff towards unmatched items, unusual rates, and incomplete records. Transacta’s merchant dashboard includes transaction-status tracking and detailed reports, while locked-in exchange rates and audit-ready transaction records support payment matching and the investigation of accounting discrepancies. Coinbase’s business invoicing documentation offers another example of structured invoice data.
Account for Crypto Retained at Period-End
When a digital asset remains on the company’s books after receipt, the finance team must apply the relevant subsequent-measurement policy. Changes in value after initial recognition belong in the period-end close rather than in the original sales entry.
Under U.S. GAAP, FASB Accounting Standards Update 2023-08 requires in-scope crypto assets to be measured at fair value in each reporting period, with changes recognized in net income. Under IFRS, the Interpretations Committee concluded that IAS 2 applies when cryptocurrencies are held for sale in the ordinary course of business. Otherwise, IAS 38 applies to cryptocurrency holdings within the scope of its analysis.
The closing process may require the business to:
reconcile the number of units held
confirm control over wallets, accounts or custodial balances
apply the approved measurement method
record required fair-value or impairment movements
prepare the relevant disclosures
The company may also need to calculate a realised gain or loss using the applicable cost-basis rules when an asset is later:
sold
converted
refunded
used
Stablecoins should remain within the close even when they target a stable value. Their units, classification, access rights, and relationship to the company’s functional currency still require verification.
The accounting file should allow a reviewer to trace each payment from the underlying sale through receipt, valuation, and any later disposal. The IRS requires taxpayers to maintain sufficient records to substantiate their digital-asset transactions, including the reported value, cost basis, and information concerning any subsequent disposal where relevant.
Accepting cryptocurrency does not change the tax treatment of the underlying commercial supply. EU VAT rules generally apply to taxable supplies of goods and services according to the nature, location, and timing of the supply. The European Commission explains that VAT is normally calculated as a percentage of the sales price and generally becomes chargeable when the goods or services are supplied, subject to rules covering matters such as advance payments.
Finance teams should distinguish the tax treatment of the sale from the evidence required to explain the crypto payment. Retention periods should follow the applicable accounting, company-law, and tax requirements in each jurisdiction.
By way of one documented and consistently applied process, crypto payment accounting should connect:
settlement model
revenue recognition
fiat valuation
fee recording
exception handling
reconciliation
period-end measurement
A process that depends heavily on manual interpretation may be manageable when payments are occasional, but it can create delays and inconsistencies as volumes grow. Putting the right structure in place early helps the business accept crypto without compromising the quality of its financial reporting.