Platform · Autonomous agents
Autonomous agents for procurement, with limits you set
A clean invoice inside your limit is approved without anybody opening it. Everything else goes to a named person.
Autonomous agents for procurement run the rules your administrators configure, at the moment a record changes rather than when somebody gets to it. What they draft, a person sends. What sits outside your limits, a person decides.
- How it got here
- An electronic invoice from the supplier
- What happens now
- The checks run — not when somebody opens it
- Your limit
- 50,000, set by your administrators
- This invoice
- 18,400
- This invoice
- 72,000 — above the 50,000 limit
- What was approved
- Nothing
- What is recorded
- The check it failed, against the invoice
- What happens next
- A person decides
The checks run as it arrives, not when somebody opens it.
The same invoice. Two different weeks.
Most procurement automation still waits for somebody to open the record before anything happens to it.
What runs without you
Eight things it does. And the limit on each one.
Not a category of software. These are the things that actually run, what starts each one, and where it stops and waits for a person.
Eight checks run when the invoice is created, re-matched, or arrives as an electronic invoice or against a goods receipt. All eight pass and it is approved and dated without anybody opening it.
One failed check stops the approval. The invoice is flagged for review and the check that failed is recorded with it, so your team sees the reason rather than working it out from the document.
An automatic approval is recorded with the amount limit in force and how the invoice matched, at the moment it happens rather than reconstructed afterwards.
Eight advisory notes: the category, the spend pattern, contract coverage, supplier risk, the budget position, possible duplicates, a suggested approver and a reading of an attached invoice.
Those notes annotate and nothing more. They change no field on the request, and the decision stays with the person who has to make it.
Where your organisation has it switched on, approval raises the order as the requester — and the requester’s own purchase order limit still applies to it.
Where enabled, a draft request for quotation with proposed suppliers, for events under the value threshold you set. A person publishes it, and a person awards it.
Commodity risk, component lifecycle, material planning, sourcing, rationalisation, supply risk and contract extraction — opened by a person, shown to a person, and written back to nothing.
Where this already runs
In operations like yours. Not vendor scenarios.
A Leading Steel Manufacturer Unifies Procurement Operations
Multi-site manufacturer handling 6,000+ purchase requisition lines a month 6,000+requisition lines a month through one entry point4 → 1systems to raise a request, down to one0SAP modules replaced Read the story
A construction products business ends buyer-led negotiation on repeat buys
Dispersed job sites buying under group approval rules 0group approval rules changed1guided intake for every project request0core systems replaced Read the storyHow it works
An invoice, start to finish. Nobody opened it.
Six steps. Two of them are rules running on their own, and the last two are people.
-
01
System
The invoice arrives
Created in the platform, re-matched after a change, or arriving as an electronic invoice or against a goods receipt. Whichever way it lands, the checks run then — not when somebody reaches it in a queue.
-
02
Rule
Eight checks run
Inside the amount limit your administrators set. Matched against the purchase order balance. A goods receipt present. Quality approved. No contract variance. No duplicate flag. Tax agreeing. The exchange rate present.
-
03
Rule
All eight pass, and it is approved
The invoice is approved and its due date is set, with no person involved. The entry records the limit that applied and how it matched, so the decision is explainable later without anybody reconstructing it.
-
04
Rule
Or one fails, and it stops
A single failed check is enough. Nothing is approved, the invoice is flagged for review, and the check that failed is recorded against it.
-
05
Human
A person picks up the exception
Your team opens an invoice that already says what is wrong with it, rather than one that needs investigating before the question can even be framed.
-
06
Human
And every decision above the limit
An amount outside the limit your administrators set is a person’s decision, every time. That is the boundary, and it is the one you configure.
Core capabilities
What autonomous agents for procurement have to get right.
Approval that happens on arrival
Eight checks the moment an invoice lands, rather than the moment somebody opens it
- Runs when the invoice is created, re-matched, or arrives electronically or against a goods receipt
- Approved and dated without a person when all eight checks pass
- Flagged for review, with the failed check named, when one does not
- The approval records the amount limit that applied and how the invoice matched
- On for every organisation, under an amount limit your administrators set
Limits you set, not limits we ship
Every automatic path stops at a number somebody in your organisation chose
- An amount limit on automatic invoice approval
- A value ceiling above which no sourcing event is drafted
- Automatic-approval ranges on your own approval rules
- Anything outside them goes to a named person rather than through
Advice that changes nothing
Eight notes on every submitted request, none of which touches the request
- Category, spend pattern, contract coverage and supplier risk
- Budget position, possible duplicates and a suggested approver
- A reading of an invoice attached to the request
- Each note is recorded with the reasoning behind it
- Intake records show whether a person, the AI or the system acted
Drafts, and only drafts
The model-written work on this platform waits for somebody to send it
- A sourcing event drafted with proposed suppliers, under your value ceiling
- A request captured in conversation, with each value marked as stated, inferred, defaulted or confirmed
- Analysis across seven areas, opened by a person and shown to a person
- Nothing drafted is published, sent or awarded — that action is a person’s
A reason, stored when the decision is made
Not reconstructed afterwards from whatever happens to be left behind
- A flagged invoice carries the check that failed
- An automatic approval carries the limit and the matching result
- An intake note carries its reasoning and how long it took
- Where a person decides differently from an AI recommendation, intake records the link between the two
Features
Autonomous agents for procurement that hold your limits.
Five groups of features, and not one of them depends on someone remembering the policy.
What it will never do on your behalf
The automatic paths are few, and each one stops at a number you chose.
- Nothing it drafts is published, sent or awarded — a person takes that action
- An amount above your invoice limit is never approved automatically
- An invoice that fails any one of the eight checks is never approved
- Advisory notes on a request change no field on it
- Analysis is opened by a person, shown to a person, and writes nothing back
A clean invoice, approved as it lands
The checks run when the invoice arrives, not when somebody reaches it.
- Runs on creation, on re-match, on an electronic invoice and on a goods receipt
- Inside your amount limit, matched against the purchase order balance
- A goods receipt present, quality approved, and no contract variance
- No duplicate flag, tax agreeing, and the exchange rate present
- All eight pass and the invoice is approved and dated with no person involved
One failed check, and it stops
An exception that already says what is wrong with it.
- A single failed check is enough to stop the approval
- The invoice is flagged for review with the check that failed recorded against it
- Your team opens an invoice that states the problem rather than hiding it
- The reason is stored at the time of the decision, not reconstructed later
- Anything above your limit goes the same way — to a named person
Eight notes before anybody opens it
Written onto every submitted request, and changing none of it.
- The category, the spend pattern, contract coverage and supplier risk
- The budget position, possible duplicates and a suggested approver
- A reading of an invoice attached to the request
- Each note is recorded with the reasoning behind it
- Intake records show whether a person, the AI or the system acted
The model-written work waits for you
Drafted, captured or analysed — and then left for somebody to act on.
- A sourcing event drafted with proposed suppliers, under the ceiling you set
- A request captured in conversation, each value marked stated, inferred, defaulted or confirmed
- Analysis across commodity risk, lifecycle, material planning and sourcing
- Rationalisation, supply risk and contract extraction in the same set
- A catalogue purchase order raised on approval, inside the requester’s own limit
Governed AI
It runs on its own. Inside a limit you set.
- Nothing it drafts is published, sent or awarded. A person takes that action.
- Your administrators set the amount limit on automatic invoice approval.
- An invoice that fails any one of the eight checks is flagged rather than approved.
- Advisory notes annotate a request. They change no field on it.
- Analysis is opened by a person, shown to a person, and writes nothing back.
- Overrides of an auction AI recommendation and of an invoice exception record the person and a required note.
- Where a human decision differs from an AI recommendation, intake records the link between them.
Three things that happen. Only one needs a person.
An invoice nobody had to open
Your limit is set at 50,000. A supplier invoice for 18,400 arrives electronically. It is inside the limit, it matches the purchase order balance, a goods receipt exists, quality is approved, there is no contract variance, no duplicate flag, the tax agrees and the exchange rate is present. All eight checks pass, so it is approved and dated, and the entry records the limit that applied and how it matched. The first person to look at it is whoever opens it out of interest.
An invoice that waits, and says why
The next invoice is for 72,000, above the same limit. It is flagged for review with the check it failed recorded against it. Nobody has to open the document to work out what is wrong — the invoice already says so, and it waits for a person who can decide.
A request that arrives explained
An engineer submits a request for a non-catalogue component. Before a buyer opens it, eight notes are on it: what category it looks like, how it compares to the spend pattern, whether a contract already covers it, the supplier risk position, the budget, whether it duplicates something already in flight, who might approve it, and what the attached invoice says. None of them has changed a single field. The buyer starts from a request that explains itself.
Set the limit at a number you are comfortable with.
Start it low, watch what gets approved and what gets flagged, and raise it when you are satisfied. That is the whole adoption curve.
Security, compliance and recognition
Checked by auditors. Judged by the industry.
Where each compliance programme stands, and what the procurement industry has given us so far.
Security and compliance
Awards
Five, presented on stage at three industry events.
- Autonomous Procurement Platform of the Year
- Procurement Technology Innovation Award
- Unified Procurement and Supplier Management Platform
- Procurement Startup of the Year
- AI in Procurement or Supply Chain Award — Solution Provider
Before you book anything. Answered honestly.
What are autonomous agents for procurement?
They are the parts of the platform that carry out a step without waiting for a person: approving a clean invoice that sits inside the amount limit your administrators set, raising the purchase order on an approved catalogue line, and annotating a submitted request before a buyer reaches it. Each one runs at the moment a record changes, each one stops at a limit you configure, and anything outside that limit goes to a named person.
What actually runs without a person?
Invoice approval, where all eight checks pass and the amount is inside your limit — the invoice is approved and dated with nobody involved. The purchase order on an approved catalogue line, raised as the requester and still subject to their own purchase order limit. And the eight advisory notes written onto every submitted request, which change nothing on it. Everything else on this page is drafted or analysed for a person, and waits for them.
Is this AI, or is it rules?
Mostly rules, and we would rather say so. Invoice approval is eight deterministic checks — no model is involved, and none of it depends on a judgement. Models are used for the advisory notes on a request, for drafting a sourcing event or capturing a request in conversation, and for the seven analysis views. None of those changes a record on its own. If a vendor tells you their invoice approval is AI, ask them which part of it exercises judgement, and what happens when it is wrong.
What stops it doing something it should not?
The limits your administrators set, and the fact that there are only a few automatic paths rather than a general permission to act. Invoice approval has an amount limit and seven further conditions, any one of which stops it. Sourcing drafts have a value ceiling. Your approval rules have their own automatic-approval ranges. And no model output on this platform publishes, sends or awards anything — a person does that.
Can we start narrow and widen it?
Yes, and most organisations do. Automatic invoice approval is the usual starting point because its boundary is a number you choose and its behaviour is easy to check: set the limit low, watch what it approves and what it flags, and raise it when you are satisfied. The drafting and analysis features are switched on separately.
Can it send something to a supplier on its own?
No. Nothing the platform drafts — a sourcing event, a captured request, an analysis — is published, sent or awarded without a person taking that action. That is a design decision rather than a setting, and it is the one we would least want to change.
One invoice. Watch it approve itself.
No slides. Set a limit, send a clean invoice through it, then send one that breaks a check and see what it says.
Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.
Not ready to talk to anyone?
Fair enough. Both of these work without giving us your email.
Explore the next step
Procure-to-Pay
The orders, receipts and invoices the eight checks run against
Intake & orchestration
Where the eight advisory notes are written, and the approval runs
Sourcing & RFx
Where a drafted event lands, and where a person publishes it
Security & AI governance
The limits, the roles and the records behind all of it