Skip to content
Convert · Validate · Send & receive on Peppol — EN 16931 · Peppol BIS 3.0 · XRechnung · EHF · Factur-X · FatturaPA · KSeF FA(3) · PINT · ZATCA

Convert, validate and deliver compliant e-invoices

MyInvoice is the e-invoicing infrastructure for developers and ERPs. Push CSV, Excel, UBL, EDIFACT, ZUGFeRD / Factur-X or your legacy XML and get back a fully validated EN 16931 document — Peppol BIS 3.0, XRechnung 3.0, Norway's EHF, Factur-X / ZUGFeRD, plain UBL 2.1, Italy's FatturaPA, Poland's KSeF FA(3), Saudi Arabia's ZATCA or Austria's ebInterface. Then send it over the Peppol network and receive inbound documents from the same API: delivery runs through our white-label partner, a certified Peppol access point, so you never have to become one.

Convert · Validate · Send & receive on Peppol · Delivery status and webhooks included

33
Countries in Europe
+14
International markets
47
Countries in total
100%
EN 16931 validated
Inputs we readOutputs we produceCSVExcelUBL 2.1CII · PDFEDIFACTLegacy XMLPeppol BIS 3.0XRechnungFactur-XFatturaPAKSeF FA(3)EHF · PINTMyInvoiceEN 16931validated

One API, 47 countries

Compliant e-invoicing across every EU member state and the wider European Peppol network — plus the major economies beyond it. Pick your market; the format, validation and delivery are already handled.

  • Austria — Peppol, Available now
  • Belgium — Peppol, Available now
  • Bulgaria — Peppol, Available now
  • Croatia — eRačun (HR CIUS), Available now
  • Cyprus — Peppol, Available now
  • Czechia — Peppol, Available now
  • Denmark — Peppol, Available now
  • Estonia — Peppol, Available now
  • Finland — Peppol, Available now
  • France — Factur-X, In progress
  • Germany — Peppol, Available now
  • Greece — myDATA, Planned
  • Hungary — Peppol, Available now
  • Iceland — Peppol, Available now
  • Ireland — Peppol, Available now
  • Italy — FatturaPA, Planned
  • Latvia — Peppol, Available now
  • Liechtenstein — Peppol, Available now
  • Lithuania — Peppol, Available now
  • Luxembourg — Peppol, Available now
  • Malta — Peppol, Available now
  • Netherlands — Peppol, Available now
  • North Macedonia — UJP e-Faktura, Conversion only
  • Norway — EHF (Peppol), Available now
  • Poland — KSeF FA(3), In progress
  • Portugal — Peppol, Available now
  • Romania — RO CIUS (e-Factura), Available now
  • Slovakia — Peppol, Available now
  • Slovenia — Peppol, Available now
  • Spain — Peppol, Planned
  • Sweden — Peppol, Available now
  • Switzerland — Peppol, Available now
  • United Kingdom — Peppol, Available now
Available now In progress Planned Conversion only

Features

The whole e-invoicing stack, not just a converter

Conversion, validation, delivery and tracking behind one API key — so you ship compliance instead of assembling it from four vendors.

Universal invoice conversion

Map CSV, Excel, UBL 2.1, EDIFACT D.96A or proprietary XML into a single canonical model, then serialise it in the format of the country you choose — Italy gives FatturaPA, Croatia eRačun, Germany Peppol.

Validation built in

Every document is checked against XSD (structure) and Schematron (EN 16931 + Peppol business rules) before it ever leaves the API.

Peppol delivery — we send it

One POST transmits invoices, orders, order responses, despatch advice, catalogues and responses over the Peppol network. Delivery runs on our white-label partner, a certified Peppol access point — you need one API key, not an AP contract.

Peppol inbound — we receive it

Documents addressed to you arrive on the network, are stored against your account with the original UBL, parsed into a readable summary, and can be accepted or rejected with a response back to the sender.

Delivery status & webhooks

Every transmission carries a normalised lifecycle — draft, pending, sent, failed, received — with a delivery timeline you can poll and webhook events pushed to your endpoint.

Batch & multi-file

Convert one CSV with hundreds of invoices into a ZIP, or upload up to 20 mixed files at once and receive a per-file summary.

Exact money maths

All monetary arithmetic uses arbitrary-precision decimals — never floating point. Totals and VAT are always recomputed from the lines.

Ready-made ERP connectors

