Skip to content

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

Switched on per tenant Many intake routes Drag and drop and the watched folder are available straight away. Mailbox, phone capture and the interface are switched on per tenant. Mails and ZIP archives are split into single documents.
First and second read Every document without an XML part is read independently by two different engines. If they differ, an arbitration step decides.
A source for every field A value only counts as certain with a source in the document. The review view shows the spot in the image.
E-invoices directly XRechnung and ZUGFeRD are read from the XML, without a detour through the image. E-invoicing in detail
Splitting bundled scans The system separates several documents in one file at reliable page breaks, otherwise with a suggestion to confirm.
Problem files are kept too Even empty, damaged or password-protected files are stored and appear as a clarification case with the original. Document recognition in detail

Check, clarify, approve

What happens between reading and handover

Rule checks Totals, tax, IBAN with check digits, VAT ID and mandatory fields are recalculated.
Clarification cases and duplicates The system names the reason, the fields and a suggestion. A file that arrives twice is recognised as a duplicate.
Review view with approval stamp Document and fields sit side by side. After approval the document is locked, and every change is logged.
Switched on per tenant Approval chains Rules by document type, amount, partner, cost centre and site. Several levels, deputies, reminders and escalation. The same person never approves two levels of one chain.
Switched on per tenant Account assignment proposal Ledger account, cost centre and tax key with a reason. A person confirms. No model is trained.
Switched on per tenant Master data matching and cases Line items against the article master, senders against the partner master. Order, delivery note and invoice are brought together.

Document types and library

More than invoices

Core document types Invoice, credit note, delivery note, contract, order confirmation, purchase order and quotation.
Switched on per tenant Document library Payslip, official notice with a calculated deadline, certificate, reminder, termination letter and correspondence.
Switched on per tenant Contract areas Contract areas with fields of their own, such as rent, insurance, leasing, energy and data processing agreements.

Answers and workflows

Ask questions, keep deadlines in view

Switched on per tenant Answers about your documents You ask in natural language. Every answer names the document, page and field.
Switched on per tenant Workflows Triggers such as intake, approval, clarification case or deadline, conditions, and actions such as mail, folder or webhook.
Switched on per tenant Deadlines in view Notice, contract end, early-payment discount and due-date deadlines trigger reminders through a workflow.
Signed webhooks Events go to a target of your choice, signed and over https only.

Export and payment

Handover to accounting and the ERP

Switched on per tenant Posting batch in DATEV format One line per tax rate. Before the export a preview shows errors and warnings, and errors block the download.
Switched on per tenant JSON and XML All documents can be exported with a schema. A continuous pull through the interface fetches new documents.
Switched on per tenant Connection to an ERP Approved documents go out by REST, MCP or as a file. A document sent again does not create a second entry.
Switched on per tenant Payment Payment status, payment proposal with early-payment discount, matching with the bank statement and protection of the bank details. The system sends nothing to a bank.

Tenants and operation

Several companies kept apart

Tenant separation Every tenant has its own database and its own files. Functions are switched on per tenant.
Roles and permissions Reader, editor and administrator. You also define which department may view, edit, approve or export which document types.
Your own look Accent colour with a contrast check, your own logo, tabs per document type and columns per department.

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

Document processing A stack is split into single documents and recognised by type. Fields are read with a certainty value, and sensitive passages are redacted.
Redaction with a second check A second, independent check verifies that every passage is covered. People correct what it finds in a dedicated workspace.
Data room Documents per property, customer or company with a checksum. Third parties get time-limited access to what is released for them.
Requirement lists and deletion concept Lists and tasks show what is still missing. Removing a document from the data room also removes its copies, redacted versions and search texts. A sync with OneDrive is possible.
Customer, company and vehicle files Documents are attached to the contact, and the company file shows in a matrix what is still missing. Bulk upload assigns documents by chassis number, licence plate or document number.
Invoice intake and e-invoices Invoices from mailboxes are collected, checked for spam and matched to the supplier. E-invoices are checked against EN 16931, and an approval controls posting. E-invoicing in detail

Flow

How a document moves through Documents

01 Intake A file, mail or the interface delivers the document
02 Recognise Determine the type, two reads, find sources
03 Check and clarify Apply rules, decide clarification cases
04 Approve Approval stamp or a chain over several levels
05 Hand over Posting batch, ERP output or webhook

Technical details

Properties at a glance

Technical details of Documents
PropertyDetail
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.

Where do documents pile up at your company?

We look at your intake and discuss which parts of Documents are worth it.