Belgian Peppol Service Provider Forum

Since 21/11/2024, key-information about the Belgian Peppol Authority (BPA) was moved to https://peppol.be (only available in FR and NL)

 

The Belgian Peppol Authority (BPA) organizes the Belgian Peppol Service Provider Forum. This forum handles various topics related to the development of Peppol, from technical issues encountered, to actions organized by the BPA... It is a critical interaction point between operators, where they can talk about their concerns, about their understanding of the specifications, and reach consensus required for true interoperability.

It meets at a frequency that varies with the need to interact (see table below). Between two meetings, exchanges take place via email and/or contents publication on the Content area (see below).

All Service Providers active in Belgium (Service Providers that signed with the BPA, and other Service Providers that operate in Belgium), are invited to participate.

Agenda, list of presence, supporting material and wrap up of the previous Forum editions

Edition

Presence

Agenda /slideware/streaming

Wrap up

Edition

Presence

Agenda /slideware/streaming

Wrap up

35  Mar 18, 2025 

13:30 - 15:00

 

SMP redirect

BE SP Forum - improving the model

Backlog / AOB / Next forum

 

34  Dec 10, 2024 

13:30 - 15:00

  • Arco

  • B2B Router

  • b2bgrid

  • B2Boost

  • Babelway - Tradeshift

  • C&W Logistics

  • Codabox

  • eConnect

  • Edicom

  • Exact

  • GHX

  • Horus Software

  • Ixor

  • Nestoya

  • Netfly

  • NTX

  • Nymus

  • Octopus

  • Odoo

  • Pagero

  • Scrada

  • soluz.io

  • Speos

  • Teamleader

  • Tradeinterop

  • UnifiedPost

  • VAT-IT

I.Knowledge of Peppol evolution

II.Organisation with 1 CBE and multiple (sub)entities receiving invoices (by Exact)

III.Use of Hermes - an update

IV.Peppol Reporting

V.SMP Redirect

VI.Peppol and Belgian forum web presence

VII.MTCI – Daily Limit

VIII.BE SP Forum - improving the model (postponed to next Forum)

IX.Backlog / AOB / Next forum

 

 

II. Organisation with 1 CBE and multiple (sub)entities receiving invoices (by Exact)

Relevant topic for SP community.
Use of branch number not recommended because not the same from one enterprise to another.
Use of CBE id as “primary” endpoint understood.
Role of business communication understood.
Limits of the standardization of this type of scenarii understood.
Analysis continues.
Potential topic for the 35th SP Forum agenda.

V. SMP Redirect

Confusion about the role of SMP and role of AP in the registration of redirect metadata in the primary SMP.
Possible limit of the specification: it says what is expected but doesn’t say how: too much freedom causes the reluctance to implement.
Requires deeper analysis and communication.
Potential topic for the 35th SP Forum agenda.

VI. Peppol and Belgian forum web presence

Please visit the section https://bosa.belgium.be/fr/themes/administration-numerique/interoperabilite-et-integration/generalisation-de-le-facturation (available FR/NL) and feel free to comment/suggest improvements.

 

33  Sep 17, 2024 

13:30 - 15:00

 

 

  • B2B Router

  • Babelway - Tradeshift

  • Billit

  • Descartes

  • eConnect

  • Edicom

  • Esker

  • Exact

  • GHX

  • Ixor

  • NTX

  • Nymus

  • Octopus

  • Odoo

  • OpenText

  • Pagero

  • Routty

  • Scrada

  • soluz.io

  • Symtrax

  • Tradeinterop

  • UnifiedPost

  • FPS Finance

I. Outcome Questionnaire

II. B2B update

III. Hermes

IV. Backlog / AOB / Next forum

I. B2B update

  • Update on e-Invoicing B2B by Wouter (FPS FInance),

  • additional comments:

    • In the BEG Hermes WG we also agreed to have a disclaimer for the senders (and the systems they use) who send invoices to receivers that are not in compliance (during the transition period)

    • Clarifying the 2nd Path

    • Recupel and BEBAT : illustrates the initial mission of Business Experts Group: to discuss and agree how scenarios needs to be handled using the Standards (as there may be many different ways to ), and to identify shortcomings (for instance in code lists). CCL: This is subject for BEG workgroup Technical issue

    • Hermes positioning: confusion clarified thanks to Stephanie’s questions. Hermes is a sender tool. After due consideration and debate in the BEG HRMS WorkGroup, it was decided to follow their recommendation and NOT recycle it to a receiver tool. It currently stays operating as a sender tool for those senders who want to use it that way to get rid of the burden of having to choose amongst multiple channels and formats. - and therefore choose a (software tool connected to a) SP - that provides the service

    • 0208 identifier and other identifiers for Belgian Enterprises

II. Outcome Questionnaire.

  • Outcome of SP Question w.r. to the SP Forum by Coralie.

  • The SP are asked to present/introduce for discussion for one of the next SP Forum. Suggestion can be shared via mail to peppol@bosa.fgov.be,

  • Topic already available:
    SBDH country
    KYC (automation)
    transmission scenarios post Jan 2026 (GHX)

