What evidence does accounting need for crypto settlements?

At minimum: invoice, approvals, address attestation, asset/network/amount, transaction hash, and posting references — plus conversion notes when fiat was converted.

Is a blockchain explorer link enough?

No. Explorers show a transfer; they do not prove internal approval or invoice matching.

How should partial crypto payments be handled?

Define tolerance and remainder rules in AP policy before the first partial occurs.

Where should the tx hash be stored?

In the AP/ERP memo fields and in the payable packet archive.

Who owns incomplete packets?

Payments ops owns completion; accounting owns acceptance standards.

Accounting handoff for crypto settlements: evidence finance needs

Accounting needs a packet, not a screenshot

If payments ops sends only a transaction hash, controllers cannot close. Design the handoff as a packet that mirrors wire evidence: who approved, what invoice, which asset/network, what amount, when it confirmed, and how it posted.

Minimum evidence checklist

Invoice PDF and payable ID.
Approval trail (maker-checker).
Destination address attestation.
Asset, network, and amount.
Transaction hash + explorer URL.
Timestamp of send and confirmation depth policy.
Supplier acknowledgment when available.
FX / conversion note if fiat was converted first.
GL account mapping.

Evidence	System of record	Failure if missing
Invoice	AP	Cannot match payable
Hash	Payments ops	Cannot prove settlement
Approval	Workflow tool	Control gap
Conversion note	Treasury	P&L unexplained

Accountant reviewing digital payment evidence

Reconciliation rhythm

Reconcile daily during pilots, then settle into a cadence that matches payable volume. Partial payments and overpayments need explicit rules — see invoice field standards once that guide is live, and keep memos consistent.

Risks and limits

Chain explorers are not a substitute for internal approvals. Price moves between conversion and payment can create P&L noise if undocumented. Wrong-asset sends create hard-to-reverse incidents.

Handoff SOP (numbered)

Ops closes the payable ticket.
Packet auto-assembles or is attached manually.
Accounting validates completeness.
Posting occurs with hash in the memo field.
Exceptions go to a named queue within SLA.

Open a Cryptobus business account to buy crypto, pay invoices, and settle cross-border.

This material is for informational and educational purposes only. It is not legal, tax, investment, or financial advice. Cryptocurrency transactions involve operational, market, and compliance risk. Outcomes depend on your policies, counterparties, corridors, and applicable law. Readers should verify primary sources and internal controls as of the action date.