Black November: −35% on all modules until 30 November Black November: −35% until 30 November Choose a module

Get in touch
WooCommerce

E-Invoice EN 16931 for WooCommerce — ZUGFeRD, Factur-X, XRechnung and Peppol BIS (Belgium, Slovakia) from your orders

EN 16931 e-invoices straight from WooCommerce orders: ZUGFeRD / Factur-X (PDF/A-3 with embedded XML) and XRechnung 3.0 in CII and UBL. Buyer VAT ID and Leitweg-ID at checkout, VAT categories with exemption reasons, gap-free numbering. Everything is created in your shop, no external service. Pro — automatic issuing with e-mails, credit notes from refunds, invoices in the customer account and a ZIP for your accountant. Since 1.1.0 — the Slovak e-faktúra (Peppol BIS Billing 3.0) for B2B invoices from 2027. Since 1.2.0 — Belgium (Peppol BIS between companies) and France (Factur-X with the 2026 / 2027 reform data). Since 1.3.0 Pro connects ePošťák for Slovakia.

Download Free
Pro · one-year licence Staging copies are included. The more sites, the cheaper each one
Compatibility
WooCommerce 8.0+ · WordPress 6.2+ · PHP 7.4+ · HPOS · classic and block checkout · ZUGFeRD 2.5 / Factur-X 1.09 (EN 16931) · XRechnung 3.0 · Peppol BIS Billing 3.0 (e-faktúra SK, Belgium) · Factur-X with the reform data (France)
Licence
a site + a staging copy, annual
Trial
7 days, no card, one per site
Updated
November 2026
Or all 509 Pro modules with All Access — 3 244 UAH / year ≈ €66

What Free has,
and what Pro adds

The free version works with no time limit. Pro adds the rest of the features in the table.

Feature Free Pro
ZUGFeRD / Factur-X: PDF/A-3b with embedded factur-x.xml, EN 16931 profile ✔ ✔
XRechnung 3.0 in both syntaxes — CII and UBL ✔ ✔
Slovak e-faktúra (from 1.1.2027): Peppol BIS Billing 3.0 (UBL) for invoices and credit notes, DIČ as Peppol address 0245 ✔ ✔
Belgium (since 1.1.2026): Peppol BIS Billing 3.0 (UBL) for invoices and credit notes between Belgian companies, enterprise number as Peppol address 0208 with the mod-97 check ✔ ✔
France (reform 2026 / 2027): Factur-X with SIREN / SIRET, category of the operation (BT-23), VAT on debits and the PMD / PMT / AAB notes, checked against the BR-FR rules ✔ ✔
Issue an invoice with one button in the order: PDF, XML and XRechnung download from the order screen ✔ ✔
Buyer VAT ID (USt-IdNr.) and Leitweg-ID (buyer reference) on the classic and block checkout, with a format check ✔ ✔
IČO and DIČ of Slovak companies on both checkouts with a format check (and the fields of the "IČ DIČ" plugin) ✔ ✔
Company number (SIREN / SIRET, Belgian enterprise number) on both checkouts with a check ✔ ✔
VAT categories S / Z / E / AE / K / G / O set automatically: reverse charge for EU B2B, export, §19 UStG — with the reason text and VATEX code ✔ ✔
UN/ECE units per product, UNTDID 4461 payment means and "pays after the invoice" per payment method ✔ ✔
Gap-free numbering from your own pattern (RE-{YYYY}-{N:5}), a separate counter for credit notes ✔ ✔
Invoice language: German for DE/AT/CH/LI/LU, French for FR/MC, Dutch for NL, for BE by the site language, English for everyone else, or one for all ✔ ✔
Settings check against a real order and an unnumbered sample PDF ✔ ✔
Plugin languages: English, Deutsch, Français, Nederlands, Slovenčina (e-faktúra strings) ✔ ✔
The last day to issue an e-faktúra and a warning in the order box ✔ ✔
A ready ePošťák connection for Slovakia: test and production, connection and delivery checks — ✔
Automatic issuing by order status and the PDF in WooCommerce e-mails, XRechnung XML for orders with a Leitweg-ID — ✔
Credit notes (type 381) from refunds: line refunds and amount-only refunds, referencing the invoice — ✔
Invoices and credit notes in the customer's My account — ✔
ZIP for your accountant per period: PDF + XRechnung + Peppol XML (SK, BE) + CSV — ✔
VIES check of the VAT ID right at checkout — ✔
Shop logo on the PDF — ✔
Hand-over of the e-faktúra to the Slovak delivery service (HTTPS API): automatic or with a button, the service's answer in the order — ✔
Hand-over of Belgian Peppol invoices to your access point: automatic or with a button, the answer in the order — ✔
France: CSV for the e-reporting of consumer sales — totals per day, currency, kind of operation and VAT rate — ✔
Updates from catcode.com.ua in Dashboard → Updates — ✔