III. MTCI.

  • Katrien (from Ixor) introduces the MTCI topic for discussion, 1.000 as daily limitation.

  • Majority is for opening the gates.

  • BOSA will come back to collect the trend and will liaise with our subco managing the HSMP i.o. to confirm the possibilities and apply best solution.

32 Nov 14, 2023 

13:30 - 14:30

  • Arco

  • B2Boost

  • b2bgrid

  • Babelway - Tradeshift

  • Billit

  • Codabox

  • Descartes

  • Digiteal

  • eConnect

  • Edicom

  • Esker

  • Exact

  • Horus Software

  • Ixor

  • Netropolix

  • Octopus

  • OptiPost

  • Order2cash/Bill Trust

  • Pagero

  • soluz.io

  • Storecove

  • Tradeinterop

  • UnifiedPost

  • iCreative

I. smp.belgium.be retirement

II. Rejection on AS4 level

III. eInvoicing Testimonials

IV. Your questions & topics

V. Backlog / AOB / Next forum

I. smp.belgium.be retirement

  • as stated on the slides,

    • smp.belgium.be retires on 31.12.2023

    • BOSA strongly recommends all SPs to be ready by 01.12.2023

    • BOSA will provide to the concerned SPs their list of records.

  • additional comments:

    • some SPs use smp.belgium.be as pit stop in the migration of Hermes participants. This practice must also be dismantled by EOY.

    • some SP report throughput limitations. pls use BOSA support channels to report and substantiate.

II. Topic suggested by Tradeshift w.r. to "Rejection on AS4 level"  and proposal by OpenPeppol support.

  • Interactions on different possibilities. no clear way forward. recognition of the need to align with MLx track, but also consider compliance process. Maturity curve issue.

  • Suggestion for the ones interested to have an additional exchange moment s on MLA/MLS and AS4 possibilities. between Belgian forum participants. Interested to be part of the meeting? Drop a mail to peppol@bosa.fgov.be

III. You are kindly invited to come with your eInvoicing testimonials to us to have it in a video.

V. Recording Belgian entities in your SMP’s need to be first done based on the CBE number “0208”.

31 Sep 12, 2023 

13:30 - 14:10

  • Advalvas

  • Arco

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Billit

  • Codabox

  • connect solutions

  • eConnect

  • Edicom

  • Exact

  • Ixor

  • Nestoya

  • Netropolix

  • OptiPost

  • Order2cash/Bill Trust

  • Pagero

  • soluz.io

  • Tradeinterop

  • UnifiedPost

  • VAT-IT

I. smp.belgium.be retirement

II. Your Topics

V. Backlog / AOB / Next forum

I. smp.belgium.be retirement

  • smp.belgium.be retires on 31.12.2023

  • available support: all SP’s currently using smp.belgium.beare have received a report with their data. Once they have migrated their participants data, they can contact BOSA for a final cross check. BOSA strongly recommends all such SPs to be ready by 01.12.2023

  • Revamping of Peppol-in-belgium page: there will be a short term change to cope with immediate concerns, and a longer term deeper revamping. Appropriate analysis in ongoing. Impact on the smp.belgium.be migration is acknowledged as negligible.

II. Answer given to the provided questions.

  • Migration from HSMP to any SMP: BOSA confirms that there is no dependency with smp.belgium.be. SPs having trouble need to check their own code.

  • Timing of B2G e-invoicing obligation: Official source is National Gazette. will publish info in function of progress of legislative process. Chancellery is sole competent institution.
    NB1: the impact of the possible report of the last milestone has only negligible impact. The key message is: B2G e-invoicing is becoming mandatory. the faster you and your customers are ready, the better.
    NB2: a Press conference was held by the Secretary of State for Digitalisation. He confirmed the update schedule. Supporting material is also available to support this communication action.
    NB3: updates (published after the meeting) of the Obligation générale de la facturation électronique vers l’administration/Algemene verplichting elektronisch factureren aan de overheid BOSA pages w.r. to the shift to 1.3.2024 for the last milestone

30 Jun 27, 2023 

13:30 - 15:00

  • FPS Finance

  • Ademico

  • Arco

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Codabox

  • Descartes

  • Digiteal

  • eConnect

  • eCreative

  • Edicom

  • Exact

  • Ixor

  • Nestoya

  • Netropolix

  • Octopus

  • OptiPost

  • Order2cash/Bill Trust

  • Pagero

  • soluz.io

  • VAT-IT

I.National developments in B2B eInvoicing by FPS Finance

II.SchemeID 9956 (& old MLR DocType) removal

III.smp.belgium.be retirement

IV.MTCI

V.Backlog / AOB / Next forum

I. Clarifications:

  • Timing: depends on parliamentary process.

  • Scope: domestic traffic only.

  • Approach:

  •  

    • Initial proposal: introduction of obligation to receive first and in one step, then introduction of obligation to send in phases.

    • However some stakeholders have concerns with the phasing. Discussions ongoing.

  • Reporting: through Peppol CTC

II. No need for additional support was raised by SPs.
Consequently BOSA starts phasing out its operation to support SPs and coordinate their actions in this matter.

III.a. BOSA will schedule removal of the SP info on the PeppolInBelgium page.

III.b. SPs are invited to provide their move-away plans by 14.7.2023 to peppol@bosa.fgov.be.

