All solutions
Functional team · Finance

A matching agent the finance team owns, tested before it is released.

Payments reach the finance team's bank lines under names that don't match the customer list.

For finance teams, and the IT team that governs their agents.

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 matches our bank payments to customer accounts.
Unflood created the agent from this conversation, ran its tests on past months and asked a person to approve the release.
  • Unflood: Matching agent created from this conversation 3m ago
  • Unflood: Tests run on past months 2m ago
  • Unflood: Released after a second person approved 1m ago
  • Unflood: Shared with the finance 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 Finance, to learn from

Example 1

Match a bank payment to the right customer account

On Unflood: An agent, a read-only bank-feed tool and a payer-alias list.

Example 2

Use earlier matches as a hint for names it has not seen

On Unflood: A second list, "seen before", beside the alias list.

Example 3

Post to the ledger only after a person approves

On Unflood: A ledger tool set to always ask, and a release a second person approves.

How the first example fits together

Tool
Bank feedRead-only. Reading needs no approval.
Agent
MatcherTakes a bank line and answers with a status and an account, using the payer-alias and seen-before lists.
Person
A second person approvesThe release needs someone other than the one who packaged it.
Tool
LedgerWrites only with approval, every time.

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 Finance: Match a bank payment to the right customer account

  • ToolsReads the bank feed and the ledger; every write waits for a person.
  • Builds itA member of the finance team describes the matching rules in plain words.
Recorded from the conversation Matcher
Bank feedSecond personLedger
Drawn on sample data.

Test it

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

In Finance: Cases written from past months, run against each version.

  • TestsCases written from past months, run against each version.
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 Finance: A second person, not the one who packaged it.

  • Release with approvalA second person approves each release; the builder cannot approve their own.
  • Approves itA second person, not the one who packaged it.
Release waiting for approval
  • Packaged byA member of the finance team describes the matching rules in plain words.
  • Needs approval fromA second person, not the one who packaged it.
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 Finance: Whoever starts a run.

  • Uses itWhoever starts a run.
Who can use it
  • The Finance teamWhoever starts a run.
  • 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.

In Finance: Every change is one entry in the ledger, with who made it.

  • 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
  • UnfloodConnects the bank feed, read only.
  • UnfloodAdds the payer aliases as reference data.
  • UnfloodConnects the ledger; every write waits for a person.
  • ApproverA second person approves the release; the builder cannot approve their own.
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

Payments reach the finance team's bank lines under names that don't match the customer list.

With Unflood

A matching agent the finance team owns, tested before it is released.

Your people do
  • Builds itA member of the finance team describes the matching rules in plain words.
  • Approves itA second person, not the one who packaged it.
  • Uses itWhoever starts a run.
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

In the reference journey's recorded replay: 10 steps, 8 by Unflood and 2 by your people. Counted from the journey fixture, on example data.

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