Documents
Receiving, checking and processing e-invoices
An XML invoice arrives, Beyonetix OS reads it, recalculates it and hands it to your accounting team together with its findings.
In short
Receiving e-invoices in Beyonetix OS (BEYOS) reads XRechnung and ZUGFeRD straight from the XML file, checks mandatory fields and totals, and puts the invoice up for approval together with all findings. It is meant for accounting teams that want to process structured invoices without retyping.
Updated: November 2026
Legal background
What the duty to receive means
Since 1 January 2025, companies in Germany must be able to receive structured e-invoices when they invoice another domestic business. The basis is section 14 of the German VAT Act as amended by the Growth Opportunities Act. The Federal Ministry of Finance letter of 15 October 2024 sets out the rules in detail.
A plain PDF without XML does not count as an e-invoice under these rules. Issuing e-invoices follows staggered transition periods. This page covers receiving.
This is no substitute for legal advice. Which deadlines and exceptions apply to your business is a question for your tax adviser.
Formats and profiles
The formats the system reads
| Format | Syntax | How it arrives | Check |
|---|---|---|---|
| XRechnung | CII, UBL | As a separate XML file or in a ZIP archive | In the ERP against EN 16931, in Documents totals, tax, IBAN and mandatory fields |
| ZUGFeRD 2.x | CII | XML inside the PDF, the PDF stays the document | In the ERP against EN 16931 |
| Factur-X | CII | XML inside the PDF | In Documents: totals, tax, IBAN, mandatory fields |
| ZUGFeRD 1.0 | CII | XML inside the PDF | In Documents: totals, tax, IBAN, mandatory fields |
| PEPPOL BIS 3 | UBL | As an XML file | In Documents: totals, tax, IBAN, mandatory fields |
Profiles and document types
Profiles, document types and what follows
ZUGFeRD defines profiles of different scope. The MINIMUM and BASIC WL profiles do not carry a complete invoice. In that case Documents takes over the header values and reads the line items from the image of the invoice.
Every e-invoice carries a type code. The system knows invoice, credit note, corrected invoice, partial invoice, self-billing and partial and final construction invoices. An unknown code shows up as a blocking finding, and a person decides.
Scope of the checks
In the ERP, the e-invoice module checks XRechnung and ZUGFeRD against EN 16931, including XML embedded in the PDF. Documents also reads ZUGFeRD 1.0, PEPPOL BIS 3 and Factur-X and checks totals, tax, IBAN and mandatory fields.
Check steps
How the ERP recalculates the invoice
| Check | What is checked | Effect on deviation |
|---|---|---|
| Mandatory fields | Invoice number, date, currency, names of seller and buyer, country and tax identifier of the seller, at least one line item | Blocking, important for an incomplete address |
| Document type | The type code is present and known | Blocking |
| Totals | Line items against net total, allowances and charges, tax per rate with commercial rounding, grand total and payable amount with prepayment, within a narrow rounding tolerance | Important |
| IBAN | Check digits per ISO 13616 | Blocking |
| VAT ID | Format and country code compared with the seller's country | Format blocking, country mismatch minor |
Findings
What happens with the findings in the ERP
Every deviation becomes a finding with a rule ID, a level and plain text. The levels are blocking, important and minor. The findings sit on their own tab on the invoice and in the record's history.
If an invoice has a blocking finding, it cannot be posted. Your accounting team opens the findings and resolves them, for example with the supplier. Once the findings are cleared, the invoice can be posted. Removing findings is reserved for accounting managers.
Once a day the system also compares the open amount in the ERP with the payable amount from the e-invoice. If the two differ, a finding appears. The system never books a payment by itself.
Intake
How the e-invoice gets into the system
In the ERP you upload XML files, PDFs with embedded XML and ZIP archives through the import assistant. The system looks for XML first. If it finds some, the values come straight from the file and text recognition stays off.
The system collects invoices from mailboxes at fixed intervals. Documents also accepts files from folders and offers an interface for systems that submit documents automatically. Mailboxes and folders are switched on per tenant.
Paper, scans and PDFs without XML go to document recognition.
- XML file, PDF with XML, ZIP archive
- Mailbox, folder, interface
- Without XML, continue with document recognition
Handover
From the invoice to the posting
The values read become a vendor bill in the ERP. The XML file or the PDF stays attached to the record, with the findings beside it. Your accounting team approves, and only then is the invoice posted.
For accounting the system exports posting batches and documents in DATEV format. Documents also passes approved documents to an ERP by REST, MCP or as a file. How the connection looks in your setup is settled in the project.
Limits
What this page does not promise
The ERP module recalculates the business rules of the standard. A check of the XML file against the schema files and the rule sets of XRechnung is not described here.
We make no statement about retaining e-invoices or about deadlines. The same holds for issuing your own e-invoices. We are happy to discuss both in the project, and the legal questions belong with your tax adviser.
Questions and answers
Questions about e-invoicing
Which e-invoice formats can be received?
XRechnung in the CII and UBL syntaxes, plus ZUGFeRD and Factur-X with XML inside the PDF. Documents also reads PEPPOL BIS 3 and ZUGFeRD 1.0. The XML can arrive on its own, in a ZIP archive or inside the PDF.
Do I have to print e-invoices?
How you retain e-invoices and whether a printout is needed is something to settle with your tax adviser. This is no substitute for legal advice. In the system the XML file stays attached to the record, so you can open it at any time.
How does the check work?
In the ERP, the e-invoice module reads the values from the XML and recalculates them. Mandatory fields, document type, totals, tax, IBAN and VAT ID are checked. Every deviation appears as a finding on the record. Documents checks totals, tax, IBAN and mandatory fields for its formats.
What happens to PDF invoices without an XML part?
In BEYOS Documents they go through document recognition. Two independent engines read the image, disputed fields go to arbitration, and a person decides clarification cases. Whether every document is also approved is set per tenant. In the ERP, invoice intake reads such invoices with text recognition and puts them in front of a person for review.
Can I also submit e-invoices through an interface?
Yes. Documents has a REST interface with an API key per tenant. Through it you can submit files and fetch checked documents again.