V. AS2 removal: nobody seems to rely on AS2.
Consequently there is no support needed (from BOSA), for SPs to comply with the AS2 Phase-out plan communicated by eDEC CMB in March.

29 May 16, 2023 

13:30 - 15:00

  • Advalvas

  • Agoria

  • Arco

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Billit

  • Brain2

  • C&W Logistics

  • Codabox

  • connect solutions

  • Descartes

  • Digiteal

  • Dynatos

  • eConnect

  • Edicom

  • Esker

  • Ixor

  • Nestoya

  • Netropolix

  • Octopus

  • OptiPost

  • Pagero

  • soluz.io

  • UnifiedPost

I. 9956 - Old MLR update

II. smp.belgium.be phase out, next step

III. Hermes Integrator agreement 

IV. Backlog / AOB / Next forum

I. update files will be provided after the meeting to the concerned SP's

II. SP's have to provide a date when they will be ready to provide the move away plan

III. To be reachable through Hermes the receivers need also to agree with the Hermes Ts&Cs

 

28 Mar 21, 2023 

13:30 - 15:00

  • Advalvas

  • Arco

  • B2B Router

  • Babelway - Tradeshift

  • Billit

  • Codabox

  • Descartes

  • Dynatos

  • eConnect

  • Edicom

  • EskerExact

  • Ixor

  • Netropolix

  • Octopus

  • OpenText

  • OptiPost

  • Order2cash/Bill Trust

  • Pagero

  • soluz.io

  • UnifiedPost

I. 9956 - Old MLR phase out completion

II. use of 0208

III. smp.belgium.be phase out, next step

IV. Hermes Integrator agreement - status

V. Backlog / AOB / Next forum

 

III. smp.belgium.be phase out, next step:

  • Some participants of the SP forum suggested to remove smp.belgium.be from the service by 1.1.2024.
    None objected.
    No SP expressed the need for particular support from BOSA in this migration process.

  • In order to give sufficient time to all SPs to perform sufficient analysis, BOSA leaves the decision open until next forum.
    SPs are invited to raise their opinion to peppol@bosa.fgov.be by then.

IV. Hermes Integrator agreement - status:

  • A question from B2B router was the opportunity to (a) reemphasize that the user is the sender, and (b) to walk through the different benefits of Hermes to the different categories of stakeholders affected.

  • As a side discussion the role of Hermes in a possible B2B mandate scenario was raised.
    At certain conditions, Hermes could take the same role of receiving-system of last resort during the transition phase , like CHORUS pro is taking in the French scenario.

  • Integration with eBox enterprises is achieved.
    It is only for use in the G2B/G2G scenario for legal reasons.

V. Backlog/AOB/Next forum:

  • Backlog: governance update (what about ISO certification): can be removed from the backlog: the InfoSec Workgroup is taking care of these aspects.
    All OpenPeppol members can join the group if they wish, or get info in due time in function of workgroup progress. See also Call for Participation Peppol Security Requirements Design Work Group - OpenPeppol

  • AOB: SPs raised their concerns to be part of the consultation rounds of the B2B obligation policy making phase.
    BOSA can only advise to get in touch with Tax Administration.

27 Jan 17, 2023 

13:30 - 14:15

  • Agoria

  • Arco

  • B2B Router

  • Babelway - Tradeshift

  • Basware

  • Billit

  • Codabox

  • connect solutions

  • Descartes

  • Digiteal

  • Dynatos

  • eConnect

  • Edicom

  • Esker

  • Exact

  • Ixor

  • Nestoya

  • Netropolix

  • Octopus

  • OptiPost

  • Pagero

  • soluz.io

  • Tradeinterop

I. Hermes Agreement Update

II. 9956 decommissioning

III. Backlog / AOB / Next forum

 

I. Language aspects:
Hermes does not provide a solution to the fact that, currently, when it comes to converting the invoice into a human readable equivalent a language could be is defaulted.
The sender has to determine the language to use (FR or NL).
How the sender sorts this out may be context-dependent and very tricky.
Hermes does not provide a solution for this.
The sender still needs to decide which language he will use. Service Providers on behalf of their customers should provide the language (FR or NL) to be used by sender.

II. 9956 decommissioning: Service Providers are asked to clean their obsolete entries before full decommissioning.

III. a. Topics suggested for upcoming SP forums:

  • CTC

  • update on planning for B2B obligations in BE

  • B2C agenda

 

 

 

 

edition

presence

agenda /slideware

report

edition

presence

agenda /slideware

report

26 Nov 22, 2022 

13:30 - 15:00

  • Advalvas

  • Arco

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Basware

  • Billit

  • Codabox

  • connect solutions

  • Descartes

  • Digiteal

  • Dynatos

  • eConnect

  • Edicom

  • Esker

  • Exact

  • Ixor

  • Nestoya

  • Netropolix

  • Octopus

  • Pagero

  • Symtrax

  • Tradeinterop

I.B2B update by FPS Finance

II.Feedback F2F meetings 11.2022

III. Hermes Agreement Update

IV. Backlog / AOB / Next forum

II. important to notice that introduction of PINT may require all current invoice receivers to support the global invoice model, which is a generalization of the current BIS. In other words, it will involve migration activities for all receivers while the benefit will not always be clear for all receivers (eg the ones having mainly domestic traffic). SPs are invited to think about (a) how it fits with their understanding of the business and (b) how they will help their customers in this.

