XRechnung, ZUGFeRD, EN 16931, Peppol and Leitweg-ID: Businesses encounter many e-invoicing terms that seem to describe similar things. In fact, they may refer to a file format, a regulation, an individual data field or transmission. This e-invoicing glossary explains 60 important terms, shows how they relate and turns technical messages into practical steps.

Technical status: . General orientation for Germany; special cases and the tax treatment of individual transactions require a separate examination.

Four levels to keep apart

01 · Default

What is required?

The law, the transitional period and the recipient requirement determine the scope.

02 · Meaning

What does the data mean?

EN 16931 describes the invoice details and their contexts.

03 · Presentation

How is the file structured?

UBL or CII are data-based; XRechnung and ZUGFeRD are used to concreteise the use.

04 · Exchange

How does she get here?

For example, by email, portal or Peppol – depending on the agreed procedure.

Note: A calculation can be a XRechnung, use UBL, be based on EN 16931 and sent via Peppol. Words do not compete with each other: they describe different properties of the same process.

All 60 look up terms alphabetically

XRechnung, ZUGFeRD, PDF and Peppol: the quick comparison

What term answers what question?
DefinitionMeaning:Do not be confused with
EN 16931European model of accounting dataA single program or mail portal
XRechnungGerman standard with specified rulesA plain XML file name
ZUGFeRD / Factur-XFormat family for PDF with structured XML dataAny PDF attachment
UBL / CIITechnical data structuresDifferent tax procedures
PeppolNetwork and rules for exchangeA guarantee for the accuracy of the facts
Leitweg-IDAllocation in public exchange of accountsInvoice number, tax number or IBAN
Viewer / ValidatorIndication / technical examinationA Tax Release

Basics, obligations and business partners

e-invoice

An e-invoice contains invoice information in a defined data structure that software can process. What matters is the structure of the content rather than whether it is sent by email. Under German VAT law, EN-16931-compliant formats are particularly relevant. Agreed interoperable formats can also meet the legal requirements. A photograph of an invoice is therefore not automatically an e-invoice. Legal basis: § 14 Paragraph 1 UStG.

Other account

The other invoice is the VAT law in invoices on paper or in electronic formats outside the legal e-invoice definition. This typically includes a normal PDF without structured invoice data. "Other invoices do not automatically mean that such invoices may be issued, depending on the business, exceptions and the transitional period. File format and legal admissibility must therefore be checked separately. Classification of the B-MF.

B2B – Business to Business

B2B refers to business between companies. A freelance translator working for an agency, for example, moves in the B2B area. However, the German e-invoice obligation does not suffice: the locality of the parties involved, the concrete turnover and legal exceptions are important. When creating a customer, it should therefore not only be "Fi Ma, but also its country and the nature of the business relationship. Requirements in § 14 UStG.

B2G – Business to Government

B2G describes transactions with public authorities, such as a ministry or a municipality. The requirements of the respective client and the relevant rules of the federal or state apply here. For example, invoices at federal offices can be requested Leitweg-ID, payment details and a contact address. Practically, a customer note helps: Recipient, invoice format, identifiers and submission method from the order before the first invoice is created. Federal information.

B2C – Business to Consumer

B2C means that a company sells to a private person. The German obligation to pay structured bills for certain domestic business transactions is not triggered solely by such retail sale. Thus, a craft business can also have B2B, B2G and B2C customers. For the organization, this distinction is more helpful than a flat-rate setting "All customers get the same format,. Other invoice obligations remain independent of this. B-M: Scope and exemptions.

e-invoice Obligation and transitional periods

The reception and exhibition are two different obligations. Domestic companies must be able to receive e-invoices since 2025 in principle; transitional rules exist for the exhibition. By the end of 2026 general facilitations apply, 2027 including with a maximum of 800.000 Euro of the previous year's sales of the exhibitor as well as for certain import procedures. From 2028 these transitions expire; legal exceptions remain. Planning should therefore begin with its own application, not with a flat-rate deadline for all invoices. Transitional right: § 27 Paragraph 38 UStG; Time limits explained in detail.

