Purchase order automation in Business Central,
from requisition to promised date
Lleverage brings purchase order automation to Dynamics 365 Business Central with an AI agent. It turns requisition worksheet lines into purchase orders priced off your vendor agreements, sends each one to the approver it needs, then reads the vendor’s confirmation from the purchasing inbox and records the promised date. Buyers only see the lines that moved.
How does purchase order automation work in Business Central?
In Business Central a buyer runs Calculate Plan, works through the requisition worksheet, picks a vendor per line, waits for each signature and then keys the vendor’s reply onto the purchase order. The agent takes that loop in 4 steps, and Business Central stays the record. More on purchase order automation from email to ERP.
Read the requisition worksheet
The lines Calculate Plan suggests for items replenished by purchase, plus the requests that come off someone’s desk by email. For each one the agent brings the purchase price list, what you actually paid last time and the lead time each vendor has managed to hold.
Create the purchase order
The order goes to the vendor you hold terms with, priced off that agreement, with a requested receipt date the vendor has met before. It is created in Business Central through its API, on the vendor card and the items your buyers already use.
Get the signature it needs
Under your threshold the order goes out on its own. Above it, the approver gets the quote and the budget line attached, in Teams or the inbox. If you run the Purchase Order Approval Workflow in Business Central, it stays in place and the order is released there.
Read the confirmation and update the purchase line
A line in the email thread, a PDF order acknowledgement or a portal export. Quantity, direct unit cost and date are compared with each purchase line. Lines that agree get the promised date and the vendor’s order number, a line that moved goes to the buyer, and silence is chased on the day the reply was due.
Every promised date on the purchase line in Business Central
Purchase orders go out of Business Central on your vendor agreements, and every promised date lands on the purchase line the day the vendor sends it, so a delivery that slips is caught while there is still time to act.
Learn moreExample data
One requisition line in Business Central, through to the promised date.
The requisition worksheet in Business Central asks for 40 bearings by 18 March. 3 vendors can supply it, and Brakveld Techniek is the one on contract price that can deliver by then.
Example data
You decide which Business Central orders need a buyer
Every check on a purchase order and its confirmation has a setting. Orders inside your terms go out, confirmations that agree land on the purchase line in Business Central, and anything outside them waits for the buyer who owns that vendor, with the reason attached.
Example data
Business Central’s purchasing tools or Lleverage: which fits when?
Business Central plans purchases in the requisition worksheet, prices them from purchase price lists and releases them through approval workflows. We read Microsoft Learn on 10 October 2026, and every statement in the middle column comes from those pages.
| Business Central purchasing | Lleverage | |
|---|---|---|
| Deciding what to buy | Calculate Plan on the requisition worksheet works out a replenishment plan for items set up with Purchase or Transfer, and fills in an action message per line: a new order, or more on an existing one. | Reads what the worksheet suggests and the requests that arrive by email. For netting demand against supply and planning parameters, we think the requisition worksheet is the stronger tool. |
| Turning lines into orders | Carry Out Action Message turns the worksheet lines into purchase orders. Lines with a warning are left unaccepted, so a person looks at them first. | Creates the purchase order itself, on the vendor you hold terms with, and leaves anything outside your rules for the buyer, with the reason attached. |
| Price on the line | Best price calculation inserts the lowest permitted price from the purchase price lists, by vendor, item, quantity, unit of measure and date. With no special price, it uses the last direct cost. | Uses those same prices, and checks price, approved vendor and lead time on every line against your agreements before the order goes out. |
| Choosing between vendors | The lead time comes from the Item/Vendor Catalog, the item card, the stockkeeping unit or the vendor card, in that order. Comparing vendors on how often they delivered on time is not described on the vendor’s pages. | Puts each request against the vendors you hold terms with: contract price, what you paid last time and the lead time each one has actually held. |
| Approving the order | Business Central’s strength. The Purchase Order Approval Workflow template, approvers with substitutes and amount limits, notifications by email or internal note, and the status goes from Pending Approval to Released. Since April 2026 a requisition worksheet batch can be sent for approval too. | Each order goes to the one person whose signature it needs, with the quote and the budget line attached. Your workflow in Business Central stays in place. |
| The vendor’s confirmation | The purchase line carries a requested receipt date, and the expected receipt date is calculated from it. Reading a confirmation that a vendor sends by email is not described on the vendor’s pages. | Read from the purchasing inbox as the vendor sends it, and compared with each purchase line on quantity, direct unit cost and date. Only the lines that moved reach a buyer. |
| Vendors who stay silent | Not described on the vendor’s pages. | A vendor who has not confirmed hears from it on the day the reply was due, in the same thread, and the buyer sees who is still silent. |
| Fits best when | Your items carry complete planning parameters, each item has one obvious vendor, and your vendors rarely change a date after the order goes out. | Requests arrive by email as well as from planning, several vendors can take the order, and your buyers spend the morning keying confirmations and chasing silence. |
We think the requisition worksheet and the approval workflows are where purchasing in Business Central should start: they are already in the product and they plan and release orders well. We think Lleverage fits when the work you want gone is choosing the vendor, getting the signature and reading what the vendor sends back. Supplier invoices are the next step, on AP automation for Business Central.
Our engineers set it up with you.
It takes on more of the buying desk as it learns.
Forward deployed engineers put the first category live with your buyers and connect it to Business Central, so the first orders come off the desk within a few weeks. From there it automates gradually: every correction teaches it your vendors, your price lists and their confirmation formats, and fewer orders need a person to look.
They work inside your operation. They load your contracts and approved supplier list with your buyers, set the confidence line together, and stay on as vendors and prices in Business Central change.
The purchasing inbox, the buying rules, 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 ↗Frequently asked questions
Can Business Central create purchase orders automatically?
Partly. Calculate Plan on the requisition worksheet suggests what to order for items replenished by purchase, and Carry Out Action Message turns the accepted lines into purchase orders (Microsoft Learn, read 10 October 2026). A buyer still reviews the lines, picks between vendors and chases the confirmations. The agent takes on that part.
Does it replace the purchase approval workflow in Business Central?
No, unless you want it to. Business Central’s Purchase Order Approval Workflow, with approvers, substitutes and amount limits, is one of its strengths, and we think you should keep it if it works. The agent can send an order into that workflow, or route the request to the approver in Teams with the quote and the budget line attached.
How does the agent handle vendor order confirmations?
It reads them from the purchasing inbox: a line in the email thread, a PDF or a portal export. Each one is tied to the purchase order in Business Central and compared line by line on quantity, price and date. Lines that agree are recorded on the order, and a line that moved goes to the buyer.
Does it work with Navision or Business Central on-premises?
Yes. Lleverage connects to Business Central online, to on-premises installations and to Navision, through the API where there is one. Servers behind your firewall are reached without opening them to the internet, and the agent gets the access a buyer has, nothing more. Our engineers set up the connection with your team. More on integrations.
Where is our purchasing data hosted?
In the EU by default, under GDPR, or on your own servers where needed. Purchase orders, vendor prices and confirmations stay in Business Central. The connection reaches only the purchasing data you scope it to, and each order the agent creates or updates is logged with the quote or email it came from. More on control and audit trails.
The rest of the back office.
↗
Quote to orderQuote & SellQuotes drafted, orders entered and confirmed the moment they land.
↗
Forecast to producePlan & ProduceThe plan reshuffled when reality changes.
↗
Order to deliveryDeliver & SupportCustomers answered with full context, in their own channel.
↗
AP & ARPay & CollectInvoices matched, real variances flagged, the rest untouched.
↗
Master dataGovern & EnableMaster data kept clean and in sync across every system.