A tailored course, built for your situation
Mastering Basel III for Associate Software Engineers in Global Financial Institutions
A complete implementation roadmap for software practitioners driving compliance-critical systems
The situation this course is for
Engineers often receive compliance requirements as finalized directives without access to the underlying rationale, making it difficult to justify technical choices when questioned by peers or reviewers. This creates friction in cross-functional settings and limits professional credibility.
Who this is for
Mid-level software engineers in global banks who translate compliance mandates into system designs but lack direct exposure to the regulatory source material
Who this is not for
Executives setting policy, compliance auditors, or junior coders working on non-regulated systems
What you walk away with
- Trace any capital adequacy rule back to its origin in BCBS publications
- Explain counterparty risk logic using EBA Q&A precedents during peer reviews
- Anticipate downstream compliance constraints during early-phase architecture
- Respond confidently to design board challenges with cited regulatory text
- Produce implementation artefacts that reflect deep understanding of Pillar 1 and Pillar 2 drivers
The 12 modules (with all 144 chapters)
- Origins of Basel I and the the current cycle Accord
- How the the current cycle Asian Financial Crisis reshaped capital thinking
- Basel II's三大支柱 and their global adoption curves
- US versus EU implementation of Basel II
- Flaws in Basel II exposed during the current cycle crisis
- G20 mandate for stronger bank regulation
- Key objectives behind Basel III development
- Timeline of BCBS consultations the current cycle, the current cycle
- National discretions in Basel III transposition
- Role of EBA, PRA, and Federal Reserve in shaping rules
- Difference between Basel III and 'Basel IV'
- Current state of Basel III finalisation across jurisdictions
- Structure of Tier 1, Tier 2, and Tier 3 capital
- Common equity Tier 1 ratio calculation
- Leverage ratio as supplementary measure
- Credit risk: Standardised Approach basics
- Foundation IRB versus Advanced IRB models
- Treatment of sovereign versus corporate exposures
- Operational risk capital under the new SA
- Market risk and the FRTB revisions
- Output floor and its effect on IRB banks
- CVA risk capital charges
- Large exposures framework thresholds
- Liquidity risk and the Leverage Ratio Exposure Measure
- Purpose and scope of the SREP process
- ICAAP documentation expectations
- Stress testing design assumptions
- Internal capital adequacy processes
- How Pillar 2A and Pillar 2B differ
- Role of internal audit in capital governance
- Stress scenario design for software simulation
- Reverse stress testing mandates
- Governance reporting flows from IT to risk
- Model validation requirements for risk systems
- Interactions between Pillar 1 and Pillar 2 outputs
- Regulator expectations on capital planning
- Scope of public disclosure requirements
- Core capital ratios to be published
- Risk exposure disclosures under CRR
- Standardised Pillar 3 reporting templates
- From AnaCredit to COREP and FINREP
- Mapping system outputs to template fields
- Data granularity expected by regulators
- Disclosure frequency and audit trail needs
- Public filings versus internal reporting
- Treatment of confidential proprietary information
- How ESMA monitors compliance
- Automated checks for disclosure completeness
- Definition of high-quality liquid assets
- Level 1 and Level 2 asset classifications
- Run-off rate assumptions by counterparty
- Stress scenario design for deposits
- Wholesale funding sensitivity factors
- Intra-day liquidity monitoring needs
- Systemic vs idiosyncratic shocks
- Data inputs for LCR calculations
- Reporting frequency and time horizons
- Back-testing LCR assumptions
- Treatment of central bank reserves
- Collateral management implications
- Available stable funding calculation
- Required stable funding by asset class
- Residual maturity treatment
- Retail versus corporate deposit stability
- Securitisation funding assumptions
- Off-balance sheet exposures
- Derivatives netting and collateral
- Long-term debt recognition
- Funding concentration metrics
- Systemic importance add-ons
- How NSFR interacts with LCR
- Implementation timelines across regions
- Definition of CVA and DVA
- Market-implied default probabilities
- Exposure at default modeling
- Potential future exposure curves
- Collateral agreement impacts
- Regulatory capital add-on for CVA
- Stressed parameter requirements
- Back-testing CVA models
- Integration with XVA platforms
- System of record for CVA reserves
- Rolling simulation needs
- Reporting to capital committees
- Boundary between banking and trading book
- Expected shortfall versus VaR
- Default risk charge calculations
- Residual risk add-on requirements
- Sensitivities-based method rollout
- Modelling requirements for non-modellable risk factors
- Liquidity horizons by asset class
- Stressed calibration periods
- Internal model approval process
- Back-testing frequency and thresholds
- Data storage for auditability
- Impact on front office systems
- Mapping BCBS guidance to ER diagrams
- Data lineage for audit trails
- Granularity needed for exposure calculations
- Integration with collateral management
- Real-time vs batch processing trade-offs
- Master data management for counterparties
- Handling jurisdictional variations
- Version control for regulatory logic
- Automated reconciliation checks
- Designing for future amendments
- Testing frameworks for capital inputs
- Change management for compliance updates
- Common findings in internal audits
- External auditor expectations on documentation
- Walkthrough readiness for design choices
- Evidence retention strategies
- Version matching between spec and code
- How to prepare for EBA stress tests
- Responding to SREP findings
- Preparing for on-site reviews
- Using control matrices effectively
- Cross-referencing with ISO 27001 controls
- Traceability from code to regulation
- Self-attestation workflows
- US SLR rule versus Basel III
- UK PRA's CRR2 implementation
- ECB guidance nuances
- APRA’s APS 110 approach
- Japan’s Basel III rollout
- Swiss FINMA adaptations
- Catalyst for divergence: internal models
- National discretions in risk weights
- Treatment of SME exposures
- Local currency exemptions
- Reporting threshold differences
- Enforcement timelines by country
- Basel 3.1 and 3.2 updates
- Output floor implementation status
- Revisions to operational risk SA
- Climate risk integration pilots
- Proposed revisions to IRB models
- Digital transformation impacts
- AI in credit risk modeling
- Cyber risk capital considerations
- Interoperability with DORA
- Preparing for systemic risk dashboards
- Long-term data architecture vision
- Roadmap for next compliance cycle
How this maps to your situation
- Basel III implementation phase
- System design under regulatory constraints
- Audit preparation and technical justification
- Cross-functional engineering alignment
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters total)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: 90 minutes per week for 6 weeks, with self-paced access to all materials
How this compares to the alternatives
Unlike generic compliance overviews, this course is engineered for software practitioners who must justify architectural choices using verbatim regulatory text and documented precedent.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.