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 article is about that one document — the written accounting policy — and how it differs from the treasury/investment policy beside it. The investment policy governs what may be held and at what risk; this one governs how whatever is held is classified, valued, recognised, and reconciled, fixed once in writing so every period is consistent and every judgement is defensible.

What the document fixes

• The policy fixes, in writing: classification (not cash by default), valuation, recognition, reconciliation cadence, and 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 and recognition: source/principal-market/timestamp, fair-value treatment, reward-at-control, internal transfers as non-disposals.
• Reconciliation cadence belongs in the policy — "eventually" fails at audit.
• It is complementary to the treasury/investment policy: risk versus 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 or savings receipt as a position, value-accruing and 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 and yield recognition, typically at control;
• internal transfers as 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 they make the treasury well-governed and well-reported. One without the other leaves either the risk or the books undefined.

Implementation checklist: drafting the accounting policy document

A crypto treasury accounting policy is a structured document, not a slide deck. The following checklist covers the minimum required sections:

Section 1 — Scope:

• Which entities, wallets, and accounts does the policy cover? The scope is explicit: named entities, named wallet types (multisig, custodial, DeFi position wallets), and any excluded accounts with the reason for exclusion.
• What accounting framework applies? (IFRS, US GAAP, local GAAP.) If the organisation consolidates across jurisdictions with different frameworks, the policy addresses how differences are handled.

Section 2 — Classification:

• A classification table listing each instrument type held (or potentially held) and its designated balance-sheet classification. Each classification is supported by the accounting analysis that justified it (one paragraph per instrument type, referencing the applicable standard).
• The policy states explicitly that no crypto asset is classified as cash and cash equivalents without a documented analysis confirming it meets the definition under the applicable standard in the specific jurisdiction.
• The policy covers the treatment of new instrument types not yet in the table: before a new instrument is deployed into, the treasury lead and the auditor/accounting adviser confirm and document the classification. No new instrument enters the books with an ad-hoc classification.

Section 3 — Valuation:

• The principal market and pricing source for each asset type, with a waterfall for when the primary source is unavailable.
• The timestamp convention: what time of day on what date is used for period-end valuations. This is the same for all assets (except where a specific standard requires otherwise) and is applied consistently.
• How off-market, illiquid, or zero-liquidity positions are valued (e.g. at the last traded price, at NAV, or with a specific discount methodology). Confirm the approach with the auditor.

Section 4 — Recognition:

• When transactions are recognised: trade date or settlement date, and the basis for the choice.
• Revenue and income recognition: staking/yield income at the point of control (typically when the tokens are received or when the right to receive them is established), confirmed per the applicable framework.
• How derecognition (disposal) is determined: FIFO, specific identification, or weighted average cost. The method is stated and applied consistently.

Section 5 — Reconciliation:

• The cadence for each reconciliation type: on-chain vs subledger (ideally daily), subledger vs general ledger (monthly at close), and policy compliance reconciliation (monthly).
• The role responsible for each reconciliation and the role responsible for reviewing it (must be different people).
• The procedure for reconciliation differences: investigation timeline, documentation required, escalation path if the difference cannot be resolved within the investigation window.

Section 6 — Controls:

• The segregation of duties matrix for treasury accounting: who can initiate, who can review, who can approve, who can post to the GL.
• The change-management process for the accounting policy itself: how changes are proposed, approved, documented, and communicated to the audit team.
• The document retention standard: how long records (subledger data, reconciliation files, valuation workbooks, audit trail exports) are retained.

Accounting treatment: applying the policy consistently

The accounting policy prevents ad-hoc judgements, but applying it consistently requires active discipline:

• New instruments: when the treasury deploys into a new instrument type (e.g. first time holding a tokenized fund share), the instrument-type assessment is completed before any accounting entries are made. The assessment is filed and a new row is added to the classification table.
• Framework changes: when an accounting standard relevant to crypto assets changes (e.g. ASU 2023-08 adoption, an IFRS interpretation update), the policy is reviewed and updated to reflect the change. The update is approved by the auditor and documented as a policy revision with an effective date.
• Judgment areas: for instruments or situations where the policy does not provide unambiguous guidance (e.g. a novel DeFi instrument type), the policy's judgment escalation path applies — the treasury team documents the question, the accounting adviser provides a written recommendation, and the conclusion is filed. The same conclusion is applied to all equivalent situations going forward.

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 that it retains the audit trail. A tool running its defaults instead of your policy is an audit finding, not compliance.

How Wag3s executes the policy

The policy itself is written by the treasury and signed off by its auditor — Wag3s does not author it. What Wag3s Ledger does is execute it: configured to the treasury's written accounting policy (per-instrument classification, valuation source and timestamp, reward-at-control recognition, 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

• FASB — ASU 2023-08, Accounting for and Disclosure of Crypto Assets: the US fair-value model that the classification and valuation sections of a US-GAAP treasury policy must reflect for in-scope crypto.
• IFRS 9 Financial Instruments (with IAS 38 for crypto-as-intangible and IFRS 13 for fair-value measurement): the IFRS basis the policy's classification, valuation, and recognition sections reference. Treatment is framework- and jurisdiction-specific — confirm with your auditor.
• The accounting-policy components described here (classification, valuation source/timestamp, reward-at-control recognition, internal-transfers-as-non-disposals, reconciliation cadence and ownership, controls) are operational; the audit tests are consistency and defensibility, and this policy is complementary to, not a replacement for, the treasury/investment policy.