Document automation
Invoices, orders and delivery notes, recorded without typing.
Reads documents received by email or scanned, checks them against the ERP and records them. Anything uncertain goes to a person.
From received invoice to ERP entry
The example shows a fictional invoice read field by field and checked against the ERP: three values match and the amount is held for review.
What you can do
- Read documents. Invoices, orders and delivery notes as PDF, image or email.
- Check against the ERP. Compares supplier, order and amounts.
- Record what is validated. Creates the ERP entry and keeps anything needing review in view.
How the work flows
An example with fictional data to explain the workflow, not a customer case.
An invoice arrives
Example Supplier emails invoice F-0000.
Reading and checking
The data is extracted and compared with order P-0000 in the ERP.
Record or review
If it matches, it is recorded; if an amount differs, a person reviews it.
Connections and control
- Connection to your ERP and the mailbox or folder where documents arrive; types and fields are agreed.
- Fields that are uncertain or do not match the ERP are held for review, never recorded blindly.
- Recording an invoice is not paying it: payments follow your authorisation process.
- Layered protection: personal-data filters and access control. Masking data before the model is not the same as anonymising it permanently.
Frequently asked questions
What if a document is badly scanned?
Uncertain fields are flagged and a person corrects them.
Does it cover customer and supplier documents?
Yes. Document types and their ERP destination are configured.
Does it pay the invoices it records?
No. It records and checks; your team authorises payment.