Push native payloads from SAP, Dynamics 365 Business Central, Dynamics 365 F&O, Infor or any standard export — no mapping project required.

Developer-first API

Predictable REST, stable machine-readable error codes, request IDs and clear validation feedback. Integrate in an afternoon.

France 2026: lifecycle & e-reporting

Factur-X PDF/A-3 straight from the API, plus the French CTC layer: invoice lifecycle statuses, payments and e-reporting (B2C and international) exported as official flux 10 XML for your Plateforme Agréée.

Diagnostics that say where to fix it

A refused document comes back with the cause, where the fix belongs — master data, the document or your mapping — and the source field: SAP IDoc segment, CSV column, Business Central / F&O field or UBL path. In English, German or Croatian.

Partner program for ERP houses & resellers

Run e-invoicing and Peppol for your own clients under your brand: a partner console and REST API to create client accounts, Peppol registrations and keys, with signed webhooks for every document event.

Formats

Speak every format

Bring the data you already have. Get the compliant document you need. No re-platforming, no rip-and-replace.

Inputs we read

  • CSVOne or many invoices in a simple spreadsheet layout.
  • Excel (.xlsx / .xls)The same schema as CSV, straight from your workbook.
  • UBL 2.1Existing UBL Invoice or CreditNote XML, re-profiled and validated.
  • CII / ZUGFeRD / Factur-XUN/CEFACT CII XML — or a ZUGFeRD / Factur-X PDF, with its embedded XML extracted automatically.
  • EDIFACT D.96A INVOICClassic EDI invoices mapped to the modern standard.
  • National e-invoice XMLFatturaPA, Facturae (Spain), KSeF FA(3), myDATA and e-SLOG read directly — e.g. to re-profile into Peppol BIS 3.0.
  • Legacy / proprietary XMLAny custom XML via a JSON field mapping.

Outputs we produce

  • Peppol BIS 3.0UBL 2.1 ready for the Peppol network (Belgium, Slovakia & more).
  • XRechnung 3.0German B2G compliant UBL 2.1.
  • EHF Billing 3.0 (Norway)Peppol BIS-conformant Norwegian billing format.
  • Factur-X / ZUGFeRDEN 16931 CII XML — or the finished Factur-X PDF/A-3 with the XML embedded, on our neutral layout or your own PDF.
  • Plain UBL 2.1Clean EN 16931 UBL without network-specific rules.
  • FatturaPA (Italy)FatturaElettronica v1.2 for SdI — beta, XSD-valid XML.
  • KSeF FA(3) (Poland)Official MF FA(3) structured invoice — beta, XSD-valid XML.
  • PINT OM (Oman)Peppol International UBL for Oman — validated by the official OM Schematron (billing + self-billing).
  • PINT AE (UAE)Peppol International UBL for UAE — validated by the official AE Schematron (billing + self-billing).
  • PINT SG (Singapore)Peppol International UBL for Singapore (GST) + legacy SG BIS Billing 3.0 — validated by the official SG Schematron.
  • PINT MY (Malaysia)Peppol International UBL for Malaysia — validated by the official MY Schematron (billing + self-billing).
  • myDATA (Greece)Greek myDATA / AADE bespoke XML (AadeBookInvoiceType) — XSD-validated and ready to submit; transmission to AADE is not included.
  • CIUS-RO (Romania)Romanian CIUS-RO (RO e-Factura) UBL 2.1 — EN 16931 CIUS validated by the ANAF Schematron.
  • CIUS-PT (Portugal)Portuguese CIUS-PT (FE-AP) UBL 2.1 — EN 16931 CIUS validated by the eSPap Schematron.
  • HR-CIUS (Croatia)Croatian HR-CIUS (eRačun) UBL 2.1 — EN 16931 CIUS with the Fiskalizacija 2.0 national extension; mandatory from 1 Jan 2026.
  • NLCIUS (Netherlands)Dutch NLCIUS (SI-UBL 2.0) UBL 2.1 — EN 16931 CIUS validated by the Peppol Authority Schematron.
  • PINT JP (Japan)Peppol International UBL for Japan (JCT) — billing, self-billing and non-tax-registered, validated by the official JP Schematron.
  • PINT A-NZ (Australia / New Zealand)Peppol International UBL for Australia & New Zealand (GST) — billing and self-billing, validated by the official A-NZ Schematron.
  • e-SLOG 2.0 (Slovenia)Slovenia's e-SLOG 2.0 — XML-serialised EDIFACT INVOIC, XSD-validated; the national format for the 2028 ZIERDED B2B mandate.
  • OIOUBL 2.1 (Denmark)Danish OIOUBL 2.1 — national UBL profile, validated by the official OIOUBL Schematron; phased out by mid-2029.
  • ZATCA / FATOORA (Saudi Arabia)Saudi UBL 2.1 — Standard + Simplified, ICV/PIH chain and QR; XSD-validated. Document only — cryptographic stamp and FATOORA clearance not included.
  • ebInterface 6.1 (Austria)Austrian proprietary XML (not UBL/CII) — generic B2B and federal-government (Bund) modes, validated by the official XSD.
  • UBL-TR / e-Fatura (Turkey)Turkish GİB e-Fatura — UBL 2.1 customization TR1.2, scenario-aware (Temel / Ticari / İhracat), XSD-validated.
  • UJP e-Faktura (North Macedonia)North Macedonia UJP clearance JSON — beta, pending the official UJP specification; voluntary from 1 Oct 2026, mandatory from 1 Apr 2027.