III. Deadline for comments agreed on 16.12.2022

IV. a. SPs are invited to submit topics proposal for upcoming SP forums

IV. b MLR BISv2 use in B2G scenario since 2016: now fully stopped. BOSA assumes MLR BISv2 is NOT used in the B2B scenario. SPs are invited to inform BOSA if it would not be the case.

IV. c. Backlog: B2B: Tax Administration to participate in an upcoming SP: done

IV. d. Backlog: collection of SP sending and receiving capabilities: to be organized by PA – preparatory collection prior to possible discussion on forum.

25 Sep 20, 2022 

13:30 - 15:00

  • Advalvas

  • Agoria

  • Arco

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Basware

  • Billit

  • Codabox

  • Descartes

  • Dynatos

  • eConnect

  • Edicom

  • Exact

  • Nestoya

  • Netropolix

  • Octopus

  • OptiPost

  • Pagero

  • soluz.io

  • Tradeinterop

I.Update from Luxembourg

II.Update on MLR-IMR

III.e-Invoicing conference

IV.Service Provider Agreement update

V. Backlog / AOB / Next forum

I. Update on the e-invoicing track in Luxembourg given by Gérard Soisson - Ministère de la Digitalisation.

II. The completion of the migration to IMR depends on the replacement of invoice senders old BIS MLR receiving capabilities by IMR receiving capabilities. Figures from Peppol Directory show that we are only 10% away in this process. From 16.11.2022 on, invoice senders who don’t receive IMR  and only old BIS MLR, will experience a disruption of their invoice response processes. In the Peppol network it is up to the Service Providers to properly inform and support their invoice senders.

III. SPs are warmly welcome to submit their candidacy to the e-invoicing award (in the category IT), and to suggest their customers who are active in invoicing to also submit (in the category entreprises).

V. Backlog / AOB / Next forum

a. Backlog: B2B: Tax Administration to participate in an upcoming SP

b. Backlog: collection of SP sending and receiving capabilities: to be organized by PA – preparatory collection prior to possible discussion on forum.

c. Next forum (26th edition): 22.11.22, 13:30

24 Jun 21, 2022 

13:30 - 15:00

  • Advalvas

  • Arco

  • B2B Router

  • b2bgrid

  • Billit

  • Codabox

  • connect solutions

  • Descartes

  • Digiteal

  • Dynatos

  • eConnect

  • Ixor

  • Nestoya

  • Netropolix

  • Octopus - Inaras

  • OpenText

  • OptiPost

  • Pagero

  • soluz.io

  • Tradeinterop

Agenda:

I. Service Provider Agreement Update

II. Backlog / AOB / Next forum

  1. Service Provider Agreement Update

(a) History, current status and issues that may arise from delayed signing by SPs:  cf slides

(b) A SP reported delay with the Legal department in Canada most probably due to workload. No specific action from BOSA.

(c) No other specific question or issue was raised impairing the resigning process at the SP side. BOSA concludes that signed agreements for all SPs will most likely be returned by July 1st; therefore, there is no reason to prepare for the unlikely scenario.

2. Backlog / AOB / Next forum

(a) Next forum scheduled 20.9 1:30PM (Teams meeting)

(b) Suggestion of the SPs to invite Tax Administration to interact on the possible upcoming B2B Mandate. Action: BOSA will contact Tax Administration representatives to relay the proposal.

23 May 10, 2022 

13:30 - 15:00

  • Advalvas

  • Agoria

  • Arco

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Basware

  • Billit

  • Breex Easybox

  • Codabox

  • Dynatos

  • Connect

  • Ecosio

  • Exact

  • Inaras

  • Ixor

  • OpenText

  • OptiPost

  • Pagero

  • soluz.io

  • Tradeinterop

  • UnifiedPost

Agenda:

I.Agreement Framework Revision

II.Invoice response: IMR live since 10/03/2022 - Update

III.Royal Decree – publications of IT solutions (B /G)

IV.Backlog / AOB / Next forum

 

Slides:

1. Agreement Framework Revision

(a) translation delayed – BOSA recommends SP to rely on English original for their internal preparation to re-signing, as the translation will match exactly. SPs haven’t raised issue with this approach.

(b) PA SR comments received and processed

2. Invoice response: status update

(a) Billit remark about wording of emails transposing IMR when receiver has not suitable RC’s: BOSA confirms  it refers to IMR, not MLR – however some Gov entities are still sending MLRs (not yet migrated to IMR), which may get turned into emails too when the receiver has no MLR RC.

(b) BOSA will investigate the feasibility of tuning such email body.

(c) Billit will check if his remark matches this scenario.

3. Royal Decree – publications of IT solutions (B /G)

(a) Anyone who can help, is welcome to participate. The initiative has been duly communicated and broadcasted.

(b) The main priority is to help the senders. The vast majority of senders who will need help in the short/medium term, need tools to send invoices. Therefore the main focus of the list that Government must publish, is on such tools.

(c) Link to the procedures :

- NL version

- FR version

(d) Translation is not provided by BOSA. SPs operating in Belgium are supposed to be OK with FR and/or NL.

