Quick answer
Tax lot accounting tracks each crypto purchase separately — enabling you to choose which specific coins you sell to minimise tax.
Reporting
Australia
Canada
United Kingdom
United States
Tax Lot Accounting
The practice of tracking each individual purchase of a crypto asset as a separate lot with its own cost basis and acquisition date.
AustraliaCanadaUnited KingdomUnited StatesUnderstanding Tax Lot Accounting on crypto
Tax lot accounting treats each purchase of a cryptocurrency as a separate 'lot' with its own acquisition date, quantity, and cost basis. This approach enables the application of cost basis methods like FIFO (oldest lots first), HIFO (highest-cost lots first), or Specific Identification (choosing exactly which lot to dispose of). By contrast, pooling methods (as required by HMRC) merge all lots into an average. Tax lot accounting is the foundation of most US crypto tax software and enables sophisticated tax optimisation strategies like minimising short-term gains and maximising long-term treatment by carefully selecting which lots to sell.
Tax lot accounting treats each purchase of a cryptocurrency as a separate 'lot' with its own acquisition date, quantity, and cost basis. This approach enables the application of cost basis methods like FIFO (oldest lots first), HIFO (highest-cost lots first), or Specific Identification (choosing exactly which lot to dispose of). By contrast, pooling methods (as required by HMRC) merge all lots into an average. Tax lot accounting is the foundation of most US crypto tax software and enables sophisticated tax optimisation strategies like minimising short-term gains and maximising long-term treatment by carefully selecting which lots to sell.
What this means for your crypto activity
HIFO and specific ID
Accurate lot tracking is prerequisite for HIFO and specific identification cost basis methods in the US.
Holding period
Each lot has its own acquisition date — essential for determining short-term vs long-term holding period.
DCA investors
DCA (dollar-cost averaging) investors have many lots to track — one per purchase.
UK pooling override
In the UK, lot tracking is irrelevant — pooling rules replace individual lot matching.
Software automation
Crypto tax software manages lot tracking automatically across thousands of transactions.
- Accurate lot tracking is prerequisite for HIFO and specific identification cost basis methods in the US.
- Each lot has its own acquisition date — essential for determining short-term vs long-term holding period.
- DCA (dollar-cost averaging) investors have many lots to track — one per purchase.
- In the UK, lot tracking is irrelevant — pooling rules replace individual lot matching.
- Crypto tax software manages lot tracking automatically across thousands of transactions.
Seeing it in action
Example scenario
Jake uses dollar-cost averaging and buys ETH monthly for 12 months — creating 12 separate tax lots. When he sells 2 ETH, he can choose (under Specific ID) to sell the two lots with the highest cost basis, minimising his taxable gain. Without lot-level tracking, he couldn't make this selection. His software identifies that his November and December purchases have the highest cost basis and allocates them to the disposal.
How this works across jurisdictions
- Australia
Individual lot tracking supported for CGT purposes; FIFO is common default.
- Canada
ACB method averages all identical property — individual lot tracking not applicable for identical assets.
- United Kingdom
HMRC's pooling rules override individual lot accounting — pool average cost applies to all disposals.
- United States
Tax lot tracking enables FIFO, HIFO, and Specific Identification methods; adequate records (date, amount, price per lot) must be maintained; Specific ID requires identifying lots at time of sale.
Take Control of Your Crypto Finances
From crypto taxes to accounting, KoinX helps you manage, track, and stay compliant and to end.
![[object Object]](/_next/static/media/ISO_27001-2022_certification.ae776691.svg)
![[object Object]](/_next/static/media/GDPR_Compliance.a2dc5933.svg)
![[object Object]](/_next/static/media/SOC_2_Type_II_certification.dd69381e.svg)
