Factur-X Electronic Invoicing for Magento 2

Changelog

[1.4.1] - 2026-11-07

Added

• Payment means code 57 (Standing agreement) in the settings "Default Payment Means Code" and "Payment Method Mapping".
• Extension point Geissweb\ElectronicInvoicing\Api\PaymentCardDataProviderInterface for the payment card data (BG-18) of the payment means 48, 54 and 55. A provider returns the card number (BT-87) and optionally the card holder name (BT-88).
• The configuration page shows a notice while a store view with an XRechnung profile uses the payment means 48, 54, 55 or 59 and no provider for the payment card data or the direct debit data is registered in di.xml.

Changed

• The payment means text (BT-82) contains the payment method name that Magento stores with the order, such as "Check / Money order", instead of "Payment via checkmo". Orders without a stored name keep the payment method code.
• Model\Document\Builder has the new constructor argument $paymentCardDataProvider.

Fixed

• XRechnung invoices with the payment means 48 (Bank card), 54 (Credit card) or 55 (Debit card) were rejected (BR-DE-24-a), because they contained no payment card data (BG-18). Without card data, XRechnung now states these payment means as ZZZ (mutually defined) with a text such as "Credit card (Payment method name)", like the payment means 59 without direct debit data.

[1.4.0] - 2026-11-03

Added

• The E-Credit Memo now contains the Adjustment Refund and the Adjustment Fee, with the VAT of the credit memo. This requires the open source module Geissweb_CreditmemoTax: composer require geissweb/module-creditmemo-tax. Magento does not calculate VAT for adjustments, and this module does. It calculates the VAT only for credit memos that you create after you install it. Without the module, the E-Credit Memo does not contain the adjustments.
• Legal registration schemes 0002 (SIREN, FR), 0037 (LY-tunnus, FI), 0106 (KvK, NL), 0154 (IČO, CZ), 0158 (IČO, SK) and 0196 (kennitala, IS).
• ISO 6523 ICD codes 0239 to 0251 of the EN 16931 code lists version 18 for the seller global identifiers (BT-29).
• Mageplaza_ExtraFee integration: extra fees of invoices and credit memos are written as document level charges (BG-21) with their VAT rate, credit memos with the refundable fees only. Setting "Process Extra Fees" (Third-Party Integrations), enabled by default.
• Download of the E-Credit Memo XML: button "E-Credit Memo" in the admin credit memo view and link "Download E-Credit Memo" on the refunds page of the customer account, several credit memos of an order as ZIP archive.
• Section "Credit Memo Settings" with the invoice settings for credit memos: attach the E-Credit Memo XML and the PDF to the credit memo email, add the E-Credit Memo XML to the PDF and include customer-visible credit memo comments (BT-22). The XML is added to the PDF of a single credit memo printed with Magento, Fooman PDF Customiser, Mageplaza PDF Invoice, Snmportal Pdfprint or Xtento PDF Customizer.

Changed

• The legal registration scheme selection (BT-30-1, BT-47-1) lists registers by country and starts with "No scheme (identifier only)", which is the new default instead of 0223. Registers without an ICD code, such as the German commercial register, are written without a scheme.
• 0147 (Standard Company Code, JIPDEC Japan) and 0204 (Leitweg-ID) are no longer selectable as legal registration scheme. Stored values are set to "No scheme" on setup:upgrade, as is a stored seller scheme 0223: saving the configuration stored the former default, so it cannot be told apart from a deliberate choice. Select 0223 again if your seller registration really uses it.
• Names of the ICD codes 0096, 0233 and 0236 follow the EN 16931 code lists version 18.
• Added the dependency on Magento_ConfigurableProduct.
• "Add E-Invoice XML to PDF" and "Include Invoice Comments" of the invoice settings apply to invoices only. The new credit memo settings take over their stored values on setup:upgrade.

Fixed

