Stablecoin records your working file can explain.

Agree the engagement and wallet scope

Begin with a list of addresses the client says belong to the business, the networks on which they operate, and the reporting period. Ask who controls each address and whether a payment processor, exchange or custodian is involved. A public address does not prove beneficial ownership. An exchange deposit address may represent a different service relationship from a self-controlled wallet.

Record these answers outside the transaction feed. The proposed workflow starts with one wallet and one identified asset per statement, so reviewers can see precisely what has been included. A future multi-client overview is planned; it should not conceal missing wallets or merge clients merely because a counterparty appears in both files.

Build the evidence trail before assigning accounts

For each movement, retain the token contract, chain, transaction reference, event index, timestamp and exact quantity. These identify the technical observation. Separately attach the invoice, credit note, expense receipt or explanation supplied by the client. A transfer’s existence does not tell you whether it settles revenue, moves treasury funds, repays a loan or returns a deposit.

Use a stable reference to connect those documents. If the invoice says CHF 900 and the wallet receives 1,000 USDC, the statement should not silently decide that they are equivalent. The relevant payment terms, exchange-rate policy, settlement timing and any residual remain matters for the accounting workflow.

Keep quantity, price and native fees separate

A token quantity is measured in the identified token. A CHF value is a separate observation that needs a source and time. The sample deliberately leaves one price unknown; an incomplete valuation must not turn into a complete-looking total. Before a real report, agree whether transaction-time prices, settlement prices or another documented basis are appropriate for each use.

Gas paid by the wallet is another asset movement. On Ethereum this is normally ETH; on BNB Smart Chain it is BNB. Do not reduce the USDC quantity by an ETH fee. A processor-paid or third-party-initiated transfer may have no gas paid by the client wallet, so the fee payer matters as much as the transaction direction.

Review the balance comparison and its limitations

The basic test is opening quantity plus incoming movements minus outgoing movements equals closing quantity. Compare that calculated result with a separately read token balance at the same cutoff. The contract, wallet and boundary blocks must match on both sides. Comparing a present-day explorer balance with last month’s event ledger does not test the same assertion.

Where the result differs, preserve both values and the residual. Request missing blocks or inspect unsupported event behaviour rather than adding a balancing payment. Even an exact match does not prove all economic activity has been understood: excluded assets, other wallets, invoices and ownership remain outside that arithmetic test.

Assemble a file another reviewer can follow

A practical evidence package contains the readable statement, row-level CSV and structured JSON, together with the input scope, cutoff convention, source references and exclusions. Keep the client’s explanation and booking decisions beside the technical records. A reviewer should be able to distinguish an observed transfer from a later classification without reconstructing your spreadsheet edits.

The sample content hash identifies a particular version of the underlying record. It is useful for detecting that content changed, but it is not a signature or proof that the observations are true. Record who reviewed the file and how unresolved questions were handled. Revision, assurance and final accounting judgements remain with the responsible professionals.

What an accounting import would need

The proposed PDF, CSV and JSON serve different purposes. PDF is readable evidence; CSV exposes rows; JSON retains structured context. None automatically supplies your chart of accounts, VAT decision, client identity or matching rules. A usable importer needs those mappings, duplicate protection, a rounding policy and a deliberate treatment of missing values.

camt.053 is an early investigation. SIX specifies bank-statement structures, and Bexio documents bank-transaction uploads, but that does not establish a compatible wallet account. USDC and USDT cannot simply be placed in a three-letter currency field. A CHF projection would need actual valuation rules and separate token quantities. Bexio and Abacus acceptance must be tested per target version; no universal import is promised.

Use the sample in a short client-file review

Before building a large workflow, take one synthetic statement through your normal review process. Can a colleague identify the period, compare the opening and closing quantities, find the payment reference, isolate the gas fee and explain the excluded token? Switch to the difference case and ask what additional evidence they would request.

For the initial discovery round, show the preview personally to five fiduciaries. Capture which fields are essential, which would be ignored, what evidence must accompany the PDF and which exact accounting software or import profile they use. Discuss price only after the file’s usefulness is clear. The objective is to validate a repeatable handover, not to replace professional judgement with a polished balance figure.

Questions

Primary references

• SIX: Swiss Payment Standards cash-management guidelines
• Bexio: reconcile bank transactions
• Swiss Federal Tax Administration: crypto guidance

Continue with Stablecoin Statements, the shareable example and the accounting workflow.