InvoiceXML
Let agents create, validate, convert, render, and extract EN 16931–compliant e-invoices across UBL, CII, Factur-X, ZUGFeRD, and XRechnung for EU B2B products.
Overview
InvoiceXML is an MCP server for the Build phase that lets agents create, validate, convert, render, and extract EN 16931–compliant e-invoices across major European formats.
What is this MCP server?
- Formats: UBL (Peppol BIS Billing 3.0), CII, Factur-X, ZUGFeRD, and XRechnung
- EN 16931 validation on create, convert, render, and extract paths
- Hosted remote with OAuth 2.1; processing described as stateless with no invoice retention
- Publisher tags span e-invoicing, compliance, peppol, and en16931
- Documentation at invoicexml.com/docs and marketing site at invoicexml.com/mcp-server
- Five named format families: UBL, CII, Factur-X, ZUGFeRD, XRechnung
- Peppol profile called out: BIS Billing 3.0
- Auth model: OAuth 2.1 on hosted MCP
Community signal: 2 GitHub stars.
What problem does it solve?
Shipping EU B2B billing without EN 16931-aware validation forces you to maintain fragile UBL, Factur-X, and XRechnung converters by hand.
Who is it for?
Indie SaaS and marketplace founders targeting German, French, or Peppol B2B invoicing with agent-assisted backend integration.
Skip if: US-only simple PDF invoices with no e-invoicing mandate, or teams that cannot use hosted OAuth remotes.
What do I get? / Deliverables
After OAuth registration, your agent can produce and check compliant e-invoices and conversions so you integrate billing faster with fewer format regressions.
- Validated EN 16931 e-invoice XML and hybrid outputs from agent workflows
- Conversion paths between UBL, CII, Factur-X, ZUGFeRD, and XRechnung
- Extracted structured invoice fields for AP or billing automation code
Recommended MCP Servers
Journey fit
Canonical shelf is build/integrations because the server is invoked when wiring compliant invoicing into backends, billing flows, and agent-operated document pipelines. Integrations subphase reflects OAuth-hosted MCP tools that replace bespoke Peppol, XRechnung, and Factur-X plumbing in your codebase.
How it compares
Compliance-focused e-invoicing MCP, not a spreadsheet macro skill or raw payment-processor SDK.
Common Questions / FAQ
Who is InvoiceXML MCP for?
Solo builders and small teams building B2B billing, ERP connectors, or AP automation who need Peppol, XRechnung, Factur-X, and UBL compliance via agents.
When should I use InvoiceXML MCP?
Use it during build integrations when you generate, validate, or convert electronic invoices and during ship security review when you document compliance controls.
How do I add InvoiceXML MCP to my agent?
Configure the hosted MCP remote from invoicexml.com/mcp-server in your client, complete OAuth 2.1 authorization, and follow invoicexml.com/docs for tool names and flows.