4. Backlog / AOB / Next forum

(a) Upcoming change in CBE ID (0208) first digit : Billit to verify that schematron implementation matches the requirement and if not, issue request on https://openpeppol.atlassian.net/servicedesk/customer/portal/1

(b) Your topics: synch issue SMP-Peppol Directory:

- Known in the SP community, recommendation is to foresee retry mechanisms to overcome possible timeouts in the processing e.g. at the level of the push to Peppol Directory

- Issue also reported today by UP to BOSA, is on its way to BOSA’s subcontractor

(c) Next Forum on June 21st– please send us your topics. Thanks in advance for your constructive participation.

22 Mar 15, 2022 

13:30 - 15:00

  • Advalvas

  • Arco

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Billit

  • Breex Easybox

  • Codabox

  • connect solutions

  • Descartes

  • Digiteal

  • Dynatos

  • eConnect

  • Inaras

  • Ixor

  • OpenText

  • Order2cash

  • Pagero

  • soluz.io

  • UnifiedPost


Agenda:

  1. Agreement Framework Revision

  2. Invoice response: old BIS (2.0) MLR phase out, IMR phase in

  3. Backlog / AOB / Next forum

Slides:

 

  1. Agreement Framework Revision
    New PA SR: SP community could be used as first place to discuss the issues some SPs face explaining the (too?) straightforward mechanism established by the new framework, to their customers

  2. Invoice response: old BIS (2.0) MLR phase out, IMR phase in
    After due check, BOSA confirms that Hermes indeed returns BIS MLR upon reception of non-compliant BIS documents (schematron violation).
    Business rejections are returned as IMR if the invoice sender supports it, else as MLR due to the Belgian legacy context with respect to the use of old BIS MLR

  3. Backlog / AOB / Next forum
    Royal Decree: BOSA refers to the B2G e-invoicing Royal Decree. Cf forum 20 (14/12/2021), topic nr 2. explanations in slides

21 Jan 25, 2022 

13:30 - 14:30

  • Arco

  • Advalvas

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Billit

  • Codabox

  • Descartes

  • Dynatos

  • eConnect

  • Edicom

  • Exact

  • Inaras

  • Ixor

  • Nestoya

  • Netropolix

  • Odoo

  • OpenText

  • OptiPost

  • Order2cash

  • Pagero

  • soluz.io

  • Symtrax

  • Tradeinterop

  • UnifiedPost

Agenda:

  1. Agreement Framework Revision

  2. B2G e-Invoicing Royal Decree

  3. Hermes

  4. Invoice response: old BIS (2.0) MLR phase out, IMR phase in

  5. Backlog / AOB / Next forum

Slides:

  1. Agreement Framework Revision

    • Each SP signs new agreement with the PA in which it is legally established.

    • Annex 5 is replaced by PA specific requirements. It is not subject to separate signing

    • Belgian PA will adjust practical details accordingly (ex: “APs” becomes “SPs” on 30/6/2022), including the organization of Belgian forum. Such adjustments should be as transparent as possible for service providers.

  2. Peppol Communication:

    • PA invites all APs to submit articles (already published or in the drafting / publication process) – id possible please communicate links instead of files.

    • PA invites APs to also suggest other third-parties communicating over Peppol to PA. PA will extend the above invitation to such third parties

    • Upon reception of such submissions PA commits to review and propose adjustments. Additional interaction AP-PA welcome. Purpose is to strengthen our common messages

    • PA invites APs to provide their FAQs to PA

Varia:
please note eDEC change: webinar scheduled February 4th 09:00CET to 10:00CET. To register: https://attendee.gotowebinar.com/register/6306258157748240144

Call for subjects for the next AP Fora, cf mail 18.1.2022

 

20 Dec 14, 2021 

13:30 - 15:00

  • Arco

  • Axi

  • B2B Router

  • b2bgrid

  • Babelway - Tradeshift

  • Billit

  • Codabox

  • Dynatos

  • eConnect

  • Exact

  • Inaras

  • Ixor

  • Nestoya

  • Netropolix

  • Odoo

  • OptiPost

  • Order2cash

  • Pagero

  • soluz.io

  • Symtrax

  • Tradeinterop

Agenda:

  1. Agreement Framework Revision

  2. B2G e-Invoicing Royal Decree

  3. Hermes

  4. Invoice response: old BIS (2.0) MLR phase out, IMR phase in

  5. Backlog / AOB / Next forum

Slides:

  1. Agreement Framework Revision

    • SPs are invited to brief their prime contact (TIA annex 1, part 4.5)

    • If need to change prime contact please issue an Annex 1 update and send to PA

  2. B2G e-Invoicing Royal Decree

    • SPs are invited to work together with BOSA to set-up supporting measures

    • Clarification : granularity of invoice details (line item level): the applicable law does not give a clear cut on this. It is up to the sender to appropriately describe the goods and services

  3. Hermes

    • Publication of list of Hermes integrators on einvoice.Belgium.be: integrators with missing partners fiche: feel free to submit your request to become partner

19 Oct 26, 2021 

