An AI payment run agent selects the invoices that are approved, due in the window and free of holds, and builds the proposed run by entity, currency and payment method.
A payment run window opens for a set date.
The agent gathers approved, unblocked invoices.
It checks holds, duplicates and bank details.
A treasury analyst reviews the run and removes items.
The run goes to approvers for release.
The agent reports what paid and what was held.
It re-checks every item at the moment of assembly for new blocks, such as an open dispute, a changed bank record, a credit to net off or a supplier on hold.
It produces a run summary with totals, exclusions and reasons, so the approver can see what is in, what is out and why.
A payment run compresses many decisions into one release, so a mistake in assembly is paid out at scale.
An invoice approved yesterday may be disputed today.
Different entities and currencies run separately.
Open credits are missed and the supplier is paid in full.
Teams approve quickly to hit the bank cut-off.
An item left out leaves a supplier wondering why.
The agent picks invoices that are approved, due in the window and not on hold.
It tests each item for disputes, bank changes, duplicates and open credits at that moment.
It splits items by entity, currency and payment method.
It shows totals, exclusions and the reasons for each exclusion.
A finance approver reviews and decides; release stays with authorised staff.
Bring a small sample and watch Flo work through it.
| Aspect | By hand | With the agent |
|---|---|---|
| Assembly | Runs are assembled from exports. | The run assembles from approved, unblocked invoices. |
| Last-minute holds | A held invoice is found after release. | Final checks run just before the review. |
| Review | Reviewers scan long lists. | Reviewers see exceptions first. |
| Explaining | Why items were left out is unclear. | Each exclusion shows its reason. |
| Reporting | Run results are tallied later. | A summary is ready after the run. |
| If | Then | Who decides |
|---|---|---|
| Invoice approved and no holds | Includes it | None |
| Invoice has an open hold | Excludes it with the reason | AP analyst resolves |
| Bank details unverified | Excludes it | Vendor admin verifies |
| Possible duplicate | Excludes it | AP analyst decides |
| Supplier is blocked | Excludes it | Vendor admin decides |
| Run total unusually high compared with past runs | Flags the total | Treasury reviews |
The agent rebuilds the run for the new date and rechecks terms. Treasury confirms.
The agent offers an off-cycle option with the same checks. An approver decides.
The agent lists failed items and reasons. Treasury decides on retry.
The agent separates entities and their bank accounts. Treasury confirms.
Talk it through with the team. We will map it to your steps and show where a person stays in control.
Assemble runs for comparison.
Run final checks.
Highlight exceptions.
Report after each run.
This shows how often items fail a last-minute check. A high rate suggests holds are being placed late or approvals are happening too early.
Quick answers to what people ask most about payment run.
Book a demoIt is a scheduled batch process in which approved, due invoices are gathered and paid together, often weekly and by payment method.
It assembles the proposed run, re-checks each item for blocks, nets credits and summarises inclusions and exclusions for approval.
No. A finance approver approves and authorised staff release it. The agent prepares and checks.
A run is the scheduled event and its logic. A batch is the specific group of payments created for a bank or method, which can be one outcome of a run.
Payment scheduling is the step of deciding on which date each approved invoice should be paid, balancing due dates, early-payment discounts, cash availability and supplier terms.
→A payment batch is a group of payments bundled together for processing through a single bank or payment method, such as one bank transfer file or one card run.
→Bank file generation is the creation of the payment instruction file that a bank accepts, listing each payee, account, amount and reference in a required format.
→Payment approval is the final authorisation, usually by finance, of a payment or batch before money is released, separate from the earlier approval of the invoice itself.
→Bring a small sample of real items. We will show what Flo handles on its own and where it hands over to your team.
