DAC7: which platform operators are in scope?
Settle the three scope gates before building the dataset.
Read the questions →Scope tells you which sellers are reportable. This is what actually goes in the file for each of them — and the quarterly breakdown is the part that catches platforms whose systems only hold annual totals.
Council Directive (EU) 2021/514 requires a reporting platform operator to report, for each reportable seller, a defined set of identity and activity information. The record is per seller and per reportable period, not per transaction — but the activity figures inside it are broken down by quarter, which means transaction-level data has to be retained and bucketed even though no transaction is reported individually.
Two blocks make up the record. A common block applies to every reportable seller. A second block applies only where the relevant activity is the rental of immovable property, and it is reported per property listing rather than per seller.
| Item | Notes |
|---|---|
| Name | Legal name for entities; first and last name for individuals. Not the display name used on the platform. |
| Primary address | As collected and verified, not as most recently self-edited in a profile. |
| Tax identification number | With the member state of issue. Where none exists, the place of birth is reported for an individual. |
| Value added tax number | Where available. |
| Business registration number | Entity sellers. |
| Date of birth | Individual sellers. |
| Permanent establishments | Each member state through which relevant activity is carried out by an entity seller. |
| Financial account identifier | Where the operator knows it, with the account holder name if different from the seller. |
For each relevant activity, the operator reports the total consideration paid or credited during each quarter of the reportable period, together with the number of relevant activities in that quarter and any fees, commissions or taxes withheld or charged by the operator. The currency in which the consideration was paid is reported with it.
Three properties of this cause most of the implementation work. Consideration is measured when paid or credited, which need not be when the activity occurred. The figure is gross of the operator’s own fees, with those fees reported separately rather than netted. And where an operator does not know the consideration — because settlement happens outside the platform — that is a scope conclusion to document rather than a field to leave empty.
Where the relevant activity is property rental, the operator reports per listed property: the address, the land registration number where known, the total consideration and number of activities per quarter, and the number of days the property was rented during the period together with the type of property. Multiple listings owned by the same seller are grouped by the address they relate to.
This block is the reason a platform can be in scope for property and hold none of the data: land registration numbers and property type are rarely captured by a booking system that only needed an address and a calendar.
Collected information must be determined reliable using records the operator holds, and, where available, electronic interfaces made available by a member state or the Union to confirm the validity of an identification number. The operator retains the records of the steps taken and any information relied on.
Where a seller does not provide the required information after reminders, the consequence is closure of the account or withholding of payment, in line with the transposition in the member state concerned. That consequence is why due diligence design cannot be deferred to the first filing cycle — the remedy is commercial, not clerical.
Primary instruments only. Each is named in full so the reference remains traceable even if a link moves.
REGREP is an independent software provider. This record explains a reporting framework in plain language and is not legal, tax or regulatory advice. Confirm scope, thresholds and submission dates with your competent authority before you file.
More on this framework, and the module that produces the filing.
Settle the three scope gates before building the dataset.
Read the questions →The framework page: population, obligations and penalty powers.
Read the requirements →Due diligence data, seller mapping and the reporting file.
See the module →The breakdown is far cheaper to capture as transactions occur than to reconstruct at filing. We scope the data model first.