Small business

Small business owners are a tax classification, not a file format and not a statement about the quality of an invoice. For the issuance of invoices for corresponding tax-free transactions, § 34a VATDV contains an exception to the mandatory e-invoice. However, this does not mean that incoming e-invoices can be ignored. Those who voluntarily settle a tax-free transaction must also reflect the applicable tax-free basis and must not simply supplement a normal VAT amount. § 34a VATV; Practical articles for small business.

VIDA – VAT in the Digital Age

ViDA is an EU package to modernise VAT in digital commerce. It includes, among other things, electronic invoices and digital messages for certain cross-border transactions. The Council adopted the package on March 11 2025; essential cross-border reporting requirements are foreseen for 2030. ViDA is neither an invoice format nor the statement that every German invoice is already automatically received by the tax office. EU Council: decision and timetable.

Standards, data structures and billing formats

EN 16931

EN 16931 is the European standard series for electronic invoices. Its semantic core model describes the meaning of the invoice information and its relationships: for example, sellers, buyers, invoice positions and tax amount. what The standard is neither a software nor a specific file extension. For the exchange, it also requires a concrete technical representation of the agreed content. European Commission on the e-invoicesnorm.

Syntax

Syntax indicates the technical structure of a message. Two invoices may contain the same technical information, but they may be stored in differently named and nested XML elements. This is comparable to two forms that both "invoice number, query, but run the field in different places. A software must understand the syntax used; merely looking for a visible word like "total, is not a reliable assignment. Example of syntax: UBL 2.1.

XML – Extensible Markup Language

XML is an award language for structured data. Names in sharp brackets mark elements; in them are values or other elements. This makes connections for programs evaluable. .xml However, it does not prove that it is an invoice, nor that it is correct. Also a product list can be XML. If you open an XML invoice, you need an ad or check that is suitable for the invoice format. W3C: XML.

UBL – Universal Business Language

UBL is a standard for electronic business documents developed by OASIS. It contains XML structures for invoices and credits, among others. UBL 2.1 is one of the syntaxes used for XRechnung. The distinction is important: Not every UBL document automatically meets XRechnung. Only the rules, identifiers and content that are also observed make a file the appropriate document for a concrete invoice exchange. OASIS: UBL specification.

CII – Cross Industry In Voice

CII is an industry-wide accounting structure from the UN/CEFAT environment. It is the second syntax in which XRechnung can be implemented and forms the XML basis of ZUGFeRD or Factur-X. UBL and CII are therefore not two different tax types. They describe different technical ways of representing invoice contents. When converting, the meaning of the information must be retained, even if the XML elements are then called differently. Ferd to XML Base.

XRechnung

XRechnung is a German standard for structured invoice data based on the European standard. It specifies requirements for German application and is particularly common in public invoice exchange. The invoice is typically transmitted as an XML file; a PDF invoice image does not necessarily belong to it. XRechnung can be represented in UBL or CII. Which version and which transmission route should be clarified with the recipient before shipment. KoSIT: the XRechnung standard; Create XRechnung.

CIUS: Core Invoice Usage Specification

A CIUS describes a concrete application of the European accounting core model. For example, it can make optional information mandatory or narrow the permitted values without any indication of the core model. For users, this explains a frequent stumbling block: an invoice can meet the general rules and still fail to meet additional requirements of an application area. XRechnung is an example of such national concretization. European Commission: Standard conformity and CIUS.

ZUGFeRD

ZUGFeRD combines a readable PDF/A-3 document with embedded XML invoice data in the usual hybrid use. People can view the invoice, programs can read the data. The Forum electronic invoice Germany accompanies the development of the format. Not the logo, file name or any XML system are crucial, but the actual compliance with the format and profile rules. Also with this format the structured content should be checked. Ferd: Building ZUGFeRD.

Factur-X

