...

This list is maintained for the sake of completeness. ePRIORis ePRIOR is the legacy system that was re-used during the pilot B2G e-invoicing project. After the pilot project the ePRIOR interface with the private sector was phased-out (and replaced by PEPPOL interface), but the interface with public sector was maintained. only Only in 2018 this interface phase-out became necessary, due to introduction of European Norm and new exchange patterns such as eOrdering.

ePRIOR is also a suite of CEN-BII-, UBL2.0-based document formats (invoice, credit note, application response, attached document , ...). based on these documents formats, the following series of flows was set up and kept alive until ePRIOR interface is completely stopped. see See also Transition from ePRIOR interface to simpl.ePRIOR (temporary section).

these These flows are:

• inbound ePRIOR Invoice
• inbound ePRIOR CreditNote
• inbound ePRIOR Attached Document
• outbound ePRIOR Application Response

...

The semantic layer are defined by standardization teams. that The new PEPPOL BIS 3 Invoice format is an implementation of the european stadard standard for electonic electronic invoice, that provides the semantic specification and the syntaxt binding. PEPPOL teams only add implementation-level specifications.

Defined document formats

the The following 2 table tables summarize the key information about the supported document formats.

Format specifications

...

...

You can validate that your message contain documents that respect format specifications  specifications with the following tools :

• https://vefa.difi.no/validator/
• https://peppol.helger.com/public/menuitem-validation-bis2

NB: the tool sallow using diferent rues set. It tools allowing to use different rules set, it is important to use the correct rule rules set, ie the latest version of the rule rules set that contains the exact format denomination (example : BISV2 INVOICE 4A).

Develop your own validation tool via :

...

• Both interfaces are available in parallel.
• the The legacy invoices and CNs, sent by (5) suppliers still using the interface implemented during the Pilot-phase (not yet PEPPOL), are only accessible through the ePRIOR interface.
• all All portal invoices (and CN), all BIS2 Invoices (and CN), and all EDIFACT-pilot invoices are accessible through both interfaces.
• only Only simpl.ePRIOR gives access to BIS3 and UNCEFACT/CII invoices and CNs.
• only Only simpl.ePRIOR enables outbound flows.

The message layer data accessible through the Mercurius Portal, enable enables the follow up of the pickup of the documents on bth both interfaces, making it very convenient to follow up.

...

1. pick up invoices through simpl.ePRIOR interface (and mark all collected invoices);
2. pick up remaining invoices on ePRIOR interface.

Definitions

References

Sample Code

This example is provided without any guarantee or support. It's only to help you and show you how to generate code based on the WSDL definition.

...