Seller details collected and checked Transactions and fees per seller Report ready for the Dutch Tax Administration

Custom DAC7 reporting for seller data

Appfront builds integrations for platform operators who must report their sellers' details under DAC7. Marketplaces and rental and services platforms collect sellers' details, check them, count transactions and fees per seller, and report to the Dutch Tax Administration (Belastingdienst) every year. The software pulls the data from your platform, flags what is missing, and prepares the report and the copy for the seller.

What is a DAC7 reporting integration for seller data?

Since 2023, digital platforms have been required under the European DAC7 directive to collect, check and report data about their sellers to the tax authorities. This covers, among other things, the sale of goods, the rental of real estate and vehicles, and personal services. The platform operator reports per calendar year, by 31 January of the following year at the latest, and every reported seller receives a copy of their own data.

In practice, the data is scattered: seller profiles in the platform, payments in a payment system, and transactions in a database. Tax numbers are missing or incorrect. Which sellers fall under an exemption is worked out by hand at the end of the year. And the report is put together at the last minute, with the risk of errors that a seller later runs into in their own tax return.

We build custom because platforms differ: which activities you facilitate, how sellers register, which data you already have, and which systems you use. Whether your platform falls under DAC7 and which rules apply to your sellers is something you determine with your tax adviser; the software makes sure the data and the report are correct.

Complete data

Seller data from your platform, checked, with a request to the seller if something is missing.

Counted per seller

Transactions and fees per seller and per period, and who needs to be reported.

Reporting ready

The report in the Dutch Tax Administration's format, and a copy for each seller.

How we build your DAC7 reporting integration for seller data

We start with your platform: which activities, how sellers register, which data you already have, and where transactions and payments are stored. It often turns out that certain data isn't requested at registration. We set up the registration accordingly, so that missing data is collected at the start from now on, rather than at the end of the year.

1
Mapping your platform

Your activities, sellers, data and systems.

2
Data and checks

Seller data collected, checked and completed.

3
Counting and determining

Transactions and fees per seller, and who to report.

4
Reporting and maintenance

Reporting, a copy for the seller, and ongoing maintenance afterwards.

What a DAC7 reporting integration for seller data actually does

The components below appear in almost every DAC7 reporting setup. Which ones you need depends on your platform.

Sellers

Data from your platform.

Validation

Missing or incorrect data.

Request

The seller completes the rest.

Counts

Transactions and fees per period.

Reporting

In the Dutch Tax Administration's format.

Copy

For every reported seller.

Who we build a DAC7 reporting integration for seller data for

The integration is intended for platforms that report under DAC7.

Marketplaces

Many sellers of goods. The counts are the core.

Rental platforms

Homes and vehicles. The data matters most.

Service platforms

Personal services. Validation is what you need.

Platform builders

Software for platforms. The reporting is the core.

Technology and integrations

This page is about DAC7 reporting. For building a platform, see our page on a marketplace platform, for VAT our page on VAT compliance software, and for identifying customers our page on KYC and AML compliance software. You can read about our approach on custom software development.

DAC7 Seller data Tax identification number Data validation Transactions and fees Exceptions Reporting to the Dutch Tax Administration Copy for the seller Payment system integration Validation record

Why Appfront for your DAC7 reporting integration for seller data?

A report compiled at the last minute produces errors that a seller later discovers in their own tax return. That's what we build against: complete data, counted per seller, and a report that's ready when you need it.

In time

Report ready before the deadline.

Accurate

Data validated and completed.

Demonstrable

The validation is recorded.

Security and privacy in a DAC7 reporting integration for seller data

The software processes personal and tax data of sellers, such as identification numbers and bank account numbers. Access is strictly set up per role, data is used only for the reporting, and every access is logged.

The software runs in a European data centre or in your own environment, with encrypted storage, daily backups and two-factor login.

Frequently asked questions about a DAC7 reporting integration for seller data

Questions that platform operators ask before getting started.

It pulls seller data from your platform, validates and completes it, counts transactions and fees per seller, determines who must be reported, produces the report in the Dutch Tax Administration's format, and a copy for every reported seller.

Per calendar year, by 31 January of the following year at the latest. The data must be collected and validated before the end of the year. What applies in your situation, you agree with your tax adviser.

That follows from the DAC7 rules. There are exceptions, for example for sellers of goods who stay below a threshold. The software applies the rules you have established with your tax adviser, and shows why a seller is or isn't reported.

The software sends the seller a request to complete it, and keeps track of when that happened. Data that is incorrect is flagged, so it can be corrected before reporting.

Yes. Every reported seller receives a copy of their own data, so it can be used in their own tax return. The software prepares that copy per seller.

Yes, if they have an interface or export. Sellers come from the platform, payments from the payment system, and the validation is recorded for your records.

Check that first. Some platform packages and payment services have a DAC7 feature, and that may be enough. Custom software makes sense when data is scattered, when you facilitate multiple activities, or when the reporting is currently done by hand at the last minute.

A DAC7 report that's ready on time?

Tell us which activities your platform facilitates, how sellers register and where transactions and payments are held. We'll show you what the checks, the counts and the reporting look like.

Edit content