In this presentation, you get an overview of what ZUGFeRD, a standard for e-invoices developed by the Forum elektronische Rechnung Deutschland is about. We look at XML standards for business, at PDF standards for archiving and we learn how ZUGFeRD combines both. We also look beyond ZUGFeRD at standards for digital signing.

1. © 2015, iText Group NV, iText Software Corp., iText Software BVBA© 2015, iText Group NV, iText Software Corp., iText Software BVBA
ZUGFeRD: an overview
FNFE (March 10, 2015)

2. © 2015, iText Group NV, iText Software Corp., iText Software BVBA© 2015, iText Group NV, iText Software Corp., iText Software BVBA
Agenda
• XML for the enterprise
• PDF standards: focus on PDF/A
• ZUGFeRD: combining PDF/A-3 and XML
• Beyond ZUGFeRD: digital signatures

3. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
XML for the Enterprise
ISO 15000 (by OASIS and UN/CEFACT)
ebXML: Electronic Business using eXtensible Markup Language
ISO 15000-5:2014 Core Components Specification (CCS)
 A common set of semantic building blocks that represent general types of business data
 Provides for the creation of new business vocabularies / restructuring of existing business vocabularies
OASIS (Organization for the Advancement of Structured Information Standards)
UBL: Universal Business Language
 20% of documents and business objects are used by 80% of electronic business partners
 PO, ship notice, goods receipts, invoice, bill of lading, price catalog,…
UNECE (United Nations Economic Commission for Europe)
UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business)
 CCL: Core Components Library
 CII: Cross Industry Invoice
 NDR: XML Naming and Design Rules
CEN (European Committee for Standardisation)
MUG (Message User Guides) CWA 16356 (CEN Workshop Agreement)
 Guide for a European Core Invoice data model with UN/CEFACT CII Implementation Guide
ZUGFeRD: an overview3

4. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
ZUGFeRD: an overview4
Is XML sufficient?
Not for human consumption
EDI requires predefined business relationship
Not well suited for SMEs

5. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
PDF: an umbrella of standards
ZUGFeRD: an overview5
PDF
Portable Document Format
First released by Adobe in 1993
ISO Standard since 2008
ISO 32000
PDF/E
engineering
Since 2008
ISO 24517
PDF/VT
printing
Since 2010
ISO 16612
PDF/X
graphic arts
Since 2001
ISO 15930
PDF/A
archive
Since 2005
ISO 19005
PDF/UA
accessibility
Since 2012
ISO 14289
Related:
• XFDF (ISO)
• EcmaScript (ISO)
• PRC (ISO)
• PAdES (ETSI)

6. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Focus on PDF/A
ISO-19005
Long-term preservation of documents
Approved parts will never become invalid
Individual parts define new, useful features
Obligations and restrictions
Metadata: ISO 16684, eXtensible Metadata Platform (XMP)
The document must be self-contained:
 All fonts need to be embedded
 No external movie, sound or other binary files
No JavaScript allowed
No encryption allowed
ZUGFeRD: an overview6

7. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Three standards
PDF/A-1 (2005)
based on PDF 1.4
Level B (“basic”): visual appearance
Level A (“accessible”): visual appearance + structural and semantic properties (Tagged PDF)
PDF/A-2 (2011)
Based on ISO-32000-1
Features introduced in PDF 1.5, 1.6, and 1.7:
 Added support for JPEG2000, Collections, object-level XMP, optional content
 Improved support for transparency, comment types and annotations, digital signatures
Level U (“unicode”): visual appearance + all text is in Unicode
PDF/A-3 (2012)
Based on PDF/A-2 with only 1 difference: attachments do not need to be PDF/A
ZUGFeRD: an overview7

8. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Accessible PDF?
ZUGFeRD: an overview8

9. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Structure and Semantics
ZUGFeRD: an overview9
title
list item
list item
list item
Label Content

10. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
How to read this chart?
ZUGFeRD: an overview10

11. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Structure of the data
ZUGFeRD: an overview11
Person 2 1.7 1.4 1.3 1.9 2.1 0.8 2.2 1.8 1.6 1 1.4
Position 3 2.3 2 1.8 3.2 3.9 2.1 3.1 3.2 2.3 2 2.1
RiskManagement
StructuredFinance
Mergers&acquisitions
Governance&InternalControl
AccountingOperations
Treasuryoperations
ManagementInformation&
BusinessDecisionSupport
BusinessPlanning&Strategy
FinanceContributiontoIT
Management
CommercialActivities
Taxation
FunctionalLeadership

12. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Structure of the data
ZUGFeRD: an overview12
Person Position
Functional Leadership 2 3
Risk Management 1.7 2.3
Structured Finance 1.4 2
Mergers & Acquisitions 1.3 1.8
Governance & Internal Control 1.9 3.2
Accounting Operations 2.1 3.9
Treasury Operations 0.8 2.1
Management Information & Business Decision Support 2.2 3.1
Business Planning & Strategy 1.8 3.2
Finance Contribution to IT Managemen 1.6 2.3
Commencial Activities 1 2
Taxation 1.4 2.1

13. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
ZUGFeRD: an overview13
Is PDF sufficient?
Parsing / scanning PDF is not trivial
Accessible PDF is mandatory for Section 508
Tagged PDF wasn’t designed for “the business”

14. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
ZUGFeRD
Zentraler User Guide des Forums elektronische Rechnung Deutschland (June 2014)
Developed by FeRD (Forum elektronische Rechnung Deutschland) founded in March 2010
Based on PDF/A-3: Archiving + Attachment
Imposes an XML schema based on CII
Goal: electronically exchange invoices
Reduce invoicing cost
Optimise processing cost
For humans as well as for machines
For SMEs as well as big corporations
ZUGFeRD: an overview14

15. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
XML in ZUGFeRD
In order to simplify mapping in future, FeRD decided to base the ZUGFeRD data model directly on the CCL.
At the semantic model level, a data model is created which is defined as being more straightforward and CII-
compatible. In order to produce XML schemas from the semantic data model, the Naming and Design Rules
(NDR) are applied. Using these rules, XML data types are created from the semantic definitions.
ZUGFeRD: an overview15

16. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
ZUGFeRD profiles
BASIC
Data fields (structured data)
Free text fields
COMFORT
Data fields (structured data)
Qualified free text fields (Tagged information)
EXTENDED
All of the above and more…
ZUGFeRD: an overview16

17. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
PDF/A-3 and ZUGFeRD
Specific XMP extension schema for ZUGFeRD with identification of profile
PDF/A-3 gives visual representation of invoice that is human-readable
Level of conformance doesn’t matter
Invoice data is imbedded as XML in the PDF/A file: 1 document = 1 invoice
Name of the file must be “ZUGFeRD-invoice.xml”
Mime-type text/xml; encoding UTF-8
Relationship: “Alternative”
Params must at least contain a ModDate
Other attachments (e.g. “Data”) are allowed
ZUGFeRD: an overview17

18. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Benefits
Save costs on printing, envelopes and postage
No need to copy, scan, OCR invoices (less errors)
Approval process can be done digitally (*)
Faster processing = faster payment?
No need to file invoices as paper documents
Different software systems only need to understand a single format (choice!)
SMEs can meet requirements of large corporations without former agreement
Mails with ZUGFeRD attachment could be detected and filed automatically
Banks could read ZUGFeRD invoices and process them immediately
…
ZUGFeRD: an overview18

19. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
ZUGFeRD: an overview19
Beyond ZUGFeRD
Integrity, authentication, non-repudiation
Digital Signatures
PAdES

20. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Integrity
ZUGFeRD: an overview20
I paid a forged invoice
and lost $40K!

21. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Authentication
ZUGFeRD: an overview21
Why am I, Emperor Constantine I,
in this picture? I never transferred
authority to the Pope!

22. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Non-repudiation
ZUGFeRD: an overview22
I didn’t do it!

23. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
Digital Signatures in PDF
ZUGFeRD: an overview23

24. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
ISO 32000 and ETSI PAdES
ISO
ISO-32000-1 (2008) based on PDF 1.7 (2006)
ISO-32000-2 will define PDF 2.0 (2016)
ETSI: TS 102 778 (2009 - 2010)
PAdES 1: Overview
PAdES 2: Basic – CMS based (ISO-32000-1)
PAdES 3: Enhanced – CAdES based (ISO-32000-2)
PAdES 4: LTV – Long Term Validation
PAdES 5: XAdES based (XML content)
PAdES 6: Visual representation guidelines
ETSI: TS 103 172 (2011 - 2013)
PAdES Baseline Profile
ZUGFeRD: an overview24

25. © 2015, iText Group NV, iText Software Corp., iText Software BVBA
ZUGFeRD: an overview25
Questions?
Bruno Lowagie
bruno.Lowagie@itextpdf.com
iText Software BVBA: +32 9 298 02 31