PART 06

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.

Every proposed match must be traceable, reviewable, and reversible

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.

BASELINE RISK

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.

CONTROLLED PILOT

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

LEDGER
Match at field level
Measure exact, partial, duplicate, missing, and wrong-entity matches by payment method, currency, language, and exception type.
Artifact: signed reconciliation sample
CONTROLS
Test separation of duties
Verify that model output cannot approve suppliers, change bank details, post journals, issue refunds, release payments, or alter source records.
Artifact: permission and adversarial test log
OPERATIONS
Count review burden and errors
Track abstentions, false matches, reviewer overrides, unresolved exceptions, close-cycle effort, and control incidents against the baseline.
Artifact: versioned pilot scorecard
Vendor speed, accuracy, and savings claims were removed because they do not establish performance on your documents, controls, languages, or accounting policy. A representative pilot supplies the evidence.

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.

Authorized ledger viewSettlement exportsException queue
Production readiness requires finance, security, privacy, and audit owners to accept measured task-specific performance and residual risk.

Pilot evidence package

  1. Approved data dictionary, accounting policy, retention rule, and system-of-record map.
  2. Representative and adversarial evaluation set covering currencies, languages, duplicates, altered bank details, tax, refunds, and timing gaps.
  3. Signed control matrix, reviewer record, incident procedure, stop thresholds, and rollback rehearsal.