Skip to content

Agent platform

AI agent for invoices and documents: from receipt to handover

The agent receives invoices, delivery notes and order confirmations, reads them and presents whatever it is not sure about.

In short

The document agent reads a document twice independently, checks it against your data and presents every uncertain field to a person with a scan excerpt. Fields read with certainty move on with the document.

Updated: November 2026

When a document goes to a target system

A document goes to a target system only once it has been read with certainty or confirmed by a person. The document types and how they are split across the modules are in the table further down.

In shadow mode, where every document type in ENGIVERITY starts, the handover produces only a preview marked provisional, and the switch for each target system is off from the start. The path into daily work is described on the page Dry run and shadow mode.

Six steps

The flow from receipt to handover

01 Receipt The document arrives by upload, photo, folder, interface or mailbox.
02 Two reading passes Two independent passes capture each field.
03 Check The system matches the document against the mirrored state of your ERP.
04 Presentation Every uncertain field goes to a person with a scan excerpt.
05 Confirmation A person confirms, corrects or discards the document.
06 Handover In live operation the confirmed document goes to the target system as a posting.

When a document counts as certain

In ENGIVERITY a field counts as certain only if all five conditions hold at the same time. A single exception is enough, and the field goes to a person for confirmation.

  1. Both reading passes return the same value.
  2. The certainty of both passes lies above the threshold.
  3. The document carries no conspicuous mark such as a strike-through.
  4. The field is legible.
  5. The check against your data has passed.

Document types

What is checked for each document

Document types and checks
Document typeCheck
Incoming invoice (Documents, ERP) Totals, tax, IBAN and VAT identification number, possible duplicate.
Outgoing and progress invoice Calculation errors, tax, due date, link to customer, project and order, duplicate and the sequence of progress payments. Plus an account assignment proposal with a reason.
Delivery note, withdrawal list, handwritten slip Part number in the master data, open order, unit, storage location and stock. A tick means taken, a red circle means to be clarified, and only ticked lines are posted.
Order confirmation Per line quantity, price, date and unit against the order, with tolerances. The deviation is stated in words.
Quotation Matching to the right enquiry by supplier, lines and date. If the match stays ambiguous, a person chooses.
Timesheet and hour record Project number including transposed digits, work step, daily and monthly total, weekend, public holiday, future dates and duplicate lines. Only with the agreement of data protection and the works council.

Invoice mail from the mailbox

The ERP has an invoice intake for invoice emails, so far in use in a customer-specific setup. It polls the mailbox at short intervals, checks for spam, bundles all attachments with the document, recognises the supplier and matches articles by article number.

An automation works only with a certainty threshold, a value limit and an emergency stop. If someone switches it off, every document waits for a person. Even without automation the invoice is prepared, and approval rests with accounting.

Cleaning up the article master

Before a changeover it pays to look at your own article master. A check run goes through the mirrored master and looks for eight kinds of cases.

  • The same part appears twice in the master.
  • A number is assigned more than once.
  • A number is attached to the wrong part.
  • The manufacturer number sits in free text.
  • A material exists in several spellings.
  • A typo has altered a number.
  • A number lies outside the numbering scheme.
  • A mandatory detail is missing.

Every case gets a proposal with a one-sentence reason, for example which number should stay because the part is in stock and used in running projects. People decide, also in bulk or through an Excel file. The result is import files marked as provisional.

Interplay

Which module carries which part

Modules of document processing
ModuleRole in the flow
Documents Recognition, clarification cases and export of documents with approval chains. More under <a href="/en/plattform/dokumente/belege-erkennen">recognising documents</a> and <a href="/en/plattform/dokumente/e-rechnung">e-invoicing</a>.
ENGIVERITY Documents for warehouse, purchasing, accounting and time recording, in shadow mode first, with confirmation screen and test week.
ERP and CRM Invoice mail from the mailbox in the customer-specific setup, the draft of the incoming invoice and the approval run.

What does not happen automatically

The agent triggers no payment. Every confirmation and every handover is entered in the log. Anyone who also wants a second person switches on the four-eyes principle for invoices.

The rules for permissions, limits and emergency stop are described under approval and control.

Questions and answers

Questions about document processing

What happens with illegible documents?

An illegible field never counts as certain. It goes to a person with the scan excerpt, who confirms the value, corrects it, has it read again or discards the document.

Who confirms the documents?

The role for the respective document type, that is warehouse, purchasing, accounting or time recording. Administrators may work in every group, except on time recording lines.

Which document types are covered?

In ENGIVERITY delivery notes, withdrawal lists, handwritten slips, quotations, order confirmations, outgoing and progress invoices as well as hour records and timesheets. The hour records only once data protection and the works council have agreed. Incoming invoices run in Documents and in the ERP.

Which accounting system can be connected?

The handover runs through an interface or as a file, for example as a posting batch. We clarify in conversation which system receives the data on your side.

Which documents do you still read by hand today?

We look at your document types and plan the test week to begin with.