CoinLedger Alternatives: Transaction Limits, Imports and Reporting

Which CoinLedger alternative should you use?

Koinly is the first alternative to test if CoinLedger's report pricing, international workflow or transaction-tier structure no longer fits.

It offers a substantial free environment for reconciliation before report purchase.

The current Koinly free plan supports up to 10,000 transactions, unlimited wallets and exchange accounts, portfolio tracking, smart transfer matching, DeFi and NFT support, exchange APIs, CSV files, EVM auto-sync and imports from several non-EVM ecosystems.

Its current paid tiers begin at $49 per tax year for 100 transactions, $99 for 1,000, and from $199 for 3,000 or more.

CoinTracking deserves the strongest comparison when your problem is different.

If you have a long history across many tax years, CoinTracking's subscription economics can be materially different from buying individual CoinLedger reports for multiple years.

Its current paid plans include tax reports across tax years, and the platform supports API imports, CSV files, manual entries and direct blockchain imports.

ZenLedger is another practical comparison for U.S.-oriented users, especially where its current 5,000-transaction or 15,000-transaction tiers align with the portfolio.

Crypto Tax Calculator deserves a test if the primary reason for leaving CoinLedger is complex smart-contract activity rather than report cost.

CoinTracker can also be worth evaluating where its portfolio and tax-filing ecosystem matches the exchanges and filing software you already use.

But CoinLedger remains the correct answer for many portfolios.

Its current data-quality tools are unusually important.

The Asset Balance Report lets users inspect the transactions CoinLedger uses to calculate balances and compare calculated balances with reported balances where available.

The Missing Cost Basis workflow attempts to trace incomplete acquisition history.

The Potential Bridges, Trades and Transfers view can surface likely pairs that were imported separately.

Those are accounting controls, not decorative features.

If the difficult part of your ledger is decentralized finance rather than CoinLedger itself, TokenToolHub's Crypto Tax Software for DeFi Users provides a more protocol-focused comparison.

When you should keep CoinLedger

Switching tax software is not inherently an upgrade.

If CoinLedger already imports your complete history, recognizes your important bridges and transfers, maintains balances that reconcile with reality, and produces the reports you need, migration can create new problems without solving an old one.

CoinLedger's current free workflow makes this particularly important.

You can import transaction history from supported exchanges, wallets, blockchains and DeFi integrations before buying the final report.

Its current pricing page also lists unlimited wallet and exchange synchronization across plans.

This means a user is not forced to choose a paid tier before discovering whether their account is messy.

The correction tools are a legitimate reason to stay

A missing cost basis warning is not merely an inconvenience.

It means the software lacks enough information to know how some asset was acquired.

CoinLedger's current troubleshooting system treats incomplete history as the primary suspect.

It can direct the user toward missing exchanges, missing wallets, duplicate data, unimported mining or staking income, unsupported smart-contract activity, direct wallet purchases and other gaps.

Its Potential Bridges, Trades and Transfers system is also designed for a real import problem.

Sometimes an exchange or blockchain source returns one side of an economic event as a withdrawal and another as a deposit.

CoinLedger can identify pairs that may belong together and suggest a transfer, bridge or trade classification.

The user can confirm, reject or reclassify the suggestion.

If your history contains many cross-chain movements, this workflow can save substantial correction time.

The Asset Balance Report adds another control

CoinLedger's current Asset Balance Report shows the transactions used to calculate an asset's balance.

For some supported sources it can compare the software's calculated balance with a balance reported from the connected exchange or wallet.

A tax report should not be trusted merely because the software produced one.

If the ledger says you own twice as much ETH as you actually own, reconciliation is unfinished.

A product that makes those inconsistencies easier to find can be worth more than a cheaper product with fewer controls.

How CoinLedger transaction limits actually affect cost

Raw blockchain activity and billable tax-software transactions are not necessarily the same number.

CoinLedger currently prices reports according to billable transactions within the relevant tax season.

Its public pricing page lists the Hobbyist report at $49 for up to 100 transactions, Investor at $99 for up to 1,000, and Pro from $199 for 3,000 or more.

Additional transaction capacity is available for users beyond the top displayed threshold.

The platform's current pricing guidance distinguishes billable transaction types from rows that do not count the same way toward the assigned plan.

Buys, sells, trades, taxable income and several other economic activities can count.

Standalone deposits and withdrawals treated as non-taxable self-transfers are handled differently from billable Transfer records for pricing purposes.

