Control Audit Lab
A six-session studio for practitioners who run risk and compliance audits across wallets, lending, remittance, and adjacent fintech rails.
Learning outcomes
- Build a control map tied to a real product flow, not a generic policy outline.
- Design sampling logic that you can defend in a walkthrough.
- Assemble an evidence index with clear ownership and retention notes.
- Write findings that separate design gaps from operating exceptions.
- State limitations without sounding evasive.
Informational pricing
₩1,150,000
Aligned with the Control Bench tier. No checkout on this site—reserve through contact.
Modules
-
1. Scope that matches the product
Translate onboarding, funding, and payout paths into audit boundaries. Practice cutting scope that looks impressive but cannot be tested.
-
2. Control language without theater
Rewrite vague “monitor transactions” statements into testable controls with owners and systems of record.
-
3. Sampling and exception trails
Choose samples for payment anomalies and AML alerts. Document why a case entered or left the set.
-
4. Evidence packs under time pressure
Index screenshots, logs, and policy excerpts so a reviewer can reconstruct your path in under fifteen minutes.
-
5. Findings and remediation owners
Draft issues with severity rationale, affected populations, and practical next steps.
-
6. Walkthrough rehearsal
Present to peers playing product, legal, and supervisory roles. Capture follow-ups that survive the meeting.
Instructor
Yoonseo Han leads the lab. She spent a decade in payments risk and internal audit across Seoul and Singapore before joining Scalewebsys as lead instructor. Her sessions favor annotated worksheets over slide monologues.
FAQ
Who is this for?
Internal auditors, compliance owners, and risk partners who already touch fintech products and need stronger audit craft—not a first introduction to what AML means.
Is the lab a substitute for licensed advisory work?
No. Scalewebsys provides training. We do not issue opinions, certifications of compliance, or legal advice for your entity.
What is a real limitation of this course?
We do not simulate a live supervisory inspection with your confidential systems. Exercises use redacted or synthetic datasets, so you still need on-the-job translation for proprietary tooling.
How much weekly time should I plan?
Most learners spend four to six hours outside live sessions preparing artifacts. Falling behind on week two makes peer review thinner.
“The walkthrough rehearsal exposed how often I buried the limitation note. Fixing that changed how product received the report.”
Jiwoo Lee · Risk partner
“Module three on sampling was sharp. Module one felt slower if you already write scopes weekly—still worth staying for the peer edits.”
Client in virtual asset services