Lleverage is an AI agent that reads incoming orders from email, PDF and Excel, checks them against the items, prices and customers in Dynamics 365 Business Central, and creates them as sales orders. Clean orders go in on their own. Anything outside your rules waits for a person, with the reason attached.
Updated October 2026
To automate sales order entry in Business Central, the agent works the shared order inbox and writes into the same records your order desk uses. 4 steps carry an order from the email to the confirmation.
An email body, PDF, Excel or CSV file from the shared Outlook inbox. The agent pulls out the customer, the delivery address, the requested delivery date, the external document number and every order line.
The order is tied to a customer in Business Central and each line to an item, including the customer’s own part numbers, which Business Central keeps as item references.
Prices are compared with what Business Central holds for that customer, and availability with the requested date, before anything is written. Credit status is checked too.
The sales order is created in Business Central through its API and the confirmation goes back to the customer. At Topa Bathroom Products customers can have it within 30 seconds.
Customers keep ordering the way they do today. Topa’s 700 or so customers send plain text emails, PDFs, CSVs and Excel sheets. At Xpol the agent reads PDF, Excel, CSV and portal exports from French, Swiss and Dutch retailers, with 25 customer-specific rulesets for units, labels and depots.
Learn moreA purchase order lands in the shared Outlook inbox at 07:14. Nobody touches it. This is what the agent does with it.
Parts, price, stock and credit are checked against Business Central before anything is written, and every check has a setting. Topa lets more than 90% of its orders go straight in, while Xpol has a person sign off every draft, and the difference is a setting.
Microsoft ships its own Sales Order Agent inside Business Central. We read Microsoft Learn’s overview, set-up and FAQ pages for it on 3 October 2026, and every statement in the middle column comes from those pages.
| Sales Order Agent (Microsoft) | Lleverage | |
|---|---|---|
| Input formats | The email body plus PDF, PNG and JPG attachments, through a Microsoft 365 mailbox. PDFs up to 50 pages and 20 MB. Excel and CSV are not listed. | Email body, PDF, Excel, CSV and portal exports, from the shared inbox your customers already write to. |
| Lines per order | Up to 15 item lines per sales document. Microsoft notes that more lines might lower the quality of the output. | Long orders are normal work. The agent at SPL Treatments reads 60-page aerospace purchase orders in 3 minutes. |
| Checks on price and stock | Checks item availability and can calculate shipment dates with capable-to-promise. Prices and discounts come from Business Central’s own logic on the quote, and requests to change them go to a user. | Parts, stock and date, price against contract and credit status are checked against Business Central before the order is created. Each check has its own setting. |
| Customers and items | Identifies the customer only by the sender’s email address on the contact card. Matches items by number, GTIN, item reference and attributes. Variant codes are not supported. | Takes customer details and the delivery address from the order itself and applies rules per customer. Xpol runs 25 rulesets for units, labels and depot splits. |
| Exceptions and review | Always creates a sales quote first. A Business Central user reviews and approves every outgoing email, and the agent asks a user for help when details are missing. | Clean orders are created on their own above a confidence line you set. Anything outside your rules waits for the person you choose, with the reason attached. |
| Languages | Validated in Danish, English, French, German, Italian, Portuguese (Brazil) and Spanish. Dutch is not on the list, and Microsoft says other languages might not function as intended. | In production on orders from French, Swiss and Dutch retailers at Xpol. At Koninklijke Dekker the agent adapts to each customer’s own terms and ordering habits. |
| Confirmation to the customer | Replies by email with the quote or order as a PDF, once a user has approved the message. | The confirmation goes back when Business Central accepts the order. At Topa customers can have it within 30 seconds. |
| Pricing | Copilot Credits, charged by the complexity of each interaction. The agent stops processing new emails when the credits run out. | One monthly price per agent, with integration and AI usage included within fair use. No seats. |
| Set-up | Built into Business Central: activate it, point it at a mailbox and give users access. No integration work. A daily email limit applies, 100 by default. | Forward deployed engineers build the first flow with your order desk. The first process typically runs supervised within a few weeks. |
| Fits best when | Orders are emails of up to 15 lines in a validated language, from contacts whose address is on file, and a person can approve each reply. | Orders arrive as PDF, Excel or CSV, run long, need rules per customer, or come in faster than a person can approve them. |
We think the built-in agent is the right start if your orders are short emails in a language Microsoft has validated and someone can approve each reply: it is already in Business Central and needs no integration. We think Lleverage fits once orders arrive as spreadsheets and long PDFs, need your own rules per customer, or outgrow one approval per email. More in our guide to sales order automation.
Sources: Microsoft Learn, Sales Order Agent overview (21 July 2026) · Set up Sales Order Agent (2 September 2026) · FAQ for Sales Order Agent (2 September 2026)
Forward deployed engineers build the first order flow with your order desk and connect it to Business Central, so orders come 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 customers, their formats and their exceptions, and fewer sales orders need a person to look.
They work inside your operation. They map every customer format and exception with your order desk, set the confidence line together, and stay on as your customers and products change. Not a licence and a manual. A team that knows your floor.
The inbox, the ERP connection, 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 ↗
Topa Bathroom Products
“We had four and a half people · about 3.8 full-time equivalents · sitting there all day long, manually entering every single order into our Business Central ERP.”
Sales orders are created through the Business Central API, with the access a person on your order desk has and nothing beyond it, so Business Central validates every field as it does for your team. Your ERP stays the system of record, nothing is copied into a second database, and Lleverage is EU hosted by default. More on integrations.
Yes. Lleverage connects to Business Central online, to on-prem installations and to Navision. Systems behind your firewall are reached without opening them to the internet, and where an older Navision version has no API the agent works the screen with the access a person has. Our engineers set up the connection with your team.
Customers who already send EDI can keep doing so. We think EDI is rarely worth setting up for the many customers who order by email: the agent reads their PDFs, spreadsheets and plain emails and creates the same sales order in Business Central. Topa serves about 700 customers this way, each in their own format.
The order is not created with a guess. The agent holds that order or line for the person you choose and attaches the reason. At Topa an unrecognised article code is flagged for human review, and at Xpol ambiguous fields are left blank on a draft that a person signs off in Business Central.
The first process typically runs supervised within a few weeks. Forward deployed engineers build the first flow with your order desk on your real orders, starting with the customers that cover most of your volume. At Xpol the largest retailer went live first, and about 60 to 70% of weekly volume followed over the next weeks.
Microsoft bills its Sales Order Agent in Copilot Credits, charged by the complexity of each interaction (Microsoft Learn, read 3 October 2026). Lleverage charges one monthly price per agent, with integration and AI usage included within fair use, and no seats. We price it after a first session with your team, so there is no public rate card.
↗
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.
↗
AP & ARPay & CollectInvoices matched, real variances flagged, the rest untouched.
↗
Master dataGovern & EnableMaster data kept clean and in sync across every system.
