PreviewYou're previewing CFO AI Ledger. Sign in to use it.Sign in
← All lessons
L0 · AI basics for finance leaders6 min read

Accountability: the company owns what its AI says and does

A common assumption is that if "the AI" made a mistake, the vendor or the tool is to blame. Courts, regulators and auditors do not see it that way. The organization that deploys AI owns its outputs, just as it owns what its employees and its website say.

Why this matters in finance

  • AI-drafted figures in reports and filings are your company's statements.
  • An AP agent that pays the wrong supplier is your control failure.
  • A chatbot that tells a customer the wrong refund or credit policy can bind you.
  • Contract clauses that shift liability to the vendor are usually narrow and capped.

Four questions to settle before go-live

  1. Who is the owner of this AI use, by name?
  2. What is the human checkpoint, and what evidence shows it happened?
  3. What can the AI commit the company to (payments, prices, policies, filings), and is that limited?
  4. How will errors be found and fixed: monitoring, sampling, complaints, a kill switch?

What good looks like

  • An inventory of AI uses with owners.
  • Approval limits for AI, like a delegation-of-authority matrix for people.
  • Customer- and supplier-facing AI that draws only on approved content.
  • Contracts with vendors that cover accuracy commitments, logging, incident notice and audit rights, while accepting that accountability stays with you.

Common traps

  • Treating a vendor's accuracy claim as your control.
  • Letting a pilot become production without anyone noticing the change in risk.
  • Customer-facing AI that answers from the open web rather than your approved policies.

What this means for the CFO

For the CFO, AI accountability belongs in the delegation-of-authority frame you already run. Every AI use that can commit money, make a statement or post to the ledger needs an owner, a limit and a checkpoint, just like a person with signing authority.

Do not rely on vendor contracts to move the risk. Use them to get evidence (logs, incident notices, audit rights), and keep the control design and the accountability in-house.

A useful first step: ask each finance leader to list the AI their team uses that can commit money, make external statements or post entries, and name an owner for each.

Real example

In Moffatt v. Air Canada (2024 BCCRT 149, February 2024), British Columbia's Civil Resolution Tribunal held Air Canada liable after its website chatbot gave a customer wrong information about bereavement fares. The tribunal rejected Air Canada's argument that the chatbot was a separate legal entity responsible for its own actions, finding the chatbot was part of Air Canada's website and the airline was responsible for all the information on it. Source: Civil Resolution Tribunal (British Columbia) — Moffatt v. Air Canada, 2024 BCCRT 149 ↗ · McCarthy Tétrault — Moffatt v. Air Canada: a misrepresentation by an AI chatbot ↗

Use it

Quick check · 3 questions

  1. 1.Who is responsible for a wrong statement made by a company's AI chatbot?

  2. 2.Which existing finance tool is the best template for limiting what AI can do?

  3. 3.What is the main value of AI clauses in vendor contracts?

0 of 3 answered

Sources

Last reviewed 2026-10-01.