One of the underappreciated consequences of institutional crypto adoption is that it has created an enormous amount of extremely boring accounting work. Not boring in a dismissive way - accounting work is important, and doing it badly has real consequences - but boring in the sense that when people imagined corporations putting Bitcoin on their balance sheets, they were probably imagining something more glamorous than "reconciling 47 wallets across 12 blockchains against exchange records while also calculating fair value adjustments for FASB ASU 2023-08 compliance and preparing documentation for the external auditors who are coming in three weeks."
And yet here we are. Public companies now collectively hold more than 1.1 million Bitcoin on their balance sheets - over 5% of the total supply. Every one of those companies needs to measure their holdings at fair value every reporting period, track cost basis at the wallet level for the IRS, file 1099-DAs, and produce audit-ready documentation that a Big Four firm will scrutinize with great thoroughness. Somewhere between the dream of "internet money" and the reality of institutional finance, someone had to build the software that makes the ledgers balance. Several someones did.
This is a guide to choosing the right one.
First, Understand What You Actually Need
Before you evaluate a single vendor, get clear on your own requirements. The market has several distinct buyer profiles, and the right platform for one looks very different from the right platform for another.
Public Companies
You face the most demanding requirements. FASB ASU 2023-08 means your crypto assets must be measured at fair value every reporting period, with changes flowing through net income. You need ASC 820-compliant pricing, principal market determination, and audit-ready documentation that can withstand Big Four scrutiny. SOC certifications aren't optional.
Private Enterprises
You have more flexibility but still need GAAP-compliant books, IRS reporting readiness, and clean ERP integration. Your primary concern is probably operational efficiency - how fast can you close the books, and how much manual reconciliation are you eliminating?
Web3 and Crypto-Native Companies
You likely have the most complex on-chain footprint - multiple chains, DeFi positions, staking rewards, token-based payroll, hundreds of wallets. You need depth of blockchain support, not just breadth, and high-volume transaction processing that doesn't break under scale.
Family Offices and Funds
You need LP-ready reporting, NAV calculations with digital asset components, multi-entity portfolio management, and tax lot optimization. Fund administrators specifically need FBO (For Benefit Of) accounting and segregated balance sheet tracking.
Don't Buy for Today's Complexity Alone
A common mistake: buying the platform that fits your current setup rather than where you'll be in 18 months. If you're a private company planning a public listing, build for public company requirements now. If you're adding DeFi exposure, make sure the platform handles it before you're already in it.
The Non-Negotiables
If a vendor can't clearly demonstrate all of these, move on.
A True Digital Asset Subledger With ERP Sync
The core function of crypto treasury management software is acting as a subledger - a layer between your on-chain activity and your general ledger. The word "sync" matters here. The platform should push journal entries directly to your ERP via API, not produce CSV files you manually import. File-based "integrations" sound fine in a demo and become a month-end bottleneck in practice.
Ask specifically: is this bidirectional? Can it push journal entries to our ERP automatically, or does someone on our team need to initiate the export?
FASB ASU 2023-08 Fair Value Support
Post-January 2025, any platform that only handles cost-less-impairment accounting is obsolete for in-scope crypto assets. You need fair value measurement at arbitrary reporting dates, pricing sourced from ASC 820-compliant data providers, and the ability to generate the balance sheet presentation required by the standard. Verify this isn't a roadmap item; it should be live and demonstrable today.
Cost Basis Methodology Flexibility
The platform should support FIFO, LIFO, HIFO, and specific identification at minimum. More importantly, it should allow you to configure different methods per entity and per asset - not force a single methodology across your entire portfolio. The IRS wallet-by-wallet accounting requirement adds another layer: confirm the platform tracks cost basis at the account level, not just the aggregate.
SOC 1 and SOC 2 Type 2 Certification
SOC 1 Type 2 covers financial reporting controls - relevant for your auditors. SOC 2 Type 2 covers security, availability, and processing integrity - relevant for your IT and compliance teams. Both matter. Type 2 (evaluated over a period of time) is meaningfully stronger than Type 1 (a point-in-time snapshot). Ask for the actual attestation reports, not just a checkbox on a security page. Ask who performed the audit and when the most recent period ended.
Multi-Entity and Multi-Wallet Support
If you have subsidiaries, multiple funds, or operations across jurisdictions, the platform needs to handle intercompany digital asset flows, consolidated reporting, and entity-specific accounting elections without requiring you to run separate instances. Verify there's no hard cap on wallet count that would constrain you as your operations grow.
Immutable Audit Trail
Every transaction categorization, journal entry, and pricing override should be logged with a timestamp and user attribution that cannot be altered. This is what your auditors will ask about. Some platforms bolt audit logging on; the better ones build it into the data architecture from the start.
The Differentiators (What Separates Good From Great)
Once you've confirmed the non-negotiables, these are the capabilities that separate a platform you'll grow into from one you'll outgrow.
Blockchain and DeFi Depth, Not Just Chain Count
Chain count is a marketing metric. What actually matters is how deeply the platform supports each chain. There's a significant difference between monitoring an address balance on a blockchain and fully parsing every transaction type - swaps, bridges, wraps, LP entries, staking reward accruals, mints, burns - and translating those into correct accounting entries.
Before any demo, list your top five most complex transaction types and ask the vendor to walk you through exactly how each one is handled, what the resulting journal entries look like, and what happens when a transaction type isn't recognized.
Real-Time vs. Batch Syncing
If your treasury is actively trading, running DeFi strategies, or processing high volumes of on-chain transactions, real-time data syncing matters. You need accurate position data to make decisions, not yesterday's numbers. If you're primarily buy-and-hold, batch syncing is probably fine and may be more cost-efficient. Know which you are before you evaluate.
Multi-Book Accounting
If you need to maintain simultaneous cost and fair value bases - common for organizations managing both GAAP reporting and internal performance tracking - confirm the platform supports this natively without manual workarounds. Not all platforms do.
Crypto Payments Integration (AP/AR)
Some platforms go beyond accounting into treasury operations, enabling you to invoice in stablecoins, pay vendors in crypto, and manage approval workflows for on-chain payments. If your organization is moving toward crypto-native payments, this matters. If you're purely accounting-focused, it's a nice-to-have.
Data Warehouse Access
For organizations that want to build custom analytics, risk models, or exec dashboards on top of their crypto data, direct export to Snowflake or Google BigQuery is a material capability. Ask whether it's included or a paid add-on.
International Compliance: CARF, DAC8, MiCA
If you have operations outside the US, the regulatory picture extends to OECD's Crypto-Asset Reporting Framework (CARF), the EU's DAC8 directive, and MiCA. Confirm the platform has live - not planned - support for the jurisdictions you operate in.
ERP Integration (Where Most Implementations Quietly Fail)
This deserves its own section because it's where the gap between demo and reality tends to be widest.
Native API vs. File Export
A vendor saying they "integrate with NetSuite" could mean anything from a certified bidirectional API that automatically posts journal entries, to a button that generates a CSV formatted to NetSuite's import template. Both get described as "integrations." Only one actually saves your team meaningful time at close.
Ask: does the integration push entries directly, or do we initiate exports? Is it certified or approved by the ERP vendor? What does the mapping configuration process look like and how long does it typically take?
The ERPs to Ask About
The major platforms buyers most commonly need covered: NetSuite, QuickBooks, Sage Intacct, SAP, Xero, and Microsoft Dynamics 365. If you use something more niche, ask upfront - don't assume it's supported.
Test the Integration With Your Data
The best way to evaluate ERP integration quality is to run a sandbox test with a sample of your actual transactions. Ask vendors if they support proof-of-concept periods before signing. Any vendor confident in their integration capability should be willing to demonstrate it with your transaction types.
Compliance and Audit Readiness
Understanding the SOC Certifications
SOC 1 Type 2: Evaluates internal controls over financial reporting. Your external auditors will ask for this.
SOC 2 Type 2: Evaluates security, availability, confidentiality, and processing integrity over a sustained period. Your IT and compliance teams care about this.
Type 2 vs. Type 1: Type 1 is a point-in-time assessment. Type 2 covers a full audit period (typically 6–12 months). For any serious enterprise evaluation, Type 2 is the standard.
Also look for: ISO 27001 (information security management), AICPA membership, and whether the audit was performed by a recognized firm rather than a boutique nobody's heard of.
Role-Based Access Control and SSO
Your auditors need read-only access. Your AP team shouldn't be able to change accounting policies. Your controller shouldn't have the same permissions as a junior analyst. Confirm the platform supports granular role-based access control, ideally at the field level. SSO (Single Sign-On) and SCIM (automated user provisioning) are standard requirements for enterprise security teams.
Big Four Relationships as a Proxy
Vendors with formal alliances with Deloitte, PwC, EY, or KPMG have typically been through a level of technical scrutiny that others haven't. If your audit firm is already familiar with the platform - or has practitioners certified on it - implementation risk drops and audit preparation becomes significantly easier.
Pricing
Most enterprise crypto treasury platforms don't publish pricing. That's frustrating for budget planning, but it's the reality of the market. Here's how to protect yourself.
Understand the Pricing Drivers
Ask what the pricing model is based on: number of entities, transaction volume per month, number of wallets, number of blockchains, or some combination? Understanding the driver tells you how costs will scale as your operations grow - and whether the quote you receive today will look very different in two years.
Surface the Hidden Costs
Implementation fees can be substantial and are rarely included in the headline quote. Ask specifically:
- Is implementation billed separately? What's a typical range for an organization of our size?
- Are advanced features - custom pricing rules, data warehouse exports, audit licenses, dedicated support - included or add-ons?
- What's the support model: dedicated account manager, shared team, or ticket queue? What are the SLAs?
Ask About Lock-In
What does data portability look like if you decide to switch platforms? Can you export your full transaction history and cost basis records in a standard format? Some platforms make this easy; others make it painful by design.
Get a Total Cost of Ownership Estimate
The right way to compare pricing isn't the monthly contract value - it's total cost including implementation, internal resource time during onboarding, and ongoing support costs versus time saved. Ask vendors to help you build this picture. If they won't, that tells you something.
Red Flags That Should Stop an Evaluation Cold
🚩 CSV-Only "Integration"
If ERP integration means exporting a file and importing it manually, that's not an integration - it's a workflow you're paying to maintain. Walk away or negotiate a real API integration as a condition of signing.
🚩 Chain Count Inflation
"Support for 200+ blockchains" sounds impressive until you discover that 150 of those chains only support basic address balance monitoring, not full transaction parsing. Push for a demo on your specific chains and transaction types before drawing any conclusions from marketing numbers.
🚩 No SOC 2 Type 2
Some vendors have SOC 2 Type 1 and are working toward Type 2. That's fine for a startup you're willing to grow with. For enterprise procurement, it's a risk. Understand what you're accepting if you proceed without it.
🚩 No Live Fair Value Accounting Support
Any platform that can't demonstrate FASB ASU 2023-08 compliance today - not on a roadmap, not "coming soon" - is not suitable for in-scope public company reporting. Full stop.
🚩 Can't Demo Your Transaction Types Live
If you ask a vendor to walk through how they handle a specific DeFi transaction type or a cross-chain bridge event, and they deflect to slides or generic examples, that's a signal. Vendors with genuine depth handle this without hesitation.
🚩 Opaque Audit Logs
Ask to see the audit trail for a set of transactions. If logs are incomplete, hard to access, or the vendor is evasive about what's captured, your auditors will find this out the hard way.
Why Bitwave Built Its Platform Around This Exact Problem
If you've read this far, you have a clear picture of what to look for. Here's how Bitwave approaches it.
Bitwave is the #1 digital asset finance platform built specifically for enterprise finance teams. The platform was designed from the ground up to bridge on-chain activity and traditional financial workflows.
What That Looks Like in Practice
Subledger with real ERP sync. Bitwave is the only approved crypto integration for Oracle NetSuite as an SDN partner, with native integrations to Sage Intacct, QuickBooks, Xero, and Microsoft Dynamics. Journal entries are pushed automatically, not exported manually.
FASB and multi-book accounting. The platform supports fair value measurement, ASC 820-compliant pricing, and multi-book accounting - maintaining simultaneous cost and fair value bases without doubling your team's workload.
80+ blockchain integrations with deep DeFi support. Bitwave covers Ethereum, Solana, Bitcoin, Arbitrum, Base, Avalanche, Cosmos, Hedera, Aptos, and dozens more, with deep parsing of DeFi protocol interactions across 50,000+ smart contracts.
Audit-ready from day one. Bitwave holds SOC 1 Type 2 and SOC 2 Type 2 certifications, with a strategic alliance with Deloitte and a formal partnership with RSM - meaning your audit firm may already know the platform.
Crypto payments built in. Beyond accounting, Bitwave supports stablecoin AP/AR, bulk vendor payments, and on-chain approval workflows - built in partnership with Coinbase Prime.
Trusted by industry leaders. OpenSea, Marathon Digital, Blockdaemon, Compound, Greenidge Generation, and others run their digital asset finance operations on Bitwave.
The platform is built for finance teams who need to move fast, stay compliant, and not be held back by software that wasn't designed for this asset class.
Ready to see it in action? Schedule a demo →
Disclaimer: The information provided in this blog post is for general informational purposes only and should not be construed as tax, accounting, or financial advice. The content is not intended to address the specific needs of any individual or organization, and readers are encouraged to consult with a qualified tax, accounting, or financial professional before making any decisions based on the information provided. The author and the publisher of this blog post disclaim any liability, loss, or risk incurred as a consequence, directly or indirectly, of the use or application of any of the contents herein.
