About

Why CloseRunbook exists

Written by someone who runs a close, for people who run a close.

I'm a VP of Accounting & AI Strategy at an operating company. Half my job is the close, the audit and the controls. The other half is working out where AI actually helps a finance team and where it creates risk we'd be signing our names to.

Most of what I found online didn't help with that. Vendor content says AI will "automate the close." Generic prompt lists skip the parts that matter to an accountant: what data goes in, what the reviewer checks, what the auditor will ask for, and where the model will confidently get it wrong. So I started writing those things down for my own team. CloseRunbook is that documentation, cleaned up and published.

What you'll find here

Editorial rules

Who's behind it

I'm keeping my name off the site for now. My employer has nothing to do with CloseRunbook, and nothing here describes my company's systems or numbers. Every workflow is written generically, from practice, and reviewed against the relevant guidance where it touches GAAP.

Nothing here is accounting, audit, tax or legal advice. Your policies, your materiality and your auditors decide.