HTX crypto accounting

HTX crypto accounting has a continuity wrinkle: HTX was Huobi until its 2023 rebrand, so a single set of books may span both names. For cost basis, the sub-ledger has to treat the Huobi-era and HTX-era activity as one continuous ledger — drop the older history and every later disposal is mis-measured. CryptaCount ingests the full record, reconciles to the venue, and posts summarised journal entries to your general ledger, built for finance teams, funds and treasuries.

HTX as a source for your sub-ledger

HTX (formerly Huobi) is a multi-product venue; CryptaCount is where its spot, derivatives and Earn activity becomes accounting. It pulls the full history — across the rebrand — into a crypto sub-ledger, applies your measurement policy, and produces summarised journal entries for your general ledger with full detail behind every line.

How to connect

1. Read-only API (recommended). In HTX, create an API key with read-only permission only — leave trading and withdrawals unchecked. In CryptaCount, go to Integrations → HTX and paste it.
2. CSV import. Export your transaction history from HTX and upload it.

A read-only key lets CryptaCount read your history for the books but never move funds — a control you can evidence directly to an auditor.

What flows into your books

An HTX account mixes spot, derivatives and Earn, and each books differently. Sorting the history into these buckets is most of the work:

Spot trades and conversions

Each spot disposal or conversion carries a cost basis and posts to realised gain/loss, often against acquisitions made under the Huobi name.

Derivatives (futures and swaps)

Closed futures and perpetual-swap positions post realised PnL, with funding booked as cost or income, in a ledger separate from spot.

HTX Earn rewards

Earn and savings rewards are recognised as income at fair value on receipt, carried forward as basis.

Deposits, withdrawals and transfers

Movements of your own assets are matched across legs rather than booked as disposals.

Built for finance teams

• Continuous across the rebrand — Huobi-era and HTX-era activity ingest as one ledger so early basis is never lost
• Automated cost basis — 12 disposal methods (FIFO, LIFO, HIFO, WAVG, Specific ID, and more); jurisdiction-mandated treatments (UK Section 104 pooling, Canada ACB) apply automatically
• Journal entries to your ERP — QuickBooks, Xero, NetSuite or Sage → ERP integrations →
• Audit-ready — every GL line drills back to the HTX transaction behind it
• IFRS / US GAAP — measurement applied in the sub-ledger per your policy

See the sub-ledger → · Accounting for firms →

One continuous ledger across the Huobi to HTX rebrand

The defining accounting fact about HTX is that it is the rebranded Huobi, renamed in 2023. Many long-standing accounts therefore have a history that straddles both names, and to the books they are one continuous ledger: the cost basis of assets still held or later sold was often set during the Huobi era. If only the HTX-era data is ingested, those earlier acquisitions are missing and every later disposal is measured against a blank — a silent error that compounds across the period.

CryptaCount treats the Huobi and HTX history as a single account, carrying basis straight through the name change, so a position opened under Huobi and closed under HTX is measured against what was actually paid. For a finance team inheriting or auditing such an account, making the rebrand invisible to the cost-basis calculation is exactly what keeps the figures defensible.

Derivatives and Earn in the books

Beyond spot, HTX runs futures and perpetual swaps and a range of Earn products. Derivatives post realised PnL and funding to the general ledger as discrete results, separate from the lot-based spot gains; where your policy marks open positions to market at period end, the sub-ledger retains the position detail to support it. Earn rewards are recognised as income at fair value on receipt and carried forward as basis. CryptaCount reads the derivatives and reward ledgers separately so neither is conflated with spot.

Reconciling across the rebrand boundary

Reconciliation is where the Huobi-to-HTX continuity is proven rather than just asserted. Exports for a long-standing account can arrive split by era or carry different naming on either side of the 2023 rebrand, and a process that reconciles only the HTX-era data will show a break exactly where the Huobi history was dropped. CryptaCount stitches the two eras into one continuous balance, tracks the running position across the name change, and compares it to what the venue reports — so the rebrand becomes invisible to the reconciliation and any genuine gap, rather than the naming artefact, is what surfaces for investigation. For an auditor, that is the evidence that the cost basis carried across the rebrand is real and unbroken.

How CryptaCount ingests HTX activity into the sub-ledger

Once your read-only key is connected, CryptaCount pulls your HTX history and keeps it current, writing each event as a discrete, timestamped record in the crypto sub-ledger. The general ledger only ever sees summarised journal entries, but the underlying detail is preserved in full so reconciliations, gain calculations and audit queries always have something concrete to stand on.

Ingestion is idempotent: each HTX event is keyed to its own identifiers, so re-syncing a period never duplicates an entry. That matters because you will refresh the data repeatedly — after a close, after a corrected export, after adding history — and balances must stay stable across every refresh rather than inflating each time. The sub-ledger becomes a dependable single source of truth for everything that happened on HTX, ready to be turned into accounting at scale.

