Skip to content
Netherlands

CESOP reporting in the Netherlands: Digipoort guide

Fintech Passport
June 22, 2026 · 12-min read
CESOP reporting in the Netherlands: Digipoort guide

CESOP reporting in the Netherlands means filing quarterly cross-border payment data to the Belastingdienst through Logius’ Digipoort, by the end of the month after each quarter, under articles 39a to 39d of the Wet op de omzetbelasting 1968. A payment service provider files once it handles more than 25 cross-border payments to the same payee in a quarter (the Belastingdienst puts it as “from 26”). Filing is machine to machine only: an XML data file and a metafile over the Digipoort FTP interface, signed with a PKIoverheid certificate. There is no web form. Since this guide was first written, CESOP has gained its own Digipoort endpoint, foreign firms without a KvK number can connect directly, and new releases arrive in December 2026 and July 2027.

Last reviewed: 8 November 2026

CESOP rests on two EU texts. Council Directive (EU) 2020/284 added Articles 243a to 243d to the VAT Directive, which set the record-keeping duty for payment service providers. Council Regulation (EU) 2020/283 amended Regulation (EU) No 904/2010 to create the central database and the collection timetable. Commission Implementing Regulation (EU) 2022/1504 adds the technical detail, including the standard electronic form. For the EU-wide rules see what CESOP reporting is, and for the build see the hub on CESOP data and system readiness.

The Netherlands transposed the Directive through the Wet implementatie Richtlijn betalingsdienstaanbieders (parliamentary file 36231). That law inserted a new Section 6, “Algemene verplichtingen voor betalingsdienstaanbieders”, into Chapter VI of the Wet OB 1968 with effect from 1 January 2024:

  • Article 39a defines the terms by cross-reference to PSD2, including payment service (Annex I points 3 to 6).
  • Article 39b sets the obligation. A provider keeps sufficiently detailed registers of payees and payments for each calendar quarter. The duty covers only cross-border payments and starts at more than 25 cross-border payments to the same payee in a quarter, counted per member state and per identifier. The payer’s provider is relieved where at least one of the payee’s providers is located in a member state, but it still counts those payments toward the threshold. Registers are kept electronically for three calendar years from the end of the year of payment.
  • Article 39b(7) is the Dutch addition that matters operationally. Where the Netherlands is the competent member state, the provider must hand the registers to the tax inspector on its own initiative. You do not wait for a request.
  • Article 39c sets the location rules: the payer’s or payee’s IBAN or other unambiguous identifier first, and the BIC of their provider only as a fallback.
  • Article 39d lists the register contents, mirroring Article 243d of the VAT Directive.

Penalties sit in article 41 of the same Act. Failing to meet the Section 6 obligations through intent or gross negligence is an offence that the inspector can fine up to the sixth category amount under article 23 of the Dutch Criminal Code. Article 41(2) applies the same fine to a provider that reports payees with fewer than 26 cross-border payments in a quarter, so over-reporting is also a breach. The power to fine lapses five years after the end of the calendar year in which the obligation arose.

2. The quarterly deadline

The deadline is not in the Dutch Act. It comes from Article 24b of Regulation (EU) No 904/2010, which applies directly. Member states collect the data “at the latest by the end of the month following the calendar quarter” by means of an electronic standard form. The Belastingdienst’s manual and its public PSP-CESOP page both state this as delivery within one month after each quarter ends.

QuarterDue at the BelastingdienstSpecification to use (per SDM notices)
Q3 202631 October 2026 (passed)Current release, XSD 4.03
Q4 202631 January 2027Release v19 (Data File spec v2.3), in force from 29 December 2026, still XSD 4.03
Q1 202730 April 2027Release v19, XSD 4.03
Q2 202731 July 2027Release v20, to be used from 1 July 2027, XSD 4.04

Other member states share the dates but not the channels (see CESOP reporting compared). CESOP also belongs in your wider Dutch reporting calendar, next to the DNB returns.

3. Digipoort is the channel, not DNB

Digipoort is the government’s gateway for electronic messages to public bodies. The Belastingdienst’s manual says the data arrives “via Logius’ Digipoort” over a secure connection under its electronic data exchange rules. CESOP uses the Digipoort file exchange interface (Bestandsuitwisseling FTP v1.6.1). Each delivery carries an XML data file and a metafile that describes it. FATCA/CRS filers will know the mechanics, but CESOP has its own message flow, Levering-PSP.

