Peppol E-Invoicing
AccountingSend and receive compliant e-invoices over the Peppol network through your certified Access Point provider. Agents transmit invoices and credit notes, track delivery status, poll the inbox for incoming documents, and validate trading partners' Peppol IDs before sending.
What This Integration Enables
E-invoicing mandates are spreading country by country, and they share one design: invoices become structured legal documents exchanged over a governed network, not PDFs attached to email. Peppol is that network for much of Europe and beyond. This connector is a provider-agnostic gateway to it: you configure your certified Access Point provider's URL and token, and FlowRunner agents send invoices and credit notes, track transmission timelines, poll the inbox, and resolve trading partners' Peppol IDs before anything is sent. The workflow view of compliance is the honest one: a mandate is not a document format problem, it is a process problem. The format is handled by the Access Point validating against Peppol BIS 3.0. What remains, recipient verification, delivery confirmation, inbox processing, exception handling, is orchestration, and that is the part agents do: - Every send is preceded by a participant check, so invoices are never fired at unreachable IDs - Structured JSON or ERP-exported UBL XML both transmit, so the accounting system does not need to change - Transmission status is polled to a terminal state and recorded, turning delivery into evidence - Inbound invoices flow from the Peppol inbox into AP with the raw UBL archived for audit - The Peppol Directory is searchable when all you have is a company name Invoices are legal instruments with tax consequences, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) layer holds the line where automation should not sign alone.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The invoice that proves it arrived
An invoice finalizes in [QuickBooks Online](/integrations/quickbooks). The agent maps the invoice data to the structured payload, runs Validate Peppol ID on the buyer, and calls Send Invoice. Get Transmission Status polls until the timeline shows delivered, and the state history is written back to the invoice record. When a customer later claims they never received it, finance answers with the network's own delivery record instead of a screenshot of an email's sent folder.
The Peppol inbox that files itself into AP
On a schedule, the agent polls List Received Documents for new inbound invoices. Each one is parsed via Get Document, sender, totals, line items, and created as a payable in [Xero](/integrations/xero), while Get Document UBL archives the exact XML that crossed the network into document storage. Duplicates are caught by document ID before posting. Supplier invoices stop arriving as attachments to be retyped; they arrive as data, already filed, with the legal original preserved.
Onboarding a trading partner without an email thread
A new EU customer signs. The agent runs Search Participants against the Peppol Directory by company name and country, confirms the match with Look Up Participant, and records the participant ID and supported document types on the customer record. First invoice out, the workflow already knows the counterparty is reachable and what it accepts. The alternative, emailing the customer's AP department to ask for their e-invoicing details, is the kind of latency this network was built to eliminate.
Human-in-Loop Highlight
Send Invoice transmits a legal tax document into the recipient's accounts payable system, and Peppol has no unsend: a wrong amount, wrong VAT treatment, or wrong counterparty is corrected only by issuing a formal credit note and reinvoicing, an error loop that is visible to your customer and your auditor alike. Credit notes themselves reduce receivables, which makes an automated credit note a machine writing off money. So FlowRunner gates both edges: invoices above a configured threshold, invoices where validation returned warnings, and every credit note are presented to the finance owner with the counterparty, totals, and triggering context before transmission. Routine invoices to validated participants flow autonomously, because the participant check and BIS 3.0 validation already caught the mechanical errors. What waits for a person is exactly what a person would be accountable for: the decision that this document, with these numbers, should become legally real.
Agent Capabilities
10 actionsSending
2- Send Invoice Creates and transmits a Peppol invoice or credit note over the network from structured JSON data. The Access Point provider validates the data against Peppol BIS 3.0, serializes it to UBL XML, discovers the receiver's Access Point via SMP, and delivers it over the secure AS4 channel. Sender and receiver are identified by Peppol participant IDs in scheme:value form (e.g. 0208:0123456789). Returns the created document with its ID and current state.
- Send UBL Document Transmits a pre-built Peppol document over the network from raw UBL/XML you already have (for example an invoice or credit note exported by your accounting system). The Access Point validates it against Peppol BIS 3.0, discovers the receiver via SMP and delivers it over AS4. Provide the UBL XML as a string. Returns the created document with its ID and state.
Documents
5- Get Transmission Status Retrieves the delivery/transmission status timeline for a document by its ID. Returns the ordered list of state changes (created, validated, in transit, delivered, failed) recorded by the Access Point, letting you confirm whether a sent invoice reached the recipient over the Peppol network.
- Get Document Retrieves the full details of a single document by its ID, including sender and receiver Peppol IDs, document type, current state, totals and line items as parsed by the Access Point. Use Get Document UBL if you need the raw XML instead.
- Get Document UBL Retrieves the raw UBL 2.1 / Peppol BIS 3.0 XML for a document by its ID. Useful for archiving, auditing, or forwarding the exact document that was exchanged over the network. Returns the XML as a string.
- List Received Documents Lists inbound documents received over the Peppol network (your inbox), newest first, with pagination and optional filtering by document type, sender Peppol ID, date range and free-text search. Use this to poll for incoming invoices and credit notes.
- List Sent Documents Lists outbound documents you have sent over the Peppol network (your outbox), newest first, with pagination and optional filtering by document type, receiver Peppol ID, date range and free-text search. Use this to review or reconcile transmitted invoices and credit notes.
Participants
3- Look Up Participant Looks up a Peppol participant by their participant ID (scheme:value, e.g. 0208:0123456789) directly against the network's SMP/SML discovery chain. Returns the business entity details, the Access Point endpoints serving that participant, and the document types they are registered to receive. Use this before sending to confirm a recipient is reachable on the network and accepts the document you intend to send.
- Validate Peppol ID Performs a lightweight check of whether a Peppol participant ID exists on the network and is able to receive documents. Returns a boolean-style result plus the supported document types, without the full endpoint/certificate detail returned by Look Up Participant. Ideal for quick recipient validation before sending.
- Search Participants Searches the Peppol Directory for participants by business name or identifier, optionally scoped to a country. Returns matching participants with their Peppol IDs and basic contact details. Use this to discover a recipient's Peppol ID when you only know their company name.
Frequently Asked Questions
What can FlowRunner do with Peppol E-Invoicing?
FlowRunner agents can run Send Invoice, Send UBL Document, and Get Transmission Status in Peppol E-Invoicing, plus 7 more actions.
Does connecting Peppol E-Invoicing to FlowRunner require OAuth?
No. Peppol E-Invoicing connects to FlowRunner with an API key, no OAuth flow required.
Can Peppol E-Invoicing trigger a FlowRunner workflow automatically?
Peppol E-Invoicing doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Peppol E-Invoicing
$100 in credits. No card required. Connect in minutes.