Skip to content
Dataspilot

Connecting your ERP or invoicing software to Peppol

Don't want to change software? Your ERP or invoicing tool can send and receive Peppol invoices via an API. The options and the steps of a project.

Guide By Administration

Switching invoicing software solely for Peppol is rarely necessary. In most cases, your current tool can be connected to an access point.

Three options

  • Your vendor's module, if it already supports Peppol: the simplest solution, provided it covers both sending and receiving.
  • An API connection to an access point: your software sends its invoices and retrieves those from your suppliers automatically.
  • Compliant invoicing software, such as Niceflow (Axio Solutions), if your current tool is no longer fit for purpose.

The steps of an integration project

  1. Inventory: where invoices are sent from, where supplier invoices arrive, and who approves them.
  2. Data mapping: VAT codes, units, customer and item identifiers to the fields of the UBL format.
  3. Registration of your company on the Peppol network.
  4. Testing sending and receiving, including credit notes and rejections.
  5. Go-live and monitoring: status of each invoice, alerts in the event of an error.

Don't forget receiving

The obligation also covers receiving supplier invoices. Plan where they arrive, who approves them and how they reach your accounts.

The Dataspilot Peppol API enables your ERP, your CRM or the software you publish to send and receive e-invoices via our access point.

Key points

  • Your current software can often be connected to Peppol via an API.
  • The core of the project: mapping your data to the UBL format.
  • Plan for both sending AND receiving invoices.
  • Peppol
  • API
  • ERP
All articles