A creator marketplace can process thousands of payments without ever being the business that files a DAC7 return. Conversely, a SaaS platform that never touches the money may still have a reporting obligation. The key question behind who files DAC7 reports is not simply who pays the seller. It is who operates the platform that enables the transaction.
For finance, operations and marketplace teams, that distinction matters. Getting it wrong can mean chasing tax data after year-end, repairing incomplete seller records, and managing a reporting process that was never designed into the product.
Who files DAC7 reports?
DAC7 reporting is generally filed by the reporting platform operator. This is an operator of software, an app, website or other digital platform that enables sellers to connect with users and carry out certain reportable activities.
In practical terms, a business may need to report where its platform enables sellers to earn income from:
- the sale of goods;
- personal services, such as creator campaigns, consulting, design, coaching or freelance work;
- the rental of immovable property; or
- the rental of a means of transport.
The rules apply across EU Member States and can also capture non-EU platform operators with an EU connection. A platform operator may be within scope if it is tax resident, incorporated, managed, or has a permanent establishment in an EU Member State. Non-EU operators facilitating relevant activity for EU sellers or users can also be in scope, subject to applicable registration and equivalent reporting arrangements.
The report is submitted to the relevant tax authority, typically by 31 January following the reportable calendar year. National implementation can affect registration, filing mechanics and deadlines, so the exact position should be checked in the Member State where the operator is required to report.
The crucial distinction: payer, platform and seller
A DAC7 report is not normally filed by every business that pays a freelancer, influencer or affiliate. A brand running a one-off campaign and paying ten creators directly is usually acting as a customer of those services, not as a platform operator.
Likewise, the creator or affiliate receiving payment does not usually file the DAC7 report. They may need to provide data to the platform during onboarding or periodic verification, and they remain responsible for their own tax obligations. DAC7 reporting does not replace a seller’s income tax return, VAT obligations or local registration requirements.
The reporting responsibility sits with the operator of the marketplace or platform where sellers can offer, sell or perform the relevant activity. That can include a creator marketplace, affiliate network, gig platform, booking marketplace or software product connecting buyers and sellers at scale.
Payment flow is relevant, but it is not the deciding test. A platform can be reportable even where funds move directly from the buyer to the seller. Equally, a payment provider that merely processes a transfer, without operating the marketplace relationship, is not automatically the DAC7 reporting platform.
When creator and affiliate platforms are likely in scope
For the creator economy, DAC7 most often becomes relevant when a business operates a structured network rather than simply buying marketing services.
Consider a platform where brands search for creators, agree campaign terms and commission work through the product. If the platform enables the creator to provide a personal service to the brand, it may fall within scope. The same analysis can apply to an affiliate platform that facilitates commercial relationships between merchants and publishers, particularly where the platform manages seller onboarding, campaign participation, earnings or settlement data.
A more straightforward agency model may produce a different outcome. If an agency contracts with a brand, procures creator services itself and remains the genuine service provider, it may not be operating a reportable multi-sided platform. But the answer can change if that agency launches a self-service portal where brands and creators contract or transact with one another.
This is why labels such as “agency”, “marketplace” or “payments platform” are not enough. The operating model matters: who can access the platform, who has the contractual relationship with the sellers, what activity the product enables, and whether the platform is facilitating transactions between distinct users.
Which sellers and activities can be excluded?
Not every seller visible on a platform must appear in a DAC7 report. The Directive includes exclusions, but teams should apply them carefully rather than treating them as a reason to avoid due diligence altogether.
Excluded seller categories can include government entities, certain listed entities and sellers with a high volume of property rentals in a year. There are also circumstances in which a platform may qualify as an excluded platform operator because it does not allow sellers to profit from the relevant activity, or because it exclusively facilitates excluded activity.
For creator, affiliate and UGC programmes, the most common reportable category is personal services. A creator paid for producing content, attending an event, promoting a product or delivering a campaign is typically providing a service. The fact that the deliverable is digital does not, by itself, remove it from scope.
A platform should not rely on broad assumptions such as “our creators are individuals” or “we only pay small amounts”. DAC7 is designed to provide tax authorities with visibility over platform-enabled income. Low-value or occasional activity can still require accurate seller records where the platform is in scope.
What information goes into a DAC7 report?
The filing is only the final step. The operational work starts when the seller joins the platform.
For individuals, the operator will generally need to collect and verify identifying information such as name, primary address, tax identification number, VAT registration number where available, date of birth and the financial account used for payment. For entities, the required data includes legal name, address, tax identifiers and business registration details.
The report also includes financial data. Platform operators generally need to calculate the consideration paid or credited to each seller during each quarter, the number of relevant activities, and fees, commissions or taxes withheld or charged by the operator. Property rental platforms have additional property-level data requirements.
This is where many teams encounter a practical problem. Campaign management, invoicing, creator onboarding and payouts often live in separate systems. One tool holds the brief, another holds payment details, a spreadsheet tracks invoices, and finance only sees a bank transfer reference. Producing a defensible annual report from that structure is slow and error-prone.
A better approach is to treat DAC7 data as operational data. Collect it at onboarding, validate it before payout, retain an audit trail of checks and keep seller status aligned with transaction data throughout the year.
A practical DAC7 workflow for platform operators
A workable process has three stages: determine scope, build due diligence into onboarding, and reconcile reportable payments continuously.
First, map your model. Identify whether your product enables reportable activities, where your entity is established or managed, where sellers and users are based, and whether another entity in your group is actually the platform operator. Document the conclusion. This is particularly valuable when product, legal and finance teams have different views of what the platform does.
Second, collect seller data before the first payment. Ask for the fields required for DAC7 alongside KYC, payout and tax information. Do not leave tax IDs, addresses or legal names until the reporting deadline is close. Sellers are far more likely to respond when missing information blocks an onboarding or payout step than when they receive a year-end email months after a campaign.
Third, create a payment ledger that can answer basic questions quickly: who earned what, for which activity, in which quarter, after which deductions, and through which legal entity? If a seller is paid in euros, pounds and dollars across multiple campaigns, finance still needs one reliable source of truth for reportable consideration.
For platforms paying internationally, the process should also account for currency conversion, failed payouts, refunds, reversals and payment timing. A payment approved in December but settled in January can create reporting questions depending on when the consideration was paid or credited under the applicable rules. These are not details to resolve manually across hundreds of seller records.
Does using a merchant of record remove DAC7 responsibility?
Not automatically. Outsourcing invoicing, settlement or tax administration can simplify the evidence trail, but it does not by itself determine which entity is the reportable platform operator.
The answer depends on the contractual and operational arrangement. If your company continues to operate the marketplace and facilitate the seller’s activity, it may remain the entity with DAC7 obligations. If another provider is genuinely positioned as the relevant intermediary and manages the seller relationship and reporting role, responsibilities may be different. The structure should be reviewed before launch, not after the first reporting year closes.
For teams managing creator payments, an infrastructure model such as Zexel Pay can centralise onboarding, payment records, invoices and tax documentation. That makes the compliance workflow more manageable, but the legal reporting analysis still needs to follow the facts of the platform model.
Common DAC7 mistakes that create avoidable risk
The most expensive mistake is assuming DAC7 is a finance-only project. Product decisions determine what seller data is collected, legal terms determine relationships, and operations teams often hold the evidence behind transactions. Reporting cannot be repaired efficiently by exporting payment data in January.
Another common issue is treating invoices as the full compliance record. An invoice may show a fee, but it may not prove the seller’s tax residence, validated identity, account ownership or quarterly payment position. The same applies to a W-9 or a local tax form: useful for its own purpose, but not a substitute for DAC7 due diligence.
Finally, do not confuse a consolidated supplier invoice with a complete platform audit trail. One invoice can simplify accounts payable. It does not remove the need to know which creator or seller ultimately earned each amount when your business is the relevant reporting operator.
The useful next step is simple: map the seller journey from onboarding to payout and ask whether every reportable field can be produced without chasing a spreadsheet, a creator or a former colleague. If the answer is no, fix the workflow while the volume is manageable.
