Traditional accounting systems—QuickBooks, Xero, SAP, NetSuite—are not designed for crypto operations. In crypto, a single transaction can be a sale, purchase, and income simultaneously. For example, a token swap on Uniswap: you sell ETH and buy USDC—that's two taxable events. Staking rewards arrive with non-obvious cost basis, and LP positions continuously change in value. Manual processing of thousands of transactions per day takes up to 20 hours—we reduce that to 20 minutes. Our crypto fund integration with accounting systems solves this: we gather on-chain events, classify them, value them, and post entries to your system. Automated classification processes transactions 50 times faster than manual effort, achieving 99.9% accuracy. Our experience spans over 50 integrations for crypto funds, including funds with portfolios of 500+ contracts and 10,000 daily transactions.
According to IFRS guidelines on crypto asset accounting, each transaction requires correct classification.
Which crypto events need accounting entries?
Every on-chain event maps to a specific entry type. Without classification, any reports will be incorrect.
| On-chain event | Accounting classification |
|---|---|
| Transfer between own wallets | Not an operation, only custody change |
| DEX swap | Disposal of one asset + Acquisition of another |
| Staking rewards | Income (ordinary income) |
| Adding liquidity to a pool | Disposal of tokens + Acquisition of LP tokens |
| Harvest LP fees | Income |
| Airdrop | Income (at fair market value) |
| Vesting receipt | Income or Capital (depends on jurisdiction) |
| Gas | Expense |
Automation analyzes the function selector and topics of the transaction. For example, a call to 0x38ed1739 (swapExactTokensForTokens in Uniswap v2) plus Transfer events means a swap. Average classification time per transaction is 150 ms.
How do we value tokens at the time of transaction?
Each taxable operation requires a fair market value at the transaction timestamp. The algorithm:
- Capture the block.timestamp of the event.
- Query price from historical price feed: CoinGecko (daily), Cryptocompare Pro (minute), or Chainlink (getRoundData).
- For illiquid tokens—on-chain TWAP from DEX pools on an archive node.
The problem with CoinGecko is daily granularity. For professional reporting, we use hourly data from Cryptocompare Pro. If price is unavailable, we apply a moving average of recent trades.
Integration with accounting systems
QuickBooks / Xero
Both systems have REST APIs. Example journal entry for a ETH → USDC swap:
Journal Entry: Debit: USDC Asset Account +$1,850 (acquired) Credit: ETH Asset Account -$1,800 (cost basis) Credit: Realized Gain/Loss -$50 (profit) + separate line for gas: Debit: Transaction Fees Expense +$2.50 Credit: ETH Asset Account -$2.50 const xeroTransaction = { Type: "JOURNAL", Reference: txHash.slice(0, 10), JournalLines: [ { AccountCode: "1150", Description: "USDC acquired", LineAmount: usdcUsdValue }, { AccountCode: "1140", Description: "ETH disposed", LineAmount: -ethCostBasis }, { AccountCode: "4200", Description: "Realized gain/loss", LineAmount: -gainLoss }, ], }; A daily reconciliation job compares entry totals with on-chain balances. Discrepancies trigger an automatic report.
SAP / NetSuite
For ERPs, we use middleware (MuleSoft, Boomi). We transform crypto transactions into RFC/BAPI or SuiteScript format, respecting approval workflows and rate limits.
Specialized platforms
If you need a ready-made crypto accounting solution, we integrate with Cryptio, Lukka, TaxBit, or Koinly. Configure the data feed via their API or CSV export.
Comparison of cost basis methods
| Method | Principle | Tax impact |
|---|---|---|
| FIFO | Sell oldest purchase first | High gain in rising market |
| HIFO | Sell most expensive first | Minimizes realized gain |
| Specific ID | Explicit lot selection | Flexibility, requires documentation |
Lot database:
CREATE TABLE acquisition_lots ( id BIGSERIAL PRIMARY KEY, asset VARCHAR(42) NOT NULL, chain VARCHAR(20) NOT NULL, acquired_at TIMESTAMPTZ NOT NULL, tx_hash VARCHAR(66) NOT NULL, quantity NUMERIC(36,18) NOT NULL, cost_basis_usd NUMERIC(18,2) NOT NULL, remaining NUMERIC(36,18) NOT NULL, method VARCHAR(10) DEFAULT 'FIFO' ); Handling special cases
Impermanent loss—when exiting a pool, the token quantities differ from those deposited. Only realized upon withdrawal. Stablecoins (USDC/USDT)—acceptable to assume $1 with a documented policy. Cross-chain bridges—disposal + acquisition or not? Requires legal opinion.
What's included
- API integration with the chosen system (REST/SuiteScript/RFC)
- Configuration of on-chain event classification by type
- FMV pricing via historical price feeds
- Cost basis tracking (FIFO/HIFO/Specific ID)
- Automated daily reconciliation job
- Documentation and training for accountants
- 3 months of post-deployment support
How does reconciliation work?
- All journal entries for the day on crypto accounts are collected.
- Current on-chain balances are queried (via RPC).
- The sums are compared: entries vs balances.
- Discrepancies trigger a detailed report.
Engagement process
- Analysis — we review your on-chain operations and accounting requirements.
- Design — mapping schema, price feed selection, cost basis method.
- Implementation — classifier code, API integration, valuation module.
- Test — load historical data, cross-check with manual records.
- Deploy — launch daily sync, configure reports.
Timeline: 6 to 10 weeks, depending on the number of data sources and systems. Pricing is individual, typically recouped within 2–3 months from reduced manual labor. Typical savings from automation range from 30% to 50% on accounting costs. We guarantee data transparency and full compliance with reporting standards.
Request a preliminary audit of your crypto fund today. Contact us for a cost estimate and integration details.