AI is showing up in remittance matching, variance drafts, planning scenarios, and exception queues — and not only inside finance. Sales, ops, and HR run their own tools while you still own the risk story and the reporting pack. Accountability can't live only in IT.

I'm talking to CFOs through AR. Soft on vendors. Sequencing and controls first: what accountability means, which categories help, and a sober shortlist of named platforms from public pages — illustrative, not a ranking.

What AI accountability means for finance

Five things you can defend in a walkthrough:

  • Audit trail — reconstruct inputs, model/version, proposal, downstream action, and who approved
  • Human-in-the-loop (HITL) — named humans at critical points (cash, recognition, material disclosures, anything relied on externally)
  • Policy — written rules that match how work actually runs
  • Model / use-case inventory — what's in production, owner, risk tier, and what's shadow
  • Cross-dept ownership — RACI across finance, IT/data, risk, and the business owner

If you can't answer those five, the pilot isn't accountable yet — it's just faster.

Workday ANZ (Matt Lovell, Dec 2025) puts the bar plainly for Australian CFOs: agents need to sit inside audit, compliance and security policies — with a human in the loop at critical points — plus credentials, orchestration, and explainability. That framing travels beyond one ERP.

Categories that help (not a #1 list)

Think in layers. Most mature shops mix them.

  1. AI governance / registry — inventory agents, models, apps, vendors; risk tiers; policy packs; evidence. Illustrative: Credo AI (registry, risk, compliance workflows; Mastercard case study on GenAI governance at scale); Holistic AI (shadow AI discovery, inventory, test/red-team, HITL approvals, framework mapping).
  2. Enterprise AI control towers — cross-estate visibility, ownership, risk workflows, runtime oversight. Illustrative: ServiceNow AI Control Tower (discover agents/models; govern risk/compliance; observe runtime; measure value).
  3. Model risk / MLOps governance — factsheets, evaluation, drift/bias/safety monitoring, approvals. Illustrative: IBM watsonx.governance (factsheets, evaluation, monitoring, Governance Console); DataRobot AI Governance (lineage, policy-once/enforce-everywhere, compliance docs, production guards).
  4. Finance platforms with embedded AI + trail — close, AR/O2C, planning where controls already live. Illustrative: BlackLine (audit trails; Verity for explainable recon/match logs); HighRadius (agentic AP/AR/reporting with approvals and logged decisions); Anaplan Intelligence (planning agents; AI Gateway permissions/auditability; Agent Studio guardrails); Workday (finance agents with HITL and audit-oriented governance messaging).

None replace chart-of-accounts discipline or month-end ownership. They encode it — if you design them that way.

Multi-department reality

Sales assistants, ops bots, HR screening tools — residual risk can land in disclosures, provisions, or reputation. Finance doesn't need every prompt. It needs a seat on inventory, risk tier, and who signs when it touches the numbers. Cross-dept RACI beats a lonely IT register nobody updates.

Buyer's checklist (finance desk)

  1. Reconstruct the decision — inputs → version → proposal → approval in under five minutes?
  2. HITL gates — named roles for cash, master data, externally relied-on outputs
  3. Cross-dept RACI — business owner, finance control owner, IT/data steward, risk reviewer
  4. Data lineage — sources, cut-offs, what the model could read
  5. Change notice — vendor model updates logged with materiality before ICFR-adjacent reliance
  6. Shadow AI scan — what's already outside the approved list

Sequence: inventory + RACI + trail → then widen autonomy. Tools amplify what you already have — including gaps.

CTA: Working the same accountability question across finance and other functions? Compare notes at financesignal.ai — practical thinking from the desk, not a product pitch.