Fees can affect tax calculations without necessarily counting as separate billable transactions.

CoinLedger also has pricing treatment designed to reduce the effect of some high-frequency micro-reward activity.

The practical implication is simple:

A 3,500-transaction wallet may not mean 3,500 billable events

One DeFi transaction can emit many token-transfer events.

A wallet can receive spam assets.

Staking systems can generate frequent rewards.

A bridge can create actions on two networks.

An exchange can break a large order into many fills.

How the accounting product normalizes those records can materially change the plan required.

This is also why transaction-limit comparisons between products need caution.

Koinly, CoinTracking, CoinLedger and ZenLedger do not necessarily count the same raw history identically for plan purposes.

When replacing CoinLedger becomes rational

Import parity before report comparison

How to test CoinLedger alternatives without inventing accuracy scores

A real accounting-software comparison needs a known input.

If you import a personal wallet whose correct tax outcome is already uncertain, you cannot measure software accuracy simply by choosing whichever result looks most believable.

The better approach is a synthetic ledger containing transactions whose source facts are known in advance.

The fixture should contain ordinary activity, deliberately difficult activity and a few intentional errors.

Each shortlisted product receives the same fixture.

Then you record what imported, what failed, what required manual correction and what remained unresolved.

This article does not claim that TokenToolHub completed a controlled paid-account fixture across every platform and every current jurisdiction.

Where a capability is discussed, it reflects documented product behavior or an evaluation method the user can reproduce.

No fictional import success rate, transfer-match percentage or alert-style accuracy number is presented.

A useful synthetic ledger

What to measure

Do not score only whether the final report downloads.

Count missing records.

Count duplicates.

Count transfer pairs that require manual merging.

Count missing prices.

Count incorrect asset mappings.

Count DeFi events requiring manual reclassification.

Record the time spent resolving each category.

Compare ending asset balances with the known fixture.

Only after those checks should you compare capital gains, income and final reports.

CoinLedger as the baseline

Koinly: strongest broad alternative

CoinTracking: strongest alternative for multi-year reconstruction

ZenLedger: useful for U.S.-oriented transaction tiers

Crypto Tax Calculator: a DeFi-heavy alternative to test

CoinTracker: another ecosystem-driven option

Report cost and transaction-limit comparison

Current prices can change.

The larger analytical point is more durable: transaction tiers are not directly comparable until you know what each product counts.

CoinLedger uses billable transaction logic for tax-report pricing.

Koinly groups certain exchange activity and excludes some spam and small rewards from transaction counts.

CoinTracking applies its own total-history transaction limits.

ZenLedger assigns a plan after the imported activity is calculated.

Import your data before declaring one product cheaper whenever the software allows it.

Multi-year reconstruction can reverse the ranking

A single-year comparison can make CoinLedger look inexpensive.

A five-year reconstruction can produce a different answer.

Suppose an investor needs downloadable reports for five tax years.

If each year requires a separate eligible CoinLedger report, the total cost is the sum of those five purchases.

Koinly also requires a plan for each tax year whose report is generated.

CoinTracking's paid-plan model is different because tax reports for historical years are included within the active plan, subject to the transaction capacity of the account.

ZenLedger offers discounts for multiple years under its current pricing structure.

This means there is no universal cheapest option.

CoinLedger migration: preserve the source history first

A tax-software migration should be treated as a new accounting reconstruction, not as a simple account export.

Before leaving CoinLedger, download the reports and transaction records you may need later.

Keep original exchange CSV files separately.

Keep wallet addresses.

Keep blockchain transaction hashes.

Keep evidence supporting manual historical prices.

Keep notes explaining manual classifications.

Keep any reports already used in a filed return.

Do not delete the old system until the replacement ledger has been reconciled.

Original data should outrank transformed data

If Coinbase supplied the original trade history, retain it.

If a transaction exists on Ethereum, retain the public address and transaction hash.

If you manually valued an OTC purchase, preserve the invoice or other valuation evidence.

An export from CoinLedger is useful, but it may already contain classifications made by CoinLedger or by you.

If one of those classifications was wrong, using only the transformed export can preserve the mistake in the new platform.

A safer six-stage migration

Transfer matching is the most important migration test

Self-transfers create one of the easiest ways for crypto tax software to produce a false gain or missing cost basis.

Consider a user who bought 1 ETH for $1,500.

