Skip to main content

​
Introduction

Peppol (Pan-European Public Procurement On-Line) is a global network for electronic document exchange, widely adopted for e-invoicing across multiple countries. It provides a standardized protocol for companies to exchange business documents like invoices, credit notes, and purchase orders. The Peppol network is particularly popular in:
  • Nordic countries (Norway, Finland)
  • Asia-Pacific region (Japan, Singapore, Malaysia, Australia, New Zealand)
  • Several EU countries for business-to-government invoicing (Germany, Italy, Croatia)
Invopop allows you to send and receive documents through the Peppol network using a single integration while continuing to work with our GOBL format. This guide walks you through the steps to register a company in Invopop and then issue and receive invoices on its behalf.

​
Setup

Let’s prepare your workspace to work with Peppol. We’ll configure the Peppol app and create three workflows:
  • Invoice issuance workflow: Send invoices through the Peppol network
  • Invoice reception workflow: Receive invoices from the Peppol network
  • Party registration workflow: Programmatically onboard companies (Parties) with Invopop
If you only want to send invoices through Peppol, you can skip step 3 and 4 of the setup. Alternatively, if you only want to receive invoices through Peppol, you can skip step 2. The Peppol app is designed to only send and receive the document, generating and importing the appropriate file is delegated to format specific apps such as Oasis UBL or UN/CEFACT CII. This is done to keep the Peppol app simple and focused on the Peppol protocol, while allowing you to use the format that best suits your needs.
1

Connect the Peppol app

  1. Within the Console, navigate to Configuration → Apps
  2. Find the Peppol app in the list
  3. Click Connect to activate it. The Peppol app should now appear in the list of Enabled apps
Connect Peppol app
2

Configure a workflow to issue invoices

Now we’ll create the workflow that converts invoices to a valid Peppol format and sends them through the Peppol network. In this example, we’ll generate a Peppol BIS Billing UBL 3.0 document.Skip this step if you only want to receive invoices via Peppol.
3

Configure a workflow to receive invoices

4

Configure the Peppol app

Within the Console, navigate to Configuration → Apps, find the Peppol App and click Configure. You’ll need to set two fields:
  • Incoming Workflow: Select the Receive Invoice Workflow created in Step 3. This is where the app will send incoming invoices (expenses) received from the Peppol network.
5

Configure a Party registration workflow

This workflow onboards companies (Peppol participants) to Invopop before they can issue or receive invoices. If you’re managing your own invoices only, you may use this workflow just once. However, if you’re offering Peppol to your customers through Invopop (white-label use case), you’ll run this workflow for each merchant you onboard.
Congratulations! Your workspace is now configured to send and receive Peppol documents and programmatically onboard Peppol participants with Invopop.

​
Running

After setup, you can perform three key operations with Peppol in Invopop: onboarding entities (parties) so they can use Peppol, sending invoices through Peppol, and receiving Peppol invoices.

​
Registering parties

Business entities are represented in Invopop as GOBL org.party objects, which we call Parties. Peppol requires Invopop to collect proof of ownership for regulatory compliance. As outlined in Section 3.3 End user Identification of the Internal Regulations II document, key details such as VAT number, address, contact information, and company name must be provided and validated during registration. To register a party:
  1. Upload it to the Silo with required company information
  2. Send it to the party registration workflow
Note for Belgium: If you’re registering for the first time in Belgium, you’ll need to use a migration workflow (a modified initial registration path required when first onboarding in Belgium) instead of the standard registration workflow. See the Belgium Peppol Guide for specific instructions on obtaining a migration key from BOSA and setting up the migration process.

​
Upload a party document

You can upload parties via the Create an Entry API endpoint or manually through the Console. For this guide, we’ll demonstrate the manual process:
  1. Find the Contacts section in the sidebar and click Suppliers
  2. Click + New Supplier to open the editor
  3. Enter the required information (or use the example below)
The mandatory fields for Peppol registration are:
  • Company name (fiscal name)
  • VAT number (tax ID)
  • Complete company address
  • Contact information
  • Peppol participant ID
If no Peppol participant ID is provided, Invopop will assign one during registration based on the VAT number and the country. All fields are required for identity validation and proof of ownership verification. Click Build to validate the document, then Save.
Peppol party example
{
    "$schema": "https://gobl.org/draft-0/org/party",
    "name": "Invopop S.L.",
    "tax_id": {
        "country": "ES",
        "code": "B85905495"
    },
    "inboxes": [
        {
            "key": "peppol",
            "scheme": "9920",
            "code": "B85905495"
        }
    ],
    "addresses": [
        {
            "num": "42",
            "street": "Calle Pradillo",
            "locality": "Madrid",
            "region": "Madrid",
            "code": "28002"
        }
    ],
    "emails": [
        {
            "addr": "billing+test@example.com"
        }
    ]
}

