ZUGFeRD 2.5.2 and Factur-X 1.09.2: SAP Regression Tests Before 1 September 2026

FeRD and FNFE-MPE published ZUGFeRD 2.5.2 and Factur-X 1.09.2 on 4 August 2026. The corrected package becomes valid on 1 September 2026. For SAP teams, this is not a reason to redesign every German invoice mapping. It is a controlled regression event focused on the corrected EXTENDED-profile structures, current CII validation artefacts and the component that generates or validates the embedded XML.

SAP Document and Reporting Compliance, Cloud Edition added ZUGFeRD 2.5.2 and Factur-X 1.09.2 Schematron support on 18 August 2026. That establishes vendor-side validator availability before the effective date, but it does not prove that a customer-specific SAP mapping, PDF/A-3 package or inbound parser is ready.

What changed in ZUGFeRD 2.5.2

ZUGFeRD 2.5 introduced functionality in the EXTENDED profile to anticipate parts of EN 16931-1:2026 and support French B2B requirements. Version 2.5.2 is a corrigendum that removes inconsistencies found in that new functionality. It remains based on UN/CEFACT CII D22B and is fully backward-compatible with D16B.

Correction or baseline	SAP relevance
EXTENDED BT-151 and tax-type-code cardinality changed from 1..1 to 0..1 in the XSD	Custom mappings that made these nodes unconditional should be checked. Optionality in the schema does not remove business-rule requirements for scenarios where the values are needed.
Rule BR-CO-27 renamed CII-SR-470 in BASIC WL, BASIC and EN16931	The rule logic is unchanged, but monitoring, automated test assertions and support procedures may need the new rule identifier.
Separate XSD and Schematron artefacts for all five profiles	Validation must select the actual profile. One generic CII validation result is not sufficient evidence for every ZUGFeRD profile.
CII D22B with D16B backward compatibility	Inbound acceptance should include both current D22B documents and still-valid documents generated by older D16B implementations.
Factur-X 1.09.2 is technically identical	Germany and France may share technical artefacts, but profile selection and country process rules must remain separate.

The mapping question is profile-specific

A frequent implementation mistake is to maintain one CII mapping and treat the selected ZUGFeRD profile as a label added at the end. That approach becomes increasingly fragile as EXTENDED gains structures that do not exist, or are not permitted, in BASIC or EN16931.

The SAP mapping decision should resolve at least:

country
+ business process
+ document direction
+ ZUGFeRD or Factur-X profile
+ CII release
+ validation package
+ effective date

Fields introduced for EXTENDED should not leak into another profile simply because the SAP source field is populated. Conversely, a field becoming optional in an XSD does not mean it should be suppressed in every business scenario.

Empty optional elements remain a production risk

ZUGFeRD 2.5 reinforced CII rule R74: an optional element without a value must be omitted. SAP serializers and middleware templates often generate a node because a source field exists in the structure, even when the runtime value is blank.

Examples to search for in generated XML include:

<ram:Content/>
<ram:URIID></ram:URIID>
<ram:CompleteNumber></ram:CompleteNumber>
<ram:ChargeAmount/>

The correct test is not a visual PDF review. Extract the embedded XML from the final PDF/A-3 file, validate that exact payload, and confirm that the XML presented to the receiver is the same XML approved in the SAP test evidence.

SAP DRC support is confirmed, customer readiness is not automatic

SAP’s 18 August update confirms ZUGFeRD 2.5.2 and Factur-X 1.09.2 Schematron support in the Peppol Exchange process. The update closes the vendor-version question, but four separate controls still need customer evidence:

1. Source mapping: the correct SAP document and master-data values reach the required business terms.
2. Profile generation: the output contains only structures permitted by the selected profile.
3. Hybrid packaging: the correct XML is embedded in a valid PDF/A-3 document with the expected filename and metadata.
4. Receiver processing: the recipient can extract, validate and post the document without applying an incompatible older rule set.

Record the active validator version in the SAP DRC tenant rather than relying only on a generic product statement. This is particularly important when the same landscape also uses an external Access Point, middleware validator or archive product.

Regression matrix for SAP outbound and inbound processing

Scenario	What to prove	Evidence
BASIC WL invoice	Required accounting data is present and renamed rule IDs do not break automated assertions.	Source document, XML, validator version and result.
BASIC and EN16931 invoice	Optional blank fields are omitted and profile-specific cardinalities are respected.	Extracted XML from the final PDF/A-3 and Schematron output.
EXTENDED invoice	Corrected BT-151 structures and French-oriented additions are generated only when applicable.	Mapping trace, XSD result and receiver acceptance.
Credit note	References, signs, tax totals and document type are accepted under the selected profile.	Original invoice link, credit-note XML and posting result.
Inbound D22B	The parser reads the current structure and preserves profile and tax semantics.	Inbound payload, parsing log and SAP posting record.
Inbound legacy D16B	Backward-compatible documents remain processable where the business route permits them.	Representative legacy payload and posting result.
Negative empty-node test	The generator omits blank optional fields or the validator rejects the deliberately invalid payload.	Invalid and corrected XML plus rule output.

XRechnung 4.0 is a separate future change

ZUGFeRD 2.5.2 becoming valid does not make XRechnung 4.0 a production target. XRechnung 4.0 is the future German implementation of EN 16931-1:2026, but the final production bundle, validation artefacts and migration rules have not yet been published. Keep the productive XRechnung 3.0.x path separate from ZUGFeRD 2.5.2 testing.

For the broader architecture decision, review Germany B2B E-Invoicing in SAP and the XRechnung for SAP guide. Peppol transport and identifier changes are covered separately in the 17 August Peppol regression guide.

Recommended implementation sequence

1. Inventory every ZUGFeRD and Factur-X profile produced or received.
2. Confirm where CII generation, PDF/A-3 packaging and validation occur.
3. Install or confirm the 2.5.2 validation artefacts in each non-SAP validation point.
4. Run the profile-specific matrix against the exact final files exchanged with partners.
5. Document mapping changes, no-impact conclusions and remaining partner dependencies.
6. Promote only after the production support team can identify and reproduce each rejection.

Primary sources

• FeRD: ZUGFeRD 2.5.2 information package and release details
• SAP: What’s New for SAP Document and Reporting Compliance, Cloud Edition
• XStandards Einkauf: XRechnung 4.0 implementation status

Release published: 4 August 2026. Valid from: 1 September 2026. Article verified: 24 August 2026.