They later move that ETH from an exchange to a hardware wallet.

The exchange records a withdrawal.

The blockchain wallet records a deposit slightly later.

The amount received may be lower because of a fee.

If the software links those records as one own-wallet movement, the historical acquisition information can continue through the ledger.

If the records remain separate, the destination deposit can appear to have no acquisition history.

A later sale may then generate missing basis or an incorrect gain.

CoinLedger's current correction path

CoinLedger can automatically detect many transfers.

If it cannot, its Potential Bridges, Trades and Transfers view can suggest likely transaction pairs.

It also provides a Create Transfer workflow for cases where one side of the event is missing and only a small amount of manual reconstruction is needed.

That tool should not become an excuse to fabricate a large missing history.

If hundreds of source records are absent, importing the source CSV or API data is more defensible than creating hundreds of synthetic transfer legs.

Bridge transactions need more than timestamp matching

A cross-chain transfer can look like a simple self-transfer.

It can also hide a swap.

A bridge route might lock native USDC and mint or release corresponding USDC elsewhere.

Another route might accept ETH, swap it to USDC, bridge liquidity and deliver USDC on the destination chain.

Those are not technically identical transactions.

Do not decide the tax classification from the word "bridge" in the application interface.

Investigate what assets actually left and what assets actually arrived.

TokenToolHub's Bridge Tokens Between Chains guide explains the technical distinction between cross-chain movement and routes that perform additional asset conversions.

Decode ambiguous transactions before changing the tax ledger

Sometimes the accounting problem is actually a transaction-understanding problem.

The tax product says "trade."

You remember a bridge.

The wallet UI says a contract interaction.

The transaction contains several transfers.

Before forcing the accounting label, establish what happened on-chain.

For supported EVM networks, TokenToolHub's Transaction Decoder can help inspect completed transaction methods, token movements, approvals, logs and execution evidence.

That tool does not determine tax treatment.

It gives you technical evidence that can be interpreted under the appropriate accounting and tax rules.

Duplicate imports can be worse than missing imports

Users often create duplicates because they are trying to be thorough.

They connect Coinbase through an API.

Then they upload a Coinbase CSV.

Then they import a wallet that contains some of the same transfers.

A duplicate acquisition can inflate asset quantity.

A duplicate sale can inflate disposals.

A duplicate reward can inflate income.

Eventually the ledger stops reconciling.

CoinLedger automatically filters many duplicates, but its current documentation explicitly warns that some combinations can still create them.

One documented example is combining API and file imports for the same exchange.

The Missing Cost Basis Troubleshooting workflow can also identify duplicated wallet or file imports as a potential source of problems.

Every alternative should face the same duplicate-import test.

Missing cost basis should trigger investigation, not guesswork

When CoinLedger warns about missing basis, the software is telling you that a later asset movement exists without a sufficiently established acquisition history.

The cause can be simple.

You forgot an old exchange.

You imported Coinbase but not the separate historical Coinbase Pro activity.

You did not import the wallet that received staking rewards.

You imported a withdrawal but not the matching deposit.

You purchased through a self-custody wallet's third-party provider and the purchase record is absent.

A smart contract is unsupported and its deposit arrived as an uncategorized transaction.

The correct response is to reconstruct the history wherever possible.

CoinLedger currently permits a Manual Position workflow for situations where basis genuinely needs to be established manually, but its own guidance recommends complete transaction history rather than treating manual basis as the default fix.

Missing historical prices need an evidence trail

An obscure token can trade without a reliable institutional price feed.

An NFT may have no standardized spot price.

A receipt token can represent an underlying position rather than a freely traded market.

Tax software should surface that limitation.

A complete-looking report built on arbitrary price assumptions is worse than a warning that requires human review.

If you enter a manual price, preserve the source used to determine it.

That could be an actual trade price, contemporaneous DEX liquidity, an exchange record, an invoice or another valuation method appropriate for the jurisdiction.

The key is reproducibility.

Solana activity can expose classification weaknesses

Not every blockchain instruction moves economic ownership.

On Solana, token approvals can grant delegated authority.

Revokes can remove that authority.

Associated token account operations can change account state.

Program interactions can create several instructions without representing a sale.

If your CoinLedger migration includes significant Solana activity, test those operations specifically.

TokenToolHub's Solana Token Approvals and Revokes guide explains how delegated token authority differs from ownership transfer.