Factur-X is the French name of the German-French format developed together with ZUGFeRD. The coordinated versions share the technical basis. Those who read in exchange "Factur-X should first compare version and profile, instead of automatically suspecting a completely different billing solution. The terms can refer to the same format family; concrete recipient requirements remain decisive. Ferd: connection of ZUGFeRD and Factur-X.

PDF, Profile and Version Numbers

PDF/A-3

PDF/A-3 is a long-term storage PDF variant that also allows embedded files of other formats. This option uses ZUGFeRD for XML billing data. However, the opposite does not apply: "PDF/A-3 automatically means e-invoice. The PDF container may contain completely different attachments. Therefore, for the assessment of an invoice, both the embedded data and the relevant accounting rules must be considered. PDF Association: embedded files.

Hybrid accounting

A hybrid calculation combines a human-readable representation and machine-readable invoice data in a file. In ZUGFeRD the PDF and XML are the two. Both should match content. If they differ from each other, the structured part is decisive for the e-invoice. Therefore, a consistent PDF alone is not sufficient quality proof. In the workflow, recipients, positions, tax amounts and final sum should correspond in particular between display and XML. B-M: hybrid invoice formats.

Profile

A profile determines the scope and rules used by a billing format in a given form. ZUGFeRD knows among others the minimum value of the invoice, BASIC WL, BASIC, EN 16931 and EXTENDE. The first two do not provide the complete structured invoice for the German e-invoice definition. "BASIC, may not be equated with "BASIC WL". Therefore, for software offers, it is necessary to ask explicitly for the supported profile, not just for "ZUGFeRD support. Ferd: Profiles; B-M: suitable ZUGFeRD profiles.

Version and Release Bundle

A version number indicates a development status of the standard. A release bundle bundles related files such as rules, examples and test artifacts. Both are not automatically identical: A bug correction package can appear without changing the main version of the standard. For a comprehensible examination, format, specification level and the rule package used should be documented. A draft of a future version is also not yet an invitation to change current invoices immediately. KoSIT: Versions and Bundles.

Accounting fields, references and identifiers

BT – Business Term

A business term is a professionally defined billing field with an identification number. BT-1, for example, refers to the billing number, BT-10 the buyer reference. These numbers help to understand error messages and documentations across the Linux network. In XML, it is not necessarily literally "Bt-1,: In UBL, the value is defined as cbc:ID Therefore, the technical field and then its technical position should be searched for first. Example: BT-1 in UBL.

BG – Business Group

A business group summarizes the relevant invoice details. BG-22 stands for the document sums, while other groups bundle stakeholders, positions or tax breakdowns. Thus, a group is not a single invoice value. For troubleshooting this is important: if an entire group is missing, there may be several data affected. In the data collection, such relationships should also remain visible, rather than placing all fields in a long list in a disorderly manner. Example: BG-22.

Cardinality and mandatory field

Cardinality describes how often a field or group may occur. 1..1 means exactly once, 0..1 at most once and optionally, 0..n Additional business rules can nevertheless require an optional field in a particular case. An empty string is not automatically a meaningful fulfilment of a mandatory field. The invoice number field shows the simple case "exactly once,. UBL field description with cardinality.

Buyer Reference (Bt-10)

The buyer reference supports the internal assignment of the invoice recipient. This can be a department identifier or another reference specified by the buyer. In German administrative processes the Leitweg-ID is registered here regularly. In the B2B area, however, BT-10 is not automatically a Leitweg-ID. The value should be called by the recipient; a self-invented identifier can have a technically readable invoice landed in the wrong work basket. Definition of BT-10.

Leitweg-ID

The Leitweg-ID is an identifier for the assignment of electronic invoices in the public exchange of invoices. It helps to reach the responsible invoice recipient or its processing area. It is neither the own tax number nor the invoice number. Whether it is needed and what value is to be used is the result of the specifications of the contracting authority. For normal invoices between private companies there is no general obligation to obtain a Leitweg-ID. German Federal Ministry of Finance: Leitweg-ID and B2B.

Order reference (Bt-13)

