Approach
Agent-centric in the middle. Human-centric on the money.
We do not drop a generic agent onto Accounts Payable. We map agents onto your existing workflow — the path a bill already takes from PO to pay — then delete the archaeology and keep the yes.
Human-centric
Agent-centric
- The agent holds the goal. People are invoked as gates.
- Success is a trustworthy payable in time for the next run.
- Routine judgment is encoded. Irreversible judgment is named.
- State lives on the record — chatter, Git, staging.
- Control is scoped tools, lock dates, and a person who posts.
First move
Mapped to your workflow — not ours.
The playbook is a lens. The process is yours: how purchasing, receiving, matching, exception, and close already run on your Odoo. Agents sit on those steps. We do not invent a second AP.
01
Audit the path you already walk
Trigger, owner, wait, decision. A bill on your floor — not a template from ours.
02
Name the outcomes you already pay for
Safe to pay before lock. First-pass match. Zero unauthorized posts. Your calendar, your language.
03
Overlay agents on your steps
Capture, match, exception, approve stay in Odoo. Rule changes stay in CICDoo. Same records, new owners of the boring middle.
04
Leave your gates in place
Who posts, who accepts variance, who changes vendor bank — we map those names. We do not replace them.
The cut line
Remove every step whose only job was carrying context between screens. Keep every step whose job is authorizing a change to money, master data, or the match rule.
| Still a person | Why |
|---|---|
| Accept, edit, or refuse the proposal | The agent does not change the PO or invent a receipt. |
| Accept-with-variance | Controller or a named delegate — not the clerk, not the agent. |
| Vendor bank change | Controller only. Hard hold. |
| Post and pay-batch release | Exception speed must not collapse into silent post. |
| Approve a rule change | Plan, staging UAT, then production. Never loosen match in prod. |
How a collaboration actually runs
01
Map your workflow
Audit the path a bill already takes. Overlay agents on those steps. Do not install a second process.
02
Split the pile
Repeatable reason codes get an owner, a clock, and one proposal. The tail stays human.
03
Promote through Git
Delivery agents change code. Business agents change records. Separate keys. Staging first.