All solutions
Support function · Procurement

Invoice and terms checks against the purchase order, before approval.

Supplier terms and invoices pile up in inboxes before anyone checks them.

For procurement teams, the procurement lead who approves their releases, and the IT team that governs them.

How the example fits together: tools and an agent built on Unflood, with a person approving before anything is written.

Made from a conversation in Claude, released to the AI platforms your team already uses, running in your own environment.

Claude
Turn this conversation into an agent that checks each invoice against its purchase order.
Unflood created the agent from this conversation, ran its tests on past invoices and asked the procurement lead to approve the release.
  • Unflood: Invoice-check agent created from this conversation 3m ago
  • Unflood: Tests run on past invoices 2m ago
  • Unflood: Released after the procurement lead approved 1m ago
  • Unflood: Shared with the procurement team Just now

See it happen in a chat

A person on the team asks for an agent. Unflood does the building in the background and comes back for the decisions that are yours.

  • Unflood tests them.
  • A person approves each release.
  • They are shared with the right people.
  • They are kept up to date, so you step in only when a decision is yours.

Examples for Procurement, to learn from

Example 1

Check each invoice against its purchase order

On Unflood: A tool that reads purchase orders; a test suite of past invoices.

Example 2

Check supplier terms against the standard terms

Example 3

Flag any price or term outside the order

How an invoice check fits together

Tool
Purchase ordersReads the order an invoice refers to.
Knowledge
Standard termsWhat supplier terms are checked against.
Agent
Invoice checkerFlags a price or term outside the order.
Person
The procurement lead approvesEach release needs someone other than the builder.

Six moments that make the difference

Each one is shown on sample data, with this team's own example where there is one.

Build it from a conversation

Describe the agent in a Claude chat. Unflood records it, its tools and its tests.

In Procurement: Check each invoice against its purchase order

  • ToolsThe purchase order register, read only.
  • KnowledgeThe standard supplier terms, bound by reference.
  • Builds itA category buyer, from the checks they run by hand.
Recorded from the conversation Invoice checker
OrdersStandard termsProcurement lead
Drawn on sample data.

Test it

Suites and a judge run it; each failed case becomes an item to fix.

In Procurement: Past invoices with known overcharges.

  • TestsPast invoices with known overcharges.
Test lab
  • A case failsJudged against the version tested.
  • It becomes an item to fixNothing is lost between runs.
  • Retest, then release
Drawn on sample data.

Release it with approval

Package a version. Nothing reaches people without a person's approval; the builder cannot approve their own.

In Procurement: The procurement lead.

  • Release with approvalThe procurement lead approves each version.
  • Approves itThe procurement lead.
Release waiting for approval
  • Packaged byA category buyer, from the checks they run by hand.
  • Needs approval fromThe procurement lead.
The builder cannot approve their own release.
Drawn on sample data.

Share it

Choose who can use it, person by person or team by team, where the team already works.

In Procurement: The accounts payable team.

  • Uses itThe accounts payable team.
Who can use it
  • The Procurement teamThe accounts payable team.
  • A named personChoose person by person or team by team.
Drawn on sample data.

Keep it up to date

Change it, retest it, release the next version. Every version can be rolled back.

Versions
  • Current versionLive.
  • Next versionChanged, retested, waiting for approval.
  • Roll backEvery version can be rolled back.
Drawn on sample data.

The organisation stays in control

Members, roles and a record of every change belong to the organisation.

  • A workspace for the organisation, on its proven domains
  • Members and roles: who uses an agent and who changes it
  • Release approval by a second person
Record of every change
  • The builderCreated the agent.
  • UnfloodRan the tests.
  • The approverApproved the release.
Drawn on sample data.

How the team gets there faster

Your people describe the work and approve it. Unflood does the building, testing and publishing.

Today

Supplier terms and invoices pile up in inboxes before anyone checks them.

With Unflood

Invoice and terms checks against the purchase order, before approval.

Your people do
  • Builds itA category buyer, from the checks they run by hand.
  • Approves itThe procurement lead.
  • Uses itThe accounts payable team.
Unflood does
  • Connects your tools and data
  • Writes and runs the tests
  • Packages each version
  • Publishes it where your team works
  • Retests every change before the next release
  • Keeps the record of who changed what

Talk to us about your team

Tell us the work your team wants an agent for. We set up a workspace with you and build the first one with the people who know the work.

Get in touch