A tax importer should not turn an approval-management instruction into a fictional disposal merely because it does not understand the program action.

Hardware-wallet histories still need complete imports

Moving assets into cold storage does not remove them from the tax record.

The old exchange acquisition history still matters.

The withdrawal still matters.

The blockchain deposit still matters.

The network fee still matters.

Future movement from cold storage needs to connect back to that history.

CoinLedger currently documents a Ledger wallet import workflow using either blockchain wallet addresses or exported Ledger Live transaction files.

If a user stores assets with a hardware wallet, the important accounting requirement is not the hardware brand.

It is preservation of acquisition and movement records.

Never give tax software a hardware-wallet recovery phrase or private key.

Public addresses, read-only data and transaction exports are sufficient for legitimate accounting imports.

Use public-wallet research as context, not as a tax report

A public wallet can help reconstruct what an old address did.

It cannot by itself tell tax software what you originally paid on a centralized exchange.

It may not reveal legal ownership.

It may not reveal an off-chain OTC agreement.

It does not determine your jurisdiction's tax classification.

TokenToolHub's Wallet Risk Scanner can provide public-address activity and counterparty context for supported networks.

Use that information to investigate the transaction history.

Do not call the result a tax report.

Ending balances are one of the strongest error checks

Suppose your real wallets and exchanges collectively contain 3.2 ETH.

The tax software says 8.6 ETH.

The ledger is not ready.

A duplicate deposit may exist.

A sale may be missing.

A staking deposit may have been interpreted as a disappearance.

A bridge may have been counted on both source and destination chains without connecting the movement.

A liquidity position may be represented incorrectly.

A spam token could be mapped to the wrong asset ticker.

The difference should be understood before generating the report.

CoinLedger's Asset Balance Report is designed to help trace which transactions produced the calculated amount.

CoinTracking similarly emphasizes balance checks after imports.

Koinly provides balance and error-reconciliation tools.

Whatever product you choose, use this control.

Jurisdiction rules come after transaction facts

Crypto tax software can automate calculations.

It cannot rewrite the law.

The same on-chain event can require different accounting treatment depending on the taxpayer's country, facts and circumstances.

That is why migration testing should separate two questions.

First: what happened?

Second: how does my jurisdiction treat it?

United States: own-wallet transfers and wallet-based basis records

Current IRS digital-asset guidance states that transferring digital assets from a wallet, address or account belonging to you to another wallet, address or account that also belongs to you is generally non-taxable.

The exception includes the digital assets used or withheld to pay transaction services.

That makes correct transfer matching important.

The software should not casually interpret the principal movement as a sale merely because one side originated at an exchange and the other appeared on-chain.

The United States also changed the importance of wallet-level record keeping.

Final digital-asset basis rules apply wallet-based or account-based ordering principles to acquisitions and dispositions beginning January 1, 2025.

Revenue Procedure 2024-28 provided a safe harbor for allocating previously unattached basis to wallets or accounts as part of the transition.

Current IRS guidance also phases in digital-asset broker reporting.

Brokers began gross-proceeds reporting for covered transactions from January 1, 2025, while basis reporting for certain transactions begins for relevant 2026 activity.

A U.S. user migrating tax software therefore needs complete wallet and exchange records, not merely a global portfolio total.

United Kingdom: beneficial ownership is central

HMRC's current Cryptoassets Manual states that moving tokens between public addresses that the individual beneficially controls is not a disposal where beneficial ownership is retained throughout the transaction.

By contrast, exchanging one token type for another is included within the disposal framework.

HMRC's cross-ledger guidance also emphasizes examining the actual facts of the transaction.

This matters for bridges.

The label "bridge" does not settle whether the economic asset remained the same throughout the route.

UK users also need strong record retention.

HMRC's published guidance emphasizes keeping transaction dates, units, sterling values, wallet addresses, exchange records and related evidence.

Australia: the fee can be different from the transfer

The Australian Taxation Office currently states that moving a cryptoasset from one wallet to another while maintaining ownership is not itself a disposal.

Its guidance also states that if the crypto holding is reduced to pay a network fee, that fee transaction can have capital-gains consequences.

This is a useful example of why tax software needs to separate principal movement from transaction costs.

A single blockchain action can contain an economically non-dispositive transfer and a fee that needs separate treatment.

Correction history matters during migration

A mature crypto tax account often contains years of human decisions.

