Today’s Most Actionable Items (2 items)
1. Start with AI inventory and sign-off rights; bank accounts and postings must never be handed to the model
- Scenario: Finance-side AI governance rollout. The focus is “who uses it, what data it touches, who signs off”, not model selection or connecting postings first.
- Actionable steps: Framework from advisor Catherine Hermanto (CA, AMCT) for finance leaders; the minimum actions can be copied directly. This week, only do a 30-minute inventory: for each tool, document name, owner, data touched, where the human checkpoint is, and last verification date. Tier into three levels by amount and judgment intensity: journal entries/reconciliations/payments require 100% human review; forecasts and variance explanations are sampled; research drafts only check exceptions. For AP, hard-code one rule: the model must not change supplier bank accounts; master data requires dual control; payment batches must be human-approved. AR collections only allow drafting; issuance must be by a human. Month-end entries can be drafted by the model, with reviewer sign-off; unexplained reconciling items exceeding your threshold must not be signed off by the close owner.
- Review controls: The CFO is not the system owner but is a joint owner of governance, controls, and audit assertions, signing jointly with CIO, CRO, and Legal. Tax outputs must be reviewed by a qualified tax professional before filing, with the model’s knowledge cutoff date verified; unsigned items must not be submitted. Audit must retain logs of every AI interaction; the model must not bypass existing approvals. The framework notes: one large payments company’s board decided against using AI on the finance side due to data risk; another pharma company is further ahead. Both approaches are valid—select your tier based on your risk appetite, do not follow trends.
- Deliverables: AI tool inventory; RACI matrix; importance tiering table; AP bank account change prohibition rule; close sign-off thresholds; tax/audit sign-off fields.
- Source: CFO Connect: Finance AI Governance Framework (Catherine Hermanto) (Advisor framework / community compilation, not an internal company document; source page does not disclose publication date; body cites 2025 BCG survey and current EU AI Act)
2. Break month-end close into four folders: each subsequent step reads only the prior step’s outputs; CFO package does not touch source data
- Scenario: Monthly management review. The focus is the handoff from “revenue → cost → BvA/forecast → board materials”, not letting one chat handle the entire close.
- Actionable steps: Public tutorial uses a demo chart of accounts to split work into four role-based folders. Revenue folder only reads transaction-level sales, customer/product performance, and current-month price adjustments. Cost folder only reads expense GL, department budgets, payroll, and production-line costs. FP&A folder only reads budget vs actual, rolling forecasts, and cash flow forecasts. Board materials role receives no financial source files, only Word report templates and PPT board templates. All finished outputs are written to the same outputs folder; each subsequent step reads only from there and does not go back to others’ source tables. Share a single KPI definition table; if gross margin calculations are inconsistent, they must be exposed before board materials are prepared, not discovered during the meeting. Do not connect to production accounts this week. Take only last month’s closed revenue detail and one expense detail, run a test according to this directory, and check whether the handoff breaks.
- Review controls: Before saving each step, the human must verify: whether responsibilities have been exceeded, whether the handoff explicitly names the next step, and whether outputs are written into the current-month folder. The board materials role must not read the GL directly. The model must not post, must not modify budgets, and must not change responsibility owners in templates. This is a tutorial demonstration, not an on-site audit conclusion from any finance team.
- Deliverables: Four inputs directories; shared KPI definitions; revenue analysis, cost analysis, BvA, and board draft in outputs; manual verification records.
- Source: YouTube: Building a Month-End Analysis Division of Labor with Claude (Luke Finance) (Tutorial / with subtitles; source page shows approximately 2026-08-26)
Accounting / Close / Controls
See Today’s Most Actionable Items item 1.
Inputs are tool list, data scope, and existing approval chain. The model is only permitted to draft entries and flag reconciling items. Humans only handle unexplained items exceeding the threshold, master data changes, and payment batches. Bank accounts, postings, and payment instructions continue to follow existing permissions. The only condition for expanding scope is that the inventory can trace every tool’s owner and last verification date, and the close owner can identify every red flag.
FP&A / Planning / Reporting
See Today’s Most Actionable Items item 2.
First fix the definition file and folder boundaries, then let the model write variance explanations. Board materials may only read prior outputs and templates; direct access to source detail is not permitted. This can extend to the sampling tier in item 1: forecasts and commentary do not require 100% line-by-line review, but assumptions must carry a name, and scenarios must be marked “model drafted / human edited”.
Treasury / Cash / Risk
Data unavailable. No recent cases within the last 365 days that simultaneously have public text and reusable steps for cash forecasting, bank statement monitoring, or DSO/O2C were identified this period. The cash flow forecast in item 2 is only one input in the FP&A folder and is not sufficient to stand alone as a treasury desk.
Tax / Compliance / Audit
See Today’s Most Actionable Items item 1.
Tax research may be performed by the model to locate provisions; filings, registrations, and positions communicated to tax authorities must be signed off by a qualified tax professional, with the knowledge cutoff date verified. Audit workpapers must retain interaction logs and human override records. This can extend to the EU AI Act: high-risk use cases must be registered first before discussing scope expansion.
CFO / Leader Team Building Experience
See Today’s Most Actionable Items item 1.
The only organizational actions that can be borrowed directly are these: CFO participates in AI governance meetings and does not delegate sign-off rights to IT; draw the RACI first, then approve new tools; use the three-tier importance system to determine human review density rather than “all strict” or “all permissive”; expand only one verified scenario in 90 days. The public material cites a BCG 2025 survey of over 280 finance leaders: approximately 45% can quantify AI ROI, with a median of approximately 10%—treat this as a benchmark for “quantify first, then expand budget”, do not present it as a number your organization has already achieved.
LinkedIn data unavailable / authentication not passed. No cross-verifiable startup finance headcount replacement cases this period.
Open Source / AI Engineering References
Data unavailable. No new repositories or n8n/Zapier workflows that have not appeared in the past few days and whose fields and steps are clear were identified this period. The folder handoff in item 2 can serve as a local directory skeleton, but it is a tutorial, not a citable open-source repository.
Pending Verification Leads
- Someone paraphrased “UK accountants believe the first half of month-end is merely assembling bank statements, matching, and initial draft workpapers, with judgment in the second half”, and is selling a one-time guide; no chart-of-accounts fields, matching rules, or reviewer details seen. X: ianjcam (2026-08-25; single-source social media / pending verification)
- Someone described manually keying freight customs clearance PDFs (invoices, bills of lading, packing lists) into the customs system and framed it as an extractable scenario; no actual finance team review or booking controls observed. X: suraj_sharma14 (2026-08; product concept / pending verification)
Small Experiments This Week
- 30-minute AI inventory, no new interfaces: List all generative tools currently used in finance. For each, fill only: owner, data scope, where the human checkpoint is, last verification date. CFO or Controller reviews. Any lacking an owner or touching official books must be disabled this week; expansion is not permitted.
- One AP prohibition rule: Take 10 already-reviewed supplier master data changes (or simulate one bank account change). The model may only flag “requires manual dual control” and must not output a new account. AP owner verifies. If any instance permits an account change, do not connect payment batches this week.
- One set of closed-month directories, not for board use: Build the four folders per item 2, placing only last month’s closed revenue and expense exports. Have the model produce revenue analysis and BvA draft. FP&A verifies whether definitions align with the KPI table. If misaligned, discard. No one may post, and no draft may be pasted directly into board materials.