
- RULESReimbursement, approval limits and the closing calendar live in Knowledge.
- INPUTEntries arrive in the message, through an n8n flow or by reading via MCP.read only
- CHECKEach item comes out compliant, differing from the rule or with no rule in the base.rule cited
- EXCEPTIONThe exception is sent for review through an n8n flow.awaiting approval
- DECISIONA person reviews and decides; the agent does not approve or pay.human decision
- RECORDTrace, cost and audit for every run.auditable
How it works
During setup, the finance rules (reimbursement, approval limits, closing calendar) go into Knowledge. The assistant answers questions about these policies and checks entries against them, item by item: what the entry says, the applicable rule with its source document, and a status that is one of three: "compliant", "differs from the rule" or "no rule in the base". Entries arrive in the message, pasted by someone on the team or sent by an n8n flow with a workspace API credential, which later fetches the result; or they are read by a read tool on the customer's MCP server. An item with no rule in the base is not marked compliant and is not filled in with market practice: it is marked "no rule in the base" and left for a person to review, like any exception. Sending the exception to the review queue is an n8n flow that runs only after a person approves. Every run keeps a trace, cost and audit record.



