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

Open

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

Open

Open

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 (26^th 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

Open

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:

Open

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 21^st– 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:

Open

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:

Open

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:

Open

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:

Open

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:

Open

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:

Open

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:

Open

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:

Open

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:

Open

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:

Open

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:

Open

• 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:

Open

• 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. Sep 15, 2020

13:30 - 15:00

• AdValvas

• b2b grid

• Basware

• Billit

• codabox

• Digiteal

• Exact

• GenerixGroup

• Inaras

• Ixor

• Netropolix

• Soluz.io

• Symtrax

• Tradeshift

Agenda:

• hrms activation
  
  

  • go live date

  • mtci user tests

  • agreements

  • smp.belgium.be support of migration key

• 9956>0208 migration

• new governance framework: update

• BIS migration completion steps

• AOB

Slides:

Open

1.a) mcti user testing – the way forward:

• the proposed approach and schedule is suitable: (1) early bird user test with direct support from Tradeshift until sept 25^th and (b) wide scale user testing with BOSA DT support from sept 28^th until oct 8^th

• upon request to BOSA, each tester will get an own test dataset assigned, mapped with the scenario it allows testing incl the blacklisting. Tradeshift prepares 20 of them.

• test data will be recycled daily

• minor changes (typos, …) to the doc will be done without formal notification. More significant changes will be notified by mail by Peppol@bosa.fgov.be

• regression testing will be supported. A more detailed description of this will be elaborated in due time.

1.d) hrms go-live is set on nov 15^th . SP are invited to make sure they can keep registering Belgian receivers afterwards, using the migration token.

2. BOSA DT will organize a monthly survey to collect figures about step 1 (no more 9956 based registrations of Receiving capabilities (RCs)), 2 (complete duplication of the 9956-based RCs onto 0208-equivalent RCs), and 3 (complete removal of old 9956-based RCs), and publish the consolidated results.

4. BOSA DT will issue a draft communication to be used by SPs as inspiration to cascade the request to their senders. The effect can be monitored in the mrcs data and will be the subject of a follow on item.

Next meeting oct 13^th at 13:30 – 15:00 – save the date

9. Jul 14, 2020 

• AdValvas

• b2b grid

• B2B Router

• Basware

• codabox

• Connect-Solutions

• Digiteal

• Esker

• Exact

• Inaras

• Netropolix

• Soluz.io

• Tradeshift

Agenda:   

Welcome from 13:30

• 9956>0208 migration

• new governance framework: update:

  • agreements

  • policies

• AOB

Closing at 14:40

Slides presented at the forum:

Open

1.   At end of the discussion moment, there is no consensus to do more than minimal scenario (A) .

      Belgian Peppol Authority will

• reassess the options to increase migration smoothness. This includes periodic gathering of data to monitor migration progress, discussing results with SPs during fora, and anticipating the offical phase out date.

• confirm other documents types also fall under the migration (not only BIS Billing).

3.  e-Invoicing Summit 2020: SPs are encouraged to take advantage of this specific communication moment on the Belgian market.

8. Jun 23, 2020 

On line:

• Advalvas

• B2B Router

• Basware

• Billit

• Codabox

• Digiteal

• Dynatos

• Esker

• Exact

• Ixor

• Netropolix

• Soluz.io

• Tradeshift

• UnifiedPost

Agenda:   
Welcome from 13:30

• Hermes MTC interface specs review / next steps

• Hermes agreements review /next steps

• Hermes sending – APs scenario: specs

• Backlog / Next forum

Closing at 14:45

Slides presented at the forum:

Open

• Hermes MTC i/f specs were approved after due review round. a final specs package will be posted soon on the Belgian Service Providers / Access Point Forum page, including the testing artefacts and an update of the schedule of the next phases.

• The sender and the integrator agreements were approved after dur review round. SPs are invited to sign the integrator agreement and proceed with the reuse of Hermes to strengthen their offering and contribution to the uptake of e-invoicing in Belgium.

• SPs were kindly asked to provide their preferred option(s) for the modifications to the hermes sender interface to suit the integration scenario. see actions recap below.

Actions:

• BOSA performs a survey to collect SP preferences on item 3 above (DONE)

