Frequently
asked questions

Find the answers to common questions about Peppol APIs and cross-border e-invoicing. Can’t find what you’re looking for? Ask our experts.

Looking for more detailed information? Check out our e-books or sign up to our newsletter for regular updates.

Peppol is a Europe-wide standardised network for exchanging electronic documents, including e-invoices. Companies use Peppol to ensure their e-invoices are both compatible with a broad network of businesses and compliant with European mandates.

A Peppol Access Point is a gateway into the Peppol e-delivery network which enables various parties to send and receive documents via its four-corner model. Once connected into Peppol via an Access Point, organisations can securely exchange standardised electronic documents with any other participant who is also connected into the network.

Peppol Access Point Providers are certified organisations or service providers that operate a Peppol Access Point, which can be used to connect to Peppol. Software companies can work with a Peppol Access Point Provider to deliver Peppol connectivity to their own users, instead of having to build and maintain their own Access Point.

Peppol works by standardising how information is structured and exchanged, so consistency and compatibility is achieved across all participating entities.

Peppol operates on a decentralised interconnected network using a four-corner model, which participants connect into via certified Peppol access points. Each participant is identified through their Peppol ID, which is held by Peppol Service Metadata Publishers (SMPs).

There are several ways to connect to Peppol: partnering with a Document Service Provider (DSP), becoming a Peppol Access Point yourself, or integrating via an Access Point provider’s API. The simplest option is to connect your software through a service provider’s API. They handle the technical setup and give you access to a Peppol Access Point, so you can send and receive documents without managing the infrastructure yourself.

APIs offer flexibility and automation; invoices can be sent and received effortlessly directly from your existing software. This not only saves time, it also reduces the likelihood of errors compared to manual workflows.

API-based e-invoicing integrates smoothly into your existing CRM/ERP systems, automating the invoicing process. In contrast, traditional methods may involve manual steps or separate platforms which can be inefficient.

Integrating an API can be straightforward, especially with well-documented REST APIs. However, the level of complexity will vary depending on your current infrastructure and the needs of your business.

You need to ensure adherence to regional-, industry- and country-specific regulations, including the upcoming B2B e-invoicing mandate and Peppol standards. Non-compliance could result in legal issues and financial penalties.

API-based e-invoicing tends to be more cost-effective due to automation and reduced manual labor. In contrast, traditional methods can incur additional fees and operational costs.

Flowin offers a monthly subscription model with a minimum commitment and fees ranging from 20 to 80 cents per company usage. See pricing page.