Invoice processing automation: what the agent takes on and what it does not
Contents
Invoice processing automation, as we run it, means that an AI agent operated by us takes each incoming invoice from arrival to handover to accounting, and its work ends there. Checking, approving, posting and paying stay with your people. Who does what in invoice intake:
| Step in invoice intake | Who takes it on |
|---|---|
| Receive the invoice: post, email, e-invoice | your intake, as today; scans and files land in one place |
| Capture header data | the agent |
| Propose the assignment to a department or cost centre | the agent |
| Create the task in the target system and hand over to accounting | the agent |
| Resolve unsure cases | a named person in accounting |
| Match against order and delivery note, check on the merits and the arithmetic | accounting and the ordering department |
| Approve, post, pay, watch payment deadlines | accounting |
Your accounting team answers questions; we run the operation
Your accounting team sets nothing up. In the first week it answers questions: which invoices arrive? Which details does it need? Who is an invoice assigned to today, and who resolves doubtful cases? From those answers we build the agent in the first two weeks.
After that we operate it: we monitor every assignment, correct the agent when suppliers or cost centres change, and take responsibility for the result. For your business this means no IT project, no new software for accounting, and nobody on your side maintaining rules. The agent writes into exactly one target system that you already use.
AI invoice processing ends at the handover
The agent does the same thing with every invoice: it captures the header data, proposes the assignment to a department or cost centre and creates the task for accounting in the target system. Every assignment is recorded with timestamp and reasoning in the decision log. Which header data that covers, and what the e-invoice changes about capture, is described in invoice capture.
Then its work ends. This boundary is fixed before every Pilotbetrieb, our entry engagement, begins:
| Area | What the agent does | What it does not do |
|---|---|---|
| Scope | One intake, one task, one destination | A second intake channel or decision rule |
| Term | Fixed, defined end | Open-ended or auto-renewing |
| Target system | Exactly one | Multiple targets, or writing back into a second |
| Action | Classify, extract metadata, route, create a task | Post, approve, pay, delete, trigger deadlines |
| Integration | Existing interface, watch folder, sFTP, email, standard API | Custom development against a legacy system |
| Stages | Single-stage | Multi-stage with branching |
Matching, approval and payment stay with accounting for good reason
Behind the approval of an invoice sits a check your business is accountable for: does the invoice match the order and the delivery note, are quantities, prices and tax right, has the supply been made? German VAT law leaves it to each business to decide how it ensures the authenticity of origin, the integrity of content and the legibility of its invoices, for example through an internal control procedure that creates a reliable audit trail between invoice and supply (section 14(3) UStG, in German).
That procedure stays yours. The agent feeds it: captured header data, a proposed assignment and a log entry with reasoning. Whether the decision log can form part of your audit trail is for you to settle with your tax adviser. Approving, posting and paying stay with the people responsible for them today; payment terms and early-payment deadlines remain with your accounting team.
The agent hands unsure invoices to a person
The agent works with a confidence threshold: when its certainty falls below it, it stops and hands the invoice to a named person in accounting. Typical cases are an illegible scan, a supplier invoicing for the first time, or an invoice that could fit two cost centres.
That person sees what the agent recognised and why it is unsure. In weeks four to seven we use these cases to correct classes and set the threshold. Through the defined human intervention path, your accounting team can also stop the agent, correct it or take over cases at any time.
Incoming orders are a separate Vorgang
Incoming customer orders have the same shape as invoices: they arrive daily, are read and land in the ERP. They are still a different Vorgang (one intake, one task, one destination), with their own question, destination and hit rate. The same goes for delivery notes, covered in delivery note processing.
A Pilotbetrieb covers exactly one Vorgang. Whoever tackles invoices and incoming orders at once cannot measure either with one number. One first, then the next: that is how AI process automation in SMEs builds up step by step. What this looks like in businesses where a new generation is taking over is described in AI in SMEs.
Seven weeks to automated invoice intake
The Pilotbetrieb takes seven weeks. Four of them are productive operation on your real invoices.
| Week | What happens |
|---|---|
| 1 | Process conversation with the Fachbereich (the department that owns the Vorgang), define classes, review examples, clarify access |
| 2 | We build and train the agent, set up quality checks and test on real documents |
| 3 | Acceptance against the agreed hit rate, go-live, handover |
| 4 to 7 | Productive operation on real volume; we monitor and correct |
| End of week 7 | Written evaluation: hit rate achieved, cases processed, time saved |
The hit rate is agreed before the start. If it 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
Is this accounts payable software?
No. We build an agent for one Vorgang, invoice intake, and operate it: we monitor, correct and take responsibility for the result. Your accounting team sets nothing up and maintains no rules. The agent writes into the system the team already uses and creates tasks there. Checking, approval, posting and payment carry on in that system, done by your people.
Does the agent match invoices against orders and delivery notes?
Not in this Vorgang. The invoice Vorgang covers three things: capture header data, propose the assignment, hand over to accounting. Matching would be a further decision rule and stays with accounting. The captured header data, including order and delivery note numbers where present, makes that matching easier. Incoming delivery notes can be a Vorgang of their own that reads, checks and forwards them.
What happens when an assignment is wrong?
Accounting sees every proposal before it releases the invoice and corrects it where it already works today. The decision log shows why the agent made that assignment. In weeks four to seven we review such cases and correct the agent. The hit rate measures how often it is right; it is agreed before the start and tested at acceptance in week three.
How does the agent reach our ERP?
Through access that already exists: a standard API, a watch folder, sFTP or email. It writes into exactly one target system, for example your ERP or your accounting software, and nowhere else. Custom development against a legacy system does not belong in a Pilotbetrieb. We agree the right access in the first week with you or your IT service provider.
When does the agent start working on real invoices?
From week three. After acceptance against the agreed hit rate, the agent goes live and works on your real volume in weeks four to seven while we monitor and correct. If the hit rate is met at the end, operation continues under a monthly operating agreement that can be cancelled monthly. If it is missed, the Pilotbetrieb ends with no further obligation. The fixed price is agreed before the start.
The next step
If your accounting team reads, assigns and passes on incoming invoices by hand today, 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.