• BOSA provides answers to questions posted in the chat during the session (DONE)
  
  

• BOSA schedules next forum (DONE - save the date sent)

 7. 

May 26, 2020 

On line:

• Advalvas

• B2B Grid

• B2B Router

• Basware

• Billit

• Codabox

• Dekimo

• Descartes

• Digiteal

• Dynatos

• Exact

• Ixor

• Netropolix

• Soluz.io

• Tradeshift

• UnifiedPost

• Vlaamse Overheid

Agenda:

Welcome from 13:30

1.      Hermes update: impact on registering participants

2.      BIS BILLING migration : assess status and discuss practical issues encountered

3.      introduction of schemeID 0208

4.      New Service Provider agreement

5.      e-invoicing Summit 2020

AOB

Ending expected at 15:30

Slides presented at the forum:

Open

1. Hermes

(a) please review the conventions (integrator/user) and provide feedback

(b) migration token:  please review the interface specification (swagger, test plan description) and provide feedback, incl answers to survey sent earlier (see below);  

(c) based on the feedback and questions collected during the forum, DT will produce a clarification on the exact positioning of hrms and put the topic back on the agenda

2. BIS Migration: based on the feedback and questions collected during the forum, DT will produce a more specific migration plan for review and execution.

3. SchemeID 0208 : based on the feedback and questions collected during the forum, DT will produce a more specifc migration plan for review and execution.

highlighted and migration from 9956. Will also be taken in a FUP exchange moment.

5. e-invoicing summit, AOB: was only introduced (short on time).  postponed to a later forum edition

DT Actions – fulfilled Jun 4, 2020 

• Next forum: Tuesday June 23rd PM- shorter timing (around 1 hour) and more limited agenda  (priority based) with focus on Hermes: invitation sent on Jun 2, 2020 

• Provide HSMP migration token interface specs (swagger, test plan description) cf Belgian Service Providers Forum

• Send questions for HSMP migration token sent by email on May 29, 2020 

• Share updated version of New Service Provider agreement cf Belgian Service Providers Forum

• Share draft hrms conventions (integrator, user) ; cf Belgian Service Providers Forum

6. Feb 3, 2020 

On-site:

• Advalvas

• Codabox

• Connect-Solutions

• Dynatos

• Inaras

• Ixor

• netropolix

• soluz.io

• Unified Post

• Flemish Gov (VO)

Remote:

• B2BGrid

• Basware

• Brain²

• Digiteal

• Exact

• SAP

• Tradeshift

Agenda:

I. news from Belgium

• new from the team

• figures

• www.einvoice.belgium.be

• HRMS

II. news from Peppol

• new branding, new website

• migrations

AOB

Streaming of the forum:  https://www.youtube.com/results?search_query=fod+spf+bosa

Slides presented at the forum:

Open

I.4 – HRMS:

(a) emails sent by HRMS are expected to be 99,99999% bounce-back-proof and blacklisting-proof;

(b) a side effect of Hermes, is that all Belgian participants are registered in Peppol and acquiring customers becomes a matter of migrating existing participants, instead of registering new participants.

(c) registering Belgian participants into smp.belgium.be is still possible, but isn’t a condition of the BE AP agreement anymore (c) Mercurius focuses on government, primarily inbound invoicing; Hermes focuses on business outbound invoicing, and will also be useful for government entities outbound invoicing (example: De Lijn).

(d) no entity can use Hermes to send invoices unless it signs an agreement with BOSA. However, BOSA is keen to discuss agreements with service providers if it would be suitable to the sector and not compromise the model.

II.2 -  Migrations:

(a) Oxalis doesn't prevent senders to send BIS2 to BIS2+BIS3 receivers. The only issue is AS2-AS4 related. It is up to the SPs to upgrade to latest Oxalis asap.

(b) Supporting AS2 (profile 2.2) is also at discretion of the SP.

(c) Noncompliance of other SPs such as missing AS4 support, can and should be reported trough the applicable channels (in particular, openPeppol support tool) ;

(d) in order to minimize issues such as the ones that highly penalized Flemish government last month, it is advised to stop converting BIS2 to BIS3, at least until more robust convertors (validated by multilateral end-to-end tests) are available and stable.

