AI × Finance
A safe finance assistant can propose matches across authorized order, invoice, payment, and refund records. It must preserve source evidence, surface uncertainty, and leave posting, approval, and payment with accountable finance staff.
Reconciliation, Exception Review & Cash-Flow Scenarios
Begin with ledger agreement and an exception taxonomy. A model may assist investigation; it is not the accounting system or the approver.
Unreconciled records and unclear ownership
Order, settlement, invoice, refund, tax, currency, and chargeback definitions differ across systems → duplicates and timing gaps are handled inconsistently → spreadsheet overrides lack durable evidence.
Proposal-only reconciliation
Freeze the data contract → replay a representative closed period → propose matches with source references and confidence → abstain on exceptions → finance owner reviews → compare with the signed ledger → stop and roll back on control failure.
Evidence to collect
Reference architecture: proposal-only finance assistant
Give each tenant and connector a separate least-privilege, read-only identity. Keep credentials and full account data outside model context; minimize fields, validate every input and output against a schema, and attach source references. A deterministic service enforces authorization, separation of duties, idempotency, approval scope and expiry, logs, stop conditions, and rollback. The model never approves, posts, pays, or refunds.
Pilot evidence package
- Approved data dictionary, accounting policy, retention rule, and system-of-record map.
- Representative and adversarial evaluation set covering currencies, languages, duplicates, altered bank details, tax, refunds, and timing gaps.
- Signed control matrix, reviewer record, incident procedure, stop thresholds, and rollback rehearsal.