Work the way that fits your workflow

Four channels, one compliant result.

REST API

The core endpoint: upload a file, pass the country whose format you need, receive validated XML — with rich response headers and request tracing.

Batch & multi-file

High-volume conversion to a ZIP archive with a machine-readable summary of every success and failure.

Email gateway

Send your invoices as email attachments with your key in the subject line and get the compliant XML back by email.

Peppol network

Skip the download: transmit the document to the receiver over Peppol and take delivery of inbound documents — send and receive through our certified access-point partner.

ERP connectors

Plug straight into your ERP

Your ERP or middleware pushes its native invoice payload with an API key — MyInvoice maps it, recomputes the totals and returns a compliant document. We never store your ERP credentials.

IDoc INVOIC02

SAP

Post the classic INVOIC01/02 IDoc as XML; partners are resolved by their PARVW role.

JSON

SAP Business One

Service Layer / DI API invoice JSON — supply the issuing company (seller) and we map documents, partners and lines.

JSON

Dynamics 365 Business Central

Map a Business Central sales invoice straight from a Power Automate flow or export.

JSON

Dynamics 365 Finance & Operations

Electronic Reporting / data-entity JSON with legal entity as seller and invoice customer as buyer.

OAGIS BOD

Infor

OAGIS Invoice Business Object Documents via ION — one BOD can carry several invoices.

Any export

Generic

Already have UBL, CSV, Excel, EDIFACT or legacy XML? Send { format, content } and you are done.

Need another system? The connector framework is built to extend — new ERPs are just a new mapping.

E-procurement

Not just invoices — the whole procurement flow

Generate the full set of Peppol procurement and response documents your trading partners expect.

T01

Order

The buyer's order to the supplier, as Peppol BIS 3.0 UBL.

T76

Order Response

Supplier acceptance, rejection or change of an order.

T16

Despatch Advice

A shipment notification covering what is being delivered.

T19

Catalogue

A product catalogue you publish to buyers, as Peppol BIS UBL.

T77

PunchOut

A shopping-cart catalogue returned to the buyer's procurement system.

T58

Catalogue Response

The buyer's acceptance or rejection of a published catalogue.

T71

Message Level Response (MLR)

Acknowledges receipt and technical processing of a Peppol message.

T111

Invoice Response

Communicates invoice status: accepted, under query, paid or rejected.

How it works

From raw data to a delivered document in four steps

You handle the business. We handle the standard — and the network.

  1. 1

    Send your data

    Upload a file via the API, push from your ERP, or email an attachment — whatever fits.

  2. 2

    We normalise it

    Your input is mapped into one canonical model; totals and VAT are recomputed from the lines for accuracy.

  3. 3

    We serialise & validate

    We produce the format of the country you chose and run XSD + Schematron checks against EN 16931, Peppol and the national rules.

  4. 4

    We deliver it

    Take the XML or a finished Factur-X PDF back — or have us transmit it over Peppol through our certified access-point partner, with delivery status and webhooks. Inbound documents land in your account the same way.

Secure and correct by design

Compliance you can trust starts with engineering you can trust.

API-key authentication

Every request is authenticated and rate-limited, with per-key usage tiers and quota enforcement.

Hardened XML parsing

XML is parsed with an XXE-safe configuration — external entities and network access are disabled.

