What Makes Crypto Transaction Data Audit-Grade? A Checklist for Finance Teams

A blockchain transaction hash is useful evidence, but it is not a complete accounting record. It can show that assets moved between addresses at a particular time. It usually cannot explain who controls those addresses, why the payment occurred, who approved it, which invoice it settled or how it was valued in the reporting currency.

Audit-grade crypto data connects the blockchain event to the company, the underlying business activity and the general ledger. The term is not a formal certification: the auditor remains responsible for deciding whether evidence is sufficient and reliable. For finance teams, the practical objective is to maintain records that are complete, traceable and reproducible.

The minimum record for every crypto transaction

Each incoming or outgoing transaction should have a structured record containing the fields below. Store the chain name as well as the transaction hash because the same stablecoin may exist on several networks.

Evidence that the company controls a wallet

Wallet accounting starts with a complete wallet register. For each address, record the legal entity, purpose, blockchain, asset scope, opening date, operating status and responsible treasury owner.

Evidence of ownership or control may include:

• Wallet-creation or custody records linking the address to the company.
• A message signed by the wallet, where the network and company policy support this method.
• A controlled test transaction with documented authorization.
• Vault configuration showing the address and authorized signing arrangement.
• Board, treasury or account-opening documentation assigning the wallet to the entity.

For a self-custodial MPC vault, no single private key may exist. MPC, or multi-party computation, distributes signing authority among several participants or devices. In that case, retain the vault configuration, signer or quorum policy, changes to authorized participants and the audit log connecting human approvals to the resulting transaction. The blockchain will generally show the wallet signature, not the identities of the individual internal approvers.

Fiat values need a reproducible methodology

Do not automatically record every stablecoin at exactly one US dollar. USDC and USDT can trade above or below their reference value, and a company reporting in EUR or GBP must also apply a foreign-exchange rate.

The accounting policy should specify:

• The approved price source and market.
• Whether valuation uses the execution price, a timestamped spot price or a defined daily rate.
• The timezone and cut-off applied at period end.
• How spreads, network fees and provider charges are classified.
• How missing or anomalous prices are reviewed.

For an on-ramp or off-ramp, preserve the provider quote, gross fiat amount, stablecoin amount, exchange rate, each fee and the bank or blockchain settlement reference. This makes it possible to reconcile both sides of the conversion rather than treating the fiat and crypto records as unrelated events.

Document approvals and counterparties

An approval screenshot is weaker than a structured audit log. The transaction record should show who requested the transfer, who approved it, when each action occurred and which policy applied. For quorum signing, retain evidence that the required number of approvals was reached before execution.

Counterparty evidence should connect the address to a legal or operational record. That may be a supplier onboarding file, invoice, employment record, customer order or account statement from an exchange. If sanctions or wallet screening is required, preserve the result, provider, timestamp and disposition of any alert—not only the latest risk score. Teams can also use a wallet screening tool such as Stablerail’s wallet checker as part of their documented review process.

Reconcile by asset, wallet and network

A monthly reconciliation should prove the movement from opening to closing balance for each asset on each network:

Opening balance + inflows − outflows − network fees ± documented adjustments = closing balance

Compare the calculated closing balance with an independently retrieved onchain balance and the corresponding general-ledger balance. Reconcile fiat accounts separately, then match on-ramp and off-ramp transactions across the two ledgers.

Use explicit statuses such as unmatched, matched, exception, reviewed and closed. Exceptions should have an owner, explanation, supporting evidence and resolution date. Common exceptions include failed or replaced transactions, deposits routed through exchange omnibus wallets, fee differences, duplicate imports and transfers that cross a reporting cut-off.

Batch payments need both levels of evidence: the blockchain transaction or transactions and the underlying list of recipients, amounts and business references. This is especially important for vendor and contractor runs made through a stablecoin payout workflow.

How to preserve exports and audit evidence

Blockchain explorers are useful for independent verification, but bookmarks and screenshots should not be the only retained evidence. Interfaces change, labels can be edited and third-party services may become unavailable.

• Export at period close: Preserve wallet activity, balances, approvals, screening results, fiat statements and ledger mappings for the reporting period.
• Keep the original file: Retain source CSV, PDF or JSON exports without overwriting them during spreadsheet cleanup.
• Create a working copy: Perform mapping, classification and reconciliation in a separate file with documented transformations.
• Record provenance: Note the system, export time, timezone, filters, user and covered date range.
• Protect integrity: Store files in a controlled repository with access restrictions, version history and retention rules. A SHA-256 file checksum can help demonstrate that an export has not changed.
• Preserve the audit trail: Retain corrected classifications, deleted records, approval changes and wallet allowlist changes rather than showing only the final state.
• Test retrieval: Confirm that another finance team member can reproduce a sample transaction from ledger entry to approval, invoice, wallet record and blockchain confirmation.

Stablerail treasury workflows can combine self-custodial MPC vault activity, quorum approvals, allowlists, screening records and audit logs into evidence packs. Finance teams should still align exports and retention periods with their accounting policy and auditor’s requirements. Product and export guidance is available in the help centre.

Period-end checklist

• All company-controlled and third-party custody wallets are included in the wallet register.
• Every transaction includes its hash, chain, timestamps, asset, amount, addresses and confirmation status.
• Network and provider fees are recorded in the correct asset and ledger account.
• Fiat values can be reproduced from the documented source and methodology.
• Each movement has a business purpose, counterparty and supporting document.
• Required approvals and quorum decisions are linked to the executed transaction.
• Wallet and sanctions screening evidence is retained as of the relevant date.
• Opening balances, activity and closing balances reconcile by wallet, asset and network.
• Unmatched items and exceptions have an owner and resolution status.
• Original exports, working files and final evidence packs are retained with version history.

The central test is straightforward: can a reviewer start from a ledger entry and independently trace it to the business document, approval, wallet, fiat valuation and confirmed blockchain event? If the answer is yes—and the same process works from the blockchain back to the ledger—the transaction records are much closer to being audit-ready.