6-lesson course · about 2 hours
Stop provisional and stale figures from reaching the exec team looking final
For CFOs, controllers, FP&A teams, accountants and finance operations professionals
Everything for Finance teamsBuild an input status register and a pre-release check that show the status and date of every management pack input, so estimates and un-updated accruals are flagged before the pack goes out.
What you’ll be able to do
By the end, you can…
How it works
A tutor that meets you where you are
- Lessons that adapt to your levelSix self-paced lessons across two modules. Later lessons are written for your level as you reach them, so you spend time on what you need, not on what you already know.
- An AI tutor you can ask anythingAsk questions typed or out loud while you work, for example how to set a staleness threshold for an input that arrives after day three of close.
- Quizzes and flashcards for each lessonShort quizzes and flashcards tied to each lesson help you check your understanding of statuses, dates and the check itself.
- Progress tracking and a certificateTrack where you are across the course and receive a certificate of completion when you finish.
Curriculum
The curriculum
The course runs in two modules: first you build the input status register and its staleness rules, then you run the pre-release check, handle flagged inputs and add an AI-assisted check with human review. Each lesson uses your own pack or a sample pack.
Module 1Build the Input Status Register3 lessons
1Why a Finished-Looking Pack Can Mislead: The Four Input Statuses
- Explain how a pack can look final while some of its inputs are estimates or provisional
- Distinguish final, provisional, estimate and unconfirmed inputs using the course's working definitions
- Classify sample inputs from your own pack into the four statuses
2Build the Input Status Register Step by Step
- Build a register with one row per pack input and the required fields
- Record the source, owner, reporting period, currency and units for each input
- Tag each input with its status and the date it was last confirmed
- Spot missing or inconsistent register entries using filters
3Set As-Of Dates and Staleness Rules
- Distinguish an input's as-of date from its last confirmed date
- Set a staleness threshold and expected confirmation date for each type of input based on your close calendar
- Write spreadsheet formulas that flag stale inputs and period, currency or units mismatches automatically
Module 2Run the Pre-Release Check3 lessons
4Design and Run the Pre-Release Check
- Define the conditions that put an input on the exception list
- Build an exception list from the register using filters or formulas
- Check that every figure in the pack maps to a register row
- Run the check at a fixed point before circulation and record that it was run
5Decide, Label and Record: Handling Flagged Inputs
- Choose whether to confirm, label or hold for each flagged input
- Apply consistent labels to provisional and estimated figures in tables, charts and commentary
- Record each decision in a decision log with who decided and why
6Add an AI-Assisted Check with Human Review
- Write a prompt that asks an AI tool to compare register statuses and dates with pack figures and list mismatches
- Review every AI-reported exception and spot-check items the AI marked as clean
- Prepare a minimal register and pack extract for an approved tool, using input IDs and pack locations in place of customer or counterparty names
Who it’s for
Made for you if…
Made for: CFOs, controllers, FP&A teams, accountants and finance operations professionals
Controllers who sign off the monthly management pack
You need to know that a figure presented as final actually is, and to have a record showing the pack was checked before release.
FP&A leads who assemble the pack from many inputs
You collect estimates, accruals and late files from several owners and need a simple way to see which ones are still provisional or out of date.
Finance managers who review the pack before it goes to the exec team
You want a repeatable check and clear labels so provisional figures are visible in tables, charts and commentary rather than buried.
Questions
Good to know
How long does the course take?
It is designed to take about two hours, across six self-paced lessons.
What do I need to know before starting?
Working knowledge of your monthly management pack and where its inputs come from, familiarity with month-end close, accruals and estimates, and basic spreadsheet skills including filters, lookups and date fields.
Do I need my own management pack?
You need access to a recent management pack or a sample pack to use in the exercises.
I haven't used AI tools for checks before. Is that a problem?
No. The AI-assisted check comes in the last lesson, after you have built the register and the manual pre-release check. You learn to write the prompt and to review every exception it reports yourself.
How does the course handle confidential data?
It covers keeping customer identifiers and nonpublic reporting information out of unapproved tools. You prepare a minimal register and pack extract for an approved tool, using input IDs and pack locations in place of customer or counterparty names.
Does it cover reconciliations or booking correcting entries?
No. Reconciliation method, correcting entries, accrual policy and estimation methodology are outside this course. It focuses on tracking input status and dates and checking the pack before release.
Does it teach how to write management commentary?
No. Writing commentary and explaining variances are not covered. The course does show how to label provisional and estimated figures within commentary so none appears as final.
Do I need to change our ERP or reporting system?
No. ERP and reporting system configuration is not covered. The register and check are built in a spreadsheet.
