WooCommerce

Turn WooCommerce orders into EN 16931 e-invoices with the Beliq plugin: generate and validate XRechnung, ZUGFeRD, Factur-X and Peppol BIS Billing 3.0.

Listing pending

A WooCommerce plugin that turns store orders into EN 16931 e-invoices (XRechnung, ZUGFeRD, Factur-X, Peppol BIS Billing 3.0) through the Beliq API. When an order reaches the status you pick, the plugin maps its lines, taxes, and totals to a valid invoice, sends it to Beliq, and stores the document for a capability-checked download from the order screen. It is HPOS-compatible.

• Source: github.com/beliq-eu/woocommerce-beliq

• WordPress with WooCommerce active.
• PHP 8.2 or newer with the curl and json extensions.
• A Beliq account and API key. The free tier is enough to evaluate the plugin.

Download the source zip (Code → Download ZIP on the repository), then in wp-admin go to Plugins → Add New → Upload Plugin, upload the zip, and activate it.

The zip contains a top-level woocommerce-beliq-main/ directory, which WordPress accepts as the plugin folder.

Open WooCommerce → Settings → Integrations → beliq:

• beliq connection: paste an API key from the Beliq dashboard (Integration → API Keys).
• Seller details: EN 16931 requires the seller block, so fill in your legal name, VAT ID, and address. XRechnung also needs the seller contact e-mail, name, and phone (BR-DE-5/6/7).
• Payment details: choose the payment means and an IBAN. XRechnung rejects a SEPA credit transfer without one (BR-DE-23-a).
• Invoice generation: pick the document format (ZUGFeRD / Factur-X hybrid PDF by default), the profile, whether to output a hybrid PDF or XML only, and whether to generate on processing (payment received) or completed.
• Buyer meta keys (optional): if another plugin stores the buyer VAT ID or a buyer reference (for example a Leitweg-ID) in order meta, name those meta keys here to carry them onto the invoice.
• Turn on Generate invoices automatically. Generation stays off until you do.

By default the plugin generates only for business orders (the buyer carries a VAT ID or a company), which is where a structured e-invoice is legally meaningful. You can widen generation to all orders.

• Generate an EN 16931 invoice from an order, in the format you choose, as a hybrid PDF or XML.
• Validate the document against the rule packs and schemas of its format before it is stored. How verification works says how deep that check goes for each format.

The document is stored in a protected uploads directory and offered as a capability-checked download from the order screen, alongside a manual (re)generate action. A generation failure never breaks the order-status change; errors go to the WooCommerce log under the source beliq.

• Quickstart: the underlying API in five minutes.
• Authentication: keys, quotas, and rate limits.
• Shopware: the same order-to-invoice flow for Shopware 6.
• API reference: the operations this plugin calls.