You may have manually reclassified a bridge.

You may have corrected a token ticker.

You may have entered an historical price.

You may have identified an old wallet as belonging to you.

You may have excluded spam.

You may have added a manual OTC acquisition.

Those decisions are part of the accounting record.

If the replacement product does not import them, they need to be documented and recreated deliberately.

A cheaper tax report can therefore be expensive to migrate into.

Measure correction effort instead of feature count

This score is an evaluation framework, not a tax rule.

Run the same fixture through each product.

Total the correction points.

Record the actual time.

The product requiring the fewest unsupported interventions on your real history has a stronger practical claim than the product with the longest integrations page.

Compare report exports before paying

A tax calculator is only useful if it produces the documents needed by the user or accountant.

Before purchasing, identify your actual output requirements.

• Capital gains and losses report.
• Income report.
• Jurisdiction-specific tax forms.
• Transaction ledger CSV.
• Audit or reconciliation report.
• Tax-preparation software export.
• Wallet-specific cost-basis records where required.
• Accountant access.
• Historical reports needed for amendments.

CoinLedger currently provides a range of IRS, tax-filing-software and CSV outputs after report purchase.

Koinly provides international tax reports, audit reports and tax-software exports on paid plans.

CoinTracking includes tax reports and a larger collection of portfolio and accounting reports on its paid plans.

ZenLedger includes detailed reports on its current DIY tiers.

A plan is not cheap if it omits the report your accountant actually needs.

Your accountant's workflow can change the decision

If a tax professional prepares your return, ask which platforms they routinely use before migrating.

An accountant familiar with CoinLedger may already know how to trace its missing-basis warnings and reports.

Another professional may prefer Koinly's audit files.

A specialist handling a long trading history may prefer CoinTracking.

Switching software can increase professional fees if the accountant must rebuild or reinterpret the ledger.

Build a complete source inventory before migration

A tax ledger can be wrong even when every imported transaction is individually accurate.

The problem can simply be that an entire source is missing.

An old exchange may contain the original acquisition of assets now stored on-chain.

A forgotten wallet may contain the other side of a transfer.

A DeFi address can exist on several EVM networks.

A user may have Bitcoin, Solana and Ethereum accounts generated by one recovery phrase but represented by unrelated public addresses.

Build the inventory first.

Security and privacy matter because tax software maps your financial life

A crypto tax account can connect a verified exchange identity with self-custody wallet addresses and long-term balances.

That dataset is sensitive.

Use read-only API permissions whenever an exchange integration supports them.

Disable trading and withdrawals on API keys created for accounting.

Enable strong account authentication.

Review the platform's privacy and deletion policies.

Export records before closing an account.

Never enter a seed phrase or private key into CoinLedger, Koinly, CoinTracking or any tax product.

Tax software needs transaction records, not asset-control credentials.

Disqualifiers for a CoinLedger replacement

CoinLedger alternatives buyer checklist

Which CoinLedger alternative fits which buyer?

Conclusion: choose the ledger that needs the least unsupported correction

The best CoinLedger alternatives are not determined by one pricing table.

Crypto tax software sits between raw transaction history and a legally meaningful report.

The quality of that bridge depends on data completeness.

It depends on transfer matching.

It depends on cost-basis continuity.

It depends on historical prices.

It depends on correct asset identification.

It depends on how DeFi activity is interpreted.

And it depends on the tax rules applying to the individual user.

CoinLedger remains a strong baseline because it makes several common failure modes visible.

Its Missing Cost Basis workflow directs attention toward incomplete transaction history instead of pretending an unknown acquisition has a known basis.

Its Potential Bridges, Trades and Transfers tool acknowledges that a withdrawal and deposit can belong to the same economic action without assuming every possible pair should be merged.

Its Asset Balance Report gives users another way to trace why the application believes a particular quantity is held.

Those controls matter.

If they already solve your portfolio, staying with CoinLedger can be more rational than chasing a cheaper report.

Koinly is the broadest direct alternative.

Its current free allowance gives users substantial room to import and inspect a complicated history before paying.

The combination of unlimited wallet accounts, smart transfer matching, international reports and broad chain coverage makes it particularly attractive for global users.

Its per-tax-year pricing means multi-year users still need to calculate the full historical cost.

CoinTracking is the more structurally different alternative.

Its current paid subscriptions cover tax reports across years and offer increasingly extensive automatic imports and advanced tools as the plan increases.

