A tailored course, built for your situation
Mastering Basel III for Software Engineers in Financial Institutions
Build compliance-aware systems with precision and confidence
Who this is for
Software engineer in a regulated financial institution working at the intersection of code, compliance, and risk controls
Who this is not for
Engineers working outside financial services or those not involved in systems subject to capital adequacy or risk reporting requirements
What you walk away with
- Map Basel III risk requirements directly to system design decisions
- Produce documentation that satisfies both engineering and compliance reviewers on first submission
- Reduce rework cycles by aligning code outputs with audit expectations from the start
- Speak confidently across risk, architecture, and compliance teams using shared, standards-based language
- Ship features faster by avoiding late-stage control rejections
The 12 modules (with all 144 chapters)
- What Basel III means for code
- Where engineers fit in the control chain
- Key obligations: CRR and CRD
- Scope of application in group systems
- Impact on data flow design
- Control expectations by layer
- Linking code to risk outputs
- Common misalignments to avoid
- Audit touchpoints by module
- Traceability from input to report
- Documenting design intent
- Versioning compliance-critical code
- RWA by asset class
- Exposure measurement methods
- On-balance vs off-balance treatment
- Derivatives: CEM and SA-CCR
- Collateral handling logic
- Thresholds and limits in code
- Validation of intermediate outputs
- Treatment of exposures to central counterparties
- Currency and tenor adjustments
- FX risk in RWA pipelines
- Debugging RWA drift
- Version control for RWA models
- Definition of Tier 1 capital
- Exposure measure components
- On-balance sheet grossing
- Derivatives notional handling
- Securities financing transactions
- Accounting for guarantees
- Treatment of unsettled trades
- Gross vs net presentation logic
- Systemic risk buffers
- Reporting frequency alignment
- Data lineage for leverage outputs
- Audit trail requirements
- Stock vs flow measurement
- High-quality liquid assets (HQLA)
- Classification of HQLA tiers
- Outflow and inflow assumptions
- Counterparty categorization logic
- Stress scenario inputs
- Time bucketing in reporting
- Concentration limits in code
- Data freshness checks
- Cash flow forecasting logic
- Validation of LCR numerator
- LCR denominator design
- CVA definition and use cases
- Exposure at default logic
- Probability of default inputs
- Calculation of potential future exposure
- FVA adjustments in pricing
- CVA volatility adjustments
- Hedging implications
- Model validation touchpoints
- Backtesting with historical rates
- Treatment of netting sets
- Collateral agreement mapping
- CVA capital add-ons
- Risk weights by counterparty
- Treatment of sovereign exposures
- Bank and corporate risk weights
- Retail exposures classification
- Securitization exposures
- Equity holdings
- Maturity adjustments
- Diversification benefits
- Large exposures framework
- Single name concentration checks
- Reporting thresholds
- Systemic importance flags
- PD modeling fundamentals
- LGD estimation inputs
- EAD for committed facilities
- Default definitions in code
- Historical observation windows
- Portfolio segmentation
- Through-the-cycle adjustments
- Model governance interfaces
- Stress testing integration
- Backtesting requirements
- IRB vs standardized switch logic
- Internal audit access points
- Basic indicator approach
- Standardized measurement approach
- Business line classification
- Internal loss data collection
- External scenario inputs
- Scenario analysis integration
- Loss event severity bands
- Frequency models in code
- Dilution factors
- Mitigating controls
- Risk scaling factors
- Aggregation logic
- Early requirements capture
- Control-aware user stories
- Automated compliance checks
- Policy-as-code integration
- Control tagging in Jira
- Pre-commit validation hooks
- Audit trail generation
- Version-controlled control logic
- Design pattern libraries
- Peer review checklists
- Compliance test suites
- Release gate requirements
- Test environment design
- Golden dataset creation
- Cross-module reconciliation
- Data consistency checks
- Control threshold validation
- Breakpoint simulation
- Recovery logic testing
- Model boundary verification
- Concurrency handling
- Time series alignment
- Schema evolution planning
- Rollback preparedness
- Audit scope by module
- Evidence collection workflow
- Traceability matrix setup
- Version control as proof
- Design decision logs
- Peer review records
- Compliance test results
- Change impact summaries
- Regulatory Q&A prep
- Third-party review readiness
- Document retention policies
- Automated artifact generation
- Tracking regulatory changes
- Impact assessment workflow
- Technical debt and controls
- Iterative update cycles
- Stakeholder alignment meetings
- Change control integration
- Backward compatibility
- Deprecation planning
- Knowledge transfer protocols
- Training for new hires
- Feedback from audits
- Benchmarking against peers
How this maps to your situation
- When aligning code with capital adequacy rules
- While designing risk data pipelines
- During audit preparation cycles
- After regulatory updates are published
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- 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: Approximately 3 hours per module, designed to fit around core development work
How this compares to the alternatives
Unlike generic compliance overviews or high-level regulatory summaries, this course delivers line-by-line implementation guidance tailored to software engineers working in financial institutions subject to Basel III.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.