Fail-closed validation

If a document does not pass the rules, it is rejected with a clear, machine-readable reason — never silently passed.

Stateless conversion

A conversion is processed in memory, returned in the response and then deleted — never persisted. We keep only an aggregate document count for quota, never the content, and never your ERP credentials. One exception: when a document is refused, the diagnosis log keeps its cause, the partner or item name and the invoice number for 90 days, so you can see problems that keep coming back. You can switch it off in Settings, which deletes what was stored.

Signed, certified transport

Peppol delivery goes over AS4 through a certified access point, which signs and seals the transport layer as the network requires. We are not that access point ourselves — our white-label partner is, and it is certified for exactly this.

Delivery data stays yours

What you send over Peppol and what arrives for you is archived in your account in the EU — the audit trail an exchange needs. Every status and inbound read is ownership-checked, so no key can see another account's documents.

Pricing

Simple, usage-based pricing

Pay per document you send over Peppol, plus a flat monthly fee per country you activate — each country is one format. Receiving, converting and validating have no per-document charge. Packages upgrade automatically as you grow.

€0.25
starting price per document
€0.095
per document at 20,000 docs
€150
country compliance fee / month
Custom
above 20,000 documents / month

FAQ

Frequently asked questions

Everything you need to know about e-invoicing with MyInvoice.

What is EN 16931?+

EN 16931 is the European standard that defines the semantic data model of an electronic invoice. Every format MyInvoice produces — Peppol BIS 3.0, XRechnung, Factur-X and plain UBL — is built on this core model, so your invoices are compliant across the EU.

Does MyInvoice store my invoices or see their contents?+

Conversion is stateless: your file is processed in memory to produce the output, returned in the API response, and not persisted afterwards — we keep only an aggregate count of processed documents per API key for your usage quota. Peppol delivery is different by necessity: a document you send over the network, and every document received for you, is archived against your account so you have the audit trail, the delivery history and an inbox to read. That is the only invoice content we hold, it is stored in the EU, and you can export or delete it yourself. We do not read, analyse, mine or share your invoice content, and all traffic is encrypted over HTTPS/TLS. One exception: when a document is refused, the diagnosis log keeps its cause, the partner or item name and the invoice number for 90 days, so you can see problems that keep coming back. You can switch it off in Settings, which deletes what was stored.

What is Peppol BIS 3.0?+

Peppol BIS Billing 3.0 is the specification used to exchange invoices over the Peppol network. MyInvoice outputs UBL 2.1 that conforms to Peppol BIS 3.0 and passes Peppol Schematron validation — and then transmits it for you over the network, so the compliant document and its delivery come from the same API.

Can you actually send the invoice, or do I get a file to deliver myself?+

We send it. POST /v1/send takes the document — invoice, order, order response, despatch advice, catalogue, punch-out, catalogue response, MLR or invoice response — validates it locally, hands it to the access point and dispatches it to the receiver you name. You can also stop at a draft, or look a receiver up in the SMP first to check they are reachable on Peppol at all. If you would rather deliver it yourself, /v1/convert still returns the plain XML.

Can I receive documents over Peppol, not just send them?+

Yes. Inbound documents addressed to you are captured with their original UBL, parsed into a readable summary and stored against your account, with unread counts and a full XML download. You can accept or reject a received invoice, which sends the response back to the sender. You read everything from our API — you never have to poll the network yourself.

How do I know a document was actually delivered?+

Every transmission has a normalised state — draft, pending, sent, failed or received — plus a delivery timeline. Poll GET /v1/peppol/status/:id, or register a webhook and we push the lifecycle events to your endpoint as they happen. Rule failures come back as the rule ids you have to fix, not as an opaque error.

Do you digitally sign my invoices?+