What it looks like

ZUGFeRD / Factur-X invoice from a WooCommerce order
Invoice RE-2026-00001 from the test shop: PDF/A-3b in German, Käuferreferenz (Leitweg-ID), buyer VAT ID, 19 % and 7 % VAT groups, payment terms with IBAN. Inside the PDF — factur-x.xml under EN 16931.
French Factur-X invoice with SIREN from a WooCommerce order
French Factur-X invoice with SIREN from a WooCommerce order (2)
French seller to a French company: invoice in French, seller SIREN, category of the operation, PMD / PMT / AAB notes. Inside the PDF: CII with the customer’s SIREN and SIRET, BT-23 and 0225 addresses.

Key points

Belgium: Peppol between companies since 1 January 2026

Since 1 January 2026 Belgian VAT payers invoice each other with structured electronic invoices only — Peppol BIS Billing 3.0, sent over the Peppol network.

France: e-invoicing reform 2026 / 2027

From 1 September 2026 every VAT payer in France has to receive e-invoices; large companies and ETI also issue them from that date, SMEs and micro-enterprises from 1 September 2027.

Works together with our other modules for Germany and the EU

E-Invoice EN 16931 was built alongside three other modules of ours, and they have been tested together in one shop:

The trial starts when you ask

A fresh install is the free version, nothing switches on by itself. The “Try Pro for 7 days” button → e-mail → the key right in the window and by e-mail.

One key — a site and a staging copy

Moving the site? Unlink the licence on the old domain and activate it on the new one yourself. A staging copy (staging., dev.) works with the same key and does not take a site slot. For studios — keys for 5 or 25 sites, or unlimited.

Technical requirements

  • WooCommerce 8.0+ with the classic or block checkout, compatible with HPOS and the legacy order storage
  • WordPress 6.2+ · PHP 7.4+ (the full run was on PHP 8.3)
  • Currency: one currency per document; BT-6 / BT-111 are not written, so the Slovak e-faktúra and French invoices are EUR only (an order of a French seller in another currency gets no invoice, with the reason in the order)
  • Invoice languages: English, German, French, Dutch (automatic by the customer’s country, for Belgium by the shop language). Interface: English, German, French, Dutch, Slovak for the e-faktúra strings.

Version history

v1.3.0 Current November 2026

Slovakia: tax point date from the earlier of the payment and delivery dates, IČO with scheme 0158, the last day to issue in the order box.

v1.2.0 October 2026

Belgium: Peppol BIS Billing 3.0 for invoices and credit notes between Belgian companies.

v1.1.0 October 2026

Slovak e-faktúra (mandatory from 1 January 2027).

All versions (4)Collapse
v1.0.0 First release September 2026

ZUGFeRD / Factur-X (PDF/A-3b, EN 16931) and XRechnung 3.0 in CII and UBL; VAT ID and Leitweg-ID on the classic and block checkout; VAT categories with exemption reasons and VATEX; UN/ECE…

Frequently bought with E-Invoice EN 16931

All Access Need more? All modules (509) under one licence, new ones are added automatically. 3 244 UAH≈ €66 Learn more →

Full module description

E-Invoice EN 16931 for WooCommerce turns every order into an electronic invoice under the European standard EN 16931: ZUGFeRD / Factur-X (a PDF/A-3 with the XML embedded) and XRechnung 3.0 in the CII and UBL syntaxes — formats that both people (PDF) and software (XML) can read. The plugin does it inside WooCommerce — no external service, no subscription, and no order data handed to third parties.