The order reference connects an invoice with an order from the buyer. BEST-2026-0042 This distinguishes them from the seller's own order number and from a general buyer reference. In the invoice process, it allows comparison with a previously released purchase. If the customer expressly asks for his order number, it should be in the appropriate structured field and not only somewhere in the invoice text. Peppol Field description: Order reference.

Endpoint ID and electronic address

An endpoint ID is an electronic address of a party. For the buyer it is shown, among other things, in BT-49. The identifier includes an indication of the identification scheme used; therefore, the character sequence alone is often not sufficient. Depending on the process, for example, a registered network subscriber identifier can be attached to it. Electronic address, general contact e-mail and Leitweg-ID perform different tasks and should not be copied unchecked into each other. BT-49 and Schema identifier.

Invoicing number (Bt-1)

The invoice number identifies the invoice within the exhibitor's number system. It is not to be confused with a customer number or an order number. A meaningful workflow grants the number checked and then uses it consistently in file, accounting and correspondence. Anyone who corrects an invoice already sent should be able to understand this reference, instead of tacitly exchanging another file under the same name. Technical definition of BT-1.

Date of performance and period of performance

The date of performance describes when the delivery or performance was performed. Instead, a performance period indicates the beginning and end of a coherent period. Both should be distinguished from the date of issue of the invoice. For example, a monthly service may be invoiced and serviced in different months. The VAT implementing regulation allows the calendar month to be specified for the time of performance. The structured picture is based on the actual business. § 31 Paragraph 4 VATV.

VAT Identification number

The VAT identification number is a tax identification number of the company. It is neither IBAN nor customer number, invoice number or Leitweg-ID. For data maintenance, it is recommended to keep this information in separate fields and not in a collection field "Number to deposit. Thus, it is clear when exporting, which identifier belongs to which party and what purpose. The general accounting requirements indicate the tax number or VAT identification number of the supplier. § 14 Paragraph 4 UStG.

Amounts, taxes and payments

VAT category

A VAT category describes the tax treatment of a position or tax breakdown. S, Z, E, AE and O have different meanings. A zero tax amount does not make these categories interchangeable: VAT exemption, a zero VAT rate, reverse charge and a transaction outside the scope of VAT are different situations. The category must match the actual service. A converter cannot reliably make this business decision from the number 0 alone. UNCL official code list 5305.

VATset

The VAT rate is the percentage value that taxes the tax base in question. It complements the tax category but does not replace it. In the simple example with 300 Euro net and 19 percent, 57 Euro VAT results. If one invoice contains several tax treatments, the respective bases and tax amounts must be allocated separately. Whether a specific sentence is correct cannot be identified by a successfully tested XML file alone. Peppol BIS: Control breakdown and calculations.

Exemption

A tax exemption reason explains why no VAT is calculated. In structured invoices, a text and/or a code provided for this, such as BT-120 or BT-121, are available depending on the case. This is something else than any hint in the PDF foot area. The reason must fit the chosen category. If a regularly taxed position is a registered exemption reason, for example, would be contradictory. Field description and related rules.

Reverse charge

Reverse Charge refers to cases where the beneficiary owes the VAT. This is not a flat-rate tax exemption and is not synonymous with any foreign invoice. Whether the procedure applies depends on the actual turnover and the legal requirements. In the structured picture, category, identification information and mandatory information must fit together. Anyone who is unsure should clarify the tax treatment before exporting instead of using another code on an experimental basis. § 13b UStG.

Rounding and rounding amount

Rounding limits the number of decimal places at specified processing steps. A rounding amount at document level is a separate indication and not a substitute for correct position and control calculations. Therefore, if a difference of one cent is used, it should first be checked which initial values and rounding steps were used. Only the visible formatting to two decimal places in a table does not guarantee that the displayed numbers are expected internally. Document sums and BT-114.

Amount of payment (Bt-115)

The amount of the payment is the sum that has to be paid after taking into account the relevant total amounts. It may differ from the gross invoice amount, for example if an already paid sum is taken into account. In the simple case without advance payments and without a separate rounding amount, both values are the same. Therefore, the correct field for the payment collection should be used, not automatically any total amount in the document. Document sums including BT-115.