13:30 - 15:00

  • AdValvas

  • Arco

  • b2bgrid

  • B2B Router

  • Billit

  • Codabox

  • Digiteal

  • Dynatos

  • eConnect

  • Exact

  • Inaras

  • Ixor

  • Netropolix

  • Odoo

  • OptiPost

  • Order2cash

  • Pagero

  • soluz.io

  • Symtrax

  • Tradeinterop

  • Tradeshift

  • UnifiedPost

Agenda:

  1. Invoice response: old BIS (2.0) MLR phase out, IMR phase in

  2. Hermes

  3. Agreement revision

  4. Peppol Security Framework

  5. Backlog / AOB / Next forum

Slides:

  1. Invoice response: old BIS (2.0) MLR phase out, IMR phase in

  2.  

    • IMR: status acknowledged (AB): our implementation meets the IMR specification, that mandates responding an invoice with an invoice response within 72 hours. This invoice response may contain a status “AB”, but does not have to.

    • eConnect is also available for IMR pilot testing

4. Peppol Security Framework

  1.  

    • APs are invited to reach out to SP Community leader to check on the possibility to participate to the workgroup on Information Security

    • BOSA will also take contact to check when the request for participation would be sent within the SP community

    • Main concern discussed is KYC – how to make sure that the people signing the contracts with SPs indeed represent the entities they pretend to. Such verification can range from quite simple to very complex. Automating it in full may not be feasible. And it is also not required. There is a trade-off to find between what is worth automating and what still must rely on manual checks. National contexts will also inevitably vary. Peppol promotes standardization but does not remove local specificities from day 1. In Belgium CBE offers relevant services (but not necessarily waterproof). Private companies active in the enterprise data collection and consolidation sector, may also offer valuable services.

18 Sep 14, 2021 

13:30 - 15:00

  • AdValvas

  • Arco

  • b2b grid

  • B2B Router

  • Basware

  • Billit

  • codabox

  • Descartes

  • eConnect

  • Exact

  • Generix

  • Inaras

  • Ixor

  • Nestoya

  • Netropolix

  • Odoo

  • OptiPost

  • Pagero

  • soluz.io

  • Tradeinterop

  • Tradeshift

  • UnifiedPost

Agenda:

  1. Invoice response: old BIS (2.0) MLR phase out, IMR phase in

  2. Update progress on CBE schemeID migration

  3. Hermes

  4. Old BIS Billing?

  5. Agreement revision

  6. Peppol Security Framework

  7. Backlog / AOB / Next forum

Slides:

Welcome to new forum participants/ Belgian SP: Nestoya

1. B2G Invoice Response and MLR

  1.  

    • Exact confirms availability for end to end test in test phase Q4 2021. Any other candidate to participate is welcome.

    • PA invites APs to trigger the old bis (2.0) MLR phase out together with their invoice senders (inform, sensibilize, …)

2. CBE schemeID migration: can be closed. Remaining registrations under schemeID 9956 are assumed to be related to the old BIS (2.0) MLR, and thereby addressed within the topic above

3.Hermes:

  1.  

    • Now 7 AP agreements

    • Unprocessable invoices: sign of a business opportunity. Following the initial presentation held during the forum, APs can take contact with BOSA. BOSA will setup a program to better handle the opportunity.

4.Old BIS billing: it is up to the APs to sort out the issue with their own customer base

5. Agreement Revision:

  1.  

    • The platinum version is available

    • The migration to the new framework will foresee an effective date irrespective of the signing date

6. Security: APs should receive an invitation to participate the workgroup through the SPC

7. AOB etc..:

  1.  

    • E-invoicing summit 21.10: still time to register as partner

    • Next forum 26.10 13:30-15:00

17 Jun 22, 2021 

13:30 - 15:00

  • AdValvas

  • b2b grid

  • Billit

  • codabox

  • Descartes

  • Digiteal

  • Dynatos

  • eConnect

  • Exact

  • Inaras

  • Ixor

  • Netropolix

  • OptiPost

  • soluz.io

  • Storecove

  • Symtrax

  • Tradeinterop

  • Tradeshift

  • UnifiedPost

Agenda:

  • What is on your mind?

  • Update progress on CBE schemeID migration

  • Hermes

  • Invoice response: old BIS (2.0) phase out, IMR phase in

  • Decommissioning old BIS Billing (2.0)

  • Agreement revision

  • AOB

Slides:

 

Welcome to new forum participants/ Belgian SP: Breex EasyBox, eVerbinding, OptiPost

  • On your mind:

  •  

    • PA specific requirements: to be addressed in topic

    • When will e-Invoicing be mandatory in the Belgian public sector: Directive 2014/55/EU makes it  already mandatory for European public-sector receivers

    • Info: the new BIS schematrons:

      • include codes related to Brexit

      • modify rules: tax total at line level is not supported anymore (as it is an extension of the EN)

  • Update progress on CBE schemeID migration:

  •  

    • 100% register receivers using 0208

    • 78% finished migration of their receivers to 0208

    • 42% removed all 9956-based RC's – a breakdown per AP of entities still publishing 9956-based RC's was made available

    • 93% of sending AP's prioritize 0208

    • 75% of sending AP's stopped using 9956

  • Hermes: SP's are invited to communicate their questions and feedback related to using Hermes, that may lead to sending without having a sender or integrator agreement

  • Invoice response: old BIS (2.0) phase out, IMR phase in:

  •  

    • Support of code AB: IMR sender must send code AB (within 3 business days of invoice reception)

    • AdValvas, eConnect and Exact have candidates for reception of IMR from pilot entities (public-sector). Additional AP's are invited to contact BOSA

  • Agreement revision:

  •  

    • BOSA confirms the trend is to sharpen information security aspects to meet state of the art practice in this field

  • AOB: next meeting: 7.9.2021 13:30-15:00