New in 1.3.0: Slovakia. A ready ePošťák connection in Pro: test or production, a connection and a delivery check. A buyer outside Peppol shows on the order. The tax point date of a Slovak seller follows the earlier of the payment and delivery dates, and the IČO goes with scheme 0158. The order box shows the last day to issue. Check how the rules apply with your accountant: the plugin is not tax advice.

Running OpenCart? There is a separate version for it — E-Invoice EN 16931 for OpenCart (4.x, 3.x and 2.3): ZUGFeRD / Factur-X, XRechnung 3.0, Peppol BIS for Slovakia and Belgium and the French reform data in Factur-X; the OpenCart licence is a one-time payment, forever.

New in 1.2.0 — Belgium and France. For invoices between Belgian companies (mandatory since 1 January 2026) the plugin creates Peppol BIS Billing 3.0 with the enterprise number as the Peppol address; for France, Factur-X with the data of the 2026 / 2027 reform: SIREN / SIRET, the category of the operation, the mandatory notes. The checkout gets a company number field with a check, and invoices also come in French and Dutch. Details are in the “Belgium” and “France” sections below.

Since 1.1.0 — the Slovak e-faktúra. From 1 January 2027 VAT payers in Slovakia issue their invoices to Slovak business customers as e-faktúra. For these orders the plugin creates a Peppol BIS Billing 3.0 (UBL) file and adds IČO and DIČ fields to the checkout; Pro hands the file over to your delivery service (doručovacia služba). Details are in the “Slovak e-faktúra” section below.

Testing of the Slovak part (1.1.0). e-faktúra invoices and credit notes from real orders — placed in a browser on the classic and the block checkout of WordPress 7.1 + WooCommerce 11.2, with a coupon discount, shipping and 23 % and 5 % rates — passed the UBL 2.1 schema, the CEN EN 16931 rules and the OpenPeppol BIS Billing 3.0 rules (locally and in the public Peppol Testbed validator, BIS 3.0.21); the document total equals the order total.

Belgian and French part (1.2.0). Orders were placed in the browser in the classic and block checkout of WordPress 7.1 + WooCommerce 11.2 — on desktop and on phones (375 and 320 px), with a coupon discount and shipping, with HPOS and the legacy order storage, on PHP 8.3 and 7.4. Belgian Peppol invoices and credit notes passed the UBL 2.1 schema, CEN EN 16931 and OpenPeppol BIS Billing 3.0.21; French ones Factur-X / EN 16931 (Mustang, veraPDF) and the French BR-FR rules (FNFE-MPE 1.4.0.04); every document total equals the order total. Updating from 1.0.0 and 1.1.0 keeps settings, licence, numbering and checkout fields; the XML of invoices already issued stays byte for byte the same and their PDF as it was issued (the seller SIREN / enterprise number is printed only on documents issued by 1.2.0). We have not connected a real plateforme agréée or a Belgian access point.

Checks of 1.3.0. On WordPress 7.1 and WooCommerce 11.2 we went through the update from 1.2.0 with settings and issued invoices kept, a buyer on the classic and block checkout, automatic hand-over to the real ePošťák sandbox, the delivery check, a buyer outside Peppol, a wrong key and a 390 px phone. This does not confirm the tax correctness of your invoices, so check how the rules apply with your accountant.

What the customer sees

  • A VAT number field (USt-IdNr.) for business customers — on the classic and block checkout. The number is normalised (“de 123 456 789” → DE123456789), and a clearly wrong format stops the order with a hint.
  • Buyer reference / Leitweg-ID — an optional field for public-sector buyers; it goes into the invoice as BT-10, which XRechnung portals require.
  • The invoice by e-mail (Pro): the PDF with embedded XML comes with WooCommerce’s order-completed e-mail, plus the XRechnung XML for orders with a Leitweg-ID.
  • Invoices in My account (Pro): customers download their invoices and credit notes themselves, without writing to the shop.