Method of payment (Bt-81)

The payment method describes the method of payment in a standardized identifier. Thus, a transfer is shown differently than a direct debit. The code is not the IBAN and does not automatically contain all the necessary bank details. A complete payment rate can therefore consist of several related information. For data input, a comprehensible selection such as "SEPA transfer, more meaningful than an uncommented free text field for technical numerical values. Field description of BT-81.

Unit code

A unit code indicates the unit of quantity of an invoice position in a standardised form. HUR for hours, C62 for a number of individual units; and KGM For kilograms. An ad may also use understandable terms. However, the appropriate code must be selected when exporting. "4 Hours, and "4 Pieces, are mathematically similar quantities, but describe different performances and may not be randomly assigned to the same unit. UNECE units in the Peppol code list.

Shipping, networks and processing

Peppol

Peppol is a network with common rules for electronic exchange of business documents. It is neither a single billing format nor simply an email address. The sender connects with the recipient's service provider via its service provider. For use, the recipient identifier, supported document type and transmission process must match. Whether Peppol is necessary or available is the result of the respective business process. OpenPeppol: Network and functioning.

Peppol BIS-Calculation

BIS stands for Business In the Internet of Things (BIS) 8. Peppol BIS Bill describes rules for interoperable exchange of invoices and credits in the Peppol environment. These include data requirements, identifiers and test rules. The term is not synonymous with any XRechnung. Furthermore, Peppol should not be reduced to "UBL only,: The current documentation also takes CII into account as an additional option. The documents supported by the involved service are decisive. Current BIS-Billing documentation.

Access Point

An access point is an access to the Peppol network. In the usual four-corner model, two such access services are between the invoice holder and the recipient. You can imagine them as agreed transfer points: They transport supported business documents based on the network rules. However, successful technical delivery does not mean that the customer has released the invoice or paid the invoice in a factual manner. For the own process, shipping confirmation, technical feedback and payment should be recorded separately. OpenPeppol: Four-corner model.

OZG-RE

OZG-RE is a billing platform for public administration. It is an access to the filing of invoices, not even the billingyntax. Which location is available and which information is required must be checked on the basis of the recipient information. The former Federal platform ZRE was shut down at the end 2025; older instructions with a flat reference to ZRE are therefore to be questioned. The correct platform address belongs in the current customer documentation. Bund: Platforms and Conversion.

Electronic Data Interchange – Electronic Data Interchange

The term is wider than e-invoice and may also apply to orders or delivery information. An expanded electronic data exchange process does not already fulfill any new invoice requirement because of its long use. It is necessary to clarify whether it meets the legal requirements or still applies a transitional rule. For certain previous electronic procedures, the VAT law provides for a transitional possibility until the end 2027. § 27 Paragraph 38 UStG.

Mapping

Mapping is the assignment of initial data to target fields. For example, in a Excel calculation, it must be determined which cell the invoice number provides, where a position begins and which number indicates the net price. An assignment should not be based solely on the screen position if the template can move later. A good practice test changes quantities, adds a position and checks whether the exported values continue to appear in the correct places.

API – programming interface

An API is a defined interface that programs exchange data or functions. In the billing process, software can, for example, retrieve master data or pass ready documents to another system. "With API, however, does not yet indicate which fields are transferred, how errors are reported or who has access. Before introduction, a concrete sample calculation should be fully performed, including a deliberately incorrect input.

Check, error messages and display

Validation

Validation is the technical examination of an invoice against a selected set of rules. For example, the XML structure and technical data rules are checked. The result also depends on which format and the standard level were checked. A successful run does not confirm that the service was actually performed or that every tax decision was made. For a reliable invoice control, technical examination, comparison of documents and technical clearance are therefore part of the group. KoSIT Validator: Test procedure.

XSD – XML Schema Definition

