SAP guides
SAPZUGFeRD

ZUGFeRD in SAP

SAP generates ZUGFeRD by embedding CII XML into PDF/A-3 via Adobe Document Services (ADS). This guide covers the specific ADS configuration for PDF/A-3 compliance, choosing between SAPscript and Smart Forms output, and the critical sRGB color profile requirement that causes 90% of PDF/A validation failures.

Prerequisites

  • SAP S/4HANA or ECC 6.0 EHP8+ with Adobe Document Services (ADS) configured
  • ADS embedded deployment or standalone ADS server with PDF/A-3 capability
  • SAP Note 2276033 for ZUGFeRD 2.x support and CII embedding
  • SAP Note 2530397 for PDF/A-3b conformance level and sRGB ICC profile
  • Smart Forms or Adobe Forms template for invoice output (not SAPscript)

Step-by-Step Setup

1

Configure Adobe Document Services for PDF/A-3 output

Transaction SPAD → Device Types → PDF (output device) → ADS Settings. Enable "PDF/A-3b" conformance level. Critical: activate "Embed ICC Color Profile" and select sRGB IEC61966-2.1. Without the ICC profile, PDF/A validation fails with "Missing OutputIntent" error. Test via /ADS/FPCONNECT.

2

Create ZUGFeRD output form in Adobe LiveCycle Designer

Open Adobe LiveCycle Designer. Create new form with PDF/A-3b preset. In File → Form Properties → PDF → enable "Create tagged PDF" and "PDF/A-3b" compliance. Add placeholder for XML attachment: Object → Attach Files Area. The CII XML will be embedded here at runtime.

3

Configure CII XML generation and embedding via SPRO

SPRO → Financial Accounting → Accounts Receivable → Electronic Invoicing → ZUGFeRD Settings. Select profile: MINIMUM (archiving only), BASIC (most B2B), EN16931 (EU compliance), EXTENDED (XRechnung compatible). For B2B in Germany, BASIC or EN16931 is typical. EXTENDED required if recipient needs XRechnung compatibility.

4

Set up output determination to use ZUGFeRD form

Transaction NACE → V3 (Billing) → Output Types. For output type ZUG (or your custom type): set transmission medium to "1" (Print) with device "PDF". Link to your Adobe Form template. Create condition records for customer/billing type combinations that should receive ZUGFeRD.

5

Test PDF/A-3 compliance with embedded XML extraction

Generate test invoice (VF01). Open resulting PDF in Adobe Acrobat Pro → View → Navigation Panels → Attachments. You should see "factur-x.xml". Extract and open to verify CII structure. Use Acrobat Preflight → "PDF/A-3b compliance" to verify PDF conforms. Upload both PDF and extracted XML to Invoice Navigator for validation.

Common SAP Errors

BR-CO-10Line Extension Amount Mismatch
Full guide →

Why this happens in SAP

SAP Adobe Document Services renders PDF with visual rounding, but the embedded XML uses full precision. When price × quantity has many decimal places, the visual PDF may show a different amount than the XML calculates.

How to fix it

Configure ADS to use identical precision for PDF and XML generation. In output template, set decimal handling to match across both outputs.

BR-DE-15Missing Leitweg-ID in XRechnung Profile
Full guide →

Why this happens in SAP

When using ZUGFeRD with XRechnung profile for B2G, the Leitweg-ID must be included. SAP users often select XRechnung profile but forget to populate the buyer reference field.

How to fix it

If using ZUGFeRD XRechnung profile, always populate Leitweg-ID in customer master. For B2B ZUGFeRD, use COMFORT or EXTENDED profile instead.

PDF-A3-CONFORMANCEInvalid PDF/A-3 Conformance
Full guide →

Why this happens in SAP

ZUGFeRD requires PDF/A-3 with embedded XML. SAP Adobe Document Services may generate non-conformant PDF/A-3 if ICC color profiles are missing or fonts are not embedded.

How to fix it

Configure ADS with proper PDF/A-3 settings: embed all fonts, include sRGB ICC profile, set conformance level to PDF/A-3b minimum.

Pre-Export Checklist for SAP

Before exporting ZUGFeRD from SAP, verify these items:

  • 1
    Verify ADS is configured for PDF/A-3 output with embedded fonts
  • 2
    Confirm ZUGFeRD profile matches recipient requirements
  • 3
    Check that line amounts match visual PDF display
  • 4
    For XRechnung profile: ensure Leitweg-ID is populated
  • 5
    Test XML extraction with a ZUGFeRD-compatible reader
  • 6
    Validate PDF/A-3 conformance with Adobe Preflight or similar tool

Testing Your Setup

Generate a test ZUGFeRD invoice and verify the embedded XML is correctly attached. Use a tool like Adobe Acrobat Pro or PDF-XChange to inspect attachments.

💡 The ZUGFeRD forum (www.ferd-net.de) provides official test files for each profile level. Use these to verify your system generates compatible output.

Validate Your Output

Upload your ZUGFeRD PDF to Invoice Navigator. The validator extracts and validates the embedded XML against your selected profile (Basic, Comfort, Extended, or XRechnung).

Validate ZUGFeRD

FAQ

What is the difference between ZUGFeRD profiles?
BASIC: minimal data for archiving. COMFORT: standard B2B data. EXTENDED: full invoice details. XRechnung: German B2G compliance. Choose based on recipient requirements.
Is ZUGFeRD the same as Factur-X?
ZUGFeRD 2.0+ and Factur-X are identical specifications. ZUGFeRD is the German name, Factur-X is the French name. Both use the same XML structure based on EN16931.

Related Guides

SAP XRechnung Setup

Ready to Test Your SAP Export?

Upload your ZUGFeRD invoice and get instant compliance feedback with SAP-specific recommendations.

Validate ZUGFeRD Invoice