By Operator One Editorial — 2026-06-14
DAC7 is now in its fourth reporting cycle, and the 2025 calendar-year filings — due to tax authorities by 31 January 2026 — were the first round where most EU Member States had fully bedded in their cross-border exchange mechanism. For brands selling across 27 EU markets and the UK, this means tax authorities in Almere, Lucca, Madrid, Warsaw and everywhere in between now hold a granular, reconciled picture of marketplace revenue that, until very recently, simply did not exist in any single place. Understanding what is reported, by whom, and against which thresholds is no longer a compliance nicety — it is the baseline for running a clean marketplace operation in Europe.
What DAC7 actually requires
EU Council Directive 2021/514, commonly known as DAC7, amended the Directive on Administrative Cooperation to bring digital platform operators inside the tax-transparency regime that already covered banks and financial intermediaries. The text was adopted in March 2021 and entered into force on 1 January 2023, with the first reports filed in January 2024 covering calendar year 2023.
The mechanics are straightforward in principle. Any platform that allows third-party sellers to offer goods, rent immovable property, provide personal services or rent any mode of transport must, once per year, collect and verify a defined set of seller data and transmit it to the tax authority of the Member State in which the platform is resident, has its place of management, or is incorporated. That authority then automatically exchanges the file with every other Member State in which a reported seller is resident or where reported immovable property is located. Non-EU platforms that facilitate relevant activities for EU-resident sellers — or for property in the EU — are pulled into the same regime via a registration mechanism in a single Member State.
For brands selling physical goods, the only one of the four "relevant activities" that matters is the sale of goods. That is the lane the entire Amazon, bol, Kaufland, Cdiscount, ManoMano, Allegro and Zalando cohort sits in.
The thresholds that actually trigger reporting
DAC7 includes a narrow de-minimis carve-out for sellers of goods, and it is the only threshold a marketplace brand will ever bump into in practice. A seller is excluded from reporting for a given calendar year only if both of the following are true on the same platform in that year:
- The seller completed fewer than 30 sales of goods, and
- The total consideration paid or credited to the seller was below EUR 2,000.
Cross either line — 30 transactions or EUR 2,000 in gross consideration — and the seller is reportable for that entire year on that platform. The thresholds are per platform, not aggregated across marketplaces, which is why a brand operating on six marketplaces will routinely appear in six separate DAC7 filings even if its total volume on any one of them is modest. For any brand running a serious cross-border programme across the EU 27 and UK, the threshold is irrelevant in practice — you are always reported.
The exact data points shared with tax authorities
The DAC7 schema is more invasive than most sellers initially realise. For every reportable seller, the platform transmits, at a minimum:
- Legal name of the entity (or first and last name for an individual)
- Primary address
- Tax Identification Number (TIN) and the Member State that issued it — separately, for every Member State in which the seller is tax-resident
- VAT identification number, where one has been issued
- Business registration number (KvK, Handelsregister, Registro Imprese, etc.)
- Existence of any permanent establishment in the EU through which relevant activities are carried out, with the Member State identified
- The financial-account identifier (typically IBAN) to which consideration is paid or credited
- The name of the account holder, if different from the seller
- Per quarter: total consideration paid or credited, the number of relevant activities, and any fees, commissions or taxes withheld or charged by the platform
The quarterly granularity matters. Tax authorities do not just receive an annual lump number — they receive four buckets that can be reconciled directly against quarterly VAT returns, OSS filings and corporate tax provisioning. Mismatches at the quarter level are the single most common trigger for an inquiry letter.
Brand-side implications
For brands, DAC7 has rewritten three things at once.
VAT and OSS reconciliation are no longer a private matter. A brand's gross consideration as reported by, say, Amazon DE under DAC7 should reconcile — with documented exceptions for returns, currency conversion and platform-charged fees — to the same brand's German VAT returns and OSS declarations. Tax authorities now run automated reconciliations between DAC7 inflows and VAT outflows. A persistent delta of more than a few percent draws attention.
Permanent establishment risk is exposed. The directive explicitly asks platforms to flag whether the seller has a permanent establishment in any Member State through which the relevant activity is carried out. Brands using FBA inventory in multiple countries, or fulfilment partners across the EU, need a defensible position on PE — one that the platform's own declaration will not contradict.
Entity hygiene became load-bearing. The TIN, VAT number, KvK / registration number and IBAN that a seller registers on each marketplace are now flowing, unaltered, to multiple tax authorities. Mismatches between marketplace records and tax records — a stale director name, an old IBAN belonging to a previous corporate vehicle, a VAT number from an entity that has since been restructured — produce structured data errors that authorities follow up on directly. This is also where the merchant-of-record model materially changes the picture: where O1 is the seller of record, it is O1's KvK 90562704, O1's Dutch VAT identification and O1's IBAN that flow through DAC7, not the brand's.
Common errors that trigger flags
Across the 2024 and 2025 reporting cycles, a consistent pattern of issues has emerged in the inquiries that follow DAC7 exchanges:
- TIN format errors — a TIN entered with spaces, a leading zero dropped by a spreadsheet, or the wrong Member State code attached to an otherwise valid number. These produce immediate validation failures at the receiving tax authority.
- Multiple tax residencies undeclared — a brand legally resident in two Member States that registered only one TIN on the marketplace. The platform reports a single residency; the second authority eventually notices the gap via cross-referenced corporate filings.
- IBAN belonging to a different legal entity — common after restructurings or when a holding company's account is used to receive marketplace payouts for an operating subsidiary. Under DAC7, the platform reports both the seller and the account-holder name, and the mismatch is visible immediately.
- Quarterly mismatches with VAT returns — a brand declaring gross sales of one figure in its OSS return while DAC7 shows a materially different figure for the same quarter on the same marketplace, with no reconciliation note for returns, refunds or fees.
- Missing permanent-establishment declaration — using fulfilment centres in a Member State without a corresponding PE or VAT registration position. The DAC7 file shows activity flowing through that Member State; the tax file shows no registration.
- Stale legal address — a head-office address that moved 18 months ago but was never updated on the marketplace account. Notices issued to the reported address never arrive, escalating the matter.
The remediation pattern is consistent: correct the master data on every platform simultaneously (a brand cannot fix it on one and let the others lag), file a voluntary correction with the relevant tax authority, and document the chain of changes so that the next reporting cycle reconciles cleanly. See the compliance glossary for the definitions used in this article and the broader DAC framework.
Where Operator One fits
Operator One has operated as merchant of record since 2021, with brand operations run from Almere (NL, KvK 90562704) and Lucca (IT) across the EU 27, the UK and 100+ marketplaces including the live Amazon IE programme. Where O1 is the seller of record on a supported marketplace — for clients ranging from a mid-market apparel brand to Dabur — DAC7 reporting flows under O1's entity, TIN and IBAN, and the brand receives a reconciled quarterly view that lines up with its own books rather than four disconnected platform exports.