Lleverage automates accounts payable in SAP S/4HANA and ECC with an AI agent. It reads supplier invoices from the finance inbox in any layout, matches every line against the purchase order and goods receipt in SAP, and posts the invoices that agree. The rest wait for finance with all 3 documents open. Releasing a payment stays with a person.
In SAP an AP clerk opens each invoice, looks up the purchase order and the goods receipt, and keys it into MIRO. With automated invoice processing the agent does that work in 4 steps, and SAP still runs its own tolerance checks when the invoice is posted. How this compares with other tools is in our guide to accounts payable automation software.
A PDF, a scan or a forwarded email, in any layout. The agent reads the supplier, the invoice number, the purchase order reference, the VAT and every line, with a confidence on each field, and ties the sender to the supplier record in SAP. Nobody uploads a file.
Each line is tied to its purchase order item in SAP and to the goods receipt posted against it. A line with no goods receipt yet waits, because SAP itself blocks such an invoice unless tolerance key DW is set to allow it.
Price against the order price, quantity against what the warehouse received, cost centre and bank details against what SAP holds. Each check has a tolerance you set per supplier or category, on top of the price (PP) and quantity (DQ) tolerance keys SAP applies per company code.
Invoices inside your tolerances are posted in SAP against the purchase order, the same supplier invoice an AP clerk creates in MIRO, ready for the payment run. An invoice with a line outside them is not posted: it goes to the person you choose, with the difference named.
Supplier invoices are matched and posted in SAP the day they arrive, so the payment run is ready on time and the ledger is current every morning. Incoming payments are applied and debtor reminders go out the same way, so your team only handles the variances and the disputes.
Learn moreA supplier invoice for EUR 18,240 lands in the finance inbox. In SAP there is a purchase order and a goods receipt that should agree with it, line by line.
Price, quantity, cost centre and bank details are checked against the purchase order and goods receipt in SAP, each with a tolerance you set. Invoices inside it are posted on their own. Anything outside it waits in finance with all three documents open.
SAP covers supplier invoices in 3 places: invoice verification inside S/4HANA (Create Supplier Invoice, MIRO), SAP Ariba Invoicing on SAP BTP for intake and extraction, and OpenText Vendor Invoice Management (VIM), an SAP solution extension. We read SAP Help Portal and OpenText’s product page on 5 October 2026, and every statement in the middle column comes from those pages.
| SAP’s own options | Lleverage | |
|---|---|---|
| How invoices get in | In S/4HANA Cloud Public Edition, Upload Supplier Invoices (F2452) creates one draft invoice per uploaded file and attaches the file to it. SAP Ariba Invoicing takes uploaded files and, with scope item 6JX, the invoice files from incoming emails. | The agent picks invoices up from the finance inbox as they arrive, overnight and at weekends too. Nobody uploads a file. |
| Reading the invoice | Ariba Invoicing extracts each upload with Document Information Extraction by default, and AI-Assisted Multi-Model Data Extraction, once activated, adds large language models. VIM extracts data from incoming documents through an add-on, OpenText Core Capture for SAP Solutions. | Any layout and any format, read on its meaning rather than a template, scans and photographs included. Every field gets its own confidence, and below your threshold it waits instead of guessing. |
| The three-way match | SAP’s strength. Invoice verification in S/4HANA checks each item against the purchase order or goods receipt with tolerance keys per company code, such as PP for price and DQ for quantity, and a configuration app holds supplier-specific limits. | The same three documents compared line by line, with tolerances per supplier or category, before anything reaches SAP. SAP’s own tolerance check still runs when the invoice is posted. |
| A line outside tolerance | The invoice is posted and blocked for payment, and a user releases it in a separate step. An invoice can also be parked in MIRO and finished later. If the invoice does not balance beyond the BD limit for small differences, it cannot be posted at all. | The invoice is not posted. It waits for the person you choose with all 3 documents open and the difference named, and a correction becomes a rule once a person confirms it. |
| Who sees the exception | VIM routes exceptions by role to the right specialists, in SAP Fiori apps, and gives suppliers self-service on invoice status. Without it, a blocked invoice waits until someone in SAP releases it. | The request lands in Teams, Slack or the inbox of the person who owns it, routed by value, category and delegation. An approval that is ageing escalates. |
| Invoices without a purchase order | MIRO can post them without a purchasing document, directly to a G/L account, and tolerance key AN can check items without an order reference against an absolute amount limit. | Nothing to match three ways, so the agent checks the supplier, the bank details and the cost centre, then routes the invoice to the approver your rules name. |
| SAP versions | MIRO and the tolerance keys are documented for S/4HANA on-premise and Cloud Public Edition. Ariba Invoicing connects to S/4HANA Cloud Public Edition, S/4HANA and SAP ERP. VIM extends RISE with SAP, S/4HANA and SAP ERP. | SAP S/4HANA and SAP ECC, in the cloud or on your own servers, reached without opening them to the internet. |
| Set-up and price | Tolerance keys are configured per company code in S/4HANA. Ariba Invoicing runs on SAP BTP and is set up as scope item 4N6, and OpenText points to its implementation partners for VIM. Prices are not described on the pages we read. | Forward deployed engineers build the first flow with your finance team. One monthly price per agent, with integration included. |
| Fits best when | Invoices arrive in modest numbers, purchase orders and goods receipts are kept clean, and your AP team works in SAP all day anyway. | Invoices arrive as PDFs and scans in every layout, variances need the warehouse or a buyer, and you want the clean ones posted without anyone opening them. |
We think SAP’s own invoice verification is enough when invoices arrive clean and in modest numbers: the three-way check is already in S/4HANA and the tolerance keys do their job. We think Lleverage fits when the work you want gone is reading every layout, matching it and chasing the variances. More on three-way matching and on filling SAP’s gaps without customising it.
Forward deployed engineers match the first invoices beside your finance team and connect the agent to SAP S/4HANA or ECC, so the run comes off the desk in the first weeks rather than at the end of a project. From there it automates gradually: every correction teaches it your suppliers, your tolerances and your cost centres, and fewer invoices need a person to look.
They work inside your operation. They agree tolerances and cost centres with your controller, set the confidence line together, and stay on through audits and SAP upgrades. Not a licence and a manual. A team that knows your ledger.
The finance inbox, the tolerances, the checks and the log are yours to configure. Our documentation and support sit behind your team, and an engineer is a call away whenever you want one.
Talk to us about either ↗Yes. Lleverage connects to SAP S/4HANA and SAP ECC, in the cloud or on your own servers. Systems behind your firewall are reached without opening them to the internet, and the agent gets the access a person in accounts payable has, nothing more. Our engineers set up the connection with your SAP team. More on integrations.
No. Our forward deployed engineers build the first invoice flow with your finance team on your real invoices, and connect it with your SAP team. Nothing is migrated or customised inside SAP: turn the agent off and SAP is exactly as it was the day before. The first process typically runs supervised within a few weeks.
VIM runs inside SAP as an SAP solution extension, with role-based workflows, Fiori apps and capture as a separate add-on, and OpenText points to its implementation partners for it (opentext.com, read 5 October 2026). We think it suits a large AP team that works in SAP all day. Lleverage works from the finance inbox and posts into SAP.
There is nothing to match three ways, so the agent checks what it can: the supplier, the bank details and the cost centre. The invoice then goes to the approver your rules name, by value and category, in Teams, Slack or the inbox. In SAP itself, tolerance key AN puts an amount limit on such items.
No. Releasing a payment is never its call. SAP blocks an invoice for payment when a variance exceeds an upper tolerance limit, and a user releases it in a separate step (SAP Help Portal, read 5 October 2026). The agent prepares that decision: it gathers the order, the goods receipt and the difference, so the controller decides in one look.
Lleverage is EU hosted by default and GDPR compliant, with on-prem where you need it. SAP stays the system of record: nothing is copied into a second database, and every action is logged with what the agent read, what it decided and why, against the SAP document it touched. More on control and audit trails.
↗
Quote to orderQuote & SellQuotes drafted, orders entered and confirmed the moment they land.
↗
Purchase to paySource & ProcureInvoices, POs and confirmations, posted where they belong.
↗
Forecast to producePlan & ProduceThe plan reshuffled when reality changes.
↗
Order to deliveryDeliver & SupportCustomers answered with full context, in their own channel.
↗
Master dataGovern & EnableMaster data kept clean and in sync across every system.