XSD is a language for describing acceptable XML structures and data types. A schema can, for example, determine which elements may occur, in what order it is in and whether a value must be a date. This can identify a part of technical errors. Whether a sum matches other values or a special tax rule is fulfilled, however, this does not automatically clarify completely. W3C: XML Schema.

Schematron

Schematron is a rule-based test technique for XML. It can control relationships between information that goes beyond the structure structure. A rule can require, for example, that an additional justification is available for a particular control category. Such tests supplement the schema test. For users, the practical question is not what the rule language looks like, but what specific information concerns a message and how it is corrected objectively correctly. KoSIT: Schema and Schematron Test.

Rules of business

A business rule describes a condition for the invoice data to be observed. It can, for example, define a necessary reference or the interaction of a tax category with a reason for exemption. Many rules have an identifier that appears in the audit report. This identifier is useful for the search: Instead of "validating the invoice, passing on the invoice, rule number, affected information and understandable error message should be documented together. Examples of conditional business rules.

Validation report

A validation report records the result of a technical check. It may contain errors, warnings and additional information. For editing, a clear order is recommended: first blockage structural errors, then technical data rules, then check instructions. A warning should not be automatically ignored, but is not equivalent to any error message. The test bench used is part of the report so that the result can be tracked later. KoSIT: Test results and reports.

Viewer and Visualization

A viewer presents structured billing data in a legible form. XML, for example, creates labeled areas for senders, recipients, positions and sums. This display facilitates control but does not automatically replace validation. It is also a representation of the original and not a new original document. When changing tools, it should be checked whether less striking information such as references or tax notes remain visible. KoSIT: Visualisation; Open and check XML invoices.

OCR – optical sign recognition

OCR tries to recognize text and numbers from an image or scan. This is different from the direct reading of structured accounting fields. A scan can, for example, "8, and "B, similar; also, downstream processing must understand which number belongs to which field. OCR can facilitate the recording, but does not automatically make an image a correct e-invoice. Recognised values still require reliable mapping and control.

Storage, corrections and signatures

GoBD

GoBD stands for principles for the proper keeping and keeping of books, records and documents in electronic form as well as for data access. It refers to requirements for the handling of tax-relevant information, not a specific invoice format. The administrative requirements have been adjusted 2025 also with regard to e-invoices. An advertising notice "GoBD-compliant, therefore does not replace the examination of how collection, storage and changes in the own operation are actually organized. B-M: GoBD change from 14. July 2025.

Original file

The original file is the actual electronic invoice received or issued, not just a screenshot of it. Therefore, the structured file should be retained in an XML invoice. As a simple operational standard, it is recommended to keep hybrid invoices completely and clearly identify additional read versions. This will allow later verification of which data has been transmitted. A printed view can facilitate access to the content, but does not represent the machine-readable structure. Storage according to § 14b UStG.

Archiving and retention period

Archiving means keeping invoices sorted and available for the required duration. In principle, eight years apply for the tax-based retention of invoices; the start of the period and possible extensions have to be considered separately. A randomly filled download folder is not yet a well thought out storage procedure. Responsibilities, retraceability, protection against unnoticed changes and a tested access should be clarified. Data backup is also useful, but not identical with all storage requirements. § 14b UStG.

Procedural documentation

A process documentation describes in a comprehensible way how tax-relevant documents are processed in the company. For e-invoices it can explain, for example, receipt, verification, release, storage, access rights and corrections. A concrete work description instead of an abstract collection of product names is helpful: Who controls the mailbox? Where is the original? What happens with an invalid file? The documented procedure should be consistent with the actual work and adjusted for changes. B-M: current changes of GoBD.

Correction of accounts

A correction of the invoice corrects missing or incorrect information of an existing invoice. The reference to the original document must be clear. This distinguishes a comprehensible correction from a silent overwriting of the already sent file. Depending on the case, different correction procedures may be required. Practically, original invoice, correction and correspondence should remain common; the legally appropriate procedure must be coordinated with the tax advice if doubts arise. § 31 Paragraph 5 VATV.

