Contractor Compliance (DAC7)
Learn what DAC7 may mean for platforms and businesses working with contractors, including reporting and documentation basics.
Important disclaimer: This article is for informational purposes only. It does not constitute legal or tax advice. DAC7 obligations vary by EU member state, and implementation details continue to evolve. Consult qualified EU tax counsel before making compliance decisions. Ruul does not provide tax advice; Ruul provides invoicing and payment infrastructure, including its own compliance processes where required.
The EU’s DAC7 directive is not about workers. It is not about whether your contractors are employees. It has nothing to do with worker classification.
DAC7 is about tax transparency. Specifically, it requires digital platforms to report income earned by sellers, including freelancers and contractors, directly to EU tax authorities. Those authorities then share the data across all member states. The goal is to close the gap between income earned through platforms and income declared to tax offices.
If your business operates a digital platform that connects sellers to buyers, this directive affects how you collect data, how you verify it, and what you file every January. If your business simply uses platforms to source contractors, the reporting obligation sits with the platform, not with you.
Understanding that distinction is the starting point for everything that follows.
What DAC7 Is
DAC7 is the informal name for Council Directive (EU) 2021/514, which amended the EU’s foundational Directive on Administrative Cooperation. It is the seventh major amendment to that framework, which is why it carries the “DAC7” label.
It entered into force on 1 January 2023. The first reporting cycle covered calendar year 2023, with reports due to tax authorities by 31 January 2024 and the first exchange of information between member states taking place in February 2024, as confirmed by the European Commission’s Taxation and Customs Union directorate.
The directive does not introduce new taxes. It does not change how income is taxed. It creates a reporting infrastructure that makes existing tax rules enforceable in the digital economy. Income earned on platforms was always taxable. DAC7 ensures tax authorities can actually see it.
Do not confuse DAC7 with the EU Platform Work Directive, which addresses worker classification and employment status. Those are separate instruments with separate scopes. DAC7 is solely about tax reporting by platforms.
Who DAC7 Applies To
The reporting obligation under DAC7 falls on “Reporting Platform Operators.” The directive defines these as entities that contract with sellers and make a digital platform available to facilitate the performance of Relevant Activities.
Both EU-based and non-EU-based platforms fall within scope if they have EU-resident sellers or facilitate the rental of EU property. An EU platform reports to its home member state. A non-EU platform must register in a single chosen member state and report there. The EU then distributes the data across member states automatically.
The Relevant Activities covered by DAC7 are:
- Rental of immovable property, including residential, commercial, and parking spaces
- Personal services, meaning time or task-based work carried out at the request of a user
- Sale of goods
- Rental of any mode of transport
The personal services category is the one most relevant to businesses engaging contractors and freelancers. Platforms like Upwork and Fiverr fall squarely within it. So does any marketplace that connects businesses to independent workers and facilitates those transactions.
Importantly, for personal services there is no minimum earnings threshold. A single transaction triggers full DAC7 reporting obligations for the platform. The €2,000 / 30-transaction threshold that does exist applies only to sellers of goods, not to personal services providers. A freelancer earning €50 through a platform is reportable.
Certain platforms are excluded from the definition of Reporting Platform Operator. Payment processors (such as Stripe, PayPal, or Adyen) that only move money without facilitating the underlying transaction are outside scope. So are platforms that purely list or advertise services without being party to the transaction or aware of its value.
Which Sellers Are Affected
DAC7 covers individual contractors and incorporated service providers transacting through platforms. The personal services category includes freelance developers, designers, writers, consultants, coaches, tutors, and anyone performing time or task-based work through an online marketplace. Drivers and couriers using gig economy platforms are also in scope.
DAC7 additionally covers sellers of goods via marketplaces and property hosts renting EU-located immovable property, even if the host is not EU tax resident.
The €2,000 / 30-transaction threshold exemption applies only to goods sellers. There is no de minimis threshold for personal services: freelance work is reportable from the first euro. Contractors are required to provide their TIN to platforms to remain compliant; failure to do so after two reminders gives the platform grounds to restrict or close the account.
Some categories are excluded entirely: government bodies, publicly traded companies, and certain large operators already subject to equivalent regulatory reporting.
What Data Must Be Reported
For each reportable seller, the platform must collect, verify, and report the following:
| Data Point | Details |
|---|---|
| Full legal name & primary address | Required for all reportable sellers |
| Date of birth | For individuals |
| Country of residence | Determines which tax authority receives the data |
| Tax Identification Number (TIN) | Issued by the seller’s member state of residence |
| VAT identification number | Required for business entities |
| Company registration number | For incorporated sellers |
| Financial account identifier | IBAN or equivalent bank account used for payouts |
| Consideration paid or credited | Per quarter and for the full calendar year |
| Number of transactions | Total for the reportable year |
| Fees, commissions, or taxes withheld | All amounts deducted by the platform |
For rental of immovable property, the report also includes the full property address, land registration or cadastral number, and number of rental days.
Platforms cannot simply accept self-certification from sellers. The directive imposes a due diligence obligation: platforms must verify that information collected is accurate and reliable. For VAT numbers, the EU’s VIES system provides a validation mechanism. For national TINs, platforms must take reasonable steps to determine reliability even where direct verification against national tax registries is not technically feasible.
Sellers must also receive a copy of the information reported about them before it is submitted to the relevant authority.
Data records must be retained for between five and ten years, depending on member state implementation. Keeping those records organised and exportable from day one is not optional housekeeping: it is a compliance requirement. Ruul’s tax-ready document storage approach reflects the same logic for freelancers and businesses operating in the platform economy.
When and How to Report
The annual reporting cycle works as follows:
- Due diligence deadline: 31 December of the calendar year being reported
- Reporting deadline: 31 January of the following year
So, data on seller activity during 2025 must be verified by 31 December 2025 and reported by 31 January 2026.
Reports are filed electronically with the tax authority of the member state where the platform is registered or has chosen to register for DAC7 purposes. The submission format uses a standardised XML schema. Once filed, that member state shares the data automatically with all other member states where reported sellers are tax resident.
Non-EU platforms must register in a single EU member state before they begin facilitating activity involving EU-resident sellers. The one-stop-shop structure means a platform does not need to register and file separately in every EU country.
If a seller fails to provide required information after two reminders, the platform is required to either close that seller’s account or withhold payment until the information is supplied. This is not optional it is a prescribed action under the directive.
Country-Level Nuances
While the directive sets a common framework, EU member states adopted DAC7 at slightly different times and with different penalty structures. Ireland extended initial deadlines into February 2024. Spain introduced its local DAC7 rules in early 2024 with retroactive effect from 1 January 2023. The Netherlands and Sweden publicly reference specific statutory fines per incorrect seller record.
From 2026 onward, reporting deadlines are expected to stabilise around 31 January, but platforms should always verify national tax authority announcements for each reporting year. Non-EU platforms choosing a member state for registration should factor in language, submission interface, and enforcement style.
Which Businesses Are NOT Reporting Platform Operators
If your business uses a platform to find and hire contractors, you are the buyer. You are not the platform. The reporting obligation belongs to the platform, not to you.
A company that hires freelance developers through Upwork does not have a DAC7 reporting obligation. Upwork does. A company that sources creative work through Fiverr is not a Reporting Platform Operator. Fiverr is. The entity that contracts with sellers and operates the technology facilitating transactions is the platform; the entity that pays for services through that platform is the buyer.
Similarly, a business that engages contractors directly outside of any marketplace has no DAC7 reporting obligation under this directive. Direct payment relationships between a business and its contractors do not constitute a platform in the DAC7 sense.
The line that matters: an internal procurement system used to manage your own contractors is not a digital platform under DAC7. A marketplace where third parties transact with each other is. If your business operates a technology product that connects independent sellers to buyers, and you facilitate those transactions, you need to assess whether you qualify as a Reporting Platform Operator.
If your software or community site has evolved into something resembling a marketplace where independent sellers and unrelated buyers interact, seek specialist tax advice before assuming you are outside scope.
DAC7 and the Agent of Record Model
When a business uses Ruul’s Agent of Record model to engage contractors, the commercial and legal structure shifts in a way that is directly relevant to platform compliance questions.
Under the AOR model, Ruul contracts with the contractor and issues the invoice to the business. The business’s relationship for reporting and payment purposes is with Ruul as a vendor, not directly with individual contractors. Ruul manages its own DAC7 compliance obligations as appropriate to its platform role.
This means businesses processing contractor payments through an AOR structure are not creating the kind of direct platform-to-seller relationship that triggers DAC7 obligations on their side. The compliance infrastructure sits with the platform, not the hiring business.
For businesses managing contractor compliance across multiple jurisdictions, the AOR model reduces direct platform compliance exposure while keeping contractor payments flowing and documentation centralised.
Due Diligence and Onboarding
DAC7 requires platforms to perform structured due diligence on sellers, particularly during onboarding. A compliant onboarding flow typically includes:
- Collecting identity and address information
- Obtaining the seller’s TIN and, where relevant, VAT number
- Verifying names, dates of birth, and registration numbers against identity documents or public registries
- Storing evidence of verification checks in secure internal systems
For pre-existing sellers, platforms had a limited window to complete verification of older accounts effectively by end of 2024 for accounts active before the directive entered into force. If contractors do not provide required data after reminders, the platform may be obligated to restrict accounts, withhold payouts, or close the seller account.
For businesses using Ruul’s contractor onboarding process, identity and tax documentation collection is handled at the point of engagement, which addresses a significant part of this due diligence requirement structurally.
Data Protection and GDPR Interaction
DAC7 operates alongside the General Data Protection Regulation. Platforms must report seller information to tax authorities while also protecting contractors’ privacy rights under GDPR. DAC7 provides a legal basis for processing contractor data for tax reporting purposes, but GDPR still requires clear privacy notices, disclosure of how data will be used and shared with tax authorities, and appropriate security measures.
Data minimisation and retention limits apply: DAC7 requires records to be kept long enough for enforcement (five to ten years depending on member state), but not indefinitely. Freelancers using platforms like Ruul should review privacy documentation to understand how invoicing and payout data will be stored, secured, and shared when required by EU law.
Penalties for Non-Compliance
DAC7 requires each member state to establish penalties that are effective, proportionate, and dissuasive. The amounts vary significantly by jurisdiction.
| Penalty Type | Examples |
|---|---|
| Fixed fines per missing or incorrect seller record | Varies by member state; Sweden references per-record statutory fines |
| Daily accumulating fines | Ireland: €19,045 initial penalty + €2,535 per day the report remains outstanding |
| Large combined fines | Netherlands: up to €900,000 for intentional non-compliance, per Fonoa’s compliance analysis |
| Operational restrictions | Platforms may be suspended from operating in certain EU markets |
| Escalated penalties for intentional avoidance | Deliberate non-reporting attracts significantly larger fines than administrative failures |
Financial penalties are not the ceiling of the risk. If a platform operator continues to fail after receiving two reminders from the member state of registration, the registration is permanently revoked. Beyond that, member states may coordinate to block the platform from operating within the EU entirely. That provision is express in the directive, not theoretical.
DAC7 data is shared across all 27 EU member states automatically. A platform that fails to report in one jurisdiction is not limiting its exposure to that jurisdiction it is creating a compliance gap visible to tax authorities across the entire EU.
Practical Steps for Platform Operators
Step 1: Determine whether you are in scope. Confirm whether your platform facilitates transactions for personal services, property rental, goods sales, or transport rental. If you are purely processing payments or listing without facilitating, the exclusions may apply. Perform a gap analysis of current onboarding, KYC, and payment flows against DAC7 data requirements before drawing conclusions.
Step 2: Implement seller due diligence at onboarding. You need a structured process for collecting and verifying seller information at the point of registration TINs, VAT numbers, addresses, dates of birth, and bank account details before sellers begin transacting. Annual aggregation at year-end is not sufficient.
Step 3: Build systems to track reportable transactions quarterly. You need per-seller visibility into consideration paid, transaction counts, and fees withheld, broken down by quarter. Back-end systems must aggregate this data throughout the year, not reconstruct it in January.
Step 4: Register with the appropriate member state tax authority. EU-based platforms report to their home member state. Non-EU platforms must select a single EU member state and register before facilitating activity involving EU-resident sellers.
Step 5: Build the January 31 annual reporting cycle into your operations calendar. 31 December is the due diligence completion deadline. 31 January is the filing deadline. Both are hard dates.
Step 6: Monitor the 2028 reform proposals. The European Commission has published proposals to reform DAC7 as part of a broader consolidation of the DAC framework. Among the proposed changes: removing the 30-transaction threshold for goods sales and raising the annual goods threshold from €2,000 to €3,000. The Irish Presidency of the EU Council is targeting conclusion of negotiations by end of 2026, with implementation by end of 2027 and most changes taking effect in 2028, per analysis by VATCalc. Due diligence obligations remain largely unchanged in the proposed reform.
Step 7: Assign internal ownership and engage qualified EU tax counsel. The technical complexity of DAC7 implementation including XML schema requirements, TIN validation, GDPR interaction, and member state variations requires specialist advice and a named internal owner responsible for the annual reporting cycle.
Conclusion
DAC7 draws a clear line. If you operate a platform that facilitates contractor and freelance transactions involving EU-resident sellers, you have reporting obligations that are active now. The first full reporting cycle has already run. Tax authorities across the EU are receiving and exchanging this data.
If you are a business that hires contractors through platforms, the obligation belongs to the platform, not to you. But if you run a marketplace or platform product, the obligation is yours and the consequences of ignoring it are substantial.
For businesses using Ruul’s Agent of Record model to engage contractors, Ruul manages its own DAC7 compliance as a platform operator, reducing your direct platform compliance exposure. Learn more about how Ruul handles contractor payments globally.
FAQs
Does DAC7 change how much tax I owe as a freelancer or contractor?
No. DAC7 does not set tax rates or create a new tax. It only changes how tax information about platform income is shared with tax authorities. The obligation to report all income in your annual tax return exists under domestic law, independently of DAC7. If your income includes earnings from a marketplace (reported under DAC7) and income from direct clients (self-reported), both go into the same annual return. Only a qualified local tax advisor can estimate your actual liability.
Will I receive a DAC7 statement from every platform I use?
Many major platforms issue annual summaries showing total earnings, fees, and transaction counts. However, DAC7 does not require platforms to issue a specific named form to freelancers the obligation is to report to tax authorities. Most platforms also share figures with sellers for transparency. Log into each platform at year-end to download transaction summaries and retain them for tax preparation.
If I work with clients exclusively through Ruul, do I need to file DAC7 reports myself?
No. If you work through Ruul’s Agent of Record model, Ruul manages any platform-level reporting obligations that apply, including DAC7 where relevant. You do not submit DAC7 reports to tax authorities on Ruul’s behalf. You use Ruul’s invoices, payout confirmations, and annual summaries when filing your own taxes. Keep your profile and tax details accurate within Ruul so that payout records are consistent with what tax authorities may receive.
Does DAC7 apply if I am based outside the EU but work with EU clients?
DAC7 scope turns primarily on whether the platform has EU-resident sellers or EU-located property not solely on where the client is located. If a non-EU contractor uses an EU-based or EU-registered platform, their income may still be reported under DAC7, and this information can be shared with EU member states and potentially forwarded to non-EU tax authorities through separate international agreements. Non-EU freelancers working frequently with EU clients should ask platforms how they handle DAC7 and consult a local advisor on double taxation treaty implications.
How can my business reduce DAC7 exposure when hiring contractors across the EU?
If your company does not want to operate its own reporting platform, avoid building a marketplace where third-party sellers transact with external buyers. Route contractor engagements through Ruul so your firm holds a single vendor relationship, and Ruul as Agent of Record manages its own compliance obligations including DAC7 where applicable. Review your contractor engagement model annually with legal and tax advisors to confirm you have not inadvertently created a platform-like environment that should be assessed under DAC7.