Billing Change Control Audit

A practitioner course on financial auditing guidance for change management controls over billing platforms — from ticket intake to post-release invoice checks.

Team discussion at a whiteboard covered with notes

Who it is for

Internal auditors, SOX testers, billing operations leads, and external advisors who need to evaluate how rating engines, plan catalogs, and invoice rules are changed without relying on vague ITGC language.

Learning outcomes

  • Map a billing release path including silent configuration channels
  • Design samples that weight revenue impact, not just ticket volume
  • Critique dual-control design when automation deploys changes
  • Draft findings that cite invoice and credit effects with clear criteria
  • Specify rollback evidence that would survive partner review

Seven weeks of structured pressure-testing

  1. Module 1 — Billing change taxonomy Separate catalog edits, rating logic, tax tables, and credit rules. Build a scope memo your engagement lead will actually keep.
  2. Module 2 — Authorization & dual control Trace who can request versus who can release. Cover emergency paths, shared inboxes, and service identities.
  3. Module 3 — Test evidence that proves billing behavior Move beyond “QA signed off” to invoice fixtures, credit memos, and mid-cycle plan switches.
  4. Module 4 — Release identity & version pins Connect production billing periods to the rate package that was live — including hotfixes that never reached CAB.
  5. Module 5 — Monitoring after go-live Define signals that reveal silent revenue drift within the first billing cycles.
  6. Module 6 — Rollback & customer remediation Rehearse incomplete reversals and document what “done” means when invoices already went out.
  7. Module 7 — Finding workshop Write and peer-critique observations using your redacted tickets. Leave with a reusable template.

Guidance from someone who has lived the tickets

Portrait of course instructor Soo-jin Nam

Soo-jin Nam

Former shared-service controls lead for a multi-country billing hub, now teaching full-time with Algo Driven API from Jeju. Soo-jin focuses on making authorization evidence readable to financial auditors who did not grow up in DevOps tooling.

Informational pricing

This flagship course is included in Control Studio (₩820,000) and Assurance Cohort (₩1,450,000). Field Briefing seats can unlock it as a single-program purchase when capacity allows — confirm via contact.

No payment is processed on this website. See Pricing for tier comparisons and Refund Policy for eligibility rules.

At a glance

  • Format: mixed video, worksheets, optional live critique
  • Effort: about 4–5 hours per module
  • Access window: up to 9 months on Control Studio
  • Language: English

Straight answers, including limits

From people who finished the finding workshop

Module 4’s version-pin exercise caught that our “production” export job still pointed at a staging catalog for one product family. Short review, long impact.

— Eun-ji Cho, revenue assurance

★★★★☆

Strong on dual control. I wanted more screenshots from legacy mainframe rating — the composite diagrams were clear, just not my stack. Still recommended to my team.

— Marcus L. · first name & city: Marcus, Incheon

Reserve a conversation about this course

Share your platform type and fieldwork month. We will confirm which access tier fits.

Contact Algo Driven API