Customer orders into AFAS Profit,
read and checked before they land
For AFAS order management, Lleverage puts an AI agent on your shared order inbox. It reads each customer order from email, PDF or Excel, finds the sales contact and the items in AFAS Profit, checks price, stock and credit, and creates the sales order. Profit’s own blocks still apply, and exceptions wait for a person with the reason attached.
How does AFAS order management work with an AI agent?
In AFAS Profit an order is a sales order under Order Management: a sales contact, a delivery address, a delivery date, the customer’s reference and lines of items. Adding one reserves the stock it sells. The agent fills in exactly those fields, from what your customer sent, in 4 steps.
Read the order the customer sent
An email body, a PDF purchase order or a spreadsheet arrives in the shared inbox. The agent picks out who ordered, the delivery address, the requested date, the customer’s order reference and every line, each with a confidence score.
Match the sales contact and the items
The sender becomes the sales contact in Profit, a different delivery address is matched to one of that contact’s known addresses, and each line to an item code. A description that fits more than one item is held for a person.
Check price, stock and credit
Each price is compared with what Profit holds for that customer, including price agreements, and each quantity with stock in the warehouse it ships from. The credit limit is checked too, so an order Profit would block is caught before it is written.
Create the sales order and confirm
The sales order is created in AFAS Profit with the customer’s reference on it, so the stock is reserved and the packing slip follows as usual. The order confirmation goes back to the customer.
What changes for an order desk on AFAS Profit?
Today someone reads each order email, opens Order Management in Profit and keys the lines by hand, or rebuilds the file to fit the import. When the agent does that, stock is reserved as the order arrives, customers get their confirmation sooner, and your desk keeps the orders that need a decision.
Learn moreExample data
One order into AFAS Profit, start to finish.
A customer’s PDF purchase order lands in the shared inbox at 07:14. The agent reads it and creates the sales order in Profit without anyone keying it.
Example data
What the agent checks in AFAS Profit before an order is created
Item codes, price agreements, stock in the warehouse and the credit limit are checked against Profit before anything is written, and each check has its own setting. Orders that pass become sales orders 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
AFAS Profit - Confirmation sent
In 28 s - Stock reserved
Warehouse
- Price off contract
Sales Ops - Below 98% sure
Order desk - Credit hold
Credit control
AFAS Profit’s own order tools next to Lleverage
AFAS Profit offers manual entry, a CSV import, received EDI orders, order blocks and a REST API for sales orders, and its AI, Jonas, works in workflows. We read the AFAS Help Center, afas.nl and the Lleverage docs on 29 October 2026.
| AFAS Profit on its own | Lleverage | |
|---|---|---|
| An order that arrives by email or PDF | The Help Center describes adding a sales order by hand, importing a file and processing received EDI orders. Reading a customer’s own PDF or order email into a sales order is not described. | Yes: the agent reads the email body, PDF, Excel, CSV and portal exports from the shared inbox, each in the customer’s own layout, as they arrive. |
| Spreadsheets from customers | Import a sales order reads a .csv file, for example one made in Excel, through an import definition under Order Management, Management. Two consecutive rows that differ on a header field such as delivery date or order reference become separate orders. | Yes: the agent takes the spreadsheet as the customer sent it, with their own columns and item codes, and maps it to the sales order itself. |
| EDI orders | Built into Profit: received EDI orders are converted to sales orders under Order Management, Sales process. A line with the status Missing data holds the order until someone fills it in or removes the line. | EDI orders keep going straight to Profit. The agent handles the orders that arrive as emails, PDFs and spreadsheets. |
| AI in AFAS | Jonas, AFAS’s AI, analyses workflow data, fills workflow fields, drafts reactions, reads expense receipts in Pocket and helps assess supplier quotes. AFAS lists no Jonas task for customer orders or sales orders. | Yes: an AI agent for the order desk that reads, matches, checks and creates the sales order. Its Skills improve from your team’s ratings, and a person approves each change. |
| Checks before the order exists | The entry layout can report a credit limit overrun or block the order, and an order can be blocked when its amount is too low or too high, or every order held until an authorised person releases it. | Yes: items, price against the customer’s agreement, stock and credit are checked before anything is written, each with its own setting. Profit’s blocks still run on the order after that. |
| Orders that need a person | The Blocks action shows which blocks are active. Someone edits the order, or a person authorised for the Release of order action releases it. No packing slip is made for a blocked order. | Yes: the order waits in the requests inbox for the person you choose, with the line, the check and the customer’s words attached. They can answer from Teams, and the agent carries on with the answer. |
| Building it on the AFAS API | The Profit REST API’s UpdateConnector FbSales adds, changes and deletes sales orders. Only connectors activated in the App connector can be called, with an AfasToken, and a request that breaks a business rule is rejected. | Yes: our engineers connect the agent to AFAS Profit with your team, as a custom integration where needed. It fills the same fields your desk fills, so Profit checks it the same way. |
| Order confirmation | A person prints an order report for the sales contact, emails a selected order as a PDF with the E-mail action, or sends a batch of selected orders through the Output action. | Yes: the confirmation goes back to the customer once the sales order is created, without anyone selecting it. |
| Fits best when | Most orders arrive by EDI or as a CSV you already import, or a person checks each order at the screen anyway. | Customers send orders in their own PDFs, spreadsheets and emails, and someone on the desk keys them into Profit today. |
We think AFAS Profit on its own is enough when your orders arrive by EDI or as a file you already import: the blocks and the stock reservation are already yours. We think Lleverage fits when your desk spends its day keying the PDFs, spreadsheets and emails customers send. More in our guide to sales order automation.
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 AFAS Profit, so the first orders come off the desk within a few weeks. From there it automates gradually: every correction teaches it your customers, their formats and their item codes, 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 with your team after go-live, as your customers and products change.
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
Does AFAS have AI that reads customer orders?
No. Jonas, AFAS’s AI, works inside Profit workflows: it analyses data, fills workflow fields, drafts reactions and helps assess supplier quotes, and it has no task for customer orders. Orders reach Profit by hand, through the CSV import, as EDI or through the API, and the Lleverage agent adds the reading of emails and PDFs.
Can we build order automation on the AFAS Profit REST API ourselves?
Yes, if you have developers. UpdateConnector FbSales adds, changes and deletes sales orders once activated in an App connector, and Profit rejects a request that breaks a business rule. The connector takes structured fields, so your code has to read each customer’s PDF or email and match the items. That reading and matching is what the agent does.
What happens to the orders we already receive by EDI?
They stay as they are. Profit converts received EDI orders into sales orders itself, and a line with missing data waits there until someone completes it. The agent works on everything else: the emailed PDFs, the spreadsheets and the order lines typed into an email by customers who will never set up EDI with you.
What if an order would exceed the customer’s credit limit in AFAS?
The agent checks credit before it writes the order, so that order waits for the person you choose, with the amount and the limit attached. Your rules decide whether it goes ahead. Profit keeps its own credit limit check in the entry layout, and only someone authorised for Release of order can release an order Profit has blocked.
How does Lleverage connect to AFAS Profit?
AFAS Profit is on our integrations page. Our engineers set up the connection with your AFAS administrator. On AFAS’s side, an outside application can call only the connectors activated in an App connector. The agent fills the same sales order fields your desk fills, so Profit reserves stock and runs its blocks as for an order keyed by hand.
How long until the first orders are created in AFAS?
The first process typically runs supervised within a few weeks. Our forward deployed engineers start with the customers who send the most orders, and someone from your desk can show the agent how they key an order on a screen-share call. A person checks each sales order at first, and the agent takes more on as its accuracy shows.
The rest of the back office.
↗
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.