Invoice-api.xhub for WooCommerce

This is a free plugin that connects WooCommerce to the invoice-api.xhub.io e-invoicing service. The plugin itself is fully open source under GPLv2-or-later. To generate invoices you need an active subscription with invoice-api.xhub.io — service plans start at modest monthly tiers, see console.invoice-api.xhub.io for current pricing.

This is the same model used by Stripe, PayPal, Mollie, Mailchimp, and Zapier WordPress plugins: free open-source connector + paid third-party service.

It targets the EU e-invoicing mandates rolling out between 2025 and 2028 — Germany (XRechnung/ZUGFeRD, mandatory B2B receive 2025, send 2027/28), France (Factur-X, mandatory 2026/27), Italy (FatturaPA, mandatory since 2019), and 11 more countries.

Supported formats (live now)

• PDF (all 14 countries)
• XRechnung (DE)
• ZUGFeRD (DE, AT)

Coming Q3 2026

The invoice-api.xhub.io API roadmap adds these formats from Q3 2026 onwards. The plugin will surface them in the format dropdown automatically once the backend supports generation:

• Factur-X (FR)
• FatturaPA (IT)
• Facturae (ES)
• ebInterface (AT)
• UBL (BE, NL, BG, RO)
• ISDOC (CZ)
• NAV (HU)

In the meantime PDF works for all 14 countries — that’s the universal fallback while the country-specific formats roll out.

How it works

1. You install the plugin and add your invoice-api.xhub.io API key.
2. You configure the default country, format, and seller details.
3. When an order reaches the configured trigger (default: completed), the plugin POSTs the order to the API and stores the returned invoice file on the order.
4. The customer-facing email gets the invoice file attached automatically (configurable).
5. The order edit screen has a meta box to manually generate, re-generate, and download the invoice.

What this plugin does NOT do

• It does not host an OCR or template engine — generation is delegated to the API.
• It does not bypass WooCommerce taxes — tax rates are derived from line totals as WooCommerce computes them.
• It does not submit invoices to government portals (Peppol, FatturaPA SDI, KSeF). The XML/PDF is produced on the server and stored on the order; submission is your responsibility.
• It does not work without an API key — sign up at https://invoice-api.xhub.io to obtain one.

External services

This plugin relies on the third-party service invoice-api.xhub.io to generate the invoice files (XRechnung XML, ZUGFeRD PDF, Factur-X PDF, etc.). It is required for the plugin to function — invoice generation cannot happen locally because the service produces standards-compliant e-invoices using server-side libraries that are not bundled with this plugin.

Endpoint: https://service.invoice-api.xhub.io/api/v1/invoice/{country}/{format}/generate

What is sent: for every order processed (auto on a status transition you configure, or manually via the meta box):

• Seller information from your plugin settings: company name, VAT ID, street, postal code, city, country, email, IBAN, BIC (if configured)
• Buyer information from the order’s billing address: name (or company), street, city, postal code, country code, email
• Order line items: description, quantity, unit price, tax rate, tax category, net/tax/gross amounts
• Order metadata: invoice number, dates, currency, payment terms, country-specific fields (e.g. Leitweg-ID for DE)

What is NOT sent: WordPress user accounts, password hashes, payment-gateway credentials, server logs, plugin/theme lists.

When data is sent: only after you have configured an API key (no calls happen on activation or before configuration), and only at one of: (a) the configured order status transition, (b) when you click “Generate” / “Re-generate invoice” in the order meta box.

Service provider: xhub.io — see the Privacy / GDPR section below for the full data-flow description.

By configuring your API key and saving the plugin settings, you consent to this data being transmitted to invoice-api.xhub.io for the sole purpose of generating compliant e-invoices.

Privacy / GDPR

The plugin stores the generated invoice file (base64-encoded) and metadata on the WooCommerce order itself, using order custom fields prefixed with _invoice_api_xhub_. This includes the buyer’s billing details that are part of the invoice payload and will appear in the generated XML/PDF.

When a WordPress administrator processes a personal-data export request (Tools → Export Personal Data), the plugin contributes the invoice number, generation timestamp, format, and filename for each order belonging to the requested email address.

When a personal-data erasure request is processed, the plugin deletes the stored invoice payload and all associated metadata for orders belonging to the requested email address.