• The seller legal registration identifier (BT-30) was dropped when no scheme was selected.
• A credit memo with only an Adjustment Refund had no invoice line and a total of 0.00. Validators rejected it (BR-16). This fix requires Geissweb_CreditmemoTax.
• The VAT rate of the shipping charge was taken from a tax code containing "ship" or the highest rate of the order instead of the rate Magento applied to the shipping. It is now read from the tax Magento stored for the order shipping. A shipping taxed at several rates, such as the proportional shipping tax of Geissweb_Euvat, is written as one shipping charge per rate.

[1.3.9] - 2026-10-12

Added

• Setting "Unit Price Decimals" (Item Settings) selects 2 or 4 decimals for the item prices BT-146, BT-147 and BT-148. With 4 decimals, quantity × net price matches the line net amount.

Changed

• Item prices are written with 2 decimals by default again. Set "Unit Price Decimals" to 4 to keep the four decimals introduced in 1.3.8.
• Declared explicit version constraints for the required Magento modules (Adobe Commerce 2.4.5 and newer) and added the dependencies on MagentoEav, MagentoSalesRule and Magento_Directory.

Fixed

• The seller tax registration identifier (BT-32) was written with the configured legal registration scheme (default 0223) instead of FC.
• Project Reference (BT-11) was missing when the order attribute of Geissweb_ElectronicInvoicingAttributes was selected as its source.

[1.3.8] - 2026-09-28

Added

• SnmportalPdfprint integration: the electronic invoice XML is embedded into invoice and credit memo PDFs rendered by SnmportalPdfprint (admin and storefront print, e-mail attachment).
• EadesigndevPdfgenerator integration: the electronic invoice XML is embedded into invoice PDFs rendered by EadesigndevPdfgenerator (admin print, e-mail attachment).
• Settings "Fixed Price Bundle Display" and "Dynamic Price Bundle Display" control how bundle items are named in the electronic invoice.
• The configuration page warns while payment means 30 or 58 (credit transfer) is configured for a store view without seller IBAN, because validators reject such invoices (CII-SR-470).

Changed

• Unit prices (BT-146, BT-147, BT-148) are written with four decimals, so that quantity × net price matches the line net amount.
• KoSIT validation in CI uses validator 1.6.3 and configuration v2026-08-31.

Fixed

• Reverse charge (AE) VAT breakdowns had no exemption reason (BR-AE-10). They now carry VATEX-EU-AE.
• Line, VAT category and document totals were rounded independently, so the sums in the XML did not add up when Magento stored amounts with more than two decimals.
• Invoices with dynamic price bundles had a line total of 0.00 and a wrong amount due, because the bundle selections were written as lines but left out of the totals.
• Payment means 59 (SEPA direct debit) without mandate data was wrongly replaced by a credit transfer with the seller IBAN, now states it as ZZZ (mutually defined).
• Items with a net amount of 0.00 were dropped, so a 0.00 invoice had no line and no VAT breakdown (BR-16, BR-CO-18). Such items keep the tax rate Magento applied instead of being reported as exempt.

[1.3.7] - 2026-08-03

Added

• SEPA direct debit for XRechnung (BG-19) via the new DirectDebitDataProviderInterface extension point.

Fixed

• Tax representative data (BT-62 to BT-70) was silently dropped for the XRechnung 2.2 and 2.3 profiles.

[1.3.6] - 2026-08-03

Added

• Amasty_Orderattr integration: custom Amasty order attributes are now selectable as source for Buyer Reference (BT-10), Project Reference (BT-11) and Purchase Order Reference (BT-13).

Changed

• Buyer Information configuration restructured for clarity: values read from the customer account are now grouped under "Buyer Identification", values read from the order under "Order & Document References".
• Include Invoice Comments (BT-22) moved to the Invoice Settings group.
• Seller field label unified with its buyer counterpart: "Legal Registration ICD Code" is now "Legal Registration Scheme (ICD)".
• Buyer Legal Registration Scheme (BT-47-1) is now always visible instead of only appearing after a registration attribute was selected.
• Seller Order Reference (BT-14) is now always the order number (increment_id); the configuration field has been removed, as BT-14 is by definition the seller's own sales order reference.
• Minimum horstoeko/zugferd version raised to 1.0.101, which is the first release containing all code list classes used by this module.
• Updated German translations