What the admin gets

  • E-invoice box in the order: issue the invoice, download the PDF, XML (CII), XRechnung CII or UBL, see credit notes and correct the buyer’s VAT ID or Leitweg-ID.
  • Settings check against a real order: the plugin builds an invoice with your details and tells you what is missing for a valid ZUGFeRD and XRechnung, before the first real invoice. There is also an unnumbered sample PDF.
  • VAT categories set automatically: standard rate S, reverse charge K / AE for a B2B customer from another EU country with a VAT ID, export G, small business under §19 UStG — E; each with a reason text and VATEX code. A product can have its own category set by hand.
  • Gap-free numbering from a pattern like RE-{YYYY}-{N:5}, restarting every year and continuing from the last number of your previous tool. A number is never “lost” when the plugin is deleted and reinstalled.
  • Payment: IBAN / BIC, days until due, terms text; the UNTDID 4461 payment means and a “Customer pays after the invoice” switch for every WooCommerce payment method.

Slovak e-faktúra (from 1 January 2027)

From 1 January 2027 Slovakia requires electronic invoices between businesses — § 85o of Act 222/2004 Coll. on VAT as amended by Act 385/2025 Coll. A VAT payer issues an e-faktúra for supplies with their place in Slovakia to taxable persons and legal entities that have their seat or a fixed establishment in Slovakia; invoices to consumers (B2C) are not covered. The format is EN 16931: the Slovak Financial Administration uses Peppol BIS Billing 3.0, and the invoice goes through a certified delivery-service provider, which passes the data on to the tax office.

  • Peppol BIS Billing 3.0 (UBL) for invoices and credit notes when the seller is in Slovakia and the buyer is a Slovak company with a DIČ, IČO or IČ DPH. Seller and buyer are addressed in Peppol by their DIČ (scheme 0245).
  • Buyer IČO and DIČ — optional fields on the classic and block checkout with a format check for Slovak addresses. If the “IČ DIČ” plugin is active, the numbers are read from its fields. They can be corrected in the order.
  • Tax point date (DUZP, BT-7) is written when it differs from the invoice date, as the Slovak transposition of Peppol BIS requires.
  • Check before issuing: seller and buyer DIČ, buyer address, currency (e-faktúra in EUR only). Whatever is wrong shows in the order, and such a document is not handed over.
  • e-faktúra UUID as defined by the Slovak specification — in the order box.
  • Free: the e-faktúra file downloads from the order, ready to upload in your provider’s portal by hand. Pro: the XML goes to your delivery service through its HTTPS API with the key in a header — automatically after an invoice or credit note is issued, or with a button in the order; the service’s answer (HTTP code and text) is stored in the order and in the order notes. For a provider with a different API there is a filter for your own adapter.

Honestly: every certified provider has its own API. If your provider takes the data differently, write to us. The tax content of the invoice is the seller’s responsibility.

Belgium: Peppol between companies since 1 January 2026

Since 1 January 2026 Belgian VAT payers invoice each other with structured electronic invoices only — Peppol BIS Billing 3.0, sent over the Peppol network. A Belgian company is found on Peppol by its enterprise number (KBO / BCE). Sales to consumers are not covered. What the plugin does for your shop:

  • for a Belgian seller and a Belgian business customer, invoices and credit notes also come as Peppol BIS Billing 3.0 (UBL): the enterprise numbers of both sides are the Peppol addresses and legal registration numbers, scheme 0208. Yours is taken from your BE VAT ID, the customer’s from the company number field or from their BE VAT ID;
  • the company number field in the classic and block checkout checks the check digits (mod 97): a wrong number stops the checkout with a hint, before the order is created;
  • a pre-check before issuing shows what Peppol still needs (number, customer address), and a Belgian consumer gets the usual PDF / Factur-X without a Peppol file;
  • invoices in Dutch or French, following the shop language;
  • Pro hands the Peppol XML over to your access point right after the invoice is issued, or with a button in the order. The provider’s answer is kept on the order; if the access point does not answer, an order note and a “send again” button appear. The Peppol XML of Belgian companies also goes into the accountant ZIP.

You need a contract with a Peppol access point — the plugin does not replace it. We tested the hand-over against our own HTTPS test endpoint (success and an HTTP 500 refusal), not yet with a real Belgian provider. Every Peppol file from the test orders passed the UBL 2.1 schema, the CEN EN 16931 rules and the OpenPeppol BIS Billing 3.0.21 rules.

