Portugal’s crypto reporting rules now form part of an operational system of user due diligence, annual reporting and international exchange. The current Article 124-A requires reporting cryptoasset service providers within its scope to communicate information concerning reportable users resident in Portugal and certain controlling persons. It still does not determine whether a reported transaction is taxable.
What changed in 2026
The earlier version of Article 124-A required persons and entities providing custody, administration or trading-platform services to report operations in which they intervened. Law 26/2026 replaced that wording with a framework tied to the Portuguese implementation of DAC8 and CARF.
The revised provision refers to reporting cryptoasset service providers subject to the duties in Decree-Law 61/2013. It imports due-diligence and reporting procedures and covers information relating to reportable cryptoasset users who are Portuguese tax resident or whose controlling persons include reportable Portuguese residents.
Facts: deadline, data and formats
Current Article 124-A sets 31 May as the annual deadline for communicating the previous calendar year’s information. It requires electronic formats approved by ministerial order, based where appropriate on European Commission technical specifications. Data-protection, security and confidentiality rules also apply.
The European Commission states that DAC8 applies from 1 January 2026. Reporting service providers collect information on reportable transactions from 2026, with first reporting and exchanges in 2027. The operational detail therefore includes both law already in force and technical implementation that must be checked in its latest official form before a filing is made.
Interpretation: the report and the return answer different questions
A service provider reports according to definitions, due diligence and data fields in the reporting regime. The taxpayer reports and pays tax according to the substantive income-tax rules. Gross transaction data, transfers and balances may not correspond to a taxable gain figure.
This is not a contradiction. It is the reason reconciliation matters. A tax authority may receive data that requires acquisition cost, holding period, ownership, transfer history or activity classification before any tax conclusion can be drawn.
Scenario: a transfer that looks like a disposal
Assume a Portuguese-resident user moves cryptoassets between two platforms. One data set shows an outbound transaction and another shows an inbound transaction. If the user controlled both accounts, the event may require different tax analysis from a sale to a third party, but the reporting data alone may not explain that ownership chain.
The user needs records showing wallet addresses, account ownership, transaction identifiers and the corresponding acquisition history. Conversely, a disposal omitted from personal records may become visible through provider data. In both directions, identity and transaction reconciliation come before legal characterisation.
The strongest objection
Reporting is not an accusation. It should not be described as if every reportable user has underpaid tax. Many reportable operations may be correctly declared, non-taxable or require adjustments before reaching a taxable amount. The regime’s effect is increased visibility and comparability, not an automatic assessment.
General practical considerations for users
Users should maintain one transaction ledger that reconciles exchanges, custodians and self-hosted wallets. Residence details and tax-identification numbers should be consistent across providers. The ledger should distinguish acquisitions, disposals, transfers, fees and receipts for work or other activities.
Tax analysis then classifies each event under the law for the relevant year. Records should explain differences between provider-reported gross data and the figures included in the return.
General practical considerations for providers
Providers need a documented scope analysis, user and controlling-person due diligence, residence procedures, data governance, retention, annual filing controls and monitoring of the approved electronic format. A legacy reporting process designed around the previous February deadline is not enough for the revised framework.
Cross-border groups should allocate responsibility clearly. Provider location, registration, user residence and the jurisdiction receiving information are separate elements of the reporting map.
Key takeaways
- Portugal’s current framework links Article 124-A reporting with DAC8/CARF due diligence and exchange architecture.
- The annual Portuguese deadline is 31 May for the previous calendar year, subject to the applicable electronic specifications.
- Reported data must be reconciled, but reporting alone does not establish a taxable gain or non-compliance.
Sources
- Portuguese Tax Authority — current Article 124-A
- Portuguese Tax Authority — previous Article 124-A wording
- Diário da República — Law 26/2026
- European Commission — DAC8 implementation
Disclaimer
This article provides general information only and does not constitute tax, legal or accounting advice. Reporting duties and tax treatment depend on the provider, user, residence, transaction, technical rules and law applicable to the reporting and tax periods.
