Belgian Peppol Service Providers Forum – 38th plenary meeting – online – 09/12/2025, 13:30 – 15:00 CET – Preparatory document
Agenda
Welcome and housekeeping
I. SMP Redirect
II. Network Quality - focus on network metadata
III. Multiple Receivers under one enterprise number
IV. Add Control On VAT Nr
V. Self-Billing
VI. GT&Cs
VII. End User Identification – Reminder (new topic)
VIII. Factoring (new topic)
Backlog / AOB / Next forum
===
Welcome and Housekeeping
This meeting is recorded. By attending it you agree with the recording.
Presence
Due to dramatic increase of the participation, the following rules will be followed from now on, admission will be limited toPeppol SPs enrolled with BPA (or in the process), or having transmitted their Annex 3 to the BP
Other organizations (such as foreign PAs, business systems, …) on a case by case basis
persons who have received the invitation directly from BPA
(do no forward: contact BPA if you wish to add colleagues to the distribution list)identified with a personal email address (no group address, no bots)
who have confirmed participation (by (tentatively) accepting the meeting invitation).
Please make sure you have done so if you plan to attend the meeting.
Participants evolution
Count of Forum members (organisations) | |
Date | Amount |
31/12/2024 | 59 |
9/12/2025 | 124 |
List of Participants : cf Annex 1.
Roles: reminder: SP Forum casting:
Service Providers: subject matter experts main contributors
BPA: Government facilitator
Chair
Proposed chair: Serge Libert (BOSA)Minutes taker
Proposed minutes taker: Davut Yildirim (BOSA)Approval of the agenda
Proposition: approve the agendaApproval of minutes of previous meeting published on Belgian Peppol SP Forum main page
No comments received so far. Proposition: approve the minutesReview of action items of previous meeting
SMP Redirect
All forum members are invited to participate (apply) to the POC – DONE.
BPA will reach out to Peppol Edge to propose participation to the POC - DONE
BPA and Nymus will progress with POC set up if/when it becomes possible to gather enough POC participants - pending
V. Multiple Receivers under one enterprise number: IBAN as KYC-compliant 2ndary ID?
Members are hereby invited to apply to a new Focus Group to progress on this topic by email to peppol@bosa.fgov.be – DONE - cf agenda item III.
VI. Add Control On VAT Nr (new topic)
Action: Members are hereby invited to apply to a new Focus Group to progress on this topic by email to peppol@bosa.fgov.be – DONE - cf agenda item IV.
Backlog / AOB / Next forum
Self-billing:
members are invited to provide their input (observations, questions, issues identified) by email to peppol@bosa.fgov.be - cf agenda item V
members are invited to apply for a focus group on the topic by email to peppol@bosa.fgov.be - DONE - cf agenda item V
GT&Cs:
members are invited to provide their input (observations, questions, issues identified) by email to peppol@bosa.fgov.be DONE- cf agenda item VI
members are invited to apply for a focus group on the topic by email to peppol@bosa.fgov.be DONE - cf agenda item VI
Next forum
BPA to organize next Belgian Service Providers Forum plenary meeting - DONE
BPA to consider organizing in-person meeting in Q1 2026 and report progress on next plenary meeting – DONE - Confer “Next Forum”
===
I. SMP Redirect - registration interface standardization
Topic owner: Leentje De Brouwer (Nymus)
Result of the invitation to apply to the POC: /
No progress due to lack of time/availability.
Reaction of people who want to bring it to the global peppol level due to Nordic interest
===
II. Network Quality - focus on network data
Topic owner: Leentje De Brouwer (Nymus)
New RFCs (Leentje)
Luxemburg: errors received from Belgian SPs (invitee: Olaf Debacker)
Luxemburg contacted BPA to report a list of non-compliances in documents received from Belgian operators. Olaf will explain.
BPA: Peppol Network Scanner - Belgian Pilot (Serge / Bart)
BPA (with support of FPS Finance and OO) has set up a Belgian Peppol network data scanner MVP. The first scan delivered :First scan (20 oct): 5.500 non-compliance, spread over 78 smp urls,
2nd scan (24nov): 80.027 non compliances, spread over 115 smp urls
NOTE: 30 smp urls have no seat ID - no smpOwnerName → compromises troubleshooting
→ Please make sure that you duly publish seatID (and smpOwnerName)
Details:
Non compliance | 20 oct | 24 nov |
Primary use of enterprise number | 3.987 | 6.926 |
Malformed ID {0208; 9925} - Mod97* | 170 | 2.264** |
Malformed ID {0208; 9925} - other | 1357 | 1.992 |
Total | 5.514 | 11.182 |
Not in Peppol Directory*** |
| 59.085 |
BIS Billing missing |
| 9.760 |
Grand Total |
| 80.027 |
Smp records | 800.000 | 1.000.000 |
*: malformed IDs details reveal a lot of dummy IDs, possibly test IDs in production.
this impairs network data quality. If such IDs derive from a real business need, there should be a way to “tag” them as test data – eg using a schemeID “test”?
**: round 1 was based on failfast methodology, round 2 not. this explains the significant increase of this figure.
***: 60.000 IDs are not in the Directory. Downsized to the entities (using the 0208 primary ID), it leaves us with 25000 absent end-users.
Although not mandatory, with the B2B mandate, presence in the PD is common sense, isn’t it?
These findings will be distributed to the responsible operators for resolution, in the coming days, along with the findings from Luxemburg.
BPA: Peppol Network Scanner - PAC TaskForce: draft requirements for a global scanner --> OO
On 9/10/2025, the Peppol Authorities Community (PAC) meeting 109 approved BPA proposal to cooperate to the drafting of requirements for a global peppol network data scanner, leveraging the above Pilot Belgian scanner (as well as other similar robots) to globalize it to the whole network, allowing distribution of findings to responsible PA for further noncompliance processing (=distribution to responsible SPs) and resolution. A taskforce was established (BE, FI, NL, NGA, SE). Initial version was drafted and reviewed. Next version, possibly release candidate, will be ready by 17/12. Next step: PAC lead submits the request to OO on behalf of PAC. NB: there are already well designed such robots, that potentially will be recycled/upscaled/integrated with the reporting tool. NB2: there is a lot of synergy with other work items (SML insourcing, PD stabilization, Critical Infrastructure workgroup).
===
III. Multiple Receivers Under 1 CBE
Topic Owner: Remko Weiers (Exact)
Focus Group setup: Applications received:
Wolter Kluwers
CW Logistics
Billit
Remko accepts to take the Lead.
Exact also assigns a second participant to the group (Lennert).
Remko will present the status in more detail during the plenary meeting.
===
IV. Add Control on VAT Nr
Topic Owner: Paul Simons (Wolter Kluwers)
Focus Group setup: Applications received:
Wolter Kluwers
CW Logistics
Billit
Paul accepts to take the Lead.
Paul will present the status/approach proposal in more detail during the plenary meeting.
NB: Luxemburg issued a RFC to strengthen quality of (End Users) IDs on the Peppol network (see also Peppol Network data Scanner)
===
V. Self-Billing scenario
Potential Discussion topic identified during Forum plenary meeting, presentation by FPS Finances regarding Self-billing solutions availability.
Focus Group setup:
Questions / Remarks received:
What is the problem with self-billing (CW Logistics)
Applications received:
Wolter Kluwers
Billit
As this potential topic derives from a presentation by FPS Finances, FPS Finance is evaluating the option to lead this topic.
Please provide us with your questions and remarks regarding the self-billing scenario.
Examples:
As all enterprises now must be able to send e-invoices, does self-billing still make sense?
wouldn’t it be better to discourage self-billing and encourage ordering by the former self-billers, with orders that are flipped into invoices by the suppliers?
What if the customers wants self-billing but the suppliers does not? (remember, there is no mandate ruling self-billing, and it is questionable whether we should extend the mandate to this scenario)
===
VI. GT&Cs
Topic proposed by Soluz.io (Walter Vander Goten)
Focus Group setup: Applications received:
CW Logistics
BOSA
Soluz.io is currently unable to participate or lead this potential Focus group. Unless another forum member would step in, this topic will be moved in backlog until further notice
Please let us know if you would step in as member and/or lead of this Focus Group.
===
VII. End User Identification – Reminder
(New) topic put on the agenda by BPA.
Given the massive enrollment of Peppol End Users following the B2B mandate, it is important to remind operators of their obligations regarding End User Identification (EUI).
What is EUI?
End User Identification (EUI) is a mandatory requirement for Peppol Service Providers (SPs) to ensure that every transaction on the Peppol network can be traced back to the actual end user (the legal entity sending or receiving documents). This is critical for compliance, security, and accountability.
The Peppol Service Provider Agreement that you, as Peppol Service Providers, have signed states the following in clause 9.2:
The Peppol Service Provider is responsible and liable for ensuring at all times that all parts of such contractual relationship with End Users respects the terms of this Agreement and the Peppol Interoperability Framework in general, and that the correct identity of the End User is verified in accordance with the Entity Identification provisions stipulated by the Internal Regulations and/or Operational Procedures and applicable PA Specific Requirements as part of onboarding of an End User. The Peppol Service Provider shall furthermore provide the Peppol Authority upon its reasonable request with adequate evidence of compliance with these obligations towards the End Users.
As National Peppol Authority, we emphasize the critical importance of security and the accurate identification of End Users by Peppol Service Providers. These obligations are established to ensure compliance with applicable laws and to prevent fraudulent activities and money laundering.
The present Terms and Conditions shall be read in conjunction with the Internal Regulations set forth in Annex 2, which form an integral part of this framework.
Furthermore, Service Providers are reminded that, pursuant to the provisions of the Crossroads Bank for Enterprises (Banque Carrefour des Entreprises), they are entitled at any time to verify the legal characteristics of their clients, including the authority of individuals to bind the respective legal entity.
We kindly request confirmation of your capacity to fulfill this critical obligation.
===
VIII. Factoring
New Topic Proposed by new member Factris (Jarn Vinders).
Jarn presents the issues that require alignment between operators.
===
Backlog / AOB / Next forum
Backlog:
EINVC-1080 | Problematic registration of end users |
EINVC-1007 | Peppol Reporting |
EINVC-1004 | handling delivery troubles (MLx) |
EINVC-1002 | KYC (automation) |
EINVC-1001 | SBDH Country |
EINVC-999 | B2C |
EINVC-998 | CTC |
EINVC-996 | inventorize SP sending and receiving capabilities (?) |
EINVC-995 | ISO certification |
EINVC-993 | B2B adoption: COMPLETED: This topic was initially mentioned in june 2022, during policy preparation phase. In the meantime, the regulation is in place, the IT infrastructure is in place, and the end-users enrolment follows the pronostics. After 1/1/2026, a new phase will start where invoicing scenarios requiring sectoral alignment will certainly pop up. Together with other initiative such as BEG, theSP Forum can serve as alignment platform between operators, reducing friction in the exchanges. this would be the matter of separate topics → DONE. |
===
Any Other Business
Credit notes issue - SCRADA
Announcements – candidates for discussion in SP forum:
Post-Award November 2025 release publication (24 November 2025 18:00)
Peppol Testbed upgrade (11 november 2025 0:09)
Publication of EU PINT Billing (2 October 2025 12:33)
Next Forum
Credit notes issue
raised by Scrada
We have noticed that many software companies implement credit notes incorrectly when they add Peppol to their software. Specifically, they send the credit notes as negative amounts. This effectively means that the credit note becomes an invoice. The credit note indication already means that everything on the invoice must be interpreted as a negative amount.
Announcements:
Post-Award November 2025 release publication
Peppol Testbed upgrade
Publication of EU PINT Billing
see details below. please let us know whether a discussion or clarification is needed and elaborate your request
Details:
Post-Award November 2025 release publication (24 November 2025 18:00)
The November 2025 release of the Peppol Post-Award artefacts (BIS documents and validation artefacts) has been published.
The Migration Plan is attached to this mail.
All changes in this release are mandatory from Monday 23 February 2026. Therefore, today is the start of the implementation period for the release.
PLEASE NOTE: Until 22 February 2026, the current version (from the May 2025 release) remains mandatory for all Service Providers.
Please prepare all implementation and support as soon as possible to be ready for the mandatory deadline when all changes take effect.This release from Peppol includes changes to code lists and the mandatory validation artefacts for all published Peppol BIS 3.0 documents. For details about changes in this release, consult the release notes.
For Billing: https://docs.peppol.eu/poacc/billing/3.0/2025-Q4/
For other BIS: https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/
The PoAC CMB has also answered all received comments from the member review. They are published on Confluence, at: https://openpeppol.atlassian.net/wiki/x/BoCoDwE
Peppol Testbed upgrade (11 november 2025 0:09)
We are pleased to announce that the Peppol Testbed has been upgraded with new capabilities and improvements
A. New Functionality
SMP test suite (G3)
A new SMP test suite (G3) is now available in the Peppol Testbed, enabling the verification of SMP implementations configured with a G3 test certificate.
Getting started:Import a Peppol PKI G3 test SMP certificate into your browser
Choose the “Enter SMP test suite” from the Testbed’s landing page
Enroll in the relevant test suite to begin testing
B. Update - Fix
PKI Complete Migration test suite (G3)
The PKI Complete Migration (G3) test suite has been upgraded to improve usability. Previously, passing the reception test cases required the use of a test SMP signing with G3 certificate. This requirement has now been removed.
This change simplifies the testing process and enables Service Providers to complete the migration tests without needing a G3 configured SMP.
C. Documentation
To assist Service Providers with the tests, the following documents are available:
The Environment Description documents provide a more detailed description of the available test cases.
The User Guide documents provide a guide on how to use each test suite user interface, as well as the key steps in carrying out the various test cases.
These documents are available in each test suite under the tab ‘Documentation’.
D. Access and Usage
The SMP test suite (G3) is accessible via: https://www.testbed.peppol.org/
To run the SMP test suite (G3), Service Providers must be authenticated using PKI client authentication. This requires obtaining a Peppol test SMP G3 certificate and importing into their browser’s keystore.
Publication of EU PINT Billing (2 October 2025 12:33)
The PoAC CMB is pleased to publish EU PINT Billing v1.0.0. This is an optional specification that can be used as of today. It is a PINT implementation of BIS3 Billing. It doesn’t replace BIS3 Billing. BIS3 Billing remains the mandatory specification in the EU.
https://docs.peppol.eu/poac/eu/
EU PINT Billing v1.0.0 is in compliance with PINT and with the European norm EN 16931.
This PINT specialization enables EU companies to bill customers outside the EU where countries have implemented their own PINT specializations. Currently these are Australia, Japan, Malaysia, New Zealand and Singapore. Cross-border exchange of PINT specializations is possible when the receiver has registered a receiving capability of PINT * by using the wildcard.
Many thanks to all members that submitted comments during the member review. The answers to your comments can be found on the member review page.
https://openpeppol.atlassian.net/wiki/x/BQDaBAE
===
Next forum
During last plenary meeting, an in-person edition was proposed by BPA and welcomed by forum participants.
BPA is organizing this.
Timing: February 24th 13:30 – 16:00
Venue: BOSA, 30 boulevard Simon Bolivar 100 Brussels, second floor, Rooms 2.15 - Bora Bora ; 2.17 - Zanzibar ; 2.18 – Fiji
Access: an invitation to the meeting will be sent to you well in advance. Upon your acceptance, you will be added to the attendees list. A few days before the meeting, you will receive an email with a QR code. This code allows you to pass the access control gates on the ground floor (left side) , take the escalators to the 2nd floor and follow the signs to the meeting premises.
Remarks:
BOSA has also requested hybrid meeting support so that online attendance will be possible.
BOSA proposes extending the duration of the plenary meeting to two hours.
====================================================================
Annex 1: Participants Lists
List of participants who joined the forum in 2025
Accai Software | Cyber-Relais (Eurologiciel) |
BRBX | alchimerys |
CD-Invest | DOK-API |
DARING.SYSTEMS | Ernst & Young Tax Consultants |
Diflexmo | Informex - Solera |
e-invoice | TITP |
Expert Vision SRL (efact) | Shyfter |
Fidbee | beprosoft |
GDev | endevops |
Godevelop - Puntoo | Renta Solutions (Mobeyond) |
IT-OPTICS - Xeolis | OkiOki |
JAK Solutions | Afas Belgium |
Multios | hooly |
ORKHON | WiseTech |
PeppolEdge | Markant |
Prismatech | a-Cube |
Qualia | Billtrust |
Simple Days | Tietoevry |
Skyforce | Semansys |
Spark IT | CONTINIA |
Tigron | August Bridge |
Travelnote N.V. | VATit Processing (Pty) Ltd |
Twikey | Invopop SL |
Winfakt | GS1 ASBL |
Montova | Peppol Service Provider Community |