(e) the option to provide feedback to sender or his SP in case he sends non-compliant documents, was discussed for years at all levels. To date there is no consistent  strategy / generally agreed way to deliver such feedback, neither globally nor in Belgium.

(f) the option to check a document was delivered using the underlying message ID (or the associated MDN),  is only available in mercurius-test. An APs proposes to add this function in production. BOSA DT will consider this.

(g) a SP notices that there are in fact 3 concurrent migrations: BIS2>3, AS2>AS4, and AS2.1>AS2.2. this is too much. In practice, al these migrations must be done.

(h) a SP advices to be more strict in the implementation of changes. In the telco world it works because of the strict adherence to common schedules. The question is how can we reach such a strict behavior without legal framework and with the current market maturity

(i) for B2G it is highly recommended to APs to check their traffic to mercurius using their special access (eGOV role “Mercurius_AP”). With that access, they always can check what invoices were duly received at mercurius level and correlate with their own logs, which is step 1 in troubleshooting.

AOB

• new framework agreement: at this point BE has no special requirement except using the CBE number to register Belgian entities. (which is common to other countries, with their respective schemes)

• remote follow up will be maintained and extended with (a) additional microphone to capture and share local attendants comments and (b) improved interactiveness with remote attendants (channel to be defined)

• next forum May 26^th at 14:00

• 12th OpenPeppol GA and F2F: only the General Assembly will take place on March 26^th 2020

5. Sep 4, 2018 

• Advalvas (AP)

• Billit (AP)

• Babelway (AP)

• Basware (AP)

• Bosa (PA)

• Codabox (AP)

• Octopus (Inaras) (AP)

• Dynatos (AP)

• UnifiedPost (AP)

• Vlaamse Overheid 

I.Belgian Governement support of uptake of e-Invoicing

• Progression of Peppol rollout in Belgium (1. B2G; 2. B2B): update

• E-invoicing rollout amongst Belgian contracting authorities

• HERMES

• Mercurius rebranding

II.Belgian AP forum discussions

•   Senders list (forum 4 agenda Item 7) – next

•   Negative MDN upon invalid payload

III.Peppol service-info:

• PKI Migration V2-V3: Timing – walk through

• certificate request procedure, new version – legal registration form / Annex1

• Peppol customization IDs registration policy update

• Peppol AS2 -> AS4

IV.AOB

Slides presented at the forum:

Open

II.Belgian AP forum discussions

• Belgian senders list publication:

  •  forum members willing to publish senders on the list: please send csv-files to Peppol@bosa.fgov.be with at least enterprise number and name.
    
    

  • all forum members can send suggestions on next steps towards improvement and stabilisation of the senders list, based on this V1.
    
    

• how to address invalid payload:

  • Post-Forum analyse was performed to assess feasibility of using an email feedback channel instead of the negative MDN discussed. Conclusion: is not practicable because (a) the SMP stores receivers info, while we try to feedback the sender's AP. (b) not all APs publish an email address on the SMP record
    
    

  • consequently forum members are invited to vote between following options, and explain why: 

    • do nothing

    • return Negative MDN only
      
      

    • send email notification to PA (Peppol@bosa.fgov.be)

    • return Negative MDN + send email notification to PA (Peppol@bosa.fgov.be)

IV.AOB

• issues with the interpretation of the semantic model (Peppol BIS), eg store the car license plate in an inappropriate ubl data element such as sellersItemIdentification:the Business Experts Group is the forum that addresses this kind of topics, as it has a strong business orientation

• next edition in Januari, PA to send a doodle soon and schedule

4. May 15, 2018 

• Advalvas (AP)

• Billit (AP)

• Babelway (AP)

• Basware (AP)

• Bosa (PA)

• Codabox (AP)

• Octopus (Inaras) (AP)

• Koalaboox (AP)

• Netropolix (AP)

• SAP (AP)

• Speos (AP)

• UnifiedPost (AP)

• Unit4-Clogic (AP)

• Vlaamse Overheid 

1.Progression of Peppol rollout in Belgium

2.OpenPeppol communication tools

3.Official webpage of the Belgian PA

