Flagship course
SaaS Control Walkthrough Lab
Financial auditing guidance for internal control review — practiced on subscription billing paths, not generic SOX binders.
Reserve a conversation
Learning outcomes
- Draft a revenue control narrative that names systems of record and handoffs.
- Run an access review that maps product roles to ERP posting rights.
- Build an evidence pack with retention notes auditors can sample from.
- Facilitate a walkthrough using inquiry scripts that invite follow-up questions.
- Log control limitations honestly when engineering work remains outstanding.
Modules
Sequence is fixed; homework timing flexes around Korea close weeks when possible.
- Module 1 — Scope the subscription risk lensDecide which ARR paths deserve formal controls versus monitoring activities.
- Module 2 — Quote-to-cash walkthrough draftingTrace one booking across CRM, billing, and cash application with owner names.
- Module 3 — Inquiry practice under pressureLive role-play with instructor-as-auditor; record unanswered system questions.
- Module 4 — Cutoff, deferred revenue, and usage metersAlign rollforwards to exports without inventing controls you cannot evidence.
- Module 5 — Access & provisioning evidence packsDesign sampling-ready packs for identity and ERP rights reviews.
- Module 6 — Limitation logs & leadership summariesTranslate gaps into actionable asks without overstating assurance.
Instructor
Jiyoon Han
Former Big Four senior manager focused on technology clients; now designs Neural API Hub labs from Gwangju with remote co-facilitators.
Jiyoon insists every cohort keeps a limitation log. She will not rubber-stamp a control that depends on an undocumented spreadsheet.
Informational pricing
Control Studio seating for this lab is listed at ₩890,000 per person. Private Assurance Cohort packaging is available on the pricing page. This site does not process payments.
FAQ
Do I need a SOX program to join?
No. Many teams arrive for investor diligence or first-year auditor walkthroughs. We adjust language intensity, but the evidence craft stays the same.
Can engineering attend?
Yes for Assurance Cohort pairs. In open Control Studio runs we allow one engineering guest for Modules 5–6 when seats remain.
What is a real limitation of this lab?
We cannot remediate broken source data. If billing exports and ERP subledgers disagree, the course will surface the break and teach you how to document it — it will not reconcile the systems for you. Teams sometimes expect tooling magic; that is outside our scope.
Is the certificate a professional license?
No. Completion confirms participation and artifact review only. It is not a Korean CPA credential or audit license.
Reviews from this lab
Module 3’s role-play was uncomfortable in a useful way. I froze on a question about who approves credit memos — then fixed the RACI the same week.
Evidence pack from Module 5 is still in our SharePoint. Deducting one star because evening sessions collided with US board prep twice.