Peppol E-Invoice Export

⚡ Built-in — Platform Built-in

Export an invoice or credit note made with Invoice Generator as a Peppol BIS Billing 3.0 (UBL) XML file for e-invoicing. The file always matches your stored invoice exactly; if it cannot, the export explains why instead of producing a wrong file. Export only — sending over the Peppol network needs a Peppol access point.

⚡ Built-in — No Setup Required This integration is built into the WebsitePublisher platform. All endpoints are available immediately — no API key needed.

Endpoints (3)

POST set-seller

Set your own company details for Peppol, once per project. Only send what changes. endpoint_scheme + endpoint_id is your Peppol address, e.g. "0106" + your 8-digit KvK number (NL), "9944" + your NL VAT number, "0208" + your 10-digit enterprise number (BE). vat_id is required for exports (with country prefix, e.g. NL123456789B01). iban is used for the payment instructions on invoices.

Field	Type	Required	Description
`legal_name`	string	No	Registered company name. Required the first time.
`trading_name`	string	No
`endpoint_scheme`	string	No	4-digit Peppol scheme code. Required the first time.
`endpoint_id`	string	No	Required the first time.
`vat_id`	string	No
`company_id`	string	No	Chamber of commerce / company registration number.
`street`	string	No
`city`	string	No
`postal_code`	string	No
`country_code`	string	No	ISO country code, e.g. "NL". Required the first time.
`iban`	string	No
`bic`	string	No
`contact_email`	string	No
`contact_phone`	string	No

GET get-seller

Your stored Peppol company details, or a hint if they are not set yet.

No input parameters required.

POST export-invoice

Export one invoice or credit note from Invoice Generator as Peppol BIS Billing 3.0 XML. Returns {xml, filename, totals, checks_passed, warnings}. You need the buyer's Peppol address (ask the buyer, or look it up in the Peppol directory) and country. For 0% VAT invoices also send vat_category ("Z", "E", "AE" or "G") and, except for Z, an exemption_reason. Government and many business buyers require their own buyer_reference (purchase order or reference code). The export refuses — with the reason — when the XML could not match the stored invoice exactly (e.g. shipping costs without VAT). Check the first exported file with a Peppol validator before sending.

Field	Type	Required	Description
`invoice_id`	integer	No	Invoice id from Invoice Generator (or send invoice_number).
`invoice_number`	string	No
`buyer`	object	✓ Yes	{"endpoint_scheme":"0106","endpoint_id":"12345678","country_code":"NL","legal_name":"...","vat_id":"NL...B01","street":"...","city":"...","postal_code":"..."}. legal_name and vat_id default to the invoice customer.
`buyer_reference`	string	No
`vat_category`	string	No	Only for 0% VAT invoices: "Z", "E", "AE" or "G".
`exemption_reason`	string	No	Required for E, AE and G, e.g. "Reverse charge".

MCP Tool Names

When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:

Endpoint	MCP Tool Name
set-seller	`peppol-export_set_seller`
get-seller	`peppol-export_get_seller`
export-invoice	`peppol-export_export_invoice`

← Back to all integrations