For Peppol, the invoice itself is not signed — the AS4 transport layer is signed and sealed by the certified access point, which is exactly what the network requires and what our partner does on every send. For national formats that mandate a document-level signature (Italy's SdI .p7m, Saudi ZATCA's cryptographic stamp, Turkey's Mali Mühür), MyInvoice produces the compliant XML with the signature slot left in place; the managed signing service is on the roadmap, so today you apply your own certificate or your local provider's. We would rather tell you that up front than have you discover it in production.

What is XRechnung and do I need it?+

XRechnung is the mandatory invoice format for billing public-sector buyers in Germany (B2G). If you invoice German authorities, MyInvoice produces XRechnung 3.0 compliant documents directly.

What is the difference between Factur-X and ZUGFeRD?+

They are effectively the same hybrid standard: a human-readable PDF/A-3 with embedded EN 16931 CII XML. MyInvoice produces both halves — the CII XML on its own, or the finished Factur-X PDF with the XML embedded (output=pdf), rendered on a neutral layout or on your own PDF.

Can you read an incoming ZUGFeRD or Factur-X invoice?+

Yes. Beyond producing them, MyInvoice reads UN/CEFACT CII XML and automatically extracts the embedded XML from a ZUGFeRD / Factur-X PDF — so you can turn an incoming hybrid invoice straight into Peppol BIS 3.0, XRechnung or any other supported output.

Do you support Peppol Logistics?+

Yes — MyInvoice implements Peppol Logistics 1.3 (2026-Q2): the post-award transport and delivery documents. Send JSON and get validated UBL for advanced despatch advice, receipt advice, transport execution plan (and request), waybill, transportation status (and request) and weight statement (T120–T129). Every document is checked against the UBL XSD and the Peppol Logistics Schematron before it leaves the API.

Are you ready for France's 2026 reform?+

Yes, for formats and data. We produce Factur-X (as XML or a finished PDF), UBL and CII with the French domestic rules (SIREN, cadre de facturation, BT-8), track the invoice lifecycle statuses (déposée, rejetée, refusée, encaissée) and payments, and build the e-reporting flux 10 for B2C and international transactions, validated against the official DGFiP XSD. Transmission through a Plateforme Agréée is not part of the service: the period export hands the official XML to the PA you work with. Lifecycle and e-reporting are add-on modules enabled per account.

When a document is refused, how do I know what to fix?+

Every response with findings carries diagnostics: the cause in plain language, where the fix belongs (master data, the document, your mapping, routing or our platform) and, where we can prove it, the exact source field — the SAP IDoc segment and partner role, the CSV column, the Business Central or F&O field, or the UBL XPath. Texts come in English, German and Croatian. The diagnosis is deterministic — a rule knowledge base, no AI guessing.

Can I offer e-invoicing to my own clients?+

Yes. ERP houses, accounting firms and resellers join our partner program: each of your clients gets its own account, Peppol registration and API key, and you manage them from a partner console or the Partner REST API, with signed webhooks for every document event. You sell under your own brand; we bill you wholesale. Talk to us to get set up.

Do you support Italy's FatturaPA?+

Yes — MyInvoice maps your invoice to FatturaElettronica v1.2 (the SdI format) and returns XSD-valid XML. It is currently in beta: it generates the XML, while the SdI digital signature (.p7m) and transmission to the Sistema di Interscambio are on the roadmap. You can try the FatturaPA output today in the sandbox.

Can I try it without signing up?+

Yes. The in-browser sandbox converts a sample or your own file right on this site: pick the country whose format you need — Germany, France, Italy, Croatia and more — and you get that country's format back (Italy → FatturaPA, Croatia → eRačun). No account required (fair-use limited).

Which ERP systems do you support?+

Out of the box we ship connectors for SAP (IDoc INVOIC02), SAP Business One (Service Layer JSON), Microsoft Dynamics 365 Business Central, Dynamics 365 Finance & Operations, and Infor (OAGIS BOD). A generic connector also accepts any standard export, and new connectors are easy to add.

Do you store my data or ERP credentials?+

No. ERP integrations use a push model — your systems send us a payload authenticated with an API key. We process the document and return it; we do not store your credentials or call back into your ERP.

Can I convert invoices in bulk?+

Yes. Send a single CSV containing many invoices and receive a ZIP, or upload up to 20 mixed-format files at once. Each response includes a per-document summary of successes and failures.

How accurate are the calculations?+

All monetary maths uses arbitrary-precision decimals rather than floating point, and totals plus the VAT breakdown are always recomputed from the line items — values supplied in the source are never blindly trusted.

How do I get started?+

Contact us for an API key and tell us which countries' formats you need — you buy countries, each one is one format, at €150 per country per month. Point your existing data at the conversion endpoint, name the country, and you are live. Peppol send and receive is switched on per account and we set up the network side. Most teams integrate in a single afternoon.

Go live on Peppol without becoming an access point

Stop stitching together a converter, a validator and a delivery provider. Convert, validate, send and receive through one API and one key — the network hop runs on our certified access-point partner.