France: e-invoicing reform 2026 / 2027

From 1 September 2026 every VAT payer in France has to receive e-invoices; large companies and ETI also issue them from that date, SMEs and micro-enterprises from 1 September 2027. Invoices between companies go through an approved platform (plateforme agréée), and sales to consumers are reported (e-reporting). The plugin prepares the Factur-X with the reform data — you hand the file to your platform:

  • SIREN of the seller and of the business customer (scheme 0002), SIRET as identifier (0009), electronic addresses with scheme 0225;
  • category of the operation (BT-23): goods, services or both, with separate codes for invoices already paid; B2B / B2C marker;
  • the VAT-on-debits option (BT-8) and the mandatory PMD, PMT and AAB notes — with standard texts you can change in the settings;
  • a SIREN / SIRET field at checkout: a number of the wrong length stops the checkout with a hint. B2B or B2C is decided by the customer’s SIREN — from this field or from a French VAT ID; a company without SIREN is marked B2C and the order shows a warning;
  • invoice in French, with the seller SIREN and the category of the operation printed on the PDF;
  • French invoices in euro only. In another currency the French rules (BR-FR-CO-12) need the VAT total in euro at the Banque de France / ECB rate of the day the VAT becomes chargeable, and neither WooCommerce nor a currency switcher has that rate. So an order in USD, CZK or another currency gets no invoice: the order says why, automatic issuing leaves a note, and the settings screen warns when the shop takes other currencies. No number is used up;
  • Pro: a CSV for the e-reporting of consumer sales — totals per day, currency, kind of operation and VAT rate, credit notes included. The official e-reporting flow is produced by your platform.

Every French invoice from the test orders — B2B and B2C, goods, services and mixed, with a coupon discount, 20 % and 5.5 % rates, a credit note — passed the Factur-X / EN 16931 rules (Mustang, veraPDF PDF/A-3b), the KoSIT validator and the French BR-FR schematron (FNFE-MPE 1.4.0.04). There is no direct connection to a specific platform.

Pro: automatic issuing, credit notes, customer account and a ZIP for the accountant

  • Automatic issuing when the order reaches the chosen status, with the PDF in WooCommerce e-mails to the customer.
  • Credit notes (Gutschrift, type 381) from refunds — line refunds and amount-only refunds, with their own numbering (GS-…) and a reference to the invoice. An amount-only refund is split over the invoice’s VAT groups proportionally — the credit note total is exact.
  • ZIP for your accountant per period: all PDFs, XRechnung files and a CSV list (UTF-8 with BOM, opens in Excel with umlauts intact).
  • VIES check of the VAT ID at checkout and your shop logo on the PDF.
  • Hand-over of the e-faktúra to the Slovak delivery service (HTTPS API) and the e-faktúra files in the accountant ZIP.
  • Updates from catcode.com.ua in Dashboard → Updates while the licence covers updates.

Works together with our other modules for Germany and the EU

E-Invoice EN 16931 was built alongside three other modules of ours, and they have been tested together in one shop:

  • EU VAT Check for WooCommerce checks the buyer’s VAT number in VIES and removes VAT under reverse charge — E-Invoice takes the verified number and sets categories K / AE. There is one VAT number field at checkout.
  • DATEV Export for WooCommerce exports the postings for your tax adviser with the E-Invoice invoice number in the document field.
  • Unit Price Grundpreis for WooCommerce shows the price per 1 kg / 1 l in the shop; invoices with such products pass the validators with unchanged line items.

How it works — step by step

  1. Fill in the seller details (name, address, VAT ID or Steuernummer, contact) and payment details.
  2. In “Check with order” pick any order — the plugin shows whether the invoice will be valid and what to add.
  3. The customer places the order; a business customer enters a VAT ID, a public-sector buyer a Leitweg-ID.
  4. You click “Issue invoice” in the order (with Pro the invoice is issued by itself at the chosen status and sent by e-mail).
  5. A refund in WooCommerce → with Pro, a credit note referencing the invoice right away.
  6. At month end — a ZIP with every invoice for your accountant, or an export with DATEV Export.

