DotsDocs
Guides

DAC7 Seller Information

Collect DAC7 seller information from EU payees through a Flow or the API.

DAC7 is the EU directive on administrative cooperation in taxation as amended by Council Directive (EU) 2021/514. It requires digital platform operators to collect identifying and tax information from sellers on their platforms and report it to the tax authority of an EU member state each year.

Dots collects this seller information from your EU payees and stores it for each App. Whether DAC7 reporting applies to your platform is a question for your own tax and legal advisors.

Turning on DAC7 collection

In the Dashboard, open the App’s settings and turn on Report under DAC7 on the Payout tab. While it is on, Dots collects DAC7 seller information from payees whose country is an EU member state.

Seller information

SellerInformation collected
IndividualLegal first and last name, date of birth, primary address
BusinessLegal business name, business registration number, registered office address
BothMember state of residence, taxpayer identification number (TIN) and its issuing member state, optional VAT number

Some member states do not issue a TIN to every resident, and DAC7 lets an individual without one give their place of birth instead. Dots does not accept this for any member state yet, so every seller needs a TIN for now.

Dots checks each TIN against the formats used by its issuing member state. For Cyprus, Hungary, Lithuania, Luxembourg, Malta and Slovakia, a TIN that matches none of the known formats is accepted and recorded as unchecked. Dots looks up VAT numbers in the EU’s VIES service after they are submitted. Financial account details come from the payee’s payout method and are not collected again.

Collecting through a Flow

The compliance step collects DAC7 seller information from EU payees when DAC7 collection is on for the App. You do not need a new step. If the payee also owes a W-8BEN, the step collects both. See Flow Payouts to create a Flow.

Requests, reminders and the payout hold

Turning on DAC7 collection does not email your payees. To ask them, open the Tax Center in the Dashboard, go to the DAC7 tab and select Request DAC7 information. Dots then emails each EU payee who has not given their seller information, in your App’s name, with a link to a Flow that collects it. To ask a single payee, select Request on their row.

Once you have asked all your payees, Dots asks new EU payees for you. It asks each one 7 days after they connect to your App. A payee who connected earlier and later moves to an EU member state is asked on the next daily run.

A payee who has not submitted gets a reminder 14 days after the first request and a final reminder 30 days after it. Each email states the date payouts will be held.

From 60 days after the first request, and never before the final reminder has gone out, the payee’s payouts from your App are held until they submit their seller information. The hold lifts as soon as they do. A payee who submits before the hold date is never held.

Collecting through the API

If you collect seller information in your own UI, send it with Submit Compliance Information in a dac7 object. Send dac7 in its own request, not together with w8ben or w9.

curl --request PUT \
  --url https://api.dots.dev/api/v2/users/{user_id}/compliance \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --data '{
    "dac7": {
      "entity_type": "individual",
      "legal_first_name": "Anna",
      "legal_last_name": "Schmidt",
      "date_of_birth": "1990-01-15",
      "address": {
        "line_1": "Hauptstrasse 1",
        "city": "Berlin",
        "postcode": "10115",
        "country": "DE"
      },
      "member_state_of_residence": "DE",
      "tin": "36574261809",
      "tin_issuing_member_state": "DE"
    }
  }'

A business sends business_name and business_registration_number in place of the name and date of birth. no_tin_issued is reserved for sellers whose member state does not issue them a TIN, and is rejected until Dots supports it.

A VAT number without a country prefix is read as belonging to member_state_of_residence. A number with another member state’s prefix keeps it.

Errors come back in two shapes:

  • When the dac7 object fails validation, the response is a 400 with the error code invalid-input and an errors array. A field with the wrong type or format has its path in loc. A rule that spans fields, such as a missing tin, returns an empty loc and names the field in msg.
  • Checks made after validation return a 400 with a top-level field. A TIN that does not match its member state’s formats returns invalid-dac7-tin, a VAT number that is not a valid EU VAT number returns invalid-dac7-vat-number, and a legal name that is blank once normalized or a date of birth that differs from the user’s returns invalid-input.

If the user’s name is already verified, the submitted legal name must match it. Small differences such as diacritics or spelling are accepted, and the user keeps their verified name. A name that does not match returns a 409 with status-conflict.

Checking a user’s status

Get a User returns three DAC7 fields in its compliance object:

FieldDescription
must_collect_dac7DAC7 collection is on for the App and the user’s country is an EU member state.
dac7_collectedThe user’s DAC7 seller information has been collected for the App.
dac7_vat_number_statusThe VIES check of the seller’s VAT number: pending, valid or invalid. null when no VAT number was given.

The VIES check runs after the submission, and can take several attempts while a member state’s service is down. When it finishes, Dots sends a user.updated webhook. A pending VAT number does not hold up dac7_collected. An invalid VAT number cannot be reported, so dac7_collected is false until the seller corrects the number or removes it, since it is optional. The compliance step asks the seller again and marks the VAT number as unverified. If you collect through the API, resubmit dac7 with a corrected vat_number or without one.