Every function in the company gets Agent Employees. Each one reasons about a single kind of thing — an invoice, a supplier, a commitment, a period, a payment run, a bank statement. How many you hire depends on your business, not on our packaging. The Agent AP Specialist is the first to go live, for SAP Business One.
Procure to Pay is the first cycle, spanning Finance and Procurement, with up to six Agent Employees. Order to Cash and People follow.
Founder
runs the whole company
Procurement
Procure to Pay
count varies by business
Sales
Order to Cash
Operations
Order to Cash
HR
People
An employee with no NEVER column is a liability, not a colleague. Every one below says what it proposes and what it will never do — and nothing on the never list can be unlocked by configuration.
Finance
Subject · One supplier invoice
Should this invoice be posted — and if not, why not?
Duties
Never
Procurement
Subject · One vendor
Is this supplier who and what it claims to be — still?
Duties
Never
Procurement
Subject · One order or receipt
What did we order, receive or invoice that does not line up?
Duties
Never
Finance
Subject · A period
Does the period reconcile, and are the working papers ready?
Duties
Never
Finance
Subject · A payment run
What should be paid, and when?
Duties
Never
Finance
Subject · A bank statement
Does the bank agree with what we believe we paid?
Duties
Never
Count the subjects you have and you have your roster. Duties that do not apply to your localization are absent, not switched off.
| Company | Employees | Why |
|---|---|---|
| UK services company — no POs, pays from the bank portal | 2 | No commitments to age, no payment run in the ERP; VAT recoverability is a duty of the AP Specialist |
| US distributor — PO-driven, 1099 filer | 5 | Use tax and withholding are AP duties; working papers a Period duty; bank reconciled elsewhere |
| Indian SMB on SAP Business One — GST, MSME exposure | 4 | GSTR-2B reconciliation is the Period Specialist's whole reason to exist here |
| Group with UK and US entities | 6 | Both localizations live at once; duties resolve per company, per document |
The rule that keeps it safe
There is no supervising agent and no employee that reviews another's work. Two agents are not segregation of duties — a human approver has a name, a signature and a career. Where two bundles of work would need grants that one of them must never hold, they are two employees. Everything else is a duty, switchable per company.
Every Agent Employee has a row: its state, its autonomy level, where it works, what it may spend alone, who is answerable and what is waiting for a decision.
| State | Autonomy | Works in | Spend limit | Answerable | Decisions | |
|---|---|---|---|---|---|---|
| Agent AP Specialist | Active | L3 · controlled | Finance | $10,000 USD | 2 owners | 2 waiting |
| Agent Supplier Specialist | Shadow | L0 · observe | Procurement | no autonomous spend | 1 owner | 1 waiting |
| Agent Commitment Specialist | Shadow | L0 · observe | Procurement | no autonomous spend | 1 owner | — |
Each Agent Employee is hired into shadow, compared against your team's decisions, then granted authority level by level — L0 to L4 — within a spend limit and with a named owner answerable for it.
A workflow assessment counts them — and tells you how many Agent Employees that is, with numbers.