Crypto Accounting Xero Integration

Xero handles fiat-side accounting beautifully. It does not handle crypto. If you've ever tried to import wallet activity into Xero as a bank feed, you know the problem: the chain of custody breaks, transactions stack at incorrect cost basis, gas fees float in their own ether, and the auditor's first question is "where does this balance come from?"

The fix is not to push more data into Xero. The fix is to insert a subledger between your wallets and Xero — and that's what crypto accounting platforms like Cryptio, Bitwave, Cryptoworth, and Wag3s do. This guide covers what the integration actually looks like in 2026, where the four main vendors differ, and the practical setup decisions that matter.

TL;DR

• Xero has no native crypto support. Integration requires a subledger.
• The subledger handles wallet/exchange connections, cost basis, per-transaction journal entries, and FX. It posts summary journals to Xero via API.
• Typical chart of accounts: per-asset balance accounts, separate income accounts for yield, gas expense account, realized gains/losses.
• The four main vendors are Cryptio, Bitwave, Cryptoworth and Wag3s Ledger.
• Setup time: 2-5 days for a clean install on a small business, 4-8 weeks for a mid-size operation with multi-chain DeFi.

Why Xero needs a subledger for crypto

Xero models accounting at the transaction level: a debit, a credit, a date, a counterparty, a description. The data model assumes one currency at a time with FX as a posting-level concern.

Crypto breaks several of these assumptions:

• One blockchain transaction can produce 4-5 distinct accounting events (swap = sell asset A + acquire asset B + pay gas + possibly LP receipt). Pushing that as one Xero transaction loses the analytical detail.
• Cost basis depends on history, not the current transaction. A single ETH disposal requires knowing the FIFO/LIFO/HIFO order across all ETH lots. Xero doesn't compute this.
• Multi-chain operations spread the same asset across multiple addresses on multiple chains. Xero has no concept of a wallet or a chain.
• DeFi positions (LP tokens, staked balances, restaking points) don't map to Xero asset classes without classification logic.
• Gas allocation requires per-transaction context that Xero lines don't carry by default.

Pushing wallet activity into Xero as a bank feed produces an output that an external auditor cannot reconcile. The subledger pattern fixes the chain of custody: every Xero line ties back to a subledger journal which ties back to specific on-chain transactions.

The integration architecture

Wallets & Exchanges
        │
        ▼
   Subledger (Cryptio / Bitwave / Cryptoworth / Wag3s Ledger)
        │
   ┌────┴──────┐
   ▼           ▼
Per-tx entry   Summary journals
(detail)       (daily or monthly)
   │           │
   │           ▼
   │       Xero (system of record)
   ▼
Audit trail

The subledger does the work. Xero shows the result. The reference field on the Xero entry points back to the subledger journal ID, so any auditor sampling a Xero balance can trace forward to specific on-chain transactions.

Daily versus monthly posting

Two common patterns:

Daily posting — the subledger pushes a summary journal to Xero each day, one line per asset class (Crypto - BTC, Crypto - ETH, Crypto - Stablecoins). Easier for cash-flow monitoring and reconciliation; produces more Xero entries (~365 per year for a single asset class).

Monthly posting — the subledger pushes a single month-end journal with a per-asset breakdown. Cleaner Xero ledger; harder to use Xero for in-month monitoring (need to query the subledger directly). Most mid-size teams default to monthly.

Either pattern works. The decision is operational, not technical.

Chart of accounts for crypto in Xero

A typical structure for a Web3 business:

Splitting stablecoins into a dedicated account simplifies the year-end review — stablecoin balances should approximate USD face value, so any material divergence flags a problem (depeg event, accounting error, miscategorization).

For multi-chain teams, tracking categories can split each asset across chains without creating account-class explosion. "Tracking Category: Chain" with values "Ethereum / Arbitrum / Base / Optimism / Polygon / Solana" is a common configuration.

How the four main vendors differ on Xero integration

Cryptio

Cryptio has one of the longer-running Xero integrations among dedicated crypto subledgers. The integration:

