What automation does and does not do
The automation takes the invoice from the shared mailbox; extracts the supplier, date, amount, tax and line items; matches it with the order and the supplier record; and opens a draft entry in the accounting software. It does not make the decision on its own: invoices that exceed the amount threshold, come from a new supplier or have unreadable fields go to a person for approval.
- Reading: extracting the fields from a PDF or an image
- Checking: comparison against order, supplier and tax rules
- Action: draft entry in the accounting software (through the official interface, the API)
- Exception: routing out-of-threshold and unclear cases to approval
- Log: storing every step with who, what and when
Irreversible actions such as issuing a payment order do not fall within the automation’s authority unless you request otherwise in writing.
There are also mature off-the-shelf tools for standard invoice reading. If they meet your need, we tell you so during discovery; the pilot method below applies in both cases.
Why start with a pilot
AI outputs can contain errors. The error rate varies with the industry, the document quality and the variety of suppliers, so it cannot be promised in advance; it is measured. A pilot is a limited trial run with real or anonymized past invoices, and it clarifies three things: accuracy, the share of work that goes to approval and the processing time.
What is written before the pilot
- Test set: how many invoices, which suppliers, which period
- Success criteria: targets for field accuracy, the share that goes to approval and the processing time
- Duration and scope: which workflow, which system, which authority
- Continuation rule: deployment if the criteria are met; stopping or narrowing the scope if they are not
The result of the pilot is reported against the same criteria. If the criteria are not met, we do not recommend moving on to deployment; the decision belongs to the business.
Automation level: recommendation, approved action, automatic except for exceptions
Every workflow can start at the recommendation level: the automation prepares the entry, and accounting checks and applies it. If the accuracy measured in the pilot meets the target, the workflow moves to approved action and then, within defined limits, to action without approval. The move always happens with the approval of the business; at every level the authority limit, the action thresholds, the action log and the stop mechanism apply.
What you need to start
- A short description of the process as it is today: where the invoice arrives, who enters it, where it is entered
- A few sample invoices from different suppliers
- The accounting or ERP software in use and whether it has an official interface
- Approximate number of invoices per month
For documents that contain personal data, a data processing agreement is signed; which data goes to which model and to a service in which country is documented before the work starts.
Frequently asked questions
Are invoices sent to the AI provider?
Which data goes to which model is documented in advance and submitted for your approval. If needed, models that run on-premises are considered.
What if our accounting software has no API?
We look for an official interface first. If there is none, screen automation (RPA) is considered; this option needs more maintenance, and that is stated clearly in the proposal.
How long does a pilot take?
It depends on the scope. The duration and the success criteria are written down before the pilot starts.
Related service: On-Premises AI. On-premises models, infrastructure agents, systems without an API.