4.Peppol certificates migration Q3/2018 

5.Implementation of the European Norm – Peppol side

6.Upcoming CEF telecom call on e-invoicing

7.Statistics on sender data

8.Practical organisation of the AP forum

9.AOB

Slides presented at the forum:

Open

Open

1.Peppol Rollout:

• Vlaamse Overheid sets up action plan to identify portal senders motivations (+/-), and stimulate them to move to Peppol

• Vlaamse overheid calls APs and IT sector to participate to a new round of info sessions pla send a mail to e.procurement@vlaanderen.be

4. Peppol certificates migration:

• general info and detailed links: Newsletter 11.04.2018 - PKI Migration, Statutes Changes/Additional GA, etc.

• active from May 21, 2018 on: url to request certficate renewal (v2 and v3): OpenPeppol Service Desk

5. European Norm:

• EN16931 = Directive 2014/55/EU obliges all public authorities in Europe to receive and process this new standard from Apr 18, 2019 on

• Peppol BIS BILLING V3= CIUS of EN 16931; link: Peppol BIS Billing 3.0.1

6. CEF telecom on e-invoicing:

• main page: 2018 CEF Telecom Call - eInvoicing (CEF-TC-2018-2)

• info day on May 17, 2018 

• Belgian PA is happy to support requests for grants from Belgian candidates, please contact us if you have plans to apply. please notice that we can help you finding admin support in the application process.

• when applying, please consider our proposal for improving your support of a truly "any to any" approach to document exchange, that the Peppol framework promotes

7. Sender stats: conclusions of the discussion:

• key data: only sender ID and Name (NB: is also in line with privacy regulations)

• scope: Belgian enterprises. other nationalities possible but not explicitly in scope

• APs will send their list of senders  - only companies that already send, or are fully capable of sending.

• PA consolidates the datasets and publishes it

• APs to raise any issue on this by May 31, 2018 . afterwards proposal will be considered approved

• more details (eg how exactly it will be published, update frequency, ...)  to be defined at next AP forum

8. AP forum organisation:

• PA will communicate with 1 single point of contact for each AP.

• AP may notify an email address/contact for this purpose

• if AP does not notify a specific email address/contact, then contact on section 4.5 of Annex 1 will be used..

9. AOB:

• SNI: PA contacted DIFI (conformance testing instance for Belgian PA). awaiting feedback. on agenda of next forum

• Invoice Response general info: see slides. More details to follow in next AP forum.

3. Sep 29, 2017 

• Advalvas (AP)

• Agoria (Sector)

• B2BGrid (AP)

• Babelway (AP)

• Basware (AP)

• Bosa (PA)

• Codabox (AP)

• Dynatos (AP)

• Inaras (AP)

• Netropolix (AP)

• UnifiedPost (AP)

Agenda:

• Progression of the Peppol receivers, public and private – information (10’)

• Need to have stats over (a) senders and (b) volumes, and how to get them – discussion (15’)

• BIS Invoice Response (063A) – publication – information  (10’)

• BIS support – implication on the participants registration – discussion (15’)

• EDIFACT support – information (10’)

• Additional instruments developed by the PA to help Access Points, and facilitate adoption of universal e-invoicing – reference: https://digital.belgium.be/e-invoicing/ - demo and Q&A (20’)

• Upcoming communication facilities for the Peppol Belgian Domain (confluence platform ) – requirements collection (20’)

• CEF telecom call on e-invoicing (10 million grants available for improving your platform interoperability) – more info: Connecting Europe Facility (CEF) Telecom virtual Info Day   - information and call for submission (20’)

• European Multi-stakeholders Forum on e-invoicing – new mandate 2017-2020 – Belgian representation  - information (5’)

Slides presented at the forum:

 Presentation Presentation

2. Need to have stats

• AP would like to have a senders registry. Identifying companies that are capable of sending Peppol is currently not possible. The high amount of Peppol senders would be the best way to convince companies to develop receiving capabilities.

• This is out of the Peppol scope but of course it could be developed, within Belgian domain (or globally).

• As a first trial to address this, senders data could be collected in the context of a national reporting – as foreseen in the annex 5. Dataset defined during the meeting: sender- sender ID – Volume (for a given time period)

 4. BIS Support:

