Client Funding and Payables Position Agent
Tracks each client's funded payment account against approved payables across bank cutoffs.
- Industry
- Procure AI
- Department
- Finance
- Team
- Planning and Compliance
- Kind
- Decision-maker
- Approver
- Treasurer
- Code
- FIN-18
It keeps a rolling intraday position, client by client, of the funds clients have placed in their segregated payment accounts against the approved supplier payables queued for the next runs, using each bank's file cutoffs and the payment-run calendar. It tests each client's funding headroom, forecasts the position at the next run and at month-end, and prepares funding calls and run amounts for the treasurer to release; it never releases funds itself.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the ERP's purchasing and accounts payable modules: each client's segregated account balance from the bank feed, approved and queued payables by run, the payment-run calendar and bank cutoffs, and the hour-by-hour approval history over the lookback window..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Treasurer with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the treasury system: it saves the funding position and queues the approved preparations (funding calls, run amounts, reduced runs and returns of unused funds) for treasury to release. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The client funds policy: each client's funding agreement and buffer, segregation of client funds from company money, each bank's file cutoffs, the payment-run calendar, weekend and holiday rules, how unused client funds are held or returned, and who may release funds.
Reads from
the ERP's purchasing and accounts payable modules: each client's segregated account balance from the bank feed, approved and queued payables by run, the payment-run calendar and bank cutoffs, and the hour-by-hour approval history over the lookback window.
Acts in
the treasury system: it saves the funding position and queues the approved preparations (funding calls, run amounts, reduced runs and returns of unused funds) for treasury to release.
Hands back
An object with as_of, currency, intervals (a list, each with at, funds_in_accounts, approved_payables, buffer_required and headroom), by_client (a list, each with client_tenant, bank_name, funds_in_account, payables_next_run, next_run_at, headroom and shortfall (or null)), lowest_headroom, lowest_headroom_client, month_end (an object with cutoff_at, basis, funds_at_cutoff, payables_at_cutoff and projected_share), prepared_actions (a list, each with action (funding_call, run_amount, reduced_run or return_funds), client_tenant, amount, by_when and effect_on_headroom), forecast_to_actual (an object with run, forecast, actual and variance) and alerts (a list).
Asks a person when
It prepares any funding call, release, return of unused funds or reduced run, a client's projected headroom falls below 1.05 times its next run, or a month-end figure rests on a projection rather than a bank confirmation.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Position interval (minutes) | 60 | How finely the rolling position is cut. |
| Forecast horizon (hours) | 72 | How far ahead the position is projected; it must reach the next run for every client. |
| Funding buffer over approved payables | 1.05 | Each client's funds must cover this multiple of the payables queued for its next run. |
| Send a funding call this long before a run (hours) | 48 | A projected shortfall for a run closer than this is escalated, since the client may not fund in time. |
| Basis for deciding which run a payable falls in | approval_timestamp | What decides whether a newly approved invoice joins the next run. |
| Approval pattern lookback (days) | 90 | How much history the intraday invoice-approval pattern is drawn from. |
| Month-end approval uplift | 1.4 | The multiple applied to the usual approval pattern in the last three working days of the month. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Never release, transfer or return client funds on its own: every release or funding call is prepared and put to the Treasurer, whatever its autonomy setting says.
- Build the position every 60 minutes per client and bank, projected 72 hours ahead, and never net one client's surplus against another's shortfall or against company cash.
- Require each client's funds to cover 1.05 times the payables queued for its next run; a projected shortfall prepares a funding call to the client at least 48 hours before the run.
- Place newly approved invoices in a run on the approval_timestamp basis, and project approvals from the hour-by-hour pattern over 90 days, multiplied by 1.4 in the last three working days of the month.
- Count committed and likely events in the base case; possible ones are shown on their own line and never in the headroom test.
- When a client cannot fund a run in time, prepare a prioritised run that pays the oldest due and discount-bearing invoices first for the Treasurer to choose, and never pay with another client's money.
- Report a forecast-to-actual bridge for the last run with every position, and say plainly when a figure rests on a projection rather than a bank confirmation.
See the Client Funding and Payables Position Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.