Pay run limits
Each run is capped by total and by individual variance from the previous run; exceptions are escalated.
Business finance
Payroll and HR
Payroll errors reach people directly; agents must stay well inside the numbers.
Payroll runs on fixed dates and exact amounts, and errors reach employees' accounts at once. Agents can prepare pay runs, handle changes and answer questions, but payments should only go out within approved totals and to verified accounts. In the US, Regulation E sets consumer protections for electronic fund transfers such as payroll deposits. AgenticOpenFinance caps each run and records every change.
What agents do
What you build on AgenticOpenFinance
Bank detail changes
Changes to an employee's account need verification and a waiting period before the next payment.
Approval before release
The payroll lead approves the run on their own device with the totals shown.
Off-cycle payments
Corrections run under a separate, smaller mandate.
Evidence per run
Inputs, changes, approvals and bank responses are sealed per pay run.
Value chain
The actors in this chain
AgenticOpenFinance connects them with one identity check, one mandate model, one policy and one evidence trail.
EmployerPayroll agentPayroll leadEmployeesBankTax authority
Typical flow
A governed agent flow, step by step
- Inputs collected
- Run prepared
- Variance and limit checks
- Payroll lead approves
- Payments released
- Confirmations
- Evidence sealed
Live demo
See it in the terminal
Maya grants the household bills agent a mandate with a passkey; its payments fill the monthly cap (demo). Demo data
DemoAll companies, people, agents and amounts are fictional. Protocol names refer to public specifications; naming one is not a partnership or an endorsement.
Glossary