This issue only includes materials that can be decomposed into inputs, actions, sign-offs, and outputs. Capital markets supplier stories, identical links covered within the past week, and interviews lacking process details are excluded from the main text.
Today’s Most Actionable Items (2 items)
1. From Booking to Close: AI Drafts Only, Posting Requires Human Sign-off
- Scenario: Document posting, account suggestions, reconciliation differences, month-end checklists, draft management reports.
- Actions: Lock in a single chain: source documents/bank advices → AI extracts fields, suggests accounts, flags exceptions → cashier/accountant reviews the exception queue → posting permitted only then. Begin with prior-month closed bank statements + GL export; instruct the model to output only “suggested accounts + candidate difference reasons”; prohibit posting.
- Review Controls: Low-confidence items, abnormal amounts, and duplicate documents route exclusively to the manual queue; AI is prohibited from posting, completing reconciliations, closing periods, or modifying the chart of accounts. Maintain three-way comparison of original, AI suggestion, and final decision.
- Outputs: Exception list, draft reconciliation workpapers, month-end checklist, review log.
- Source: Coursiv · 2026 AI-Controlled Bookkeeping Workflow｜2026-07-28｜Practical manual, not a finance team self-reported case study.
2. 13-Week Cash Forecast: Clean Receipts Data First, Then Model Customer Payment Dates
- Scenario: Treasury/FP&A short-term cash forecasting; largest errors typically arise from actual customer payment dates rather than payroll or rent.
- Actions: First export 18–24 months of cleared invoices (invoice date, due date, amount, customer, actual receipt date); use customer historical average overdue days or a simple model to predict receipt weeks for outstanding invoices; continue using calendar rules for payroll, taxes, rent, and debt service—do not feed into the model. Run in parallel for 8–12 weeks and compare only whether “forecast receipts vs. actual receipts” outperforms the existing schedule.
- Review Controls: Generative models may only draft “why this week’s variance occurred” and must not output forecast numbers directly; weekly commentary requires Treasury lead sign-off before distribution to CFO/bank. In EU contexts, credit scoring natural-person customers requires separate legal review and is not treated as standard forecasting.
- Outputs: Daily refreshed cash flow base table, customer payment date predictions, weekly variance commentary, version archive.
- Source: Tommaso Maria Ricci · Cash Forecasting Practical Guide｜2026-10-13｜Independent practitioner methodology note, not a customer implementation white paper.
Accounting / Close / Controls
See Today’s Most Actionable Item #1. Coursiv
Vendor Materials / Market Scan (Not Best Practice): Multi-entity reconciliation can follow “bank/payment channel integration → historical account matching → low-confidence items to review → generate only draft entries; ERP remains the book of record.” Matched items carry evidence; unmatched items carry source, GL entry, difference amount, and possible causes. Suitable for comparing against existing Excel workpapers; not suitable for direct system replacement.
- Source: Truewind · 2026 AI Reconciliation Guide｜2026-10-05｜Vendor blog.
FP&A / Planning / Reporting
Data unavailable. No new, independently verifiable budget/forecast/narrative implementation cases this period. The “draft management report commentary” from Item #1 and “weekly variance commentary” from Item #2 can serve as narrative pilots: input reviewed P&L or cash forecast versions; AI writes only three paragraphs of reasons; FP&A owner edits before packaging.
Treasury / Cash / Risk
See Today’s Most Actionable Item #2. Cash Forecasting Practical Guide
Priority sequence: cleared invoice quality → customer payment dates → then discuss accuracy. Payroll, taxes, and debt service use rules; receipts use behavioral prediction. No new open-source bank statement matching templates.
Tax / Compliance / Audit
Data unavailable. No new AI implementation cases or practical methods for tax research, SOX/internal controls, or audit evidence management within the past 365 days identified this period.
CFO / Leader Team Building Experience
Shared Services Center AP/AR: AI Handles Volume, Humans Manage Exceptions; Project Still in Scoping
- Scenario: Consultant account of a global shared services center with ~35 people manually processing invoices; evaluating process mining + AI to consolidate transactional work to a small headquarters expert team.
- Actions: First map the division between “standard invoices vs. exception invoices”; do not set headcount reduction targets upfront. AI/tools perform extraction and matching; retained staff handle only exceptions, vendor relationships, and process oversight.
- Review Controls: Author stresses that insights do not automatically translate into behavior; Finance BPs must still translate numbers and drive business actions. Estimate cost, governance, and change management upfront to avoid “tool implementation increasing workload.”
- Outputs: SSC current-state time tracking, exception definitions, target role descriptions. Counterparty still in scoping phase; reduction from 35 people to a “small expert team” is not a verified outcome.
- Source: The CFO Club · Christian Franz Hansen Interview｜2026-07-21｜Consultant interview, not a user-team completed retrospective.
Named enterprise finance leads and cross-verifiable new organizational cases: Data unavailable. LinkedIn data unavailable / authentication failed; do not substitute job title snippets for facts.
Open Source / AI Engineering References
n8n AP Reference Implementation: PDF → Validation → Slack Approval → Booking, but Synthetic Data
- Reusable Architecture: Six independent workflows + Postgres for state and audit; extract line items, not just totals; validate totals, vendor master data, amount outliers, duplicate invoice numbers; high-confidence items auto-post, others route to one-click Slack approval.
- Suitable for Pilot: AP invoice receipt. First run with dummy PDFs / desensitized invoices to validate field extraction and duplicate detection; do not connect to actual payments.
- Note: Author explicitly states this is a demo using synthetic data; in a small sample of 19 invoices, 11 auto-posted. Accuracy cannot be extrapolated to real vendor formats. Low-star reference implementation; use as architecture cue only, not recommended as production template.
- Source: GitHub · Orbient/invoice-intelligence-pipeline｜Source page shows updates as of 2026-08｜Open-source demo.
This Week’s Small Experiments
- Bank Reconciliation Comparison: Accountant exports prior-month signed bank statements and cash account details. Per Item #1 rules, model outputs only “matched / timing difference / unidentified difference.” Controller ticks through unidentified items line by line. Output: three-layer reconciliation table + review log. Pass criteria: unidentified items no fewer than manual list, with no missed reconciled items.
- Receipt Date Baseline: Treasury pulls Top 20 customers’ cleared invoices for the past 18 months and calculates median “actual receipt date − due date.” Provides expected receipt week for outstanding invoices, run in parallel with existing 13-week schedule for 4 weeks. Owner: Treasury; Reviewer: CFO. Pass criteria: absolute weekly receipt error lower than prior schedule.
- Invoice Extraction Without Payment: AP runs 10 historical PDFs (or dummy invoices) for field extraction: vendor, invoice number, date, tax amount, total. AP owner reconciles against originals. Output: field comparison table. Automatic payment prohibited even below amount thresholds.
- Narrative Commentary Draft: FP&A pastes prior-month reviewed P&L; model permitted only to write “top 3 variance drivers + amounts/percentages + open questions.” Prohibited from inventing business reasons. Owner edits before month-end package. Pass criteria: editing time shorter than writing from scratch, with no unsupported figures.