​
Send to the registration workflow

Once the document is saved:
  1. Click the Select Workflow button
  2. Select the Register Supplier workflow created during setup
  3. Click Run Workflow
The execution should succeed, and the silo entry’s state will change to “Processing.” The first step creates a registration link that you can extract from the Meta tab or via the API:
Sending party to the registration workflow
This link leads to a webform where you can upload proof of ownership documents and confirm your company details:
Peppol registration wizard
After submitting the webform, Invopop will be notified and will validate your information within up to 72 hours. The approval status will be shown in the Meta tab of the entry.

​
Programmatic registration (white-label)

For programmatic integration, you can use our API instead of the webform. This is particularly useful for white-label implementations where you want to integrate the registration process into your own application. You can achieve this by uploading the proof of ownership document using the API. This launches the validation process automatically.

​
Completion

When Invopop approves your registration, we will automatically register your party with the Peppol network as before. You’ll see the Peppol Participant ID in the Meta tab of the entry and the supplier’s entry will contain an inboxes array. This information should be included in each invoice issued by this supplier.
Peppol inboxes

Peppol participant inboxes

The party can now send and/or receive invoices in Peppol via Invopop.

​
Sending invoices

To send an invoice, you need to store it as a Silo Entry with the
  1. Store it as a Silo Entry with the Peppol inboxes previously obtained.
  2. Send it to the Sending Invoice Workflow created during setup
You can perform these steps manually via the Console or programmatically via the API using the Create an Entry and Create a Job endpoints. For API usage, refer to our quickstart guide. When creating your invoice, ensure you:
  1. Set the appropriate $regime field based on the issuer’s country (e.g., NO for Norway, FI for Finland)
  2. Add the eu-en16931-v2017 addon to enable validations and extensions needed for Peppol
Peppol B2B Invoice
{
    "$schema": "https://gobl.org/draft-0/bill/invoice",
    "$regime": "ES",
    "type": "standard",
    "series": "INV",
    "code": "PP000003",
    "issue_date": "2025-04-03",
    "currency": "EUR",
    "tax": {
        "rounding": "currency"
    },
    "supplier": {
        "uuid": "0195f6ab-1292-7000-9ecb-84732e730ddf",
        "name": "Cyberdyne Systems Spain S.L.",
        "tax_id": {
            "country": "ES",
            "code": "B98602642"
        },
        "addresses": [
            {
                "street": "Paseo de la Castellana 120",
                "locality": "Madrid",
                "region": "Madrid",
                "code": "28020",
                "country": "ES"
            }
        ],
        "emails": [
            {
                "addr": "billing@cyberdynesys.com"
            }
        ]
    },
    "customer": {
        "name": "Invopop S.L.",
        "tax_id": {
            "country": "ES",
            "code": "B85905495"
        },
        "addresses": [
            {
                "street": "Calle Pradillo 42",
                "locality": "Madrid",
                "region": "Madrid",
                "code": "28002",
                "country": "ES"
            }
        ],
        "emails": [
            {
                "addr": "billing+test@invopop.com"
            }
        ]
    },
    "lines": [
        {
            "i": 1,
            "quantity": "12",
            "item": {
                "name": "Sambox services",
                "price": "145.00",
                "unit": "one"
            },
            "sum": "1740.00",
            "taxes": [
                {
                    "cat": "VAT",
                    "percent": "21.0%",
                    "ext": {
                        "untdid-tax-category": "S"
                    }
                }
            ],
            "total": "1740.00"
        }
    ]
}

​
Receiving invoices

Invopop automatically processes invoices received from the Peppol network using your configured Incoming Workflow. The workflow converts Peppol documents to GOBL format and creates Silo Entries for each invoice. Configure your workflow with webhooks or Google Drive integration to deliver these invoices to your systems.

​
FAQ

Please contact the Invopop support team if you have any questions that are not listed here.
The visibility of your Peppol Party determines what documents you can send and receive.
  • smp: Only SMP, should be used for testing
  • smp+sml: SMP and SML, useful when you want to send documents but not receive them
  • smp+sml+peppol: SMP, SML, and Peppol Directory, recommended for both sending and receiving documents as you will be visible in the Peppol Directory
In general, you should use the highest visibility available.
You can disable Peppol for a Party by running a workflow with the Register Peppol Party step and setting the Status to Disabled.
⌘I