Supplier invoices, captured and posted without the keying.
An on-premise system that ingests supplier invoices, extracts them with AI, learns how your team posts, and files the A/P invoice through the SAP Business One Service Layer, as a draft or final.
See it in action
Three minutes, from supplier PDF to posted in Business One
An invoice arrives, vision AI reads it, and the system matches it against what it has already learned from your posting history. A person verifies, approval routes, and the A/P invoice files through the Service Layer. Every screen is the real system running against SAP Business One.
+–Read the transcript
This is the heart of our new AI-enabled AP automation system for SAP Business One, where you can see exactly what data was extracted from an AP invoice. You can see the line details. This one’s already been posted, and you can see it’s learned from what was actually set up and imported into SAP Business One.
If you run AP automation for a company using SAP Business One, then this is probably what your email inbox looks like, with loads of PDF invoices waiting for you to process them.
And your whole day consists of basically working in this screen, finding the vendor, trying to remember if it should be an item-based invoice or a service-based one, what GL account should you use, copying the descriptions and pricing, and trying to get all of that to match up. That is an awful lot of work, and there is a better way to do this.
So in our system, when a new invoice arrives via an email inbox or from a folder, the system picks it up, it finds the PDF, uses an AI vision model to extract the data, matches that with the rules in the system, and then gets it ready for you to verify.
An invoice from a new supplier will always be verified first, and the system will learn as we go along. So here we can see the invoice, the data that was just extracted, the details of all the lines, and it’ll actually search Business One and find the matching ones.
And because we have the approve step on, it will first be submitted for approval. And if we go to our approval user, we see they have an approval, and they can review all of this and then approve and post the final.
So now in Business One you can see there is our new AP invoice, and it almost posted itself. It drastically speeds up the whole process.
And the system learns as it goes along. It writes new rules as it posts new data. Every time you make a change or adjust settings or adjust data on an extraction, it will update the rules.
There’s an approval matrix which helps you to set up approvals if you want to use that. There’s a whole audit log that shows exactly what went on, and there is very flexible line coding which helps the system to match, and you can set up rules for GL accounts, item mappings, as well as for vendors.
The system is extremely powerful, and it is smart out of the box, and the best part is, the more you use it, the smarter it gets.
Built for the way finance teams actually work
Every control a CFO expects, in a system that earns autonomy gradually, never blindly.
Capture from anywhere
Email, a watched folder, or manual upload. Each attachment is classified and de-duplicated on arrival.
AI extraction with confidence
Vision AI reads the document and the maths is validated deterministically, so confidence means something.
Learns your posting decisions
Every correction becomes a rule. Rules earn auto-posting autonomy gradually, and lose it the moment they're wrong.
PO & GRPO matching
2- and 3-way matching with a proper tolerance engine: price, quantity, and document caps, per vendor.
Fraud & duplicate controls
Duplicate-payment checks against posted B1 invoices, dual-control on bank-detail changes, and sanctions screening.
Segregation of duties
Creator can never approve their own work, and a hard approval threshold no rule can bypass.
Free tool
Before you look at automation, work out what you spend today.
Put your own volumes and rates in and get your real cost per invoice, including the approval loop most teams have never priced. No email needed to see the result.
APPROVAL ROUTING
Your delegation of authority, not a single threshold.
B1's own approval procedures do not fire for Service Layer documents when the term is based on a user query, so a threshold configured there can silently miss everything this system posts. The approval matrix here is ours, and it is authoritative.
Ordered rules, first match wins. Steps at the same level run in parallel, ascending levels run as sequential stages, and any step can require a quorum. So “any 2 of these 4 directors” is one step, not four rules.
Amount tiers, exclusive or cumulative
Either the top band alone signs, or each band adds a signature to the ones below it.
Owners instead of rule explosion
Every cost centre routes to its budget holder from one rule and a lookup table, not fifty rules. Same for vendors, G/L accounts and projects.
Per-approver authority limits
An approver whose limit is below the invoice is filtered out of the pool. Never quietly passed through.
Risk-based routing
Non-PO spend can require a signature that PO-backed spend does not.
Delegation with attribution
A dated out-of-office window, and the audit records the delegate who actually signed as well as the person they signed for.
Fails closed, always
No matching rule still means approval. An empty pool or a quorum that cannot be reached stops the invoice rather than letting it through.
The route is frozen when the invoice enters approval, so editing the rules tomorrow never rewrites yesterday's evidence. Correcting an amount re-plans the route and discards signatures collected against the old one. And the learning engine can never add, promote or relax an approval rule: routing is operator configuration, exclusively.
FOR FINANCE LEADERS
Control that's enforced in the data, not just the UI.
On-premise and Windows-native, with no cloud data-residency questions. An append-only, tamper-evident audit trail records what was extracted, what a person changed, and exactly what was posted to Business One.