Fixed

• Buyer legal registration (BT-47) was written with the Leitweg-ID scheme (0204) when no registration scheme was configured. The identifier is now written without a scheme qualifier in that case.

[1.3.5] - 2026-07-06

Added

• Fooman_PdfCustomiser integration
• Xtento_PdfCustomizer integration (version 2.17 and below)

[1.3.4] - 2026-06-10

Fixed

• Issue with giftcards not getting the correct tax code in XML

[1.3.3] - 2026-06-01

Added

• Mageplaza_PdfInvoice integration: embed the electronic invoice XML into Mageplaza-generated invoice PDFs for both the e-mail attachment and print/download paths

[1.3.2] - 2026-04-14

Fixed

• Buyer reference field (Attributes module) not taken into account when generating the invoice XML

[1.3.1] - 2026-03-17

Added

Introduce display options for configurable products in the e-invoice to provide more information about the product variant - Append selected options: Appends variant options to the name, e.g. "Product (Color: Red, Size: M)" - Use selected options as item description: Writes variant options into BT-154 (Item description) - Use child product name: Uses the simple product name instead of the configurable parent name

Changed

• Reenable Xrechnung 2.2 und 2.3 profiles for generation to support older versions

[1.3.0] - 2026-01-28

Added

• XRechnung 3.0 Support
• Buyer Reference (BT-10) configurable attribute select
• BR-DE-15 compliance: buyer reference falls back to order increment_id when no attribute is configured
• Seller Order Reference (BT-14), and Project Reference (BT-11) attribute configuration options
• Buyer Registration attribute and scheme (BT-47) with ISO 6523 ICD code selector
• Invoice comments inclusion in XML (BT-22)
• Configurable XML storage path via system configuration
• Console command geissweb:einvoice:verify-amounts for round-trip validation against database
• Multipurpose voucher detection and VAT categorization for gift card items
• Magetrend PDF integration
• Dedicated seller fields for Leitweg-ID, GLN, and DUNS numbers (BT-29)
• XRechnung Tax Representative validation improvements
• Aheadworks_Giftcard integration for handling gift cards as prepaid amounts (BT-113)

[1.2.0] - 2025-10-20

With this version we have full support for the EN 16931 COMFORT (and lower) profile. X-Rechnung and PEPPOL support is on the roadmap.

Added

• Possibility to select any customer attribute to use as customer number (BT-46)
• Possibility to add tax representative data for B2B transactions with tax representatives
• Possibility to add Trading names, GLN, DUNS, Leitweg-ID (seller), legal registration numbers and electronic addresses
• Simple tax case detection and automatic VAT categorization
• Due days configuration to handle invoices which are paid (online) or due (for offline methods)

Fixed

• Email attachments for Magento 2.4.8
• Discount handling reliability
• Amounts not matching Magento values

[1.1.1] - 2025-07-24

Fixed

• Tests now also work with PHPUnit 10
• Smaller bugfixes like deprecation notice with PHP8.4
• Removed unneeded logging
• Add missing Magento dependencies to composer.json

[1.1.0] - 2025-07-21

Added

• Intelligent VAT category mapping system (VatCategoryMapper) for automatic tax categorization
• Payment terms and means configuration for each payment method
• Enhanced ZUGFeRD/XRechnung xml format compliance
• Console command geissweb:einvoice:generate-xml for batch XML generation of invoices and credit memos
• Console command geissweb:einvoice:validate-xml for XSD validation of generated XML files

[1.0.0] - 2023-11-01

Added

• Initial release of the Geissweb_ElectronicInvoicing module
• Support for generating electronic invoice XML files compliant with ZUGFeRD, XRechnung, and Factur-X standards
• Support for attaching XML files to invoice emails
• Support for embedding XML files in PDF invoices
• Support for downloading XML files from the admin panel and frontend
• Basic configuration system for electronic invoicing settings
• Integration with horstoeko/zugferd package for XML generation and validation