Skip to main content

This page has been translated using TexTra by NICT. Please note that the translation may not be completely accurate.
If you find any mistranslations, we appreciate your feedback on the "Request form for improving the automatic translation ".

FAQs: About Peppol e-invoice Interactions in the Peppol Network (Overview)

  • The content of this FAQ is as of July 21, 2023, and is subject to change without notice due to changes in the rules and operation policies of OpenPeppol, etc.

Q2-1

What does it mean to "exchange Peppol e-invoice in the Peppol network"?

A2-1

Specifically, it refers to the exchange of invoice data sets between the seller's access point (C2) and the buyer's access point (C3) in accordance with Peppol's standard specifications.

The mechanism of Peppol is a so-called "four corner" model. The user (seller) (C1) connects to the Peppol network through its own access point (C2), transmits the invoice data set to the buyer's access point (C3), and receives it to the buyer (C4).

The invoice data set is then automatically processed by the system machines of the seller (C1) and the buyer (C4).

Illustration of electronic invoicing in the Peppol network, where invoice data flows from the seller to the buyer through an access point.

Q2-2

Is there a mechanism within the Peppol network to store the Peppol e-invoice exchanged there?

A2-2

There is no mechanism within Peppol to store the invoice data sets that are exchanged.

(*) Under the Consumption Tax Act, sellers are required to retain qualified invoices for Issue (paper) and electromagnetic records provided in lieu of qualified invoices (so-called "electronic invoices"), and buyers are required to retain qualified invoices for Issue and electromagnetic records provided in lieu of qualified invoices (so-called "electronic invoices") for the purpose of applying the Purchase Tax Credit.

(*) Some Peppol Certified Service Providers offer their own service products that store the invoice data sets exchanged, separate from the regular Peppol Service.

Q2-3

Does it mean that it is not necessary to use the invoice dataset according to the JP PINT for "between C1 (the seller side) and C2 (the access points)" and "between C3 (the access points) and C4 (the buyer side)"? If it is not necessary to use it, isn't a standard specification for it formulated?

A2-3

JP PINT is a Japanese standard for Peppol e-invoice that is exchanged between a seller's point of access (C2) and a buyer's point of access (C3).

Therefore, it is not necessary to use this in other parts (for example, "seller side (C1) and seller side access point (C2)" and "buyer side access point (C3) and buyer side (C4)").

However, depending on the Peppol Certified Service Provider providing the vendor Access Point (C2) service, the vendor (C1) system machine may be required to generate the invoice data set accordingly.

The standard specification of the invoice data set exchanged between "C1 (seller side) and C2 (seller side access point)" and "C3 (buyer side access point) and C4 (buyer side)" is not within the scope of Peppol.

Q2-4

Does the seller (C1) have to be aware of "Rules" and generate the invoice data set?

A2-4

"Rules" are rules for the validation (validation) of the invoice dataset exchanged in the Peppol network at the access points (C2) on the seller side.

Therefore, the step of generating the invoice data set (the system machine on the seller side (C1)) does not necessarily generate the invoice data in accordance with the "Rules".

However, depending on the Peppol Certified Service Provider that provides the Access Point (C2) service, the vendor's (C1) system machine may be required to generate the invoice data set according to its content, including this "Rules".