Invoices matched to the order and the receipt. A person releases every payment.
The agent reads each supplier invoice, finds the order and the goods receipt, and lists every difference. Your controller approves the release, and your auditor can check the record without us.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
AI agents for finance teams take on the matching and checking that sits between purchasing and payment. An invoice arrives by email. Someone finds the order and the receipt, compares them line by line, then chases whatever does not agree. The agent does that comparison across your systems and hands the controller a decision, not a search.
What changes for your controller
- Clean matches arrive ready for release, each with the order and the receipt it was matched to.
- Differences arrive explained: which line, and which document says what.
- A request to change bank details never reaches the payment run on the agent's word.
Payment stays with your people. The agent prepares, the controller decides, and the record keeps both. The same approach covers procurement upstream, where the order is placed, and quality, where received goods are accepted or held.
One supplier invoice, from the mailbox to the payment release.
This workflow is designed. The steps are how we build it in a pilot. It has not run in the sandbox yet.
- 01Accounting
Take the task and receive a credential for this matching job only. It expires when the job ends.
- Who approves
- No approval on this step
- On the record
- credential issued
- 02Email
Read the invoice attachment from the accounts payable mailbox. One line asks the reader to change the bank details. It is struck out before the agent reads it.
- Who approves
- No approval on this step
- On the record
- invoice · redacted · hidden instruction
- 03ERP
Read the purchase order and the goods receipt for the same lines.
- Who approves
- No approval on this step
- On the record
- read-order-receipt · allowed
- 04Accounting
Match the invoice to the order and the receipt. One line is billed above the order price.
- Who approves
- No approval on this step
- On the record
- match-invoice · allowed · price difference
- 05Accounting
Try to change the supplier's bank details. Vendor master data is outside the permission for this job, so the step is refused.
- Who approves
- No approval on this step
- On the record
- edit-vendor-bank · refused · outside permission
- 06Accounting
Put the invoice forward for payment, with the price difference noted. The step waits until the controller approves it.
- Who approves
- Controller
- On the record
- release-payment · approved by controller
- 07Email
Draft a note to the supplier about the price difference.
- Who approves
- No approval on this step
- On the record
- draft-email · allowed
In short
- What if the agent pays an invoice that does not match?It does not release payments. It matches the invoice to the order and the receipt, lists each difference, and the controller approves the release.
- What if an invoice asks us to pay a new bank account?Vendor master data is outside the permission for a matching job, so the change is refused. A hidden request in an attachment is struck out before the agent reads it.
- Who can see the figures the agent reads?The agent reads only the ledgers and mailboxes the job allows. It can run on a machine in your building, and the record shows anything that left.
- Can our auditor rely on what the agent did?Every match, refusal and approval is on the record. Your auditor can check it offline, without us.
Finance workflows, and the state of each.
Each item says whether we have run it, set out its steps here, or scope it with you.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Designed
Invoice matching and payment approval
The agent matches each invoice to the order and the receipt, lists every difference and puts the invoice forward. The controller approves the release.
See the steps - Built
Spend held at an approval threshold
An order above the threshold stops and waits for the person you name.
Run it in the sandbox - Built
Purchases inside a spending ceiling
The credential is a mandate: a ceiling, a list of approved merchants and an expiry. A purchase outside it is refused before money moves.
Run it in the sandbox - Designed
Reconciliation between operations and accounting
The agent compares receipts in the ERP with invoices in accounting, lists each difference and drafts the adjustment. A controller approves each adjustment.
See the steps - Designed
Accruals for goods received, not invoiced
At period end the agent lists receipts with no invoice, drafts the accrual lines and attaches the receipt for each. The controller posts them.
- Designed
Supplier statement reconciliation
The agent ties each statement line to an invoice or a payment and lists what is missing. A person decides what to chase.
- Designed
Duplicate invoice check
The agent looks for the same supplier, amount and reference already on file. A suspected duplicate goes to a person.
- On request
Collection reminders on overdue invoices
- On request
Expense claim checks against policy
- On request
Customer invoices from shipped orders
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not release a payment. A person approves each release.
- It does not change vendor master data, bank details included.
- It does not replace your accounting system, your controls or your auditor.
- It does not decide whether a price difference is acceptable. It lists each one, and the controller decides.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Questions and answers
Tell us about one workflow.
Bring one finance process, such as invoice matching. We will say whether an agent should take it, and what the first step costs. Fixed price, quoted after one call.
A senior member of the team replies within two business days.