Classifying and reconciling HTX transactions

CryptaCount turns raw HTX data into accounting events by classifying each record: a spot trade, a derivatives open or close with its realised PnL, a funding payment, an Earn reward, or a transfer — whether the record carries the Huobi or the HTX name. Each maps to the right accounts, and the rebrand boundary is treated as a continuation of the same account rather than a break, so cost basis carries straight through.

Reconciliation proves the books against the exchange. CryptaCount tracks the running balance implied by your classified history and compares it to the position HTX reports, so a gap in history or an unclassified line surfaces as a discrepancy instead of quietly distorting balances. Any break between the sub-ledger and the venue is explainable and visible in your crypto sub-ledger → — the same control discipline an accountant applies to a bank reconciliation.

Cost basis and gain/loss for the books

Every disposal on HTX — a sale, a conversion into another asset, or a withdrawal your policy treats as a disposal — needs a cost basis so the realised gain or loss can be measured and posted. CryptaCount maintains acquisition lots per asset and consumes them on disposal under your chosen method, then books the resulting gain or loss to the general ledger alongside the asset movement.

Because the lots live in the sub-ledger, the posted figure is never opaque: you can drill from a gain on the GL back to the specific acquisitions it consumed, even across thousands of trades. See the available cost-basis methods → for how each consumes lots and shapes your reported results.

Transfers between your own accounts

Finance teams frequently move assets between HTX and other venues or wallets, and every one of those movements is a chance to mis-book a disposal. When you move an asset out of HTX into your own wallet, or in from another account, nothing has been sold — yet a naive import sees a withdrawal and a deposit and risks recognising a gain that never occurred. CryptaCount matches the two legs into a single movement of the same asset, carrying the original cost basis across the move instead of resetting it.

Matching considers asset, quantity, timing and direction, and flags anything it cannot confidently pair for human confirmation rather than guessing — exactly what an auditor wants to see when an asset crosses between accounts.

Fees and internal movements

HTX charges fees on its activity, and in aggregate those fees are a material part of the economics. CryptaCount captures each fee and treats it per your policy — adding a trading fee to an acquisition's cost basis, netting it against proceeds on a disposal, or booking it as an expense — so reported cost and gain reflect what activity actually cost.

• Trading fees — capitalised into basis or netted against proceeds per your measurement policy.
• Derivatives funding — recorded as cost or income, kept distinct from trading fees.
• Earn rewards — recognised at fair value on receipt and given a cost basis for the later disposal.
• Internal movements — paired across your own accounts and excluded from gain calculations, with basis carried forward intact.

Controls and the audit trail

The HTX connection is read-only — transaction history only, never trading or withdrawal access — a control you can evidence directly to an auditor or board. Every general-ledger line CryptaCount produces is traceable: a posted journal entry drills back through the sub-ledger to the exact HTX event behind it, with its date, asset, quantity and the figures that produced it. That unbroken chain from GL to source is what makes high-volume crypto books auditable, produced as a by-product of normal processing rather than reconstructed under deadline pressure at close.

Summarised entries keep your ERP clean while the transaction-level evidence stays in the sub-ledger, and the same data feeds your crypto compliance reporting → so statements and sub-ledger never diverge. The journals — debits, credits and account mappings — are reviewable before they reach the GL via journal entries →, so nothing is posted blind.

Multi-entity and treasury considerations

Organisations operating on HTX at scale rarely run through a single account or a single legal entity. CryptaCount's workspace model keeps each entity's HTX activity in its own books, with its own measurement policy and chart of accounts, while still reporting across the group when needed — a fund running several strategies, a firm serving multiple clients, or a treasury spanning subsidiaries.

That separation underpins both accuracy and governance. Cost basis, transfer matching and gain calculation all run within an entity's books, so a movement between two entities is treated as the intercompany transfer it is, not netted away. Review and permissions are scoped per workspace, supporting the segregation of duties auditors expect.

Common pitfalls when accounting for HTX activity

• Forgetting the Huobi era. Pre-2023 history is part of the HTX cost basis; dropping it at the rebrand boundary breaks later disposals.
• Skipping the derivatives ledger. Futures and swap PnL and funding are separate from spot.
• Missing Earn income. Rewards are income at receipt and set later basis.
• Booking transfers as sales. Moving assets to your own custody is not a disposal — match the legs.
• Hand-keying summaries into the GL. Manual entry breaks the trail back to the HTX (or Huobi) event behind each figure.

How CryptaCount uses your HTX data

CryptaCount reads your full HTX history — across the Huobi rebrand — through a read-only connection, classifies every spot trade, derivative position, funding payment, Earn reward and transfer into accounting events, carries basis through the name change, reconciles back to the venue, and posts summarised journal entries to your ERP — with full detail retained in the sub-ledger so every figure is traceable to its source.