Under the hood

  • Standards: EN 16931 (urn:cen.eu:en16931:2017), ZUGFeRD 2.5 / Factur-X 1.09 with XMP metadata and the factur-x.xml attachment (AFRelationship Alternative), XRechnung 3.0 (CustomizationID xrechnung_3.0) in CII and UBL.
  • Peppol BIS Billing 3.0 (UBL 2.1) for the e-faktúra: Peppol CustomizationID / ProfileID, EndpointID with scheme 0245 (DIČ), e-faktúra UUID as in the Slovak specification (UUIDv5).
  • PDF/A-3b with an sRGB profile and embedded Liberation Sans fonts (OFL); characters outside the font print as “?” in the PDF and stay correct in the XML.
  • Totals by the EN 16931 rules: VAT is calculated on the group base (BR-CO-17), and the difference to WooCommerce’s per-line rounding is closed with RoundingAmount — the amount due always equals the order total.
  • File access is checked: customers download only their own documents; guests and other customers get 403.
  • Numbering in separate counters that are kept on uninstall, as is the invoice metadata in orders — documents have to be retained by law.

Installation

  1. Plugins → Add New → Upload Plugin: choose catcode-e-invoice-en-16931-for-woocommerce-1.2.0.zip and activate.
  2. WooCommerce → E-Invoice: seller details, payment details, numbering, VAT categories.
  3. “Check with order” — pick an order and make sure the invoice will be valid.
  4. For Pro: paste the licence key from the e-mail after payment or start the 7-day trial, then choose the status for automatic issuing.

Questions
about the module

Didn't find the answer? Message us on Telegram and we'll reply within a business day.

@catcode_support Setup, compatibility, activation
Do I need an external service or an e-invoicing subscription?

No. PDF and XML are created inside your WordPress; order data is not sent anywhere. Only the Pro VAT ID check calls the European Commission's VIES.

Will portals and accounting software accept my invoices?

Every invoice and credit note from our test run passed the official validators: KoSIT 1.6.3 with the XRechnung 3.0.2 configuration and Mustang 2.26 (EN 16931 + veraPDF PDF/A-3b).

Who is responsible for the tax content of the invoice?

The seller. VAT categories and exemption texts come with sensible defaults, but they are settings, not tax advice. For unusual cases (services outside the EU, §19 UStG, complex B2B chains) check with your tax adviser.

An invoice for pay-by-invoice says "paid". Why?

WooCommerce sets a paid date when the order becomes Completed. For methods where the customer pays after the invoice (bank transfer, cash on delivery, cheque) switch on "Customer pays after the invoice" — the invoice then comes out unpaid, with a due date.

Does it work together with EU VAT Check?

Yes. There is one VAT number field at checkout, the invoice uses the already verified number, and reverse charge gives categories K / AE with the exemption reason.

Is it ready for the Slovak e-faktúra from 2027?

The plugin creates the file in the format the Slovak Financial Administration uses (Peppol BIS Billing 3.0), with the DIČ as the Peppol address, and Pro hands it over to your delivery service through its HTTPS API.

Is it ready for Belgium since 2026?

Yes, for invoices between Belgian companies: the plugin creates Peppol BIS Billing 3.0 with the enterprise number as the Peppol address (scheme 0208), and Pro hands the file over to your Peppol access point.

What about the French reform 2026 / 2027?

The plugin adds the mandatory reform data to the Factur-X — SIREN / SIRET, the category of the operation, the notes — and checks them against the French BR-FR rules. Your plateforme agréée sends the invoices to the tax administration: you upload the Factur-X there; the plugin has no direct connection to a platform. French invoices are EUR only.

What stays free?

Issuing ZUGFeRD / Factur-X and XRechnung with a button, the Slovak e-faktúra file, the Belgian Peppol invoice, Factur-X with the French reform data, the checkout fields (including IČO, DIČ and the company number), VAT categories, numbering and the settings check — with no time limit.

Not quite what you are looking for?

We build custom modules for WordPress, WooCommerce, OpenCart and Shopify. Tell us about the task and we'll prepare an estimate.

Order a custom module