The endpoint changed. From 1 October 2025, Digipoort opened a dedicated CESOP endpoint, oe-cesop.procesinfrastructuur.nl, so that large CESOP volumes cannot slow other message flows. Its use has been mandatory since 1 January 2026. The general endpoint oe.procesinfrastructuur.nl no longer accepts these messages. The change brought a new Digipoort server certificate for your truststore, renewed again in August 2026. A shared FTP account needs a change request at Logius, and in July 2026 Logius asked all FTP users to complete its contact form to keep their CESOP connection.

4. The steps to file, in order

Step 1: confirm that the Netherlands is a filing state for you. You report to your home member state, and to each host member state where you provide payment services through a branch, an agent or under the freedom to provide services. A Dutch-licensed provider files its home-state data here. A provider licensed elsewhere files here for the payment services it provides in the Netherlands. Then test the 25-payment threshold per payee and per member state, and record the conclusion. Article 41(2) penalises reporting payees below the threshold, so the count matters in both directions.

Step 2: subscribe to SDM. The Belastingdienst’s developer support service is called Ondersteuning Digitaal Berichtenverkeer (ODB) in Dutch and Support Digital Messaging (SDM) in English. A support subscription gives you the technical specifications, the Validation Test Service (VTS), the service desk and the PSP_CESOP news releases. The Belastingdienst says no separate tax registration is needed to report. What you need is the technical connection.

Step 3: build or buy the XML generator. It must apply the scope and location rules, aggregate per payee, produce XML to the Belastingdienst’s data file specification and give every file a unique identifier, which the Belastingdienst quotes whenever it writes about that file. For the field-level logic, see how the quarterly CESOP file is built.

Step 4: validate in the VTS. Send test messages and fix what fails. One limitation: SDM said in August 2026 that business rules 40111, 40120 and 40130 cannot be checked by the VTS, so passing the VTS does not prove those rules pass in CESOP. Logius also offers its Aansluit Suite Digipoort, a test environment for the connection itself.

Step 5: get the connection. You need a Digipoort FTP account for Levering-PSP and a PKIoverheid certificate from an accredited trust service provider. Configure the CESOP endpoint, ports and IP addresses from Logius’ technical connection form, and whitelist them.

Step 6: deliver. Upload the data file and metafile, keep the Digipoort receipt, and process both feedback messages (section 6).

5. Foreign providers without a KvK number

The route starts with an email to the Belastingdienst’s PSP-CESOP account management team (the address is in the SDM notice of 2 March 2026). An account manager then takes you through the steps: an FI number, an OIN (the government organisation identification number), the PKIoverheid certificate and the FTP account. Start months before your first deadline.

RouteWho holds the certificateFits when
Direct connection (since March 2026)Your firm, through the Belastingdienst account-manager processYou want to control the filing and the feedback loop yourself
Dutch branchThe branch, which is registered in the Handelsregister (KVK)You already have, or plan, a Dutch establishment
Intermediary (reporter)A service company that files on your behalfYou prefer to outsource the technical connection

With an intermediary, your firm is the source (owner of the data and the obligation) and the intermediary the reporter. Invitations, correction requests and reminders go to the source; processing messages go to the reporter. The legal duty stays with you. For the broader choice between a branch and cross-border services, see branch vs freedom of services.

6. Feedback and the correction route

Each delivery gets up to two return messages, and they come at different stages:

  1. Digipoort receipt and technical check by the Belastingdienst. The Belastingdienst checks the XML against the schema. If the file has no technical errors, it goes to CESOP and you get a no-error message. If it has errors, you get an error message and the file goes no further.
  2. Business-rule check by CESOP. CESOP checks the content. Its result comes back by the route CESOP, Belastingdienst, Digipoort, you: validated (possibly with warnings), partially rejected or fully rejected.
OutcomeWhat you send
Technical error (Belastingdienst)A complete new file, delivered the same way as the original, with a new unique identifier
Fully rejected (CESOP)A complete corrected file
Partially rejected (CESOP)A correction message carrying only the payees in error, each linked to the original record. Under the Commission’s User Guide this means message type CESOP101 with CorrDocRefId
Validated with warningsNo resubmission needed, but warnings are stored centrally and administrations may follow them up

The Commission’s guidelines recommend resubmitting within 30 calendar days of a rejection. CESOP processing has been slow several times: SDM posted delay notices in 2025 and in January, July and October 2026. In February 2026 SDM told providers not to resubmit while waiting, whether with a new file name or a new MessageRefId. It also said that once you can retrieve the Digipoort “.ok” message for a delivery, you have met the formal obligation to file by the deadline. CESOP’s content checks follow later and are handled separately. Keep the .ok messages with your quarterly filing evidence.

7. XSD versions and the 2026-2027 releases

