Invoicing, receivables, expenses, vendor payments, reconciliation, budgeting, forecasting, and reporting.
This sector is locked, not idle
Deepak's instruction 2026-10-20: the Finance agent stays OFF in the backend; the finance guardrails live in the UI only for now. Money is the one place where 'nobody gave it work yet' is not a safety property, so this is a recorded refusal rather than an empty queue. The Finance REGISTRY RECORDS and the payments / obligations / counterparties / access-grant tables are fully built; what does not exist is any path by which a Finance agent can run. See docs\ELISA-FLEET.md 'The Finance lock' for the five layers and what undoing it would take. Every agent in it carries runtime_locked = 1. That is a deliberate instruction, not an empty queue — an idle agent would run if given work, and these will not. The screens below are visibility only.
Ledger
What is invoiced, what is paid, what is due and what is overdue enough to chase.
Agent 1 — Money In
Recorded expenses, vendor bills and their proof, classified and approved.
Agent 2 — Money Out & Reconciliation
Transaction matching between the ledger and what actually moved.
Agent 2 — Money Out & Reconciliation
Missing proof, duplicate transactions, unusual amounts and approval gaps — surfaced, never swallowed.
Agent 2 — Money Out & Reconciliation
Budget against actuals, variance, scenarios and runway.
Agent 3 — Budget, Forecast & Reporting
Spend, cost per lead and CAC, by segment and scenario.
Records
Would raise invoices, track due dates and name the collection action for an overdue receivable; registry record only, runtime locked
finance.agent_1
Would raise invoices, track due dates and name the collection action for an overdue receivable; registry record only, runtime locked
finance.agent_1
Would raise invoices, track due dates and name the collection action for an overdue receivable; registry record only, runtime locked
finance.agent_1
Would classify expenses, bills and vendor payments, validate proof and reconcile transactions into an exception queue; registry record only, runtime locked
finance.agent_2
Would classify expenses, bills and vendor payments, validate proof and reconcile transactions into an exception queue; registry record only, runtime locked
finance.agent_2
Would classify expenses, bills and vendor payments, validate proof and reconcile transactions into an exception queue; registry record only, runtime locked
finance.agent_2
Would classify expenses, bills and vendor payments, validate proof and reconcile transactions into an exception queue; registry record only, runtime locked
finance.agent_2
Would maintain budget, forecast, variance and cash-flow reporting against the ledger, preserving its calculation inputs; registry record only, runtime locked
finance.agent_3
Would maintain budget, forecast, variance and cash-flow reporting against the ledger, preserving its calculation inputs; registry record only, runtime locked
finance.agent_3
Would maintain budget, forecast, variance and cash-flow reporting against the ledger, preserving its calculation inputs; registry record only, runtime locked
finance.agent_3
Would maintain budget, forecast, variance and cash-flow reporting against the ledger, preserving its calculation inputs; registry record only, runtime locked
finance.agent_3
Would own who is owed what and on what terms — the counterparty and payment-obligation records behind every future movement of money; registry record only, runtime locked
finance.agent_4
Would own who is owed what and on what terms — the counterparty and payment-obligation records behind every future movement of money; registry record only, runtime locked
finance.agent_4
Would own who is owed what and on what terms — the counterparty and payment-obligation records behind every future movement of money; registry record only, runtime locked
finance.agent_4
Would own who is owed what and on what terms — the counterparty and payment-obligation records behind every future movement of money; registry record only, runtime locked
finance.agent_4
Would own the register of who may approve and who may execute which payment — the single most dangerous record type in the system, and the clearest reason the lock is structural...
finance.agent_5
Would own the register of who may approve and who may execute which payment — the single most dangerous record type in the system, and the clearest reason the lock is structural...
finance.agent_5
Would own the register of who may approve and who may execute which payment — the single most dangerous record type in the system, and the clearest reason the lock is structural...
finance.agent_5
Would own statutory obligations and the finance audit trail — what was filed, when, against which records, and what must be retained; registry record only, runtime locked
finance.agent_6
Would own statutory obligations and the finance audit trail — what was filed, when, against which records, and what must be retained; registry record only, runtime locked
finance.agent_6
Would own statutory obligations and the finance audit trail — what was filed, when, against which records, and what must be retained; registry record only, runtime locked
finance.agent_6
Would own statutory obligations and the finance audit trail — what was filed, when, against which records, and what must be retained; registry record only, runtime locked
finance.agent_6
Would route money-in, money-out, reconciliation, planning and reporting across the six finance specialists; it is a registry record only and no path exists by which it can run
finance.orchestrator
Would route money-in, money-out, reconciliation, planning and reporting across the six finance specialists; it is a registry record only and no path exists by which it can run
finance.orchestrator
Would route money-in, money-out, reconciliation, planning and reporting across the six finance specialists; it is a registry record only and no path exists by which it can run
finance.orchestrator