Document processing11 min read

Intelligent document processing (IDP): what an operated agent takes over

Contents

Intelligent document processing (IDP) means software reads incoming documents, recognises what they are, extracts the details that matter and hands them, structured, to the system where the work continues. An operated agent takes over five of those steps, for one Vorgang (one intake, one task, one destination) and exactly one target system:

  1. Capture: it collects the document from the intake, whether scan, email attachment, upload or watch folder.
  2. Classify: it recognises the document type or the responsible department.
  3. Extract metadata: it reads sender, date, subject and identifiers such as a file reference, order number or delivery note number.
  4. Route: it passes the document to exactly one existing target system, such as the DMS or the ERP.
  5. Create a task: it creates the task there for the department and records the assignment with timestamp and reasoning.

When its certainty falls below the agreed confidence threshold, it hands the case to a person. Posting, approving, paying, deleting and triggering deadlines are not part of its job.

OCR is the first step, not the processing

Optical character recognition (OCR) turns an image into text. It does not know whether that text is an invoice, an objection or a delivery note, and it does not know who should work on it. Intelligent document processing starts where OCR stops: recognising the document type and passing it to the right place.

Many projects stop halfway. The document sits as a searchable PDF in a folder or an electronic file, but someone still has to read it, assign it and forward it. That assignment is the daily manual work IDP is meant to take over.

StageWhat it deliversWhat is still manual afterwards
ScanningPaper becomes an image fileReading, assigning, retyping details, forwarding
OCRThe image becomes searchable textAssigning, retyping details, forwarding
Classification and extractionDocument type or department recognised, details as metadataForwarding and creating the task
Operated agentAssignment, metadata, task in the target system, entry in the logThe cases below the threshold and the work on the matter itself

What has to exist before an agent can work on the intake at all is the Poststelle, the mailroom process that captures incoming post; the article on the digital mailroom covers it.

The freer the document, the more the agent has to understand

How much reading is needed depends on the form. A structured record, such as an e-invoice in the XRechnung or ZUGFeRD format, already carries its details in fields. A form or a delivery note has fixed places for numbers and dates, even if every sender arranges them differently.

A letter, a complaint or an objection has no fixed form. Here the agent has to understand the content to recognise the document type and who is responsible: a letter quoting the file reference of a planning application belongs somewhere else than a question about dog tax, even if both open with "Dear Sir or Madam".

Most intakes mix all three forms. That is why, in the first week, the Fachbereich (the department that owns the work) does not just name the classes but reviews examples for each class from the real intake with us. The agent learns from the documents that actually arrive, not from samples.

Metadata turn a document into a task someone can work on

A document in the right department has only half arrived. It becomes workable when the task in the target system already carries the details the department searches, sorts and files by. The department decides which details those are, not the agent.

Document typeTypical metadataWhere the task goes
Letter to a public authoritySender, date, subject, file referenceResponsible department in the DMS
Citizen enquiryRequest, sender, contact channelResponsible office
Delivery noteSupplier, delivery note number, order number, dateWarehouse, quality assurance or accounting
InvoiceInvoice number, invoice date, supplier, header dataAccounting

Which metadata a Vorgang needs is agreed with the department in week 1 and tested on real documents in week 2.

The boundary is fixed before the first document

What the agent does and does not do is set before it sees its first document. The boundary protects both sides: it stops a system from doing things nobody wants to answer for, and it makes the result measurable.

We do thisWe do not do this
ScopeOne intake, one task, one destinationA second intake channel or decision rule
TermFixed, defined endOpen-ended or auto-renewing
Target systemExactly oneMultiple targets, or writing back into a second
ActionClassify, extract metadata, route, create a taskPost, approve, pay, delete, trigger deadlines
IntegrationExisting interface, watch folder, sFTP, email, standard APICustom development against a legacy system
WorkflowSingle-stageMulti-stage with branching

The action row matters most. The agent completes the assignment in full; the decision on the matter stays with the department. Whether an invoice is paid, an application approved or a deadline set is for a person in the department. That person works with the document and the metadata the agent supplied.

A single-stage Vorgang can be measured with one number

A Vorgang is everything that arrives daily, answers the same question and lands in the same system. The narrow scope is deliberate. Only when every document answers the same question is there a single hit rate: the share of cases the agent assigns correctly.

The hit rate is agreed before the start and tested at acceptance in week three, on real documents. A second intake channel, a second target system or a branch would break that number apart. So each becomes its own Vorgang with its own hit rate, not an extension of the first.

Not every document is a case for IDP

Intelligent document processing fits where a lot of similar material arrives and assigning it costs time today. It fits poorly where reading the document already is the casework.

  • Rare documents: a handful of cases a month does not justify a Vorgang of its own, and there are too few examples for a reliable hit rate.
  • Processes with branches: if a document passes through several offices, each with its own sign-off depending on the content, that is a multi-stage workflow outside the boundary.
  • Two target systems: if the same document has to be created in both the DMS and the ERP, that is two Vorgänge.
  • Judgements on the matter: whether an objection is justified or a complaint valid is for the department to judge. The agent makes sure the case reaches the right person quickly.

Every document follows the same sequence, and every assignment is logged

In operation, the agent works through every document in the same order:

  1. It reads the document and recognises the details the department defined as metadata.
  2. It weighs the agreed classes and rates how certain it is for each.
  3. If the highest certainty is above the confidence threshold, it assigns the document and creates the task in the target system.
  4. If it is below, it creates no task and hands the case to a named person.
  5. Either way, it writes an entry to the decision log: what arrived, which classes it weighed, how certain it was, what the assignment rests on and which task was created.

