Creating orders in Exact Online takes time: selecting a customer, searching for items, entering quantities, setting delivery dates. With Ledger Botje, you do this in one sentence via the MCP protocol.
Creating sales orders
Tell your AI assistant: "Create a sales order for customer Bakkerij Jansen with 200 units of item BR-001 and 50 units of item BR-002."
Ledger Botje looks up the customer, finds the items, creates the order and adds the lines. You immediately receive a confirmation with the order number.
Creating purchase orders
The same works for purchasing: "Create a purchase order at supplier Van Dijk Supplies for 1000 units of item VP-500." The AI looks up the supplier, checks the item and creates the order.
Adding order lines
Already have an existing order? You can add lines: "Add 100 units of item C-300 to sales order SO-2026-0153."
Booking goods receipts
When a delivery arrives, you simply book the receipt: "Book a goods receipt for purchase order PO-2026-0089, 500 units of item VP-500." The stock is automatically updated in Exact Online.
Processing goods deliveries
When shipping orders: "Create a delivery for sales order SO-2026-0153." You can also include a track & trace code so your customer can track the shipment.
Important: Basic vs. Advanced
Creating orders, booking receipts and deliveries is only available with the Advanced plan. With Basic you can search orders and view details, but not create or modify them. View the plans and pricing for a full overview.
Haven't set up MCP yet? Follow our setup guide and you'll be ready in 5 minutes. Also read how to check stock levels with your AI assistant.
Where the manual work in orders actually sits
Creating an order in Exact Online does not take fifteen minutes. What costs time is everything around it: finding the customer, checking the item exists, pulling the right price, seeing whether there is stock and whether the delivery date is feasible. Only then do you type the order in.
Those are exactly the steps an AI assistant can chain. You give the instruction in plain language and the assistant looks up the customer, checks the item and creates the order. If the customer name is spelled slightly differently, you get a suggestion list rather than an error.
Creating an order in practice
A realistic instruction looks like this: "Create a sales order for Bakery Jansen: 200 units of A1001 and 50 units of B2003, delivery next Friday."
The assistant finds the customer, checks both items exist, pulls the customer-specific prices and creates the order. What you get back is the order number plus a summary of what was recorded. That summary is the important part: check it before moving on.
Three things to watch
- Check the lines, not just the header. An order with the right customer but a wrong item code looks fine at first glance.
- Watch the price. If a customer has tiered or contract pricing, check it was applied. Ask explicitly if unsure.
- Name the administration. With several administrations the order may otherwise land in the wrong set of books.
When this pays off and when it does not
This pays off for orders that differ each time: a customer calls, emails or messages with a varying composition. Then the assistant is faster than the entry screen.
For a steady stream of identical orders - every webshop order becomes a sales order - an iPaaS scenario fits better, because it runs unattended. See MCP versus iPaaS for that trade-off.
Starting without risk
Only enable write access after a week of read questions whose answers checked out. Then start with one bounded task - sales orders only - and verify the first ten by hand in Exact Online. More on how write access works is on the security page.