Credit note and credit note

The German term ‘Gutschrift’ is ambiguous. For VAT purposes, it can mean an invoice issued by the recipient of the service under a prior agreement, known as self-billing. In everyday business, the same word is also used for a reduction of an invoice, referred to as a ‘Credit Note’ in data exchange. Do not treat these meanings as interchangeable without checking. What matters is the actual transaction, the appropriate document type and the correct references to other documents. Credit in VAT; UBL document types In Voice and CreditNote.

Digital signature

A digital signature can secure the origin and immutability of electronic data. However, a qualified electronic signature is not mandatory for every e-invoice; the VATright also provides for other ways of ensuring origin and integrity. Differentiating from this is the signing of a software: it concerns the delivered program and its publisher, not automatically any invoice created with it. § 14 Paragraph 3 UStG; Digital signature of TabellenFaktura.

Practical example: How the terms come together in one invoice

A fictitious office calculates four hours of document processing for each of the two companies for a total of EUR 75 net. For this simplified example, a regular rate of 19 per cent taxed service is assumed. There are no discounts, surcharges, advance payments or separate rounding amounts. The customer calls an order reference and wishes XRechnung.

Fictives calculation exampleRE-2026-0042
From the invoice position to the payment amount
DetailExample valueMeaning
Quantity and unit4 hours · HURFour hours worked
Net unit price75,00 €Price per hour without VAT
Net line amount4 × 75,00 € = 300,00 €Net charge of the single item
Tax payable by:300,00 € × 19 % = 57,00 €In the example of regular taxation
Total357,00 €Net amount plus VAT
Amount357,00 €Here identical to the gross amount

The same data is given different tasks: RE-2026-0042 identifies the invoice, the order reference assigns it to a purchase, and the electronic address supports the intended exchange. None of these details replaces the other. The example shows the calculation logic, but is not a complete invoice.

  1. ask about the requirements. Which type of invoice, which format, which reference and which way of receiving the invoice is required by the customer? This information will be deposited with the customer.
  2. The data are allocated to the data. Mapping combines the template's values with the correct billing fields. Numbers, prices, taxes and addresses remain separate.
  3. Create and check file. The export creates the structured invoice. The validator checks it against the appropriate rule level; the detected information is checked in the viewer.
  4. Transfer and store. The invoice is sent to the customer via the coordinated route. The original and the corresponding documents remain traceable.

Simple figures are sufficient for an initial test. Then check the same template with two line items, a longer description and a different quantity. This makes it easier to see whether only one example works or the mapping is reliable in everyday use. For advice on the Excel starting point, see Create e-invoice from Excel.

Typical messages: What to do now?

From technical notification to next step
Reporting or monitoringProbable DirectionConcrete next step
"Bover Reference is missing,Buyer Reference / BT-10Ask the customer for reference and enter it in the field provided for this purpose.
‘Endpoint scheme missing,Electronic address without schemaNot only the identifier, but also its identification scheme match with the recipient data.
Totals do not matchItems, taxes, surcharges or reductionsCalculate from the position amount and check internal decimal places.
Reason for exemption is requiredTax category triggers a ruleFirst, check the tax treatment, then supplement the appropriate reason.
PDF looks right, test failsImage and structured data differView the XML content and compare it with the original data.
File valid, recipient rejectsAdditional recipient or process requirementCheck references, accepted version and shipping route based on the feedback.

The table is a guide, not an automatic fault diagnosis. A message can have several causes. For a request to the software provider, the rule identifier, the test bench used and an anonymized example are much more helpful than a single screenshot with "invalid,. Personal or confidential invoice data should not be uploaded unchecked into public audit offers.

Five confusions that can be easily avoided

"XML is automatically called XRechnung.

No. XML is the technical language. First, content and rules show which document type is actually available.

"Peppol replaces ZUGFeRD or XRechnung.

This is not the way to compare the network and the transported documents.

"Without Leitweg-ID no e-invoice is possible.

This is incorrect for general B2B invoices. The references required depend on the particular process.