Every assignment can then be explained later, even by someone who has never seen the agent. The answer to why a document landed where it did no longer depends on anyone's memory.

Below the confidence threshold, a person assigns the case

The confidence threshold is the certainty below which the agent does not act but hands the case to a person. It is agreed with the department before the Pilotbetrieb (our fixed-price entry engagement) starts and tuned on real volume during the productive weeks.

The person receives everything needed for a quick assignment: the document, the classes weighed with their certainty, the class the agent would have chosen and the reason for its doubt. Their assignment is logged and feeds the next correction.

The path also runs the other way. Through the human intervention path, a named person can stop the agent at any time, correct an assignment or take over a case.

AI document processing without an internal project: we build and operate it

With an operated agent, it is clear who does what. If you buy intelligent document processing software, someone in your organisation sets it up, trains it and watches it. With an operated agent, that someone is us. The department contributes its knowledge of the Vorgang, IT provides access, and we build and run the agent.

WhoWhat they contribute
Departmentanswers the process questions in week 1, names classes and examples, works the matter and resolves the cases handed over
IT or data centreprovides access to the target system: standard API, watch folder, sFTP or email
Agentclassifies, extracts metadata, routes, creates the task and hands over unsure cases
Agentivobuilds the agent in weeks 1 and 2 and then operates it: monitors, corrects, takes responsibility

For us, operation means more than hosting. When responsibilities change, a new document type appears or a sender changes its layout, we correct the agent and take responsibility for the result.

According to the Federal Statistical Office (Destatis), slightly more than one in four German enterprises with at least ten people employed used AI in 2025. Text mining, the analysis of written language, is among the technologies those enterprises use most.

Enterprises that have considered AI but not yet adopted it most often cite a lack of knowledge, a lack of clarity about legal implications and data protection concerns, according to the Destatis survey on reasons against AI.

With an operated agent, these questions are answered before the start. The operator brings the knowledge. For data protection and evidence, this applies:

  • Operation entirely within the EU, responsibility from Düsseldorf.
  • GDPR-compliant processing with an AVV (data processing agreement) included.
  • A complete decision log available as evidence for EU AI Act audits.
  • A defined human intervention path, documented and triggerable at any time.

Which EU AI Act obligations apply in your case is a question for your legal team or data protection officer. We provide the AVV and the log for it.

IDP starts with one Vorgang that arrives every day

Intelligent document processing pays off where the same kind of document arrives every day and is distributed by hand today. Four Vorgänge are typical starting points:

VorgangWhat the agent does
Incoming postcaptures the incoming PDF, assigns it to the responsible department and creates a task in the DMS
Citizen enquiryrecognises the request, routes it to the responsible office and confirms receipt
Delivery notereads the details, checks them and forwards them to warehouse, quality assurance or accounting
Invoicecaptures the header data, proposes the assignment and hands it to accounting

In a public administration, incoming post is an obvious start; the article on the incoming mail workflow in the DMS shows how the assignment reaches the DMS. How the classes for post at department level come about is covered under document classification.

How to set up one such Vorgang step by step is shown in the article on how to automate document processing with AI. For an SME, one Vorgang is the smallest sensible start to AI process automation. An overview of our AI employees is in the catalogue.

Seven weeks from the first examples to productive operation

The entry point is the Pilotbetrieb: one Vorgang, fixed price, agreed before we start. It takes seven weeks, four of them productive operation on your real documents.

WeekWhat happens
1Process conversation with the department, define classes, review examples, clarify access
2We build and train the agent, set up quality checks and test on real documents
3Acceptance against the agreed hit rate, go-live, handover
4 to 7Productive operation on real volume; we monitor and correct
End of week 7Written evaluation: hit rate achieved, cases processed, time saved

If the agreed hit rate is met, operation begins under a monthly operating agreement that can be cancelled monthly. If it is missed, the Pilotbetrieb ends with no further obligation.

Frequently asked questions

What is the difference between OCR and intelligent document processing?

OCR turns an image into searchable text, nothing more. Intelligent document processing also recognises the document type, extracts the important details as metadata and passes the document to the system where it is worked on. An operated agent additionally creates the task there and logs every assignment with timestamp and reasoning, so each one can be explained later.

Is this intelligent document processing software?

Not in the sense of a product you install, configure and monitor yourself. We build an agent for one Vorgang and then operate it: we monitor it, correct it and take responsibility for the result. Your department answers questions in the first week, your IT provides access to the target system, and nobody on your side trains a model or maintains rules.

What happens to documents the agent cannot assign with certainty?

They go to a named person. If the agent's certainty is below the agreed confidence threshold, it creates no task and hands over the case with the classes it weighed and the reason for its doubt. The person assigns it, the assignment is recorded in the decision log and serves as an example for the next correction. Nothing is left lying, and nothing is assigned automatically in doubt.

Why does the agent not post invoices?

Because posting, approving, paying, deleting and triggering deadlines lie outside the agreed boundary. For invoices, the agent captures the header data, proposes the assignment and hands it to accounting. Posting and release stay with your staff. Every payment remains a human decision, and the log shows what the preparation was based on, which is what an auditor will ask about.

Does intelligent document processing need a new system?

No. The agent writes into exactly one target system you already use: a DMS, an ERP, a specialist application or a ticket system. It connects through access that already exists, such as a standard API, a watch folder, sFTP or email. Custom development against a legacy system does not belong in a Pilotbetrieb. We agree the right interface in the first week.

The next step

If the same kind of document arrives every day and is read, assigned and forwarded by hand, that is the Vorgang for a Pilotbetrieb: one intake, one task, one destination. Fixed price, agreed before we start. Seven weeks, four of them productive operation on your real documents.

Request a Pilotbetrieb

← Back to insights