Beyonetix OS module
Documents: document intake, data room and files
Documents arrive, get read, checked and handed over. In the ERP there is also a data room, files and the receipt of e-invoices.
In short
Documents is the Beyonetix OS (BEYOS) module for documents of every kind. It accepts invoices, delivery notes and contracts from any source, reads them with a source reference and hands them on after checking. It is meant for accounting, purchasing and administration.
Updated: November 2026
Who it is for
What it is about and who it is for
Documents has two parts. BEYOS Documents is the standalone, multi-tenant application for documents, from the incoming invoice to the contract. In the ERP, a data room, files, document processing and invoice intake complete it.
Anyone who wants to question a large archive that has grown over the years is better off with RETRAYA. Documents sorts, reads and passes on what arrives every day.
- Accounting: check and pass on invoices
- Purchasing: match order, delivery note and invoice
- Administration: contracts, deadlines and files
- IT: submit and fetch documents through an interface
Intake and recognition
Getting documents in and reading them
Check, clarify, approve
What happens between reading and handover
Document types and library
More than invoices
Answers and workflows
Ask questions, keep deadlines in view
Export and payment
Handover to accounting and the ERP
Tenants and operation
Several companies kept apart
In the ERP
The second part of Documents works inside the ERP. Document processing, data room, files and invoice intake run there, with the check of e-invoices as part of it.
Document functions in the ERP
Process, file, share
Flow
How a document moves through Documents
Technical details
Properties at a glance
| Property | Detail |
|---|---|
| Intake routes | Upload, watched folder; switched on per tenant: mailbox, phone capture, REST interface |
| Input formats | PDF, images, office formats, text, mail, ZIP, XRechnung, ZUGFeRD |
| Output formats | JSON, XML with schema, posting batch and master data in DATEV format |
| Interfaces | REST with a description, API key per tenant, pull of new documents, signed webhooks, ERP output by REST, MCP or file |
| Roles | Reader, editor, administrator, plus department and site |
| Tenants | Own database and own files per tenant |
| Languages | Interface in German, reading of German and English documents |
| Data path | Both reads on own infrastructure, external arbitration optional and switchable off per partner |
Questions and answers
Questions about Documents
Who checks the results of the recognition?
Every document without an XML part is read independently by two engines, and every value read carries a source. For e-invoices the XML is authoritative. Whatever stays disputed lands with a person as a clarification case. Whether an approval is also required is something you set per tenant.
Which e-invoice formats are supported?
Documents reads XRechnung in CII and UBL, plus ZUGFeRD and Factur-X with embedded XML. The check against the EN 16931 standard runs in the ERP. The details are on the e-invoicing page.
What happens if a document cannot be assigned with certainty?
Then the system does not guess. It shows candidates, and a person confirms the assignment.
Does Documents also run without an ERP?
Yes. Documents is an application of its own and passes approved documents on by REST, MCP or as a file. Which connection suits your environment is settled in the project.
How does an account assignment proposal come about?
The system proposes ledger account, cost centre and tax key and names the source of the proposal. A person confirms or changes it. No model is trained. We switch the function on per tenant.
Where do my documents go during recognition?
Both reads run on Documents' own infrastructure. An external arbitration step is optional, can be switched off per partner and is enabled by platform administration per tenant only.