Week 1 — Integrity as a product surface
Frame intake, validation, queues, and evidence as four surfaces. Map your current close against that model and pick one KPI to carry through the studio.
Flagship course
Six weeks to design, stress-test, and document a financial data integrity app workflow your close team can actually run.
Controllers, FP&A leads, and data partners who share responsibility for month-end numbers. You should already know your chart of accounts; we will not teach basic bookkeeping.
Teams mid-migration are welcome, with the caveat noted in the FAQ: week five moves quickly if your source systems are still unstable.
Frame intake, validation, queues, and evidence as four surfaces. Map your current close against that model and pick one KPI to carry through the studio.
Define schemas, freshness SLAs, and rejection behaviour. Practice writing contracts colleagues can enforce without you in the room.
Build rule sets for row counts, hash checks, dimension completeness, and soft-delete leakage. Peer critique of rule wording.
Design triage boards, materiality bands, and escalation paths. Run a simulated Friday afternoon backlog.
Assemble attachments, narratives, and lineage notes. Stress-test whether a stranger can reconstruct your KPI.
Present your integrity runbook to an instructor and cohort peers. Incorporate feedback before graduation.
Former group reporting lead turned educator. Naomi has guided 31 Analytics Metrics cohorts and specialises in reconciling finance language with data-engineering constraints. Based in the United Kingdom.
Ledger Truth Studio sits in the Ledger Lab tier at £2,450 per seat. Team discounts apply from four seats. Enrolment is invoiced after a short scoping call — this page does not process payments.
“Week 4’s simulated backlog exposed how vague our escalation path was. We rewrote it before the next close and stopped losing breaks in Slack threads.”Owen T., Group Accountant — Cardiff
Strong on structure. I still needed extra coaching on multi-entity eliminations — the studio assumes you already have that process mostly mapped.First name + city format · Sofia, Glasgow
Helpful but not mandatory. Many participants implement rules in spreadsheets or existing BI tools. If you plan a full financial data integrity app build, bring a data partner to Control Room instead.
We do not remediate broken ERP master data for you. If dimensions are chaotic, week two will surface that pain clearly — but cleaning master data remains an internal project outside the six-week scope.
Yes, with friction. Week five expects relatively stable extracts. Teams mid-cutover often pause after week four and rejoin a later cohort for evidence packs — we allow that once without extra fee.
See our refund policy for eligibility windows before cohort start.