Payment Data Model and Mapping

What You Can Do After This Chapter

Learning objective. Learner designs a payment data model, including parties, accounts, instructions, transactions, and statuses, and maps fields between a core banking system and ISO 20022 messages. Learner demonstrates this skill using realistic banking examples, explaining each step clearly and using correct terminology throughout.

Practical assessment. Learner builds a data model for a payment instruction with at least twelve entities and their relationships, then maps twenty core banking fields to pacs.008 and pain.001 fields in a table. Learner then identifies three mapping gaps, proposes a resolution for each, and explains how a status change from pending to settled is stored and audited. Learner submits the work with all calculations, sources, and assumptions stated clearly, and checks the result against the chapter checklist before final submission.

Expected deliverables.

• Payment data model diagram with twelve entities
• Field mapping table for twenty fields
• Mapping gap register with three gaps
• Status change and audit design note

Completion criterion. Learner models at least twelve entities with correct relationships, maps at least sixteen fields correctly, and resolves all three gaps plausibly. Completion is judged on accuracy, completeness, and clear reasoning throughout the submitted work.