Purchase orders into SAP,
checked, then created
Lleverage automates SAP sales order entry with an AI agent. It reads purchase orders from email, PDF and Excel, finds the sold-to and ship-to party, maps each customer part number to your material and checks price, stock and credit before it creates the sales order in SAP S/4HANA or ECC. Exceptions go to a named person.
How SAP sales order automation fills the order, field by field
In VA01 your desk picks an order type, enters a sold-to party and the customer’s reference, then adds one line per material. The agent fills those same fields from what the customer sent, in 5 steps, and SAP then runs its own determination and checks on the order.
Read the purchase order where it lands
An email body, a PDF, an Excel or CSV file or a portal export arrives in the shared inbox. The agent takes the customer’s PO number and date for the customer reference, the requested delivery date and every line, without anyone uploading a file.
Pick the order type and sales area
Most customer orders become a standard order, OR on screen. Free-of-charge deliveries, returns and orders for another sales organisation follow the rules your desk uses today, which our engineers set up with you.
Settle the sold-to and ship-to party
VA01 copies the ship-to from the sold-to only when the customer has a single one. For customers with many sites, the delivery address on the PO decides the ship-to party, and an address the agent cannot place waits for a person.
Map customer part numbers to materials
Buyers order with their own article numbers. SAP links them to your material in the customer-material info record, which can also set the delivering plant. The agent maps each line to one material and unit, and holds a number it cannot tie to one.
Check, create and confirm
Price against what SAP gives that customer, stock and date, and credit status are checked first, each with its own setting. Then the sales order is created, SAP prices it and runs its availability check where the item category asks for one, and the confirmation goes back.
What does this change for the order desk?
Once orders run on their own, sales no longer wait on how fast the desk can type in VA01. Customers get their confirmation sooner, the warehouse gets clean orders, and your people spend the day on customers and on the orders that need judgement.
Learn moreExample data
One order into SAP, start to finish.
A purchase order lands in the shared inbox at 07:14. Nobody touches it. This is what the agent does with it.
Example data
What does the agent check against SAP before it creates the order?
Materials, price, quantity, delivery date and credit are checked against SAP before anything is written, and every check has a setting. Orders that pass are created on their own. The rest wait for the person you choose, with the reason attached.
Example data
- Parts known
- Stock and date
- Price vs contract
- Credit status
- Sales order created
SAP - Confirmation sent
In 28 s - Stock reserved
Warehouse
- Price off contract
Sales Ops - Below 98% sure
Order desk - Credit hold
Credit control
SAP’s extraction apps, its sales order API or Lleverage: where each fits
SAP offers 2 apps that turn a purchase order file into a sales order request, Create Sales Orders - Automatic Extraction and, in S/4HANA Cloud Public Edition, Create Sales Orders - AI-Assisted Extraction, and sales order APIs for your own code. We read SAP Help Portal and the Lleverage docs on 12 November 2026.
| SAP’s own tools | Lleverage | |
|---|---|---|
| How an order gets in | Automatic Extraction takes PDF and image files that a sales representative uploads after entering a company code. AI-Assisted Extraction can also read an email channel set up in SAP Document AI, from the body, the attachments or both. | The agent picks every order up from the shared inbox: email body, PDF, Excel, CSV and portal exports, each in the customer’s own layout. |
| What comes out | A sales order request, which SAP calls a sales order draft. A person completes it, can simulate the order and converts it into a sales order. | A sales order in SAP for every order inside your rules. The rest wait for the person you choose, with the reason attached. |
| Ship-to party | Not a required request field by default. SAP advises checking it before creating the order, because an empty one can end up different from the purchase order. | Checked on every order with the address, alongside parts, stock and date, price against contract and credit status, each with its own setting. |
| Prices | Extracted prices can be copied into the item’s price fields for reference only. They do not change how SAP prices the order. | The price on the PO is compared with the price SAP gives that customer before the order is created. A price off contract goes to the person you name. |
| Customer part numbers | Proposal rules suggest the sold-to party, ship-to party and product from the extracted data, and key users can override them with custom logic in a BAdI. | Each customer number is mapped to your material, and one that fits no material is held. A correction becomes a change to the Skill once a person approves it. |
| Building it yourself on the API | Sales Order (A2X, OData V2), API_SALES_ORDER_SRV, creates an order in one synchronous call. It covers sell-from-stock orders, takes one sales order per change set in a $batch and has no incompletion log. | The reading of each email or PDF, which the API leaves to your own code, is the agent’s work. Our engineers connect it to SAP with your SAP team, and the SAP account it uses decides what it can see and change. |
| Exceptions | The app’s list shows each request’s extraction, completeness and creation status, and a person fixes an incomplete one on its object page. | The person you choose gets the exception in Requests or in Microsoft Teams, where a pending approval takes a typed reply, and the agent carries on with the answer. |
| Quotes and confirmations | The apps create sales orders of a limited number of sales order types. Confirmations to the customer are not described on their pages. | The same SAP connection creates sales quotations, and a new sales order in SAP can start the workflow that confirms it to the customer. |
| Releases and set-up | Automatic Extraction is in the SAP S/4HANA docs since 2021. AI-Assisted Extraction needs SAP Document AI and an activated SAP Business AI feature. Both run inside SAP, with nothing outside it to connect. | SAP S/4HANA and SAP ECC, in the cloud or on your own servers, connected by our engineers. One monthly price per agent, with integration included. |
We think SAP’s apps make sense on S/4HANA when orders come in as PDFs in modest numbers and someone reviews each draft in SAP anyway: the draft stays in SAP and nothing has to be connected. We think Lleverage fits when the reading, checking and chasing around every order is the work to remove, on S/4HANA or ECC. SAP also lists sales use cases for Joule, its generative AI copilot, in S/4HANA Cloud Public Edition; we compare the two in SAP Joule vs Lleverage.
Our engineers set it up with you.
It takes on more of the order desk as it learns.
Forward deployed engineers build the first order flow with your order desk and connect it to SAP, S/4HANA or ECC, so orders come off the desk within a few weeks. From there it automates gradually: a correction becomes a change to the Skill once a person approves it.
They work inside your operation. They map every customer format and exception with your order desk. The confidence line is yours. 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 ↗Frequently asked questions
What is the order type for a standard sales order in SAP?
A standard order is sales document type OR on screen and TA in SAP’s database, in sales document category C. SAP’s OData V2 APIs and BAdIs use the on-screen key OR, while its OData V4 and SOAP APIs use TA. Unless your rules say otherwise for a customer, the agent creates OR.
Can VA01 or SAP Fiori create sales orders from customer emails?
VA01, which Fiori opens as Create Sales Orders - VA01 or from Manage Sales Orders, is for a person keying the order. Automatic Extraction reads uploaded PDF and image files, and AI-Assisted Extraction can also read an email channel. Both stop at a request that a person converts. The agent creates the sales order once it passes your rules.
Why can a sales order created through the SAP API still be incomplete?
SAP says a request to its sales order API can succeed while messages report a field it could not process, and its API comparison lists no incompletion log. Such an order then turns up in List Incomplete Sales Documents. We think the checks belong before the order exists, which is where the agent runs them.
Where does SAP keep a customer’s own part numbers?
In the customer-material info record, per customer, sales organisation and distribution channel. It links the customer’s number to your material, and a plant set there wins over the product master’s. When a line carries a number that fits no material, the agent holds it for a person, and the fix becomes a change to the Skill once approved.
Our order desk still works in SAP ECC. Can the agent create orders there?
Yes. Lleverage connects to SAP ECC as well as S/4HANA, on your own servers too, and reaches systems behind your firewall without opening them to the internet. SAP documents its extraction apps for S/4HANA. Our engineers connect ECC with your SAP team, and the SAP account it uses decides what the agent can change. See SAP integration.
What happens when SAP can only confirm part of an order line?
SAP’s availability check shows when and how much it can deliver, sometimes as several partial confirmations on one line. You decide what the stock and date check does with that: an order that misses it waits for the person you choose with the shortfall attached, and a deviation reaches a person before any confirmation goes out.
The rest of the back office.
↗
Purchase to paySource & ProcureInvoices, POs and confirmations, handled against the order.
↗
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.