16 May 4, 2021 

13:30 - 15:00

  • AdValvas

  • Arco

  • AXI

  • b2b grid

  • Basware

  • Billit

  • Brain2

  • codabox

  • Digiteal

  • Dynatos

  • Generix

  • Inaras

  • Ixor

  • Netropolix

  • Odoo

  • soluz.io

  • Symtrax

  • Tradeinterop

  • UnifiedPost

Agenda:

  • Security Requirements

  • Update progress on CBE schemeID migration

  • Hermes

  • Invoice response: old BIS (2.0) phase out, IMR phase in

  • Decommissioning old BIS Billing (2.0)

  • AOB

Slides:

Welcome to new forum participant/ Belgian SP: Odoo

  • News on Peppol Security Requirements: the proposal is considered a good evolution.

  • CBE schemeID: It is reminded to receivers (or their AP, acting on their behalf) to proceed with cleanup of their 9956-based SMP data as soon as possible.
    After 17.5.2021 such data become pointless an can only cause confusion/misuse, as the schematrons will block any document containing such code.

  • Hermes: extending Hermes to support cross borders traffic (incoming to BE): poll results: 50/50. comments and questions raised:

    • could make the Hermes decommissioning more difficult

    • could also boost adoption

    • could also be more consistent with cross-borders nature of Peppol.
      BOSA will take this feedback into account.

  • IMR@GOV, identification of parties: need to support issuerParty / recipientParty: poll result: yes: 0%, no: 20% ; don’t know 80% comment: Commercial acceptance should be the first focus (Paul)

  • Old BIS(2.0) BILLING decommissioning:

    • B2G / G2G: decommissioned

    • Next step: B2B / G2B. BOSA encourages AP to keep educating and supporting their customers senders and receivers.

  • Next AP Forum on June 22nd.

 

15 Mar 16, 2021

13:30 - 15:00

  • Arco

  • b2b grid

  • B2B Router

  • Basware

  • Billit

  • codabox

  • Descartes

  • Dynatos

  • Exact

  • Inaras

  • Ixor

  • Netropolix

  • soluz.io

  • Storecove

  • Tradeinterop

  • Tradeshift

  • UnifiedPost

Agenda:

  • Update progress on CBE schemeID migration

  • Hermes

  • Decommissioning old BIS Billing

  • migrating MLRv2 to IMR (business)/MLRv3 (technical)

  • AOB

Slides:

Welcome of our guest → Etat de Luxembourg and of our new AP's → Storecove and Tradeinterop. 

  • Update progress on CBE schemeID migration

    • Statistics presented based on the forms filled in by the AP's.

    • Moving forward with the migration.

    • BOSA reminds APs to keep filling in the complete survey each month (takes 1 minute), to contribute to the efficient tracking of the migration.

  • Hermes

    • AP whitelisting: BOSA explains the testing approach

    • BOSA will publish the testing procedure soon on the forum page and inform the APs

  • Decommissioning old BIS Billing

    • Last call before decommissioning.

    • To the question on AP's being ready by 31.3.2021 to remove old BIS, none of the Access Point came with an issue on this. So everyone is confident the Old BIS BILLING phase out of Government will go smoothly.

  • Migrating MLRv2 to IMR (business)/MLRv3 (technical) on Mercurius

    • Clarification over the limitation of the response codes to AP/RE during IMR introduction: it does not involve that the receiving system can be 100% sure that it won't receive other codes. The receiving system must therefore be able to handle the other scenarios (at least in a minimal way). no issue was raised with this clarification.

    • MLR: to the question about the specification that states that parent document sbdh data must be referenced in the MLR (not payload data), no opposite opinion is voiced. BOSA will align mercurius with this spec.

14 Feb 9, 2021

13:30 - 15:00

  • AdValvas

  • b2b grid

  • B2B Router

  • Basware

  • Billit

  • codabox

  • Descartes

  • Dynatos

  • Exact

  • Generix

  • Inaras

  • Ixor

  • Netropolix

  • soluz.io

  • Symtrax

  • Tradeshift

  • UnifiedPost

Agenda:

  • Update progress on CBE schemeID migration

  • Hermes

  • Decommissioning old BIS Billing

  • migrating MLRv2 to IMR (business)/MLRv3 (technical)

  • AOB

Slides:

1. Update progress on CBE schemeID migration

  • It is reminded that the schemeID 9956 is removed in the Peppol BIS schematrons spring release. So it becomes unusable from 17/5 on. So it is a hard stop. It is communicated on the BE AP forum and through the release notes. further broadcasting of the new by APs to potentially affected stakeholders is welcome. SchemeID 9925 is out of scope - but bear in mind that Belgium PA discourages use of the VAT ID for routing purposes, as it is over-using this ID and is not sustainable. In Belgium, prefer rather the enterprise number.

  • BOSA resends the january survey request to updated distribution list

  • all SPs to fill in the survey each month (takes no more than 2 minutes time).