For a user reconstructing many years, that can change total economics substantially.

The trade-off is a denser accounting interface and a transaction limit that needs to be considered across the imported history.

ZenLedger is a sensible U.S.-oriented comparison, particularly around its current 5,000-transaction Gold tier.

Crypto Tax Calculator deserves attention where DeFi parsing rather than report pricing is the real bottleneck.

CoinTracker is another established option where its portfolio and filing integrations match the user's ecosystem.

But none should be selected before import parity is established.

Give every candidate the same history.

Start with original exchange data.

Add every public wallet.

Add every relevant blockchain.

Include old accounts that now show a zero balance.

Include staking and reward history.

Include bridges.

Include DeFi.

Include NFTs.

Include manual transactions.

Then ask whether the product reconstructs the actual asset quantities.

If ending balances are wrong, stop there.

If basis is missing, find the acquisition.

If transfers are broken, repair them.

If a bridge looks like a trade, inspect the underlying transaction.

If a historical price is unavailable, document the valuation rather than accepting an invented number.

If two products disagree, find the transaction that created the difference.

The jurisdiction layer comes next.

United States users now have additional reasons to preserve wallet-specific records because digital-asset basis rules applying from 2025 use wallet-based or account-based principles.

The IRS also makes clear that movement between taxpayer-owned wallets is generally not a taxable event by itself, while transaction-service fees can require separate treatment.

HMRC similarly focuses on beneficial ownership and distinguishes movement between addresses a person controls from exchanges into different token types.

The ATO likewise distinguishes own-wallet movements from disposals and specifically identifies network-fee implications when crypto is used to pay the fee.

This is why a tax application's default label cannot be accepted as tax law.

The application organizes evidence.

You, your accountant and the applicable tax rules determine the reporting treatment.

Migration cost should also be measured realistically.

A $50 saving can disappear quickly if the replacement creates four hours of manual bridge correction.

A more expensive tool can be the cheaper accounting system when it accurately imports the protocols responsible for most of your activity.

A subscription can be more economical than one-time reports when many historical years need reconstruction.

A one-time report can be more economical when you need only a single year.

There is no universal cheapest structure.

Before leaving CoinLedger, preserve your audit trail.

Download tax forms.

Keep the transaction ledger.

Keep original CSVs.

Keep wallet addresses.

Keep transaction hashes.

Keep manual valuation evidence.

Keep notes explaining unusual classifications.

Do not close the old account while the replacement still contains unexplained balances or basis.

If a transaction is technically ambiguous, investigate it independently.

TokenToolHub's Transaction Decoder can help establish what occurred in a supported EVM transaction.

The Wallet Risk Scanner can provide additional context around supported public addresses.

Neither is a tax calculator.

Their role is to improve the evidence available when the accounting software produces a questionable interpretation.

If an alternative does not improve that equation, it is not a better tax system for your portfolio.

FAQs

References and primary documentation

• CoinLedger integrations
• CoinLedger current report pricing and transaction tiers
• CoinLedger Potential Bridges, Trades and Transfers documentation
• CoinLedger missing cost basis guidance
• CoinLedger Asset Balance Report documentation
• CoinLedger duplicate transaction troubleshooting
• CoinLedger report download documentation
• CoinLedger Ledger wallet import documentation
• Koinly integrations
• Koinly current pricing and transaction limits
• CoinTracking current pricing
• CoinTracking exchange, wallet and blockchain imports
• CoinTracking import and reconciliation guidance
• ZenLedger current DIY pricing
• Crypto Tax Calculator product information
• CoinTracker crypto tax and portfolio platform
• IRS frequently asked questions on digital asset transactions
• IRS digital assets guidance and 1099-DA reporting information
• IRS Revenue Procedure 2024-28 on digital-asset basis allocation
• HMRC guidance on cryptoasset disposals and beneficial ownership
• HMRC guidance on transfers between distributed ledgers
• HMRC cryptoasset record-keeping guidance
• Australian Taxation Office cryptoasset guidance

Crypto tax software pricing, transaction limits, integrations, tax-form support and calculation behavior can change. Tax treatment depends on jurisdiction and the actual economic facts of each transaction. Preserve original records, reconcile complete transaction history, verify material classifications against current official tax guidance and consult a qualified tax professional where treatment is uncertain. This guide is educational research and does not constitute tax, legal, accounting or investment advice.