
A XRechnung is not a PDF with a new file name, but a structured billing data set. Each address, position, tax rate and payment amount is given a machine-readable meaning. This is exactly what makes the format powerful – and demanding. This guide explains the entire way from an existing Excel invoice to the professionally tested XML file, ordnates the legal situation 2026 and shows where most of the errors occur in practice.
A XRechnung is created by assigning complete billing data to the semantic model of the European standard EN 16931 and the additional rules of the standard XRechnung. The output is as XML in an approved syntax, regularly UBL or UN/CEFAT CII. Before dispatch, schema, business rules, sums, mandatory information and recipient requirements are checked. For invoices to public authorities, Leitweg-ID and defined transmission routes are often added.
What makes a XRechnung
The term "electronic invoice" has long been used for almost every digitally sent invoice. Since the recast of § 14 UStG, the delimitation is much sharper. A e-invoice must be issued, transmitted and received in a structured electronic format and allow electronic processing. A simple PDF is therefore not an e-invoice in the legal sense, but a different invoice.
The XRechnung meets this requirement as a purely structured data set. Unlike ZUGFeRD, the file does not contain an inbuilt invoice image. The XML is the invoice. A viewer can create a readable representation from it, but does not change the relevant technical data.
| Feature | Simple PDF | ZUGFeRD | XRechnung |
|---|---|---|---|
| Basic structure | visual document | PDF/A-3 with embedded XML | Structured XML file |
| Machine processing | not reliable without text recognition | via the XML part | directly via the XML |
| Readability for People | Direct | directly via the PDF | via a viewer |
| e-invoice according to § 14 UStG | yes | from version 2.0.1, except for the MINIMUM and BASIC WL | yes, with correct form and content |
| Typical use | only within the transitional rules or outside the obligation | B2B with desired invoice image | B2G and structured B2B processes |
The file extension .xml is not a quality feature alone. Any XML structure does not become XRechnung, just because fields with invoice values are included. Only the interaction of approved syntax, semantic data model, XRechnungs business rules and correct content results in a compliant invoice.
Why the topic is economically relevant
The conversion does not only affect companies with large ERP systems. According to the Federal Statistical Office 2023, about 3,2 million companies and thus 99,3 percent of the companies considered were small and medium-sized enterprises. 82,6 Percent were micro enterprises. Especially there, invoices often arise in manageable, individually grown processes – often with Excel.
Small and medium-sized enterprises in Germany
Source: Federal Statistical Office, Business Structure Statistics 2023, level 11. September 2025.
The figures explain why a technically strong e-invoice solution does not automatically have to be a heavy accounting system. The largest economic user group consists of companies whose accounting process involves rather few people, own templates and clear work routines. Nevertheless, the technical depth of the standard remains the same.
e-invoice Obligation 2026: What is the deadline?
For domestic B 2B transactions, e-invoice has been the legal rule since 1. January 2025 The practical requirement for issuing is, however, governed by transitional regulations. The date of the transaction, not only the date of issue of the invoice, is decisive.
Exceptions remain important. Small amount invoices up to 250 Euro and travel cards can be issued and transmitted as other invoices. Certain tax-free transactions are also excluded. Small business owners are exempt from the issuing obligation according to the current BMFF presentation, but must be able to receive e-invoices. For a reliable classification, the concrete turnover always counts.
B2B and B2G requirements must be distinguished. The B2B VAT rules under the German VAT Act (UStG) and the e-invoicing regulation for federal government contracts have different thresholds, additional information requirements and transmission channels. Invoices to federal, state or local authorities are also subject to the rules of the respective customer and platform.
Four levels: EN 16931, XRechnung, syntax and transport
Many misunderstandings arise because technical content, national rules, file structure and shipping are treated as one single "format". In fact, four levels are above each other.
EN 16931: the common technical language
The European standard defines a semantic core data model. A billing number is not called "Bt-1 because XML tags are numbered, but because Business Terms form a technical reference independent of the customer. The same field can look completely different in UBL and CII and still bear the same meaning.
XRechnung: Germany’s Core Invoice Usage Specification
XRechnung is a national application specification of EN 16931. It supplements or tightens rules without changing the European model as desired. The coordination office for IT standards publishes the normative specification and the technical components as bundle. According to the current overview XRechnung 3.0 is decisive; the bundle 3.0.2 Winter 2025/26 is replaced by 31 January 2026.
UBL and CII: two ways to achieve the same content
UBL 2.1 and UN/CE Fatt Cross Industry In registries are permitted syntaxes. Syntax conversion is therefore not simply a renaming of elements. Namespaces, element hierarchies and individual picture rules differ. A good process internally works with unique technical billing data and generates the required syntax from it.
Transport is not format
A valid XML can fail on the wrong portal, with a wrong recipient address or via an unauthorized channel. Conversely, Peppol does not make a faulty file correct XRechnung. File quality and delivery require separate checks.
Create XRechnung: the complete process
A robust process starts before XML generation and does not end when the file is saved. Eight steps form a resilient process chain.
The order is essential. Lack of payment data can sometimes be categorized as an empty or optional field. However, an ununderstood control logic cannot be repaired by XML-Syntax. The earlier technical ambiguities become visible, the less the effort is at the end.
Required fields: from accounting to BT field
A XRechnung requires mandatory VAT data first. In addition, there are requirements from EN 16931, XRechnung and, if necessary, from the order process. For the Federal Administration, § 5 calls E-RechV among others Leitweg-ID, payment conditions, bank details and e-mail address of the invoicer. Order and supplier numbers become mandatory if they were communicated at the time of the order.
| Technical information | Business Term | Practical importance | Typical error source |
|---|---|---|---|
| Invoice number | BT-1 | unique document identifier | Spaces, dublettes or subsequent changes |
| Invoice date | BT-2 | Date of issue | Confusion with date of performance |
| Type of invoice | BT-3 | Invoice, correction or credit | wrong type of document |
| Currency | BT-5 | ISO currency of the invoice | Currency only available as visible symbol |
| Buyer Reference | BT-10 | regular Leitweg-ID for federal accounts | Missing or assigned to the wrong job |
| Order Reference | BT-13 | Link to procurement | Order number only in the free text |
| Salesperson Name | BT-27 | legal name of supplier | Trademark name instead of invoice issuer |
| Supplier number | BT-29 | Internal identifier of the contracting entity | confused with customer number |
| Seller e-mail | BT-43 | Electronic contact information | for B2G not in the designated field |
| Purchaser name | BT-44 | Legal recipients | Deviating department without correct reference |
| Position description | BT-153 | clearly verifiable performance | on general terms such as ‘working, |
| Position quantity | BT-129 | Quantity charged | Text ‘Pair, without structured quantity and unit |
| Unit code | BT-130 | Standardised unit of measurement | free German abbreviation instead of code |
| Net position price | BT-146 | Price per unit of price excluding VAT | Gross price or total price registered |
| Amount | BT-115 | Amount actually due | Prepayments or rounding missing |
The table is a guide, not a complete specification. Business cases with tax exemption, reverse charge, intra-Community delivery, interim invoice, discount, surcharges or multiple tax rates require additional information and rules.
Master data are not secondary
In XML invoices, every unclear master data maintenance is more noticeable. The visible letterhead cannot replace a missing structured information. The legal name, the full address, tax or VAT identification number, buyer data, e-mail contact, IBAN and, if applicable, BIC are particularly important. Trademark name and legal person must be clearly kept apart.
Service description with sufficient expressiveness
All VAT mandatory information must be in the structured part according to the BMF management concept. A reference to an unstructured annex is not sufficient if the necessary service description can be found there. Additional details may be provided as an attachment; the structured invoice itself must, however, clearly and easily be verified.
Continuous example: from the Excel to XRechnung
A simple example shows how visible table values are translated into technical data. The starting point is a consulting invoice with two positions.
The fill-in template contains a neutral sample sender, clearly marked placeholders for the invoice recipient, prepared position lines and verified calculation formulas. Before using all red placeholders and at least one invoice position must be completed. The automatically set invoice date should be stored in a completed invoice as a fixed value. For B2G cases, additional information such as a Leitweg-ID may be required. The Excel file itself is not yet XRechnung; the structured XML file is created only when conversion is done. For the subsequent creation of a XRechnung or ZUGFeRD file from the completed template, TabellenFaktura The
| Pos. | Description | Quantity | Unit | Net unit price | Line sum |
|---|---|---|---|---|---|
| 1 | Establishment of an invoice template | 2 | Hour | €95.00 | €190.00 |
| 2 | Examination and documentation | 1 | Flat rate | 140,00 € | 140,00 € |
| Net total | 330,00 € | ||||
| 19 % VAT | 62,70 € | ||||
| Amount | 392,70 € | ||||
In a table view, "hour, and "put-down, sufficient" works. For XML, each line needs a standardized unit code. The position description remains text, while quantity, unit, price, and tax category belong in separate data fields. The tax amount is not only taken as a finished number: tax base, tax rate, category and amount must logically match.
1 × 140,00 € = 140,00 €
190,00 € + 140,00 € = 330,00 € net
330,00 € × 19 % = 62,70 € VAT
330,00 € + 62,70 € = 392,70 € Number amount
The XML does not store the optical position of a cell, but the meaning of the value. "B17, is meaningless for a standard invoice. Only the assignment "B17 contains the invoice number, creates a resilient model. This is exactly why a uniquely cleanly configured template is much more reliable than a purely optical text recognition.
Calculation logic: why a cent can stop an invoice
XRechnung checks relationships between values. A plausible total is not enough if the intermediate values do not rise. Typical equations include net line amounts, net document amount, surcharges and deductions, tax base, tax amount, gross sum, advance payments and payment amount.
- Line level: The quantity and price must be the net amount of the line, taking into account a unit price, discounts and surcharges.
- Tax level: The same tax category and the same rate are combined into a tax base.
- Document level: The sum of net amounts net of lines plus additional amounts in the document and less any additional amounts in the document gives the net amount of invoices.
- Payment level: Gross amount minus amounts already paid plus rounding gives the amount due.
Excel can expect more decimal places internally than visible ones. Two cells show for example 10,01 Euro each, although internal 10,005 Euro are stored. The visible addition and the internally exported sum may differ. A reliable export therefore needs a deliberately defined rounding strategy and must not rely exclusively on cell formatting.
Display, calculation and export must use the same technical logic. An XML generator should not attempt to tacitly compensate differences by changing positions. Deviations are made visible before output and are professionally clarified.
Validation in five levels
"Files have been created, is not a test result. A robust validation examines at least five levels. Although the BMF does not refer to validation as an immediate prerequisite for tax recognition, it expressly recommends that it be used to prevent errors when creating and shipping.
1. Well-formed XML
- correctly closed elements
- valid character encoding
- clean namespaces
- no corrupted file
2. Schema
- Permitted elements and order
- correct data types
- valid cardinalities
- suitable UBL or CII structure
3. Business rules
- EN-16931 rules
- XRechnungs rules
- Sums and dependencies
- Code lists and mandatory fields
4. Business content
- Real recipient of the invoice
- The applicable tax case
- understandable performance
- correct payment and reference data
5. Process
- Current level of regulation
- Approved transmission channel
- Receiving or error status
- Unchanged archiving
The result
- Error: Invoice not ready
- Warning: Technically tested
- Note: Note context
- Stocks: Nevertheless, perform visual inspection
A technical success report does not prove that the agreed performance, the correct customer or the correct bank account is actually included. The validator does not know the contract or the real performance period. Conversely, a technically correct calculation can be technically unusable if a mandatory code or element is missing.
Correctly classify typical error messages
| Error Image | Probable Cause | Meaningful Trial |
|---|---|---|
| Buyer reference missing | BT-10 has not been used | Order documents and check the notified Leitweg-ID for B2G |
| Total of lines is not correct | Rounding, price unit or discount mistreated | Track each row of unrounded baselines |
| Excise duties incomplete | Tax category, rate or justification missing | Match tax case by item and document level |
| Endpoint ID invalid | electronic address or schemeID does not fit | Compare recipient and transmission profile |
| Unit code unknown | free abbreviation instead of permitted code | assign understandable unit to a valid code list |
| IBAN formally invalid | Spaces, typos or incomplete account data | Check normalised IBAN and payment method |
| XML is displayed unreadable in the browser | no stylesheet or viewer available | Visualize file with a XRechnungs viewer; readability is not equal to validity |
| Portal rejects valid XML | additional portal, receiver or channel rule violated | Check file size, attachment, Leitweg-ID, registration and channel specifications |
Do not equate warning and error
A mistake usually violates a mandatory technical or professional rule. A warning may indicate an unusual but permissible constellation. A professional process blends warnings not out at all, but documents why they are acceptable in the concrete business case.
Document version of the Validators
A file can deliver different results with an old test package than with the current bundle. Standard version, test date and validator stand are required for reproducible tests. This is particularly valuable for long-term contracts and recurring invoices.
XRechnung to authorities: Leitweg-ID and additional fields
For invoices to the Federal Administration, Leitweg-ID serves to address and forward to the responsible invoice recipient. It is communicated by the client and entered in the buyer reference BT-10. Invoice holders do not need their own Leitweg-ID.
The Leitweg-ID does not replace the buyer's address, order number or supplier number. It answers another question: Which organizational point within the administration should the invoice be directed to? Even a formally plausible but technically incorrect Leitweg-ID can lead to rejection or misdirection.
In addition to the tax information, the Federal Administration states Leitweg-ID, payment conditions, bank details and e-mail address of the invoicer. Supplier and order numbers are required if they were transmitted at the time of the order. Project reference, contract reference, award reference, billing object and service period can be additionally decisive depending on the order.
Federal states and municipalities use different platforms and national legal forms. Therefore, the examination of the concrete invoice recipient is part of the order acceptance – not only at the end of the invoice.
XRechnung send: select channel by receiver
In general B2B use, e-invoices can be transmitted by email, through a portal, via an interface or over an agreed network, among other options. Following consolidation, OZG-RE is the central platform for Germany’s federal administration. It supports web entry, uploads, email and Peppol.
| Channel | Suitable for | Strengths | To be noted |
|---|---|---|---|
| small to medium amounts and direct B2B vote | known procedure, low entry hurdle | correct address, file name, system rules and proof of delivery | |
| Portal upload | Low B2G invoices | Direct portal check and status display | Registration, manual steps and recipient assignment |
| Weaver version | Individual cases without own creation software | no local XML generation needed | Double recording, limited reuse and manual control |
| Peppol | Regular or large quantities | Standardised machine-to-machine exchange | Service provider, participant identifier and technical connection |
| Direct API | Integrated B2B processes | Automation and status feedback | Individual interface, authentication and operation |
When sending an e-mail to the OZG-RE, stricter rules apply than for a normal message: one e-invoice per e-mail; additional external attachments can lead to fault. Accounting documents must be embedded in the XML according to the respective specifications or linked via intended functions. Subject and message text do not replace invoice data.
Delivery is a status, not a click
The shipping button documents only the output. For the process completion, at least file copy, recipient, time, channel and feedback are relevant. For platforms, technical acceptance, formal examination, technical processing and payment can be separate status. An automated receipt is not yet a payment release.
Correction, credit, discount and attachments
Correction
If the original turnover is subject to an e-invoice obligation, a correction must be made as e-invoice. The correction document needs a clear reference to the original invoice and the technically appropriate invoice type. An already sent XML file should not be changed quietly and stored again under the same name.
Credit
The tax term "crediting" refers to a billing by the recipient of the benefit. In everyday life, the same word is often used for an accounting correction. In structured data, it must be clear which business case is actually present. A wrong translation of the visible word into the document type can reverse the technical meaning.
The amount of the deductions and the final invoice
Advance payments, partial fees and amounts already invoiced must be presented in such a way that the remaining amount of the payment is comprehensible. According to the BMFF-FAQ, the deduction of partial fees collected can be made in an unstructured annex in the case of a final invoice if the structured part expressly refers to this. For practical processing, a structured picture remains as clear as possible.
Annexes
Performance certificates, hourly notes or detailed documentation can be added to an invoice. However, mandatory information may not be completely outsourced to an installation. Technically, plants must be embedded or substantiated according to the selected syntax and the specifications of the transmission channel. File type, size and security check are own acceptance criteria.
Archiving: the XML is the original
According to § 14b UStG, incoming and outgoing invoices must be kept for eight years. In the case of an e-invoice, at least the structured part must remain intact in its original form. A subsequently generated PDF view does not replace the received or sent XML.
Store
- original XML file
- embedded accounting assets
- relevant signature evidence if used
- Where necessary, transmission and error protocols
Organisational security
- Protection against unnoticed modification
- Retrieval by number, customer and period
- Readability and machine evaluation
- Backup, Recovery and Documented Process
The file name can support the search, but is not the only order mechanism. Unique number circles, unchangeable original files, comprehensible correction chains and regularly checked backups have proven themselves. In cloud storage, access rights, export possibilities, contract end and storage location are also counted.
Create XRechnung from Excel: when this is useful
For many small businesses, Excel remains the familiar tool for accounting. Spreadsheets can calculate performance, map individual layouts and record recurring master data. However, they do not know either EN 16931 or XRechnung on their own. The crucial question is therefore not "Excel or e-invoice?", but "How are table values reliably transferred to structured billing data?
Suitable starting point
- one or a few stable invoice templates
- manageable number of invoices
- clearly defined cells for billing and customer data
- Table positions with consistent columns
- conscious release of each invoice
Warning signals for a wider process
- several persons assign parallel invoice numbers
- very high quantities of receipts or complex release chains
- many companies, currencies or international tax cases
- automatic matching with stock, time recording and accounting
- Peppol or API shipment with ongoing status processing
An extension of Excel can close the gap between template and standard by assigning cells to professional fields, by codifying units and tax cases, by creating XML and by validating the invoice. It does not replace tax assessment and no organisational responsibility. Its value lies in the reproducible translation of already existing billing data.
How TabellenFaktura structured the process
TabellenFaktura works locally on the Windows PC and integrates the existing Excel template into a guided process. Billing fields and position columns are assigned once. Understandable information such as "piece, or "hour, can be assigned standardized codes. Before output, mandatory data, computational relationships and technical rules are checked.
Depending on the recipient, a XRechnung or a ZUGFeRD invoice is created. The structured view remains controllable before a file is released. Billing content does not have to be transferred to an online converter or a general AI for conversion. Thus, the approach combines the flexibility of a grown Excel template with a comprehensible e-invoice process.
A good e-invoices solution not only generates XML. It explains which field is missing, which calculation is not performed and which recipient request is affected. First understandable diagnosis makes a technical standard a manageable workflow.
Decision matrix for the right way
| Situation | Appropriate approach | Reasons |
|---|---|---|
| Individual invoice to an authority | Web version or portal | No own export process required |
| Regular invoices from stable Excel template | local Excel extension | Template is retained, assignment is reused |
| Many bills from the commodity industry | Integrated invoice or ERP system | Master data, number circle and booking interlock |
| Large quantities with regard to the authorities | Peppol or API connection | automated shipping and status processing |
| complex Group and country requirements | specialized e-invoicing platform | several formats, networks and compliance rules centrally controllable |
What ViDA means for the next stage
The EU’s ‘VAT in the Digital Age’ package, finally adopted in 2025, links e-invoicing more closely to digital VAT reporting. From 1 July 2030, cross-border B2B transactions within the EU are intended to be subject to digital reporting requirements based on electronic invoices. E-invoices therefore become structured data sources for timely reporting systems as well as documents exchanged between businesses.
For today's processes, this does not mean that every invoice is transferred to the cloud. Data quality, interoperability and reliable structured fields are crucial. A locally generated, norm-compliant data set can have the same semantic quality as a cloud calculation. Future reporting paths can require additional interfaces, status information and shorter response times.
Long-term security is therefore less created by a catchphrase than by clean foundations:
- Invoice data is structured professionally rather than optically.
- Standard versions and code lists can be updated.
- Format, transport and archiving remain separate, verifiable building blocks.
- Original data can be exported completely and stored independently.
- Errors and status are documented for people.
Practice check before shipping
The following checklist bundles technical, technical and organizational controls. It is suitable as a release routine regardless of the program used.
Business case
- correct type of invoice
- B2B or B2G requirement clarified
- Tax case subject to technical examination
- Date of performance or period available
Parties
- legal names and addresses complete
- Tax number or VAT ID no. suitable
- E-mail and electronic addresses correct
- Trade mark and invoice issuer not confused
References
- Leitweg-ID if needed
- Order and supplier number
- Contract, project or award reference
- original invoice for correction
Line items
- Unique performance descriptions
- Quantities and unit codes
- Price unit, discounts and surcharges
- Tax category per item
Totals
- Line sums are comprehensible
- Tax base per rate correct
- Gross, advance payment and payment amount in accordance with the rules
- Rounding differences clarified
Payment
- IBAN and account holder correct
- Maturity or condition of payment
- Use clearly
- Discount structured and understandable
Technology
- correct syntax and current version of XRechnung
- Scheme and business rules passed
- Warnings professionally evaluated
- File controlled in a viewer
Shipping and Archive
- Authorised receiver channel
- Embedded systems correctly
- Status or confirmation documented
- Original XML archived unchanged
Glossary: central terms in one sentence
- Business Term (Bt)
Syntax independent defined technical information of the EN 16931, for example the invoice number.
- Business Group (BG)
Group of logically related Business Terms, such as an address or payment order.
- CII
Cross Industry Invoice by UN/CEFACT, an approved XML Syntax for European billing data.
- CIUS
Core Invoice Usage Specification; specifies how the European core invoice data model is used.
- EN 16931
European series of standards for the semantic data model of electronic invoices.
- Leitweg-ID
Addressing identifier for public administration invoice recipients, for federal accounts in BT-10.
- OZG-RE
Online access law-compliant billing platform of the Federal Government.
- Peppol
Standardised network and rules for the electronic exchange of business documents.
- UBL
Universal Business Language, a popular XML Syntax for XRechnung and other e-invoicesprofiles.
- Validation
Checking an invoice against XML structure, scheme, business rules and technical requirements.
A XRechnung is the precise translation of a real business process into standardized data. The quality is not created in the last export click, but through clear master data, comprehensible positions, correct control logic, current rules, multi-stage validation and documented shipping. A well-structured Excel template can continue to be the starting point for this if a specialized solution takes over the technical assignment and technical examination.
Create XRechnung and ZUGFeRD from Excel →
The basis for the FAQ of the Federal Ministry of Finance about e-invoice (as of March 2026), § 14 UStG, § 14b UStGThe Versions and bundles of the KoSITThe information of the Federal Administration on Mandatory information and Transmission channelsThe SME data of the Federal Statistical Office and the ViDA timetable of the Council of the European Union. State of the article: 2. September 2026. The article is for general information and does not replace tax or legal individual consultation.
For benefits under the exemption from small business, the contribution e-invoice for small businessmen: obligations and accounting example the differences between reception, issuance and tax-free structured expenditure.
For the recipient page, the guide explains Open, read and check XRechnung suitable viewer, control of XML data and handling of different invoice amounts.
Frequently asked questions
What is a XRechnung?
A XRechnung is a structured XML invoice according to the German standard XRechnung based on the European standard EN 16931. It contains machine-readable invoice data and basically no built-in PDF invoice image.
How can a XRechnung be created?
Billing data is assigned to technical fields, output in an acceptable XML syntax such as UBL or CII and then validated against schema, EN-16931 rules, XRechnungs rules and recipient requirements.
Can a XRechnung be created from Excel?
Yes. A specialized extension can assign cells and position columns to a Excel template to the required accounting fields, add standardized codes, create XML and check technical rules.
Is a PDF file a XRechnung?
No. A simple PDF does not contain fully structured billing data and is therefore not considered to be XRechnung. ZUGFeRD combines a PDF/A-3 with embedded XML.
What is the difference between UBL and CII?
UBL and UN/CEFAT CII are two different XML syntaxes for technically comparable billing data. The elements and hierarchies differ, while the underlying Business Terms of EN 16931 retain the same meaning.
When is a Leitweg-ID required?
The Leitweg-ID is used particularly to address invoices to public-sector customers. For federal invoices, it belongs in buyer reference BT-10 and is provided by the customer. There is no general Leitweg-ID requirement for ordinary B2B invoices.
Does a XRechnung have to be validated?
The Federal Ministry of Finance does not refer to validation as an immediate requirement of tax recognition, but expressly recommends it for error prevention in the case of creation and dispatch. Recipient platforms may reject incorrect files.
How does a XRechnung become readable?
A XRechnung can be translated into a human readable display with a suitable viewer. The financial management also provides an e-invoicesviewer for XRechnung and ZUGFeRD via ELSTER.
How long must a XRechnung be stored?
According to § 14b UStG, the tax retention period is eight years. At least the structured part must be preserved intact in its original form.
Which XRechnung version is current in 2026?
The KoSIT runs XRechnung 3.0 as the current version of the standard. The technical package currently available for the article status is the bundle 3.0.2 Winter 2025/26 with version of 31. January 2026.
Can a XRechnung be sent by e-mail?
In the B2B area, email is a possible transmission route, provided the recipient requirements are met. The specifications of the respective platform apply to authorities; the OZG-RE allows e-mail, upload, Weber version and Peppol among others.
What does a XRechnungs validator not check?
A validator does not know the underlying contract and the real business process. He cannot therefore conclude whether the content of the service, customer, tax case or bank connection has been chosen correctly.