AP automation for Business Central with an AI agent: Lleverage reads supplier invoices from the finance inbox, matches every line against the purchase order and the posted receipt in Dynamics 365 Business Central, and posts the invoices that agree. Variances stay unposted for finance with the difference named. Releasing a payment stays with a person.
In Business Central an AP clerk opens each PDF, finds the vendor, runs Get Receipt Lines on a new purchase invoice and checks every line by eye. The agent does that work in 4 steps and writes into the same purchase documents your team uses. How it fits wholesale is in our post on invoice automation in Business Central.
A PDF, a scan or a forwarded email lands in the finance inbox. The agent reads the vendor invoice number, the order reference, the VAT and every line, each with a confidence, and ties the invoice to the right vendor card in Business Central before anything else happens.
Each invoice line is tied to its purchase order line and to the posted purchase receipt behind it, the lines a clerk would pull in with Get Receipt Lines. A line the warehouse has not received yet is held back rather than invoiced on trust.
Direct unit cost against the order, quantity against what was received, dimensions against the order, and the bank account on the invoice against the vendor bank accounts Business Central holds. You set the tolerance per supplier or category.
The purchase invoice is created through the Business Central API, linked to its receipt lines. Inside your tolerances it is posted and lands in the vendor ledger, ready for the payment journal. Outside them it stays unposted and goes to the person you choose, with the difference named.
Supplier invoices are matched against the purchase order and the posted receipt, and the clean ones are posted in Business Central the day they land, so the vendor ledger is current and the payment journal is ready on time. Your AP team only opens the invoices with a real variance.
Learn moreA PDF invoice for EUR 18,240 arrives from Noordkamp Lagers. Business Central already holds the purchase order and the posted receipt it should agree with, line by line.
Direct unit cost, quantity received, dimensions and the vendor bank account are each checked against Business Central with a tolerance you set. Invoices inside it are posted on their own, and anything outside it stays unposted for finance with the order and receipt open.
Microsoft ships its own Payables Agent inside Business Central, next to the approval workflows the product already has. We read Microsoft Learn’s overview, set-up and FAQ pages for the Payables Agent and its purchase approval walkthrough on 6 October 2026, and every statement in the middle column comes from those pages.
| Payables Agent (Microsoft) | Lleverage | |
|---|---|---|
| How invoices get in | It monitors one Microsoft 365 mailbox, or one folder of it, per company. Only emails with PDF attachments are processed, and an email with more than 10 attachments is skipped. | The agent works the finance inbox your vendors already write to, and reads PDFs, scans and forwarded emails as they arrive, at weekends too. |
| Size and volume | No PDFs over 10 pages or 5 MB. At most 100 emails and 500 invoices a day. | AI usage sits inside the monthly price within fair use, and a change in volume is talked through before it appears on an invoice. |
| Reading and language | Extracts the PDF with Azure Document Intelligence. Validated and supported in English only, in the Australian, British, American and New Zealand locales. | Reads on meaning rather than a template, with a confidence on every field. Business Central customers such as Xpol already run it on orders from French, Swiss and Dutch retailers. |
| Finding the vendor | Matches on VAT registration number, GLN, name and address, then an AI search. On instruction it can create a vendor, which stays blocked until someone unblocks it. | Ties the invoice to the vendor card and checks the bank account on the invoice against the one on file. An unknown vendor goes to a person. |
| Matching to the purchase order | Proposes order lines, and Business Central validates quantity, receipt, unit of measure and price. A price warning appears above the E-Document Matching Difference %. Charge (Item) and prepayment lines are not supported. | Every line checked against the order and the posted receipt, with tolerances per supplier or category, before the invoice is written. |
| What ends up in Business Central | A person reviews the draft, then the agent finalises it into an unposted purchase invoice. It never posts an invoice: a user does. | Invoices inside your tolerances are created and posted. The rest stay unposted, waiting for the person you choose with the difference named. |
| Approvals | Business Central’s strength. Approval workflows with approvers, substitutes and amount limits per user, notified by email or internal note, and a Purchase Invoice Workflow can post a released invoice. The agent has no approval flow of its own and leaves those to Business Central. | Requests land in Teams, Slack or the inbox of the person who owns them, routed by value and category. An approval that is ageing escalates. |
| Set-up and price | Built in: activate it, point it at a mailbox and give users access. The first 50 invoices are free in trial mode, then it uses Copilot Credits, and it stops taking new invoices when the credits run out. | Forward deployed engineers build the first flow with your finance team. One monthly price per agent, with integration included, and no seats. |
| Fits best when | Invoices arrive as short PDFs from known vendors, in English, well under 500 a day, and your AP team reviews and posts each one in Business Central. | Invoices come as scans and long PDFs in several languages, variances need a buyer or the warehouse, and you want the clean ones posted without anyone opening them. |
We think the Payables Agent is a sound start if your vendors send short English PDFs and your team wants to review and post every invoice itself: it is already in Business Central, the first 50 invoices cost nothing, and your approval workflows keep working. We think Lleverage fits when the volume, the languages or the variances outgrow that review. More on three-way matching and on sales orders in Business Central.
Forward deployed engineers match the first invoices beside your finance team and connect the agent to Business Central, 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 vendors, your tolerances and your G/L accounts, 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 Business Central updates. 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 ↗For some teams, yes. It reads PDF invoices from one mailbox, drafts the purchase invoice and proposes purchase order matches, but it never posts, handles at most 500 invoices a day and is validated in English only (Microsoft Learn, read 6 October 2026). We think it fits short English PDFs that a person reviews anyway.
Through the Business Central API, with the access a person in accounts payable has and nothing beyond it, so Business Central validates every field as it does for your team. Topa and Koninklijke Dekker already run Lleverage agents that create sales orders in Business Central this way. More on integrations.
Yes. Lleverage connects to Business Central online, to on-premises installations and to Navision. Servers behind your firewall are reached without opening them to the internet, and where an older Navision version has no API the agent works the screens with a clerk’s access. Our engineers set up the connection with your team.
We think you should, if it works for you: approvers with amount limits are one of Business Central’s strengths. The agent can leave an invoice unposted for that workflow, or route the approval to Teams, Slack or the inbox of the person who owns it. Either way, releasing a payment stays with a person.
Freight, energy and service bills often come without one. With nothing to match three ways, the agent checks what it can: the vendor card, the bank account and the dimensions. It then sends the invoice to the approver your rules name, by value and category, and nothing is posted before that person agrees.
Lleverage is EU hosted by default and GDPR compliant, with on-prem where you need it. Business Central stays the system of record, nothing is copied into a second ledger, and every run is logged: what the agent read, what it decided and why, and which purchase invoice 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.
