Monitoring replaces the annual surprise
An annual audit or a yearly controls review reports what went wrong months after it happened. A vendor's bank details change in February, and the audit sample drawn the following January may or may not include the payment that followed. Continuous monitoring runs the same tests every week or month over every transaction, so a failed control shows up in the cycle in which it failed.
The tests are plain rules wherever possible: a payment released by the person who approved the vendor change, a journal entry posted and approved by one user, an invoice number repeated for the same vendor. Statistical outlier models add a second layer for patterns rules miss, such as a vendor whose monthly spend suddenly doubles. Every flag carries an explanation a controller can read in one line. Our article on ten automated tests lists a typical starting set.
AI agents are users with permissions
When an AI agent codes invoices, matches payments or drafts journal entries, it acts in your accounting system through an account that holds rights. Treat it like any other user. It needs its own credentials, the least access that does the job, and no combination of rights that would be a segregation-of-duties conflict for a person. If it can code an invoice, it should not be able to approve one. Its actions should be logged, and a person should approve anything above a set amount. The agent that approved itself is an illustrative scenario of what happens when that rule is missed.
Three AI frameworks, mapped once
COSO published Achieving Effective Internal Control Over Generative AI on 23 February 2026. It maps the 17 principles of the COSO internal control framework to generative AI, sets out a six-step roadmap that begins with governance and an inventory of AI use, and pays particular attention to shadow AI, meaning tools staff adopt without approval.
The NIST AI Risk Management Framework organizes the same ground into four functions: govern, map, measure and manage. NIST is revising AI RMF 1.0 following the July 2025 AI Action Plan, and its Generative AI Profile, NIST AI 600-1, remains current. ISO/IEC 42001:2023 sets requirements for an AI management system that accredited bodies can certify.
We map one set of finance controls to all three, so you run one program and keep one body of evidence. The AI Governance for Finance offering covers the work in detail.
Built for you to own
Dashboards, data pipelines and internal tools we build run in your accounts, with the code in your repository and documentation your next hire can follow. You own the code and pay no license fee to use it. If we recommend a commercial product instead, we disclose any relationship with its vendor. A monitoring subscription pays for the work of running tests and reviewing results, not for access to your own data.



