Advanced · Compliance · 3 days · prerequisite: CS300 session 2 or equivalent
The mandate, the messages, and the mapping — taught from the legacy side, which is where implementations actually fail. Built around BSP Circular 1223 and the CBPR+ working set.
Cohort / corporate first self-paced release follows recording
Every session ends in a lab on your own environment. Labs are machine-checked against expected outputs — you and your L&D team always know exactly where you stand.
BSP Circular 1223 read closely: the dates, the scope, what one use-case means, and why the circular exists at all. The translator phase-out as the definition of full compliance.
LAB Map your institution's obligations against the circular's own sections.
ISO 20022 anatomy — business areas, versions, schemas; validation versus conformance. The working set: pacs.008 in depth; pacs.002 and pacs.004; camt.053/054 overview; the BAH; pain.001.
LAB Read, validate and break real-shaped messages.
Fixed-format record to pacs.008, field by field: decimal-exact amounts from packed, dates and UTC offsets, UETR, the charset rules, code translation to external code sets.
LAB Map the demo extract, then corrupt it subtly and see what schema validation misses.
Completeness proofs — control totals versus CtrlSum; equivalence checks; citation-backed findings; the rehearsal motion before cutover.
LAB Capstone: produce a conformance report on a seeded corpus and defend every finding.
Your seat is a private, full conformance bench: synthetic payments core plus the assessment toolkit in the browser — nothing to install, snapshot and reset per exercise. By the end of the course the lab harness will have verified: a conformance report produced and defended on a seeded-defect corpus.