"A green test confirms everything.

It confirms the result of the concrete technical examination. Content of performance, eligibility and tax classification still need attention.

"Zero tax is always the same case.

Tax exemption, zero rate, reverse charge and lack of taxability are different categories.

What versions are current on 17. September 2026?

Versions deserve a look: "Newly published, does not automatically mean "already binding,. Especially with XRechnung this distinction is important in September 2026.

The audited status of this contribution
StandardUpdatedClassification
XRechnungVersion 3.0 · Specification 3.0.2Also the current standard; current summer bugfix bundle of 31.08.2026.
XRechnung 4.0.0Preliminary specification of 15.09.2026 (PDF)No successor version in force yet. Do not confuse the prior publication with an immediate conversion obligation.
ZUGFeRD / Factur-X2.5.2 / 1.09.2Package of 04.08.2026; valid since 01.09.2026.

Sources for the version specifications: KoSIT: XRechnung versions and bundles and Ferd: ZUGFeRD 2.5.2 / Factur-X 1.09.2The availability published there does not automatically indicate which version a single software or a particular portal is already processing.

What does this mean for invoices from Excel?

A familiar Excel template and a structured e-invoice perform different tasks. Content can be captured and designed in Excel. For the structured output, the individual data must then be clearly assigned. A nice print view alone does not solve this problem.

For the entry with TabellenFaktura, three things should be available: an anonymised model calculation, the requirements of the actual recipient and a simple test case with well recalculated amounts. After that, it is checked whether positions, taxes, references and sums in the generated document arrive correctly. Which formats and functions support the specifically used version must be checked regardless of the general state of a standard.

For further information: ZUGFeRD or XRechnung?, Create ZUGFeRD invoice and Set up future-proof calculations with Excel.

FAQ

Frequently asked questions

What is the difference between e-invoice and PDF invoice?

A e-invoice contains structured invoice data for electronic processing. A normal PDF provides a readable page. ZUGFeRD connects both: a PDF/A-3 document and embedded XML data that must meet the requirements of the selected profile.

What distinguishes XRechnung from ZUGFeRD?

XRechnung describes structured billing data according to concrete German rules and is typically exchanged as XML file. ZUGFeRD combines PDF and XML in hybrid use. The format that fits depends on the recipient's requirements and the intended workflow.

Are XML and XRechnung the same?

No. XML is a general language for structured data. XRechnung is a standard of billing with certain content and rules. A file can contain XML without being an invoice or a valid XRechnung.

Does each e-invoice need a Leitweg-ID?

No. A Leitweg-ID is used for the allocation in the public exchange of invoices. For ordinary B2B invoices there is no general Leitweg-ID obligation. Other buyer references or electronic addresses may still be required depending on the standard and process.

Is Peppol a billing format?

No. Peppol is a network with rules for electronic document exchange. The transported invoices must match the document types and requirements provided there. Network, billing format and technical syntax are different levels.

What does BT-10 mean in an error message?

BT-10 is the buyer reference. It supports the assignment to the recipient. For authorities, this is often the Leitweg-ID, for private companies, it can be another predefined reference. The correct value should be asked for by the customer.

Is a successfully validated invoice automatically tax correct?

No. The validation checks technical and defined technical data rules. Whether a service was actually provided, the price was agreed or the tax classification was correct, must be additionally checked.

Is XRechnung 4.0 already valid in September 2026?

As of 17 September 2026, XRechnung 3.0 with specification 3.0.2 remains current. Specification 4.0.0, published on 15 September, is preliminary and is not yet the applicable successor version.

Does every e-invoice have to be digitally signed?

A qualified electronic signature is not required in general. Origin and integrity must be ensured; the VATright allows different procedures for this. The signing of a software must be considered separately.

Can a Excel file be sent directly as e-invoice?

A normal Excel calculation is not yet a structured e-invoice according to the relevant requirements. The data must be transferred to an appropriate format, correctly assigned and checked. Excel can remain the starting point for data collection.