The Netherlands adopts Commission schemas on its own timetable. The Dutch position as of 3 November 2026:

  • XSD 4.03 has been required for Dutch deliveries since the Q1 2025 reports.
  • Release v19 applies from 29 December 2026. It stays on XSD 4.03 and contains small changes that follow from CESOP release 1.8.2. The Q4 2026 report due in January 2027 must follow the latest Part 2 Data File specification (v2.3). SDM moved that date from 12 October 2026 because CESOP’s production date slipped.
  • Release v20 applies from 1 July 2027 and moves to XSD 4.04, the Commission’s newest schema, with larger changes. An earlier SDM notice of 28 October gave 29 December 2026 for v20. SDM’s clarification of 3 November gives 1 July 2027, and that is the date to plan against.

SDM’s known-error list also notes that the isotypes schema lacks the new currency code XCG, so ANG is still reported until a fix is announced.

8. Three worked scenarios

Facts: An e-money institution licensed by DNB (see the Dutch EMI licence) holds accounts for an online seller that is located in Belgium by its IBAN. In Q1 2027 the seller receives 140 payments from payers in Germany and France through accounts the institution provides. The institution is the payee’s provider. The payments are cross-border and above 25 for that payee, and the Netherlands is the home member state. It reports the payee and all 140 payments to the Belastingdienst by 30 April 2027, using release v19 and XSD 4.03.

Facts: A payment institution licensed in another member state serves Dutch merchants under the freedom to provide services and has no Dutch establishment. It owes the Netherlands a host-state file. Instead of an intermediary, it now writes to the Belastingdienst’s account management team, works through the FI number, OIN, certificate and FTP account, and tests in the VTS.

Facts: A provider delivers its Q4 2026 file on 25 January 2027 and gets the Digipoort .ok message, then hears nothing from CESOP for a week because of a backlog. It does not resubmit. Three weeks later CESOP partially rejects 12 payees for a business rule that the VTS cannot check. The provider sends a CESOP101 correction for those 12 payees only, linked to the original records, well inside the recommended 30 days.

9. FAQ

Which Dutch law implements CESOP?

Articles 39a to 39d of the Wet op de omzetbelasting 1968, inserted by the Wet implementatie Richtlijn betalingsdienstaanbieders with effect from 1 January 2024. Article 41 of the same Act sets the fine. The deadline comes directly from Article 24b of Regulation (EU) No 904/2010.

Can I file CESOP through DNB’s reporting portal?

No. CESOP goes to the Belastingdienst through Digipoort. DNB DLR is for prudential and statistical returns to a different authority.

I am a foreign provider with no KvK number. Can I file myself?

Yes, since 2 March 2026. The Belastingdienst’s PSP-CESOP account management team arranges the FI number, OIN, PKIoverheid certificate and FTP account. A Dutch branch or an intermediary are still options.

Which XSD should I use?

XSD 4.03 now and under release v19 from 29 December 2026. Under release v20, XSD 4.04 applies from 1 July 2027. Check SDM before each release, because Dutch dates can differ from the Commission’s.

What if CESOP has not answered and the deadline is close?

Do not resubmit. SDM’s guidance is that a retrievable Digipoort .ok message shows you filed on time. CESOP’s content feedback follows separately.

Can I be fined for reporting too much?

Yes. Article 41(2) Wet OB 1968 applies the article 41 fine to reports about payees with fewer than 26 cross-border payments in the quarter.

10. What to do, today

  • Document whether the Netherlands is your home or host state, and the threshold test per payee.
  • Check that your Digipoort configuration uses oe-cesop.procesinfrastructuur.nl, holds the current Digipoort certificate in its truststore, and that the Logius FTP contact form is done.
  • If you are a foreign provider using an intermediary, decide whether to switch to the direct route available since March 2026, and start the FI number, OIN and certificate steps early.
  • Build release v19 (Data File v2.3, XSD 4.03) before the Q4 2026 filing, and put release v20 (XSD 4.04) on the roadmap for 1 July 2027.
  • Add checks for business rules 40111, 40120 and 40130 to your own pre-submission tests, because the VTS does not cover them.
  • File the Digipoort .ok receipt with each quarter’s evidence, and set a 30-day clock for every CESOP rejection.
  • Work the Dutch leg into your multi-state plan. Digipoort covers the Netherlands only. Compare Germany and Spain.

11. Sources

Official texts and Belastingdienst, Logius and Commission material checked for this review on 8 November 2026:


Related: CESOP data and system readiness · What is CESOP reporting? · Building the CESOP file · CESOP reporting compared — national channels · DNB DLR — Dutch supervisory reporting channel · FATCA/CRS filing in the Netherlands · Handelsregister (KVK) — the Dutch company register · The Dutch reporting calendar

Related reads.