Automation Features Blog Pricing Contact

Create a UBL Invoice API

Test the UBL 2.1 REST API, submit your invoice details and download a validated Peppol BIS Billing 3.0 XML. No code required.

Have an existing invoice? Upload a PDF and we'll prefill the form
Invoice Details
Seller (From)
Buyer (To)

Invoice Automation Wherever You Work

Built for developers and AI-driven workflows. Make your invoices compliant on your ERP or AI Agent via our secure MCP server and REST API.

REST API

Full-featured API for developers. Integrate invoice conversion into any stack.

No-Code Platforms

Connect via NoCode platforms like Zapier, Make and n8n, no engineering required.

MCP for AI Agents

Let your AI agents validate and convert invoices autonomously via our MCP server.

For Developers
Developer API

Built for Developers

Submit invoice data as form fields, receive a validated Peppol BIS Billing 3.0 UBL 2.1 XML. Built for ultra-high concurrency and sub-second generation.

  • Supports all formats: DOCX, XLSX, PDF, images, no preprocessing needed
  • Works on scanned and photographed invoices
  • Every response validated against official Schematron rules

Supports ZUGFeRD · Factur-X · XRechnung · UBL · CII · EN 16931

API Documentation
Terminal 
$ curl -X POST https://api.invoicexml.com/v1/create/ubl \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: multipart/form-data" \
  -F "InvoiceNumber=INV-2025-001" \
  -F "IssueDate=2025-07-01" \
  -F "SellerName=Acme GmbH" \
  -F "BuyerName=ACME Corp"
// => 200 OK
// => { "id": "inv_8f3k...", "status": "completed" }

Beyond the Form: Automate Your Peppol UBL Workflow

This form is perfect for one-off invoices. But if you send dozens or hundreds of invoices over the Peppol network, InvoiceXML gives you the tools to automate the full pipeline, from structured data to Peppol-ready UBL 2.1 XML, with zero manual steps.

1. Developer-First REST API

Integrate Peppol UBL generation directly into your ERP, billing system, or custom application with a single HTTP call:

  • • Single Endpoint: POST your invoice fields as JSON and receive a validated UBL 2.1 XML back instantly, ready for any Peppol access point.
  • • Stateless & Secure: We process your data in memory and return the XML. No financial data is stored or logged.
  • • Full Compliance: Every generated XML passes EN 16931 Schematron rules and Peppol BIS Billing 3.0 constraints before delivery, the exact validation a Peppol access point runs on receipt.
  • • Global Reach: The same endpoint serves Norway, Denmark, Sweden, Singapore, Australia, New Zealand, and every other Peppol corner, one spec, one API call.

Pro Tip: Check out our API Documentation to see the full request schema and response format.

2. Email Gateway, Send JSON, Receive Peppol UBL

The InvoiceXML Email Gateway is the simplest integration imaginable, no API keys in your code, no webhook setup:

  • • How it works: Email a JSON attachment containing your invoice data to your dedicated InvoiceXML gateway address. We generate the UBL 2.1 XML and email it back, validated and Peppol-ready.
  • • Zero Setup: Any system that can send an email can trigger UBL generation, legacy ERPs, accounting software, or even a simple script.
  • • Batch Support: Send multiple invoice objects in a single JSON array and receive all corresponding UBL XML files in return.

3. No-Code Automation (Zapier, Make.com & n8n)

Connect InvoiceXML to the tools your team already uses, no developer required:

  • • ERP & Accounting: Trigger UBL generation automatically whenever a new invoice is approved in your system, no manual export step.
  • • Google Sheets / Airtable: Turn a row of invoice data into a Peppol-ready UBL 2.1 XML and route it straight to your Peppol access point.
  • • End-to-End Peppol: Combine UBL generation with a Peppol access point connector in the same workflow to fully automate B2G invoice delivery.

Why Peppol UBL Is the Global Standard for E-Invoicing

The Peppol network connects over 400,000 businesses and government entities worldwide. Peppol BIS Billing 3.0, built on UBL 2.1 and EN 16931, is the mandatory invoice format for public procurement in Norway, Denmark, Sweden, Finland, Singapore, Australia, and New Zealand, with rapid B2B expansion underway in the Netherlands, Belgium, and Italy. A single UBL 2.1 document, generated once, can reach any of them.

FeatureOur UBL Implementation
StandardEN 16931 + Peppol BIS Billing 3.0
Output FormatStandalone UBL 2.1 XML
SyntaxOASIS Universal Business Language 2.1
Submission ChannelsAny Peppol-certified access point globally
ValidationEN 16931 Schematron + Peppol BIS 3.0 rules

Complete UBL Toolkit

Everything you need to create, convert, validate, and preview UBL invoices, via REST API or online.

Create UBL API

Build a validated UBL 2.1 XML from structured data, Peppol BIS Billing 3.0 compliant.

Try it out

Validate UBL API

Validate UBL XML against EN 16931 and Peppol BIS Billing 3.0 Schematron rules.

Try it out

PDF to UBL API

Convert any PDF invoice into a Peppol-compliant UBL 2.1 XML using AI extraction.

Try it out

Preview UBL as PDF API

Render a UBL XML as a human-readable PDF for review and approval.

Try it out

Frequently Asked Questions

No. We process your invoice data in memory and discard it immediately after the XML is generated and downloaded. Nothing is persisted.
Yes. The output is a fully validated UBL 2.1 XML conforming to Peppol BIS Billing 3.0 and EN 16931. You can submit it to any Peppol-certified access point globally, in Norway, Denmark, Singapore, Australia, and beyond.
Both are valid EN 16931 syntaxes. UBL 2.1 is the native format of the Peppol network (Peppol BIS Billing 3.0), use it when your recipient or delivery channel is Peppol-based. CII is used by ZUGFeRD and Factur-X hybrid PDFs, which are more common in Germany and France.
Peppol BIS Billing 3.0 is mandatory for B2G invoicing in Norway, Denmark, Sweden, Finland, Singapore, Australia, and New Zealand. The Netherlands, Belgium, and Italy are actively extending Peppol to B2B transactions. The EU's ViDA directive will further expand mandatory electronic invoicing across all member states by 2028.
Yes. The InvoiceXML Email Gateway lets any system that can send email trigger UBL generation. Email a JSON attachment to your dedicated gateway address and receive the validated UBL 2.1 XML in reply, no API integration required.

Ready to automate your invoices?

Start your 30-day free trial. No credit card required.

Get Started For Free