Skip to content
Solved
SearchBrowse
Sign in

Contents

Official guidance
International Exchange of Information Manual

IEIM8000500 · Reporting Requirements

  • IEIM8000510 · Introduction
  • IEIM8000515 · The types of information to be reported to HMRC
  • IEIM8000520 · Relevant transaction
  • IEIM8000530 · Acquisition and disposals of relevant cryptoassets against fiat currencies
  • IEIM8000540 · Acquisitions and disposals of relevant cryptoassets against other relevant cryptoassets
  • IEIM8000550 · Exchange types
  • IEIM8000555 · Wrapping and liquid staking
  • IEIM8000560 · Reportable retail payment transactions
  • IEIM8000565 · Transfers other than reportable retail payment transactions
  • IEIM8000570 · Transfers to the reportable user
  • IEIM8000575 · Transfers by the reportable user
  • IEIM8000580 · Collateral
  • IEIM8000585 · Transfers to external wallet addresses
  • IEIM8000590 · Valuation requirements for reportable retail payment transactions and other transfers
  1. Reporting Requirements
  2. Introduction

IEIM8000510 | Introduction

From HM Revenue & Customs · International Exchange of Information Manual

The Reporting Cryptoasset Service Providers (Due Diligence and Reporting Requirements) Regulation 2025 (the ‘Regulations’) introduce transaction-based reporting on relevant cryptoassets. These transactions must be reported on an aggregate basis per user, categorised by relevant cryptoasset and the type of transaction.

The Regulations require that UK RCASPs use a dedicated XML Schema and User Guide to provide the information to HMRC. The information reported to HMRC on cryptoasset users who are resident in a CARF implementing jurisdictions outside the UK will be exchanged annually. Information on UK cryptoasset users will be reported by UK RCASPs to HMRC, as well as received from other CARF implementing jurisdictions.

Some RCASPs may choose to use a third party to submit their information to HMRC. The RCASP will remain responsible for the accuracy and completeness of information where a third party is used.

Next
PrivacyTerms