• Posts per-transaction journals or summary journals; user choice
• Supports multi-entity Xero organizations (useful for groups with separate legal entities per market)
• Handles FX revaluation in cooperation with Xero's FX module
• Strong on multi-chain reconciliation
• Enterprise-tier pricing with the Xero connector included in the standard plan (check Cryptio's current pricing — it is quote-based)

Weakness: the per-transaction posting can flood Xero with thousands of entries on DeFi-heavy operations. Most users switch to summary posting after a few months.

Bitwave

Bitwave's Xero integration is generally less mature than its NetSuite or QuickBooks integrations — NetSuite is Bitwave's flagship. Capabilities (confirm current scope with Bitwave):

• Summary journal posting
• US GAAP fair-value accounting (ASU 2023-08) is a strength
• Audit-trail tooling backed by independent review recognition

Weakness: the Xero connector lags Bitwave's other ERP integrations in features. NetSuite is Bitwave's flagship; Xero is a secondary support tier.

Cryptoworth

Cryptoworth focuses on mid-market accounting firms and their crypto clients. Xero integration:

• Summary journal posting
• Multi-entity supported
• Broad DeFi protocol coverage
• Mid-market positioning aimed at accounting firms (check Cryptoworth's current pricing directly)

Weakness: the chart-of-accounts mapping is configurable but not intuitive — initial setup takes 2-3 calls with the Cryptoworth implementation team.

Wag3s Ledger

Wag3s Ledger provides:

• Daily or monthly summary journal posting to Xero
• Multi-entity Xero organizations
• Per-chain tracking category support for multi-chain operations
• Multi-chain reconciliation across 20+ chains (see multi-chain reconciliation)
• Audit trail with on-chain hash, subledger journal ID, and Xero reference ID on every entry
• Stablecoin tagging (issuer + chain) for DAC8 reporting alignment
• Multi-currency functional currency (USD, EUR, GBP, CHF)

For comparison with the other vendors, see Wag3s vs Cryptio and Wag3s vs Bitwave.

Setup timeline and key decisions

Realistic timeline for a mid-size Web3 business (10-50 staff, 5-15 wallets, 3-5 chains):

The bottleneck is almost always historical reconciliation. A team with two years of unreconciled multi-chain activity will need 3-6 weeks of clean-up before the first clean monthly close. Tools accelerate the process but don't eliminate the judgement calls (gas allocation methodology, DeFi event classification, lost-transaction handling).

Key decisions before signing

1. Cost basis method — FIFO is the default and works in most jurisdictions. LIFO is required by Italy, allowed by US GAAP, prohibited under IFRS for inventory but the analogy debate for crypto is unsettled.
2. Daily vs monthly posting — monthly is the default; switch to daily only if cash-flow monitoring in Xero is a requirement.
3. Per-transaction vs summary entries — almost always summary. Per-transaction explodes Xero record counts.
4. Stablecoin treatment — single "Stablecoins" account or split per issuer (USDC, USDT, DAI). Split is recommended for entities with >$1M aggregate stablecoin exposure.
5. Tracking categories vs separate accounts for chains — tracking categories are simpler operationally; separate accounts give better isolated reporting per chain.

How Wag3s helps

Wag3s Ledger integrates with Xero out of the box and adds the multi-chain reconciliation, DeFi event classification, and audit-trail layer that Xero alone cannot provide. For Web3 finance teams already on Xero, Wag3s Ledger sits below Xero and feeds clean summary journals on the cadence you choose.

See the Wag3s Ledger product page for module details.

Further reading

• Crypto Accounting NetSuite Integration — sister article for the NetSuite stack
• Crypto Accounting QuickBooks Integration
• On-Chain Bookkeeping Basics for Web3 Finance Teams — the underlying accounting fundamentals
• Multi-Chain Reconciliation Across 20+ Blockchains
• IFRS vs GAAP for Crypto Assets
• Crypto Audit Readiness
• Month-End Close for Web3 Teams

Sources

• Xero Developer Documentation — Manual Journals API
• Cryptio — Xero Integration documentation
• Bitwave — Xero Integration overview
• Cryptoworth — Xero connector
• FASB ASU 2023-08 — Accounting for Crypto Assets