> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fincelo.app/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Agents — Overview & Governance

> How Fincelo's 7 agents work, credit system, autopilot rules, and governance.

### AGENTS OVERVIEW — Q\&A

***

**Q: What are the 7 agents in Fincelo?**

| Agent                       | Phase | Primary function                                              |
| --------------------------- | ----- | ------------------------------------------------------------- |
| Collections agent           | 1     | Dunning orchestration, payment prediction, escalation         |
| Compliance guardian         | 1     | GST/TDS deadlines, IRN cancellation windows, filing alerts    |
| Smart billing agent         | 1     | Billing accuracy, advance billing, FX exposure                |
| Period close agent          | 2     | Close checklist, period locking, backdated entry routing      |
| Revenue anomaly agent       | 2     | Statistical baseline, Z-score anomaly detection               |
| Renewal agent               | 2     | Renewal pipeline, health scoring, grace period, ARR at risk   |
| Customer intelligence agent | 3     | Health scores, churn signals, CLV, ICP scoring                |
| Orchestration layer         | 3     | Event bus, agent coordination, conflict prevention            |
| CFO co-pilot                | 3     | Natural language interface, daily briefings, decision support |

***

**Q: How does agent governance work — can agents act autonomously?**

Every agent action has one of 3 governance states:

Auto: agent executes immediately, no human approval needed.
Approval: action goes to the approval queue, human approves before execution.
Disabled: action is switched off for this workspace.

Finance teams configure the governance state per action in Settings → Agents.
Every auto action is logged with agent name, action type, timestamp, and outcome.
Every approval action is logged with who approved, when, and any notes.

Fincelo's principle: agents amplify the CFO's capacity. They never replace
the CFO's judgement on material decisions.

***

**Q: What is the approval queue?**

A unified inbox for all actions waiting for human approval.
Priority levels: P1 (4h expiry), P2 (24h expiry), P3 (no expiry).
Expired approvals are escalated to the next person in the chain.
Each item shows: what the agent wants to do, why, supporting data, approve/reject buttons.

***

**Q: What happens if two agents try to act on the same customer simultaneously?**

The orchestration layer has a conflict prevention system.
When Agent A takes an action on Customer X, a cooldown lock is placed.
Agent B sees the lock and either waits or routes the action to the queue.
No two agents can send a customer communication within the configured cooldown window.
Default cooldown: 24 hours per customer per channel.

***

**Q: How does the event bus work?**

All modules and agents communicate via the `domain_events` table.
When a significant event occurs (contract approved, payment received, invoice overdue),
an event is written to `domain_events`. All subscribed modules react to it.

Example: PAYMENT\_FAILED fires → Collections agent starts dunning,
Integration hub sends alert, AI CFO flags the anomaly, Metrics updates failure rate.
All 4 reactions happen from one event. No direct module-to-module calls.

***