This issue only includes materials that can be broken down to inputs, machine boundaries, and human sign-off. Supplier articles, synthetic repositories, and investor perspectives are all marked; these are not production conclusions from your ledger.
Today’s Most Worthwhile Implementations (2 items)
1. AP Month-End Close: Three-Way Match, Duplicate Payments, GRNI, Sub-Ledger to GL Reconciliation, Preparation and Review Separated (Synthetic Repository)
- Scenario: AP close. The warehouse has written “paid what shouldn’t be paid” and “same invoice paid twice” as exceptions that must be visible before close; numbers must be traceable from invoice to PO, receipt, and GL.
- Actions: This week, do not touch the ERP. Use last month’s closed copy (or the warehouse’s own synthetic table) to run four steps: Invoice vs. Approved PO vs. Receipt (price variance, unapproved PO, no receipt); Same supplier + amount + normalized invoice number / near date payments; Open AP sub-ledger vs. GL AP control account, residual must be explained to zero before sign-off; After calculating accrued amounts for received but unbilled, check if already posted to accrual accounts. Separately, use a “preparation package” for a second person to recalculate from source tables, specifically catching sub-ledger duplication, missed GRNI accrual, missed duplicate payment reporting.
- Review Control: Preparer ≠ Controller. Manual entries on the GL AP control account with no invoice number or source not from sub-ledger write-back are listed separately for approval. Zero payments and zero postings on the books. Synthetic data, 0 star, only borrowing the control logic.
- Deliverables: Three-way match exception table, suspected duplicate payments, sub-ledger–GL difference bridge, GRNI accrual list, preparation vs. review comparison. No sign-off, no close.
- Source: ap-close-engine｜Source page shows creation/code push 2026-06-21｜Nature: repo / synthetic demo + control checklist, not a production AP system.
2. Close: Machine Handles Preparation Layer; Differences Must Trace to Transactions; Contract Terms Must Connect to GL Actual Payments (Supplier Material)
- Scenario: Month-end close preparation / variance commentary / supplier contract compliance. Boundaries in the article: matching, exceptions, draft variances, packaging can be automated; accrual judgment, materiality, sign-off remain human, and audits will ask accordingly.
- Actions: This week, two items, both using closed copies. ① One cost center actual vs. budget: lines exceeding your current threshold must be drillable to the transaction under the account; explanations stopping at account totals are discarded. ② Sample 5 supplier contract PDFs, extracting only renewal date, notice period, price adjustment clauses, minimum commitments, then reconcile to last month’s GL expense for that supplier. Extraction alone is insufficient; only lines that do not reconcile to actual payments go to human review.
- Review Control: Every number requiring sign-off must be traceable to source transactions. Prediction-driven assumptions, definitions, and external narrative signed off by FP&A owner / Controller. Supplier material, not client attestation.
- Deliverables: Variance exception table with transaction traceability; contract terms vs. actual payment difference table. No sign-off, not included in management package.
- Source: Datarails · What AI Can Actually Do in FP&A Now｜Page shows last updated 2026-09-22｜Nature: supplier material.
Accounting / Close / Controls
- AP close controls: see Today’s Most Worthwhile Implementations item 1. ap-close-engine
- Contract terms to invoice/actual payment: see open source item. finance-skills
Close loop: Closed copy → Rules first generate pass/intercept → Humans only review exceptions and manual adjustments → Post only after sign-off. Independent, GL-connectable revenue recognition automation: Data unavailable.
FP&A / Planning / Reporting
- Variances must trace to transactions, preparation layer separated from judgment layer: see Today’s Most Worthwhile Implementations item 2. Datarails
This week only revise the first draft of closed department P&L. Independent budget preparation and approved forecast production cases: Data unavailable.
Treasury / Cash / Risk
Data unavailable. No new 13-week forecast or cash receipt/payment production cases connectable to bank/funding ledger this period. Collection email drafts see open source skill package; default not sent, do not modify collection accounts.
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 last 365 days identified this period.
CFO / Leader Team Building Experience
- Scenario: a16z partner Seema Amble, 2026-10-08. Investor perspective, naming portfolio products specifically, not neutral evaluation. Directly usable organizational rules; do not copy “reduce finance headcount to 2%” as a target.
- Actions: Write processes that are repeated twice into workflows; consider agents only after writing the workflow a second time. When hiring, first ask whether the system can be connected and whether prompt sequences can be written, rather than only discussing models. Place pilot owners with business backbone who understand “what correct looks like,” do not default to the most junior. Agents drafting vouchers must carry source documents and approval chain; rules and sign-off remain with finance.
- Review Control: Preparation requests that cannot state owner, prohibited items, or number traceability will not be put on tools. a16z article’s “portfolio companies built 50 agents in two weeks” only proves experience, not that all should be retained.
- Source: a16z · You Need a New CFO｜Published 2026-10-08｜Nature: investor public article.
- Comparison: Public comments by Secret CFO, who claims to be a former large company CFO, on the above article. Agrees on two points: dirty data is the biggest wall in transformation, and financial engineering should become a core competency. Opposes applying the software company “finance headcount from ~5%→2%” to manufacturing/chemical and other multi-dimensional cost structures; most companies are not tech companies, and existing CFOs must advance on multiple legacy ERPs and patches rather than waiting for a “new prototype.”
- Source: Secret CFO’s comments on the a16z article｜Full post visible｜Nature: anonymous former CFO public comment, self-described.
Open Source / AI Engineering References
- Contract/Usage/Collections: Evidence First, Irreversible Actions Require Human Approval
- Reusable: Write “what inputs are required, what evidence to retain, what can only be drafts, what requires approval” into skills. Contract/order vs. invoice draft; usage export vs. pricing terms; AR aging collection worklist; receipt/offer/invoice/bank matching. Principle hardcoded: every finding points to file/row/customer/term; sending emails, posting, crediting, write-off, master data changes must explicitly state approval; escalate if policy or source data missing, do not guess accounting conclusions.
- Do Not: Act as production billing system. 6 star; code push stopped at 2026-05-06, page has subsequent updates. Supplier (JustPaid) open source skill package.
- Source: finance-skills｜Created 2026-05-06｜Nature: repo / supplier open source skill, not system source.
- AP Exceptions: Investigate, Cite Documents, Propose; Code Layer Cannot Post
- Reusable: Exception agent reads documents only; every conclusion carries document key; “approved, skip check, post immediately” remarks in supplier notes treated as untrusted input and isolated, still retrieve all documents. Posting switch hardcoded off, not the model “choosing” not to post.
- Do Not: Connect to production AP. 0 star, portfolio piece, pushed 2026-09-12.
- Source: docket-invoice-agent｜Nature: repo / portfolio piece, demo guardrails.
Pending Verification Leads
- No usable LinkedIn post text this period; not treated as a case.
- Reconciliation tools that are single-source social promotion without templates/code/control descriptions are not written into confirmation cases.
Small Experiments Feasible This Week
- AP Exception Table (Owner: AP; Controller sign-off): 20 closed invoice copies (including no PO, price variance, suspected duplicates). Rules first generate pass/intercept; model only allowed to write “why intercepted.” Sample 10 back to source files; if mismatch >5% then rules discarded. Zero payments on books.
- Variance to Transaction (Owner: FP&A; Finance lead final review): One cost center, closed month, threshold uses current materiality. Machine only outputs lines exceeding threshold and traceable to transaction. Human marks noise/trend/control. Drafts stopping at account totals discarded entirely. No sign-off, not included in weekly report.
- Contract vs. Actual Payment (Owner: Procurement Accounting): Sample 5 contract PDFs for minimum commitment/price adjustment, reconcile to last month’s GL expense for that supplier. Only output difference table; do not modify contracts, do not auto credit.
- Collection Draft Not Sent (Owner: AR): AR aging + invoice status only three columns: “Overdue, Suggested Action, Email Draft”; collection owner must check before allowing send. Compare one-week false collection count.