• in order to facilitate the respect of the BIS mandatory support, in application of the conclusions of the discussion, smp.belgium.be registration interface will be modified to reject registration of formats of document types for which the corresponding BIS is not yet registered.

• It is technically possible to register such formats in another SMP. However, (a) this is out of our span of control, and (b) Belgian receivers are expected to be registered in smp.belgium.be. our jurisdiction is limited to this scope of participants.

 6. additional instruments

• Test message lookup tool: enter the ID of the AS2 message containing the document. Notice that the tool should also support the ID of the AS2 MDN returned by the receiving AP. The supplier misunderstood this. It will be fixed as soon as possible.

• APs ask the smp.belgium.be online lookup to be more user friendly, incl sort functionality. This will be added in the backlog.

7. upcoming communication facilities (confluence)

• APs ask (a) a product roadmap for mercurius and (b) a Peppol hot issues log

2, Mar 29, 2017 

• Advalvas (AP)

• Agoria (Sector)

• Babelway (AP)

• Basware (AP)

• BRAIN²(AP)

• BOSA DT (PA)

• Codabox (AP)

• Codit (AP)

• Dynatos (AP)

• Ixor (AP)

• Koalaboox (AP)

• MVG (PA)

• Speos  (AP)

• PAGERO (AP)

• UnifiedPost (AP)

• UNIT4(AP)

Agenda:

• Status SMP.belgium.be

• Status B2G

• Status tests B2G

• Business agreements

• Setup Business Experts Workgroup

Slides presented at the forum:

Open

N.A.

1, Jan 25, 2017

• Advalvas (AP)

• ARCO (AP)

• ASA (PA)

• Babelway (AP)

• Basware (AP)

• Codabox (AP)

• Codit (AP)

• Dynatos (AP)

• Fedict (PA)

• Ixor (AP)

• Koalaboox (AP)

• MVG (PA)

• PAGERO (AP)

• Speos  (AP)

• UnifiedPost (AP)

• UNIT4(AP)

Agenda

• Status roll out e-Invoicing within Belgian authorities

• My eGOV Roles management and Mercurius web interface

• Contents of the invoices : requirements from the public sector

• Tests: structured approach – Peppol conformance testing, end2end Testing– how to avoid wasting time

• Invoice Response - MLR

• New from the business – business discussion forum

• Smp.belgium.be – record Belgian participants

Slides presented at the forum:

Open

1. Status Roll out e-invoicing within Belgian Authorities.

Status of the roll out by Serge Libert (for the federal) and Johan Van Steelandt (for Flanders).

Status of the roll out in Brussels and Wallonia by Luc Gathy.

Brussels will choose for Mercurius and for intelligent scanning.

Wallonia is updating their back office system to receive e-invoices.

2. My eGov Roles management and Mercurius web interface

Serge Libert explains the possibilities of the eGov Roles Management and shows the new website.

https://digital.belgium.be/e-invoicing

 3. Contents of the invoices: requirements of the public sector.

Peppol BIS/CEN BII fulfill most of the requirements so far

However there’s an agreement to set a meeting with business experts in order to look for answer to specific issues.   (See 6.)

4. Tests, overview.

• Peppol conformance testing

• Mercurius testing

• End to End testing. (Procedure from the Flemish Region).  (See annex)

Remarks:

• Sometimes there’s a discrepancy between the promotion initiatives by an authority and the actual readiness to receive e-invoices.

• End to end test will continue with a selection of the Flemish back offices.

5. Invoice response – MLR

New Peppol Bis document on invoice responses expected by  4^th quarter of 2017.

Explanation on the MLR by Serge Libert. see slides

6. New from the business – business discussion forum

Experts will be invited for a meeting on several issues as:

• Cash discount (a) transport (b) automation

• VAT exemptions (a) transport (b) automation

• Spare parts VAT liftups (a) transport (b) automation

 7. SMP.BELGIUM.BE

• Only for enterprises with a Belgian CBO-number.

• Access points should support foreign SMP for customers and suppliers from abroad.

 8. Frequency of the meeting -  requirements

• at the start, each two months.

• later on, each three months.