Unit4 invoice automation works in layers. Unit4 itself handles purchase requests, purchase orders, goods receipts and 2 or 3-way matching against tolerances. Capture tools, Unit4's own service among them, read the invoice and register it. An AI agent working alongside Unit4 handles what both leave behind: messy emails, non-PO invoices, mismatches and supplier confirmations. You keep Unit4 in every case.
At Lleverage we think a Unit4 team should switch on everything Unit4 already does before buying anything, and then put an AI agent on the documents that still land on a person's desk. Clean, matched invoices already pass through Unit4. What lands on a desk is the scanned PDF with three purchase order numbers on it, the freight surcharge nobody ordered and the buyer's email that says "same as last month, but 40 instead of 25". Our AI agents for procurement and AI agents for accounts payable are built for that work. If you want to see it on your own Unit4 documents, book a demo.
What does Unit4 automate for purchase orders and invoices out of the box?
Unit4's own documentation of its procurement process in Unit4 ERPx describes a full procure-to-pay chain. A requester picks items from an internal catalogue, or punches out to a supplier's catalogue, and submits a purchase request. The request goes through an approval workflow with a budget check. Approval limits follow your delegation of authority, so a project request goes to the project manager and a larger one also to the cost centre manager.
Once approved, Unit4 turns the request into a purchase order on its own, and can merge several requests for the same supplier into one order. The order can be linked to a contract so it carries the agreed prices, and it can be emailed to the supplier as soon as it is approved. Unit4 also flags orders whose delivery date has passed without a full receipt.
On the invoice side, Unit4 registers an incoming invoice against the order number. Entering that number pulls in the order lines and the cost allocation from the purchase order. Unit4 then runs a 2 or 3-way match against the tolerances set on the order, for ordered quantity, amount and received quantity. An invoice inside the tolerances is approved by the workflow and posted to the general ledger and the payables ledger. An invoice outside them goes to a person to review, and a missing goods receipt creates a task for whoever should book it.
| Step | Unit4 on its own | Capture tool | AI agent alongside Unit4 |
|---|---|---|---|
| Purchase request | Catalogue request, approval by delegation, budget check | Not its job | Turns a free-text request from email or Teams into a request or draft order |
| Purchase order | Created from the approved request, emailed to the supplier | Not its job | Drafts the order on contract terms for a person to sign |
| Supplier confirmation | Reply read and keyed by a buyer | Not its job | Reads the reply and compares it with the order line by line |
| Invoice data entry | Registered by a person against the order number, or read first by Unit4's own Invoice Data Capture service | Reads the invoice and registers it | Reads any layout, finds the order even when the number is missing or wrong |
| Matching | 2 or 3-way match within tolerances | Uses Unit4's match, some add their own | Explains the mismatch and gathers the evidence |
| Exceptions | Workflow task for a reviewer | Validation screen | Asks the right person with the order, receipt and invoice attached |
Where does manual work remain in Unit4 procurement and invoicing?
Unit4's matching starts once an invoice is registered with an order number. Most of the hours go before that point and in the exceptions after it. According to Ardent Partners' Accounts Payable Metrics that Matter in 2026 report, the average invoice exception rate is 19.9%. In Ireland's Central Statistics Office survey of enterprises for 2023, only 36% of manufacturers used electronic invoices suitable for automated processing. The same survey found 46% of manufacturers still used paper invoices.
Invoices arrive in every layout. Suppliers send PDFs, scans, photos and emails with the invoice in the body. One supplier puts the order number in the header, the next in a line description, a third leaves it out. Someone has to read each one and find the order before Unit4 can match anything.
Energy, rent, freight, repairs and subscriptions often arrive with no purchase order at all. Unit4's process description covers contract invoices for periodic costs such as utilities, but anything without an order or a contract still needs someone to choose the supplier, the cost centre and the approver.
Price and quantity mismatches go to review in Unit4, which is the right control. The reviewer then opens the order, the receipt and the invoice, works out whether the gap is a price change, a partial delivery or a surcharge, and emails the supplier or the buyer.
Supplier order confirmations arrive by email, often with a new delivery date or a substitute article. Unit4 emails the order to the supplier, and in most teams a buyer reads the reply and updates the order by hand. Our post on purchase order confirmation automation goes into that step in detail.
Purchase requests often come in as free text. The catalogue works for office supplies, but a production lead who needs 40 bearings by Friday sends an email or a Teams message, and a buyer retypes it.
Which AI tools automate purchase order and invoice processing in Unit4 ERP?
There are 2 kinds of tool to put next to Unit4's own features.
Capture tools read invoices and hand the data to Unit4. Unit4 sells its own Invoice Data Capture service, which combines OCR with Microsoft-powered AI and is built into Unit4 ERP. Arribatec sells a service that connects Unit4 ERP and ERPx to Rossum's OCR, shares purchase order and supplier data with it, takes invoices from email and matches them to purchase orders. Kefron's accounts payable product syncs suppliers, purchase orders, goods receipts, tax and GL codes from Unit4, runs 2 and 3-way matching and sends the approved invoice data back to Unit4.
AI agents do the work around the documents as well as reading them. An agent reads the invoice, decides what it is, finds the order, compares it with the receipt, and when something is off it gathers the evidence and asks the person who can decide. The same agent can read a supplier confirmation or turn a buyer's email into a draft order.
How does an AI agent handle Unit4 invoice automation step by step?
Take a supplier invoice from Noordkamp Lagers B.V. that arrives as a PDF in the finance inbox, for 3 order lines and a freight charge.
- The agent reads the PDF, whatever the layout, and pulls out the supplier, invoice number, dates, lines, VAT and totals.
- It finds the purchase order in Unit4. If the invoice quotes no order number, it searches open orders for that supplier by article, quantity and amount.
- It compares each line with the order and the goods receipt, using the same tolerances your team uses.
- If everything agrees, it enters the invoice in Unit4 against the order, filling the fields a clerk would fill, and Unit4's own matching and approval workflow takes it from there.
- If the freight charge is not on the order, it routes the invoice to the buyer who placed the order, with the three documents side by side and a one-line summary of the gap.
The agent scores how sure it is of each invoice. Below the line your team sets, a person decides. Above it, the invoice goes through on its own. Only you move that line. Start with every invoice reviewed and raise the line as the numbers earn it. The agent never releases a payment: that stays in Unit4 with your finance team.
The same pattern covers purchase orders. A request arrives as an email, the agent matches it to the contracted supplier and price, and drafts the order for a person to sign. Our guide to purchase order automation from email to ERP walks through that flow.
Who approves what when an AI agent works in Unit4?
Keep Unit4's approval workflow as the place where invoices and orders are approved, under your existing delegation of authority. The agent prepares the work and asks the questions.
In practice that means 3 kinds of question:
- A decision: the invoice is 4% over the order price, so the agent asks the buyer to accept, reject or query the supplier, and carries on with the answer. In Lleverage this is a decision request assigned to a named person, who can correct a line in the table before approving.
- Missing information: with no purchase order and no contract, the agent asks the budget holder which cost centre the invoice belongs to, in Teams, Slack or by email.
- A rule change: when a supplier changes its invoice layout, or a new surcharge becomes normal, a person approves the change to how the agent works, and the agent applies it from then on.
Every action is logged, and the account the agent uses in Unit4 decides what it can see and change. Give it the same rights a payables clerk has, or fewer. Our control and governance page covers roles, scopes and the audit trail.
How does an AI agent connect to Unit4?
Unit4 is not one of the ERPs named on our integrations page, and we do not offer a ready-made Unit4 connector. The agent connects through Unit4's own interfaces, set up as a custom integration by our engineers with your Unit4 team.
Unit4 is built to exchange data with outside systems: partner products such as Kefron's already read purchase orders and goods receipts from it and send invoices back. Its Extension Kit runs flows that start on a schedule, on a webhook from another application, or on an event published in Unit4 ERP, and its actions include calling a REST API and publishing an event. Unit4 says ERP7 customers, in the cloud and on-premises, can request Extension Kit access from their account manager. An event in Unit4 can therefore start the agent's work, and the agent writes its results back through Unit4's interfaces.
On our side, a custom integration stores the Unit4 credentials securely, outside chat and instructions, with the access scope you choose. Supported sign-in methods include OAuth2 client credentials, API keys and Windows (NTLM) authentication, which matters for on-premises Unit4 installs. Where a screen has no API behind it, the agent can work the screen with the access a person has. Nothing is migrated and Unit4 stays your system of record.
Should you choose a capture tool or an AI agent for Unit4?
| Your situation | Better fit |
|---|---|
| Most invoices quote a valid order number and match first time | Unit4 on its own, or a capture tool |
| The main cost is typing invoice data into Unit4 | Capture tool |
| Many invoices have no order, a wrong order number or a surcharge | AI agent |
| Mismatches take longer to resolve than invoices take to enter | AI agent |
| Buyers chase supplier confirmations and retype purchase requests | AI agent |
| You want one agent across ordering, confirmations and invoices | AI agent |
What should a first Unit4 pilot look like?
- Pick one stream: invoices from your 20 largest suppliers, every non-PO invoice, or supplier confirmations for one buying team.
- Count the baseline: documents a week, the share that matches first time in Unit4, and how long exceptions take.
- Use the tolerances and approvers already in Unit4, and write down who decides each kind of exception.
- Start with a read-only connection. The agent reads orders and receipts and proposes the entry, and a person enters it.
- Review every proposal for a few weeks. Track how often the agent was right and why it was wrong.
- Let the agent register invoices in Unit4 above the confidence line, and keep the rest with a person.
- Add suppliers, then confirmations or purchase requests.
"It’s a matter of building trust in the organisation with these kinds of initiatives. You can’t just throw something like this over the fence." Cees Maaskant, General Manager, Xpol
At Lleverage our forward deployed engineers build the first process with your team, and it typically runs supervised within a few weeks. Our post on three-way matching automation covers the matching rules in more depth.
Frequently asked questions
Does Unit4 have built-in invoice matching?
Yes. Unit4's documented procurement process registers an incoming invoice against the purchase order number, pulls in the order lines and cost allocation, and runs a 2 or 3-way match against tolerances set on the order. An invoice inside tolerance is approved by workflow and posted. One outside tolerance goes to a reviewer, and a missing goods receipt creates a task.
Do I need to replace Unit4 to use an AI agent?
No. The agent works alongside Unit4 through Unit4's own interfaces and, where useful, events from Unit4's Extension Kit. Unit4 stays your system of record for orders, receipts, invoices and approvals. The agent fills the same fields a person fills, so Unit4 checks its work with the same rules it applies to your team.
Can an AI agent process non-PO invoices in Unit4?
Yes, with a person in the loop where the rules are unclear. The agent reads the invoice, checks it against contracts and past invoices from the same supplier, and proposes a cost centre and approver. When it is unsure, it asks the budget holder in Teams, Slack or by email and carries on with the answer.
Does Lleverage have a ready-made Unit4 connector?
No. Unit4 is not on our integrations page as a named ERP. Our engineers connect to Unit4 through its own interfaces as a custom integration, with your Unit4 team, during delivery. The credentials are stored securely with the access scope you choose, and the Unit4 account the agent uses decides what it can see and change.
Who approves invoices when an AI agent is involved?
Your people, through Unit4's existing approval workflow and your delegation of authority. The agent prepares the invoice, explains any mismatch and asks the right person to decide. You set the confidence line below which a person reviews every invoice, and the agent never releases a payment.
Start with the invoices that wait longest
Pull last month's Unit4 invoices that sat in review for more than a week and look at why. That list tells you whether a capture tool or an AI agent fits. If it is mostly missing orders, mismatches and supplier questions, book a demo and bring a sample. We will show the agent working on your own documents and tell you what it would and would not take off your desk.



