The payment run prepared and checked. A named person releases it.
The agent builds the run from approved invoices, holds any payment to a changed bank account and refuses a payment split to pass a limit. The release stays with your finance lead.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for payment approval prepares the payment run and checks it before anyone signs. Each week someone gathers the invoices due, confirms each one was matched and approved, looks for accounts that changed since the last run, and builds the proposal. The agent does that preparation. Your finance lead releases the run, as today.
This workflow is designed and has not run in the sandbox yet. It starts where invoice matching ends. A related step is built: in the sandbox, an order above a threshold stops and waits for a named person. The guarantees set out what holds in both.
One payment run, from the approved invoices to the remittance advice.
The steps as designed, each with its system and its line on the record.
- 01Accounting
Take the payment run and receive a credential for this run only. It may prepare payments and may not send money.
- Who approves
- No approval on this step
- On the record
- credential issued · this run only
- 02Accounting
Read the invoices due in this run and their due dates.
- Who approves
- No approval on this step
- On the record
- read-due-invoices · allowed
- 03Accounting
Check that each invoice has a match and an approval on the record. One has neither, so it stays out of the run.
- Who approves
- No approval on this step
- On the record
- check-approvals · allowed · one held
- 04Accounting
Compare each supplier's bank account with the account used in the last run. One changed, so that payment is held for a call-back.
- Who approves
- No approval on this step
- On the record
- bank-change · allowed · payment held
- 05Accounting
A request in the queue asks for one large invoice to be paid in two parts, each under the approval limit. Splitting a payment is outside the permission, so the step is refused.
- Who approves
- No approval on this step
- On the record
- split-payment · refused · outside permission
- 06Documents
Draft the payment proposal, with each held payment and its reason listed.
- Who approves
- No approval on this step
- On the record
- draft-proposal · allowed
- 07Accounting
Release the run. It waits until the finance lead reviews the proposal and approves it.
- Who approves
- Finance lead
- On the record
- release-run · approved by finance lead
- 08Email
Send each supplier its remittance advice. Account numbers are masked before the email leaves.
- Who approves
- No approval on this step
- On the record
- remittance · redacted · account numbers
The systems, by type
We name systems by type. Yours are named in the assessment.
Accounting
Due invoices, approvals, bank accounts on file and the payment run itself.
Documents
The payment proposal the finance lead reviews.
Remittance advice to each supplier, checked before it leaves.
The approval, the refusal, the record
- A person approves: Release the run. It waits until the finance lead reviews the proposal and approves it.Releasing the run moves money out of the company, so the finance lead reviews the proposal and its held items and approves it.
- Refused: A request in the queue asks for one large invoice to be paid in two parts, each under the approval limit. Splitting a payment is outside the permission, so the step is refused.Two payments under the limit would avoid the approval the limit exists to force, so the permission does not allow a payment to be split.
- On the recordEach invoice in the run, each payment held and why, the refused split, who released the run, and what was masked in each remittance.
What goes on the record
- credential issued · this run only
- read-due-invoices · allowed
- check-approvals · allowed · one held
- bank-change · allowed · payment held
- draft-proposal · allowed
- release-run · approved by finance lead
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not send money. Your accounting system and your bank route do that, after the release.
- It does not confirm a changed bank account. A person calls the supplier on a number already on file.
- It does not set your approval limits. You set them, and the record shows each change.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.