Crypto Treasury Accounting Policy: The Document the Audit Tests You Against

Ask a crypto treasury "what's your accounting policy?" and a worrying number answer with a description of last quarter's spreadsheet. An auditor does not test a spreadsheet; they test consistency and defensibility against a stated method. This guide is the document that method has to be.

TL;DR

• The policy fixes, in writing: classification (not cash by default), valuation, recognition, reconciliation cadence, controls.
• It exists because the audit tests are consistency and defensibility — an ad-hoc approach fails both.
• Classification: each instrument per its nature (stablecoin, fund share, position, in-scope fair-value).
• Valuation/recognition: source/principal-market/timestamp, fair-value treatment, reward-at-control, internal transfers non-disposals.
• Reconciliation cadence belongs in the policy — "eventually" fails at audit.
• Complementary to the treasury/investment policy — risk vs reporting.

Why a written policy

Consistency and defensibility are the audit tests. An undocumented, ad-hoc approach produces period-to-period inconsistency and judgements no one can defend later. The policy turns recurring judgements into a stated, repeatable method an auditor can test you against — the same "documented judgement" discipline as the audit trail and the classification articles, made into a single governing document.

What it fixes: classification

The policy states that crypto is not cash by default and how each instrument is classified per its nature and the applicable framework:

• a stablecoin per its structure;
• a tokenized fund interest as a fund share;
• an LP/savings receipt as a position (value-accruing, not cash);
• in-scope crypto under the fair-value model.

So the same instrument is treated the same way every period — not re-decided ad hoc.

What it fixes: valuation and recognition

• valuation basis and source — principal market, pricing source, timestamp convention;
• fair-value movement treatment under the applicable framework;
• reward/yield recognition — typically at control;
• internal transfers — non-disposals (see internal transfer vs disposal).

Fixing these in writing is what makes two periods comparable and a year-end number defensible rather than reconstructed.

Why cadence is in the policy

Reconciliation done "eventually" is reconciliation that fails at audit. The policy sets:

• how often positions are reconciled to on-chain reality and policy limits (ideally continuous);
• who performs and reviews it;
• how exceptions are handled.

A stated cadence with ownership is the difference between a maintained audit trail and a year-end scramble (see stablecoin treasury accounting controls).

Two policies, complementary

Together: well-governed and well-reported. One without the other leaves either the risk or the books undefined.

Practical guidance

1. Write the accounting policy — classification, valuation, recognition, cadence, controls.
2. State "not cash by default" and the per-instrument classification logic.
3. Fix valuation source/timestamp and reward-at-control in writing.
4. Put reconciliation cadence and ownership in the policy.
5. Keep it complementary to the treasury/investment policy.
6. Confirm the policy with your auditor; review on framework change.

How vendor tools support an accounting policy

Cryptio and Bitwave implement classification, valuation, and reconciliation that a policy should govern. Confirm the tool's settings can be configured to the written policy (classification rules, valuation source, cadence) and retains the audit trail — a tool running its defaults instead of your policy is an audit finding, not compliance.

How Wag3s helps

Wag3s Ledger is configured to the treasury's written accounting policy — per-instrument classification (not cash by default), valuation source and timestamp, reward-at-control recognition, and a stated reconciliation cadence — with the audit trail that makes every period consistent and defensible. See the Ledger product page and the Wag3s for accountants page.

Further reading

• Crypto Treasury Board Reporting
• Crypto Treasury KPIs
• Crypto Treasury Segregation of Duties
• Stablecoin Treasury Accounting Controls
• Stablecoin Accounting Treatment
• Crypto Audit Trail and Piste d'Audit Fiable

Sources

• Crypto-treasury accounting-policy components: classification (not cash by default, per-instrument), valuation (source/principal-market/timestamp, fair-value treatment), recognition (reward at control, internal transfers non-disposals), reconciliation cadence + ownership, controls
• Audit tests are consistency and defensibility — a written, repeatable policy is what an auditor tests against (vs ad-hoc inconsistency)
• Accounting policy is complementary to (not a replacement for) the treasury/investment policy; framework- and jurisdiction-specific (confirm with auditor)