A tailored course, built for your situation
Mastering IFRS 17 for Data Engineers in Financial Services
Implement and govern IFRS 17-compliant data frameworks with precision and cross-functional reach
The situation this course is for
IFRS 17 compliance requires more than accurate models, it demands traceable, auditable, and interpretable data pipelines that cross engineering, actuarial, and reporting boundaries. Engineers who can bridge these silos are rare, and those who do are quietly shaping the future of financial reporting.
Who this is for
Data Engineer in a financial institution, working at the intersection of data systems, actuarial models, and regulatory compliance, with growing responsibility for IFRS 17 data readiness.
Who this is not for
This course is not for auditors, accountants, or actuaries looking for policy-level guidance. It’s also not for engineers working outside financial services or those not involved in IFRS 17 data pipeline design.
What you walk away with
- Design IFRS 17-compliant data models aligned with LDT and PV calculations
- Produce audit-ready lineage documentation for key data transformations
- Coordinate with actuarial and finance teams using standardized data artifacts
- Implement governance workflows that scale across lines of business
- Reduce rework by baking compliance requirements into early-stage data architecture
The 12 modules (with all 144 chapters)
- IFRS 17 scope as it impacts data engineering
- Liability for Remaining Coverage (LRC)
- Contractual Service Margin (CSM) pipeline needs
- Present Value of Intrinsic Options and Guarantees
- Discounting and yield curve data feeds
- Granularity rules for cohort-level reporting
- Data retention for multi-year simulations
- Aggregation paths from transaction to report
- Actuarial model dependencies
- Policy count thresholds for segmentation
- Sensitivity testing data design
- Version control for assumption inputs
- Identifying distinct insurance contracts
- Modifications vs. cancellations
- Coverage units and duration tracking
- Allocation of acquisition costs
- Fronting vs. reinsurer relationships
- Time slicing and duration buckets
- Grouping rules for reporting units
- CSM amortization tracking fields
- Loss components and recognition timing
- Risk adjustment for non-financials
- Currency translation layers
- Policy-level vs. portfolio views
- LDT calculation inputs
- PV of future cash flows pipeline
- Yield curve ingestion workflows
- Inflation index data integration
- Survival probability sourcing
- Sensitivity scenario branching
- Monte Carlo output formatting
- Simulation run metadata
- Cash flow timing alignment
- Discount margin processing
- Non-recoverable CSM flags
- Interim cohort adjustments
- Data lineage for compliance audits
- Versioned assumption repositories
- Change control for model inputs
- Automated reconciliation points
- Audit log schema design
- Access control for sensitive assumptions
- Documentation templates for reviewers
- Data quality checks at ingestion
- Null value handling in actuarial feeds
- Reprocessing triggers and controls
- Sign-off workflows for data packages
- Cross-team review cycles
- Actuarial data request patterns
- Shared schema conventions
- Common calendar for runs
- Data dictionary ownership
- Staging area protocols
- Feedback loops from actuarial review
- Error classification and routing
- Priority tagging for urgent fixes
- Documentation for non-engineers
- Glossary alignment with accounting
- Meeting rhythm integration
- Shared tooling for data validation
- Template-based pipeline generation
- Region-specific discounting rules
- Product-onboarding checklists
- Batch scheduling for quarter-end
- Parallel run coordination
- Error retry mechanisms
- Monitoring for CSM drift
- Alert thresholds for anomalies
- Pipeline rollback design
- Data packaging for export
- Compression and storage strategy
- Scalable indexing for retrieval
- Differences in liability measurement
- Data segregation strategies
- Reconciliation data points
- Dual output formatting
- Tax jurisdiction tagging
- Local statutory adjustments
- Currency reporting thresholds
- Regulatory vs. internal views
- Run logic branching
- Data masking for GAAP-only fields
- Audit boundary definition
- Cross-reporting consistency checks
- Identifying reinsured contracts
- Fronting fee allocation
- Risk transfer validation data
- Reinsurance recoverables tracking
- Collateral data fields
- Duration matching checks
- Ceded vs. net liability views
- Reinsurance profit recognition
- Contractual modifications
- Reinstatement clauses data
- Reporting to cedants
- Audit trails for cessions
- Range checks for assumptions
- Cohort-level consistency rules
- CSM sign validation
- PV monotonicity checks
- Currency balance validations
- Cash flow sign rules
- Survival probability bounds
- Discount margin reasonableness
- Policy count reconciliation
- Migration data verification
- Backward compatibility rules
- Automated anomaly detection
- Snowflake schema patterns
- Databricks pipeline orchestration
- Azure Data Factory integration
- Power BI dashboards for finance
- SAP actuarial input feeds
- Oracle general ledger alignment
- API design for actuarial calls
- Metadata tagging standards
- Data catalog integration
- CI/CD for data changes
- Containerization of runs
- Infrastructure-as-code templates
- Quarterly assumption update cycle
- Versioning for regulatory submissions
- Backward compatibility planning
- Stakeholder notification patterns
- Rollout to actuarial teams
- Finance data freeze periods
- Emergency patch protocols
- Documentation change tracking
- Impact assessment workflows
- Legacy data sunsetting
- User acceptance testing
- Post-release validation
- IASB amendment tracking
- Jurisdiction-specific guidance
- Local regulator expectations
- Data retention law changes
- ESG-linked reporting overlaps
- Climate risk scenario integration
- Digital reporting formats
- XBRL tagging readiness
- Audit trail expansion
- Public disclosure data layers
- Stakeholder communication updates
- Internal training materials
How this maps to your situation
- Actuarial data handoff
- Quarter-end reporting cycle
- Regulatory audit preparation
- Cross-functional project rollout
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 access.
Time investment: Approximately 3 hours per module, designed to fit around core responsibilities, total time investment around 36 hours over 6-8 weeks.
How this compares to the alternatives
Unlike generic IFRS 17 courses focused on accounting, this course is built specifically for data engineers. It skips theory and focuses on implementable data design, pipeline patterns, and governance workflows used in real financial institutions.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.