Crypto accounting for NetSuite

CryptaCount is the crypto sub-ledger for NetSuite. A direct NetSuite integration is on the roadmap: it will ingest high volumes of on-chain and exchange activity, calculate cost basis and gains, and post clean period journal entries to NetSuite — across subsidiaries and mapped to your chart of accounts — while the transaction-level detail stays in the sub-ledger.

The NetSuite connector is coming soon. Today you can run the full crypto sub-ledger in CryptaCount and export journal entries for import into NetSuite.

How it will work

NetSuite is the GL for the group; it isn't designed to reconcile wallets and token cost basis at transaction volume. CryptaCount will do that and feed NetSuite clean entries:

1. Ingest every transaction from your exchanges and wallets, at scale,
2. Calculate cost basis and realized gains/losses (your choice of method) and apply your measurement policy,
3. Summarize the activity into journal entries per period per subsidiary, and
4. Post them to NetSuite, mapped to your chart of accounts.

Your GL stays clean; every line will drill back to the underlying transactions in CryptaCount.

How it will connect

In CryptaCount, you will go to Integrations → NetSuite and connect using token-based authentication (NetSuite's recommended method for server integrations — no stored password). You will map your crypto GL accounts — digital assets, realized gain/loss, income (staking, mining, rewards), and fees — to your chart of accounts, assign the right subsidiary for each entity, and set your posting frequency.

Available today: export for NetSuite

Until the direct connection ships, you can run the full sub-ledger in CryptaCount and export summarized journal entries to import into NetSuite — the same double-entry, period-level postings, by subsidiary, mapped to digital assets, realized gain/loss, income, and fees.

What will sync

• Period journal entries — summarized, double-entry, by subsidiary
• Chart of accounts mapping — your GL accounts, kept aligned
• Multi-entity — entries routed to the correct subsidiary
• Drill-down — every posted line traces to transaction-level detail in the sub-ledger

Why finance teams use CryptaCount

• Built for volume — handles high transaction counts across many exchanges and wallets
• Multi-subsidiary — separate sub-ledgers and postings per entity, for groups and funds
• Cost basis at scale — 12 disposal methods (FIFO, LIFO, HIFO, WAVG, Specific ID, and more), applied consistently; jurisdiction-mandated treatments (UK Section 104 pooling, Canada ACB) apply automatically
• Clean close — summarized entries, not raw transactions, in the GL
• Audit-ready — a traceable trail from each GL line to the source transaction
• IFRS / US GAAP — measurement handled in the sub-ledger per your policy

Explore the engine: Crypto sub-ledger & cost basis → · Accounting for firms →

Why the sub-ledger posts summaries, not every transaction

NetSuite is the general ledger for the group — engineered for consolidation, multi-subsidiary reporting and high finance volumes — but it was not built to reconcile wallets and token cost basis across hundreds of thousands of on-chain events. That is the role of CryptaCount, the crypto sub-ledger in front of your GL. When the connector is live it will post summarized journal entries per period, per subsidiary, rather than a line for every transfer, swap, fee and reward. At enterprise volume the difference is decisive: pushing raw crypto transactions into NetSuite would balloon the ledger, slow consolidation and obscure the net figures the financial statements actually need.

The sub-ledger model is the same one NetSuite users already trust for payroll, inventory or a high-volume billing system: the operational engine holds the line-by-line record, and only summarized debits and credits reach the GL. CryptaCount aggregates each period into entries that move digital assets, realized gain/loss, income (staking, mining, rewards) and fees by their net amounts, with every posted line drilling back to the underlying transactions. The group ledger stays clean while the full detail stays reconcilable. The crypto sub-ledger → page describes the engine behind it.

Mapping to your chart of accounts

Before anything posts, you decide where each kind of crypto activity lands in your NetSuite chart of accounts. CryptaCount separates acquisitions, disposals, internal transfers, income receipts, fees and revaluations, and lets you map each to a specific GL account — holdings to asset accounts, disposals to realized gain/loss, staking and reward income to a revenue or other-income account, and network and exchange fees to expense accounts. Because you control the mapping, the postings line up with the account structure your group already reports on, and with the segments and classifications NetSuite uses for analysis.

• Digital asset accounts — combined, or split by asset, venue or strategy
• Realized gain / loss — disposals measured under your chosen cost-basis method
• Income — staking, mining, rewards and airdrops recognized at value on receipt
• Fees — network (gas) and exchange fees, kept separate from trading results
• Subsidiary routing — each entry directed to the correct entity in the group

Mapping is set once and reused every period, so the entries stay consistent across closes and across subsidiaries. Add an entity, exchange, wallet or token and it flows into the same structure with no rebuild. See how postings are assembled on the journal entries → page.

What the integration will and will not do

At enterprise scale a clean division of labor matters even more, so it is worth being precise. The connector is a posting and mapping bridge between the sub-ledger and NetSuite — not a replacement for either.

What it will do: ingest high volumes of activity from your exchanges and wallets, calculate cost basis and realized results under your policy, summarize each period into double-entry journal entries per subsidiary, map them to your chart of accounts, and post them to NetSuite with drill-down back to the source transactions. What it will not do: it will not turn NetSuite into a crypto data warehouse, will not post raw transactions, will not disturb your existing financial workflows, and will not make accounting-policy decisions for you. Measurement, classification and method selection stay under your control inside the sub-ledger; NetSuite remains the system of record for consolidated reporting.

The close and reconciliation workflow

A group close with crypto follows a repeatable sequence once the sub-ledger is in place. CryptaCount ingests each period's transactions across every connected exchange and wallet, attributes them to the right entity, and flags whatever needs a decision — an unknown counterparty, an unrecognized token, or a transfer that may be an internal move rather than a disposal. Your team resolves those exceptions, confirms on-chain balances reconcile per entity, and reviews the cost-basis results before generating per-subsidiary entries and posting them.

Reviewing at the NetSuite end stays fast even at scale, because each subsidiary receives a handful of summarized lines per account, each backed by a full transaction list. Self-transfers between your own wallets net to zero rather than creating phantom gains, balances reconcile to the chain before anything posts, and closed periods stay closed. The same controlled process repeats every period across the whole group.

Controls and the audit trail

For a group subject to external audit, an unbroken trail is non-negotiable. Every summarized line posted to NetSuite will trace to the exact disposals, receipts and fees behind it, and each of those ties to a transaction hash or an exchange record — financial statement to journal to lot to transaction to blockchain, per subsidiary. That chain is recorded as activity happens rather than reconstructed at year-end. Cost-basis method, measurement policy and classification are applied consistently and retained so any figure can be reproduced. For how this supports group reporting, see crypto compliance reporting →.

Multi-entity and multi-currency considerations

Multi-subsidiary structures are exactly where the sub-ledger earns its place. CryptaCount keeps a sub-ledger scope per entity and posts each period's entries to the correct subsidiary, so intercompany crypto movements stay clean and consolidation is not distorted by mismatched bases or double-counted transfers. Transactions are valued when they occur and can be presented in each entity's functional currency and the group's presentation currency, so the entries reaching NetSuite reflect the reportable position rather than raw token quantities. Measurement under IFRS or US GAAP is applied in the sub-ledger per your group policy — see IFRS crypto accounting →.

Common pitfalls this design avoids

• Raw transactions in the GL — overwhelms NetSuite and slows consolidation; the sub-ledger posts per-subsidiary summaries instead
• Lost cost basis on transfers in — coins moved between entities or platforms with no basis distort every later gain; CryptaCount carries basis with the asset
• Self-transfers booked as sales — moving funds between your own wallets should never create a disposal or a phantom gain
• Cross-entity contamination — activity attributed to the wrong subsidiary muddies consolidation; entries are routed per entity
• Inconsistent cost-basis methods — switching method mid-period produces results no one can reconcile; the engine applies your method consistently
• Spreadsheet closes at group scale — unmaintainable and unauditable; a reconciled sub-ledger replaces them

How CryptaCount will work with NetSuite

CryptaCount will do the crypto-specific heavy lifting — ingestion at volume, cost basis, classification, per-entity reconciliation — and hand NetSuite what the group ledger should receive: clean summarized journal entries per subsidiary, mapped to your accounts. Today you can run the full sub-ledger and export those entries by subsidiary for import into NetSuite; when the direct connector ships it will post them for you, with drill-down behind every line. NetSuite stays the system of record; the transaction detail stays where it can be reconciled and audited. For a group already running NetSuite for consolidation, that means crypto stops being the one asset class your close cannot absorb cleanly, and starts behaving like every other sub-ledger feeding the group ledger. Explore the crypto sub-ledger → and journal entries → for the engine in detail.

Will it post to the correct subsidiary automatically?

Yes. Each wallet and exchange source is attributed to an entity, and the period entries are generated and posted per subsidiary. That keeps consolidation clean and avoids activity landing in the wrong company within the group.

Can it handle our transaction volume?

Yes. The sub-ledger is designed to ingest high transaction counts across many exchanges and wallets and then post summarized entries, so the volume lives in CryptaCount and only the net result reaches NetSuite. That is precisely how the GL stays performant.

Does it support our intercompany crypto movements?

Transfers between entities you control are recognized as internal movements rather than disposals, so they do not create phantom gains. Basis follows the asset across the move, which keeps each subsidiary's later results accurate and consolidation clean.

How will it authenticate to NetSuite?

Via token-based authentication, NetSuite's recommended method for server integrations, so no user password is stored. You grant the connector scoped access, and it posts entries within those permissions.

How will fees and income be presented across subsidiaries?

Each subsidiary receives its own summarized entries, with income recognized at value on receipt and fees kept separate from trading results. That means staking, mining and reward income lands in the revenue or other-income accounts you map per entity, while network and exchange fees go to their own expense accounts rather than being netted into proceeds. Keeping these distinct at the subsidiary level preserves accurate per-entity reporting and a clean group consolidation, because nothing is blended that the financial statements need to show apart.

Can we run the sub-ledger before the direct connector ships?

Yes. You can run the full crypto sub-ledger today — ingestion at volume, cost basis, classification and per-entity reconciliation — and export summarized journal entries by subsidiary for import into NetSuite. The accounting result is the same period-level, double-entry posting; the direct connector simply automates the posting step when it is available, so adopting CryptaCount now does not mean waiting to get your crypto books in order.