3. Decommissioning old BIS Billing

It is reminded that Government will remove old BIS Billing Receiving Capabilities on 31/3/2021.

4. B2G - migration from old BIS (2.0) MLR to BIS (3.0) IMR/MLR

  • AP’s provide their statistics to PA on MLR they receive - asap; by end of the week at the latest

  • BOSA provides a description of the migration approach and timing based on the outcome of the discussion and the additional stats received

13 Jan 12, 2021

13:30 - 15:00

  • AdValvas

  • b2b grid

  • B2B Router

  • Basware

  • Billit

  • codabox

  • Descartes

  • Dynatos

  • Exact

  • Generix

  • Inaras

  • Ixor

  • Netropolix

  • soluz.io

  • Symtrax

  • Tradeshift

  • UnifiedPost

Agenda:

  • Update progress on CBE schemeID migration

  • Hermes

  • BIS migration completion (V2 to V3)

  • AOB

Slides:

 

1. Update progress on CBE schemeID migration

  • The timeline initially agreed is CONFIRMED. No need to delay Milestone B. Each AP can put whatever is needed in place to suit his own context, such that the code 9956 can be removed by then.

  • PA keeps monitoring progress through monthly surveys. To support data quality, AP's are asked to respond.

  • Exact schedule of milestone B is 17/5/2021

2. Hermes

  • Since Hermes/HSMP are LIVE, 10k participants were added on smp.belgium.be. This seems to confirm that Hermes boosts adoption.

  • AP whitelisting (technical side of the Hermes integrator agreement) is in user testing. Expect more definitive status/info/news next forum.

  • APs are enco.uraged to also consider signing Hermes integrators agreement, and contact us to this respect.

3. Decommissioning old BIS BILLING

  • Decommissioning rescheduled to 31/03/2021. Do not expect any additional delay.

  • BOSA will keep monthly monitoring decrease of old BIS invoices received by/transiting on Mercurius.

  • 2/3 of these invoice are generated by less than 20 senders. That means 2 or 3 per AP.
    Please prioritize your communication with your senders.

Actions:

  • All AP’s are requested to answer the SchemeID Migration questionnaire.

  • All AP’s are requested to act upon the ask to "get out of BISv2".

  • All AP’s can suggest a SME testimonial that could be used on e-invoicing website.

12 Nov 24, 2020

13:30 - 15:00

  • AdValvas

  • b2b grid

  • B2B Router

  • Basware

  • Billit

  • codabox

  • Descartes

  • Digiteal

  • Dynatos

  • Exact

  • Generix

  • Inaras

  • Ixor

  • Netropolix

  • OpenText

  • soluz.io

  • Tradeshift

  • UnifiedPost

Agenda:

  • Update progress on CBE schemeID migration

  • Hermes & HermesSMP

  • BIS migration completion (V2 to V3)

  • AOB

Slides:

  • Update progress CBE schemeID migration

  • progression : cf slides

  • discussion:

    • consider more detailled approach proposed by Basware: Migration enablement / Migration / Migration Close

    • in this approach spring releaase would coincides 9956 deprecation, and fall release would coincide 9956 removal.

    • howeverBasware confirms spring release is technically possible.

    • Some AP's confirm spring release remains possible

    • AP's ask for clear deadlines

Conclusion: BOSA will(a)  sharpen monthly questionaire; (b) work on communication/ AP survey to reassess migration timeline feasability

2. Short update given on the HSMP Migration Token Collection Interface and hrms activation / communication support - cf slides

3. Decommissioning old BIS billing (2.0)

  • BOSA keeps communicating message and figures to SPs, to Regions

  • BOSA calls for relaying message to senders

11 Oct 13, 2020 

13:30 - 15:00

  • AdValvas

  • b2b grid

  • B2B Router

  • Basware

  • Billit

  • codabox

  • Descartes

  • Digiteal

  • Dynatos

  • Exact

  • Generix

  • Inaras

  • Ixor

  • Netropolix

  • OpenText

  • soluz.io

  • Tradeshift

  • UnifiedPost

Agenda:

  • Update progress on CBE schemeID migration

  • HermesSMP - Migration Token Collection Interface test debrief

  • BIS migration completion (V2 to V3)

  • Call for success stories (SMB)

  • Peppol Agreements framework

  • Backlog

  • AOB

Slides:

  • Update progress on CBE schemeID migration

    • Call to action: SPs to answer the poll each month - NB: for the time being no answer will be considered as “NO”answer on all 3 questions

    • Complication caused by concurrent activation of Hermes (15/11) and CBESchemeID migration (9956>0208) :

      • instant poll: all expressed opinions is that they see no problem here

      • action: BOSA: further investigate the issue and give feedback.

  • HermeSMP - Migration Token Collection Interface test debrief

    • Call to action: SPs to request their dataset and perform tests

  • Decommissioning old BIS billing (2.0)

    • BOSA will keep communicating message and figures to SPs and call for relaying message to senders

  • Call for success stories (SMB)

    • Call to SP'S for suggesting success stories in the segment of SMBs to publish on efacture.belgium.be and inspire the market

10.