search

peppolautoriteit-nl / Invoice-Processes-Draft

Draft documents regarding invoice to payment processes, and which documents to send in which scenario
0 stars 8 forks source link

Storecove - Routing identifiers #9

Open PatrickVHL opened 2 years ago

PatrickVHL commented 2 years ago

"I find the Rinis document confusing regarding the roles of the different parties and their identifiers. Routing-wise, Response documents SHALL be routed back to the envelope sender. Some SPs may choose to use a routing identifier that is part of the invoice, i.e. PartyIdentification, PartyTaxScheme or PartyLegalEntity. Others may choose to implement separate routing identifiers per receiver for response documents (e.g. GLN). This is important for the scenario where the sending and receiving AP are not the same. Other SPs may even have all their response documents routed to a single identifier."

PatrickVHL commented 2 years ago

Based on discussions within several NPA and OpenPeppol related working groups the NPA has defined a best practice for routing, which can be found here: https://github.com/peppolautoriteit-nl/Invoice-Processes-Draft/blob/main/Invoice_to_Payment_Process/Invoice_to_Payment_Process.md#323-routing This section states that routing should be done based on EndUser identification (C1) and not based on a generic Endpoint from a ServiceProvider. Not only from a generic and standardization point of view, but also to create better insight in the amount of endusers that are capable of sending documents through Peppol.