|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/advanced-guide-iso-20022-swift-mx-messages/
课程评论：没有评论
Coursera 课程：高级指南 - ISO 20022 SWIFT MX 消息 **课程概述：** 本课程是三部分系列中的第二部分，旨在为寻求可靠 ISO 20022 SWIFT MX 消息资源的人士提供全面指导。课程将涵盖 CBPR+ 用法指南和消息结构及要素的全面理解，深入剖析 Pacs.008、Pacs.009、Pacs.004、Pacs.002、Pain.001 和 002 的消息结构。学员还将学习如何创建 MX 消息（包含作业和资源），并通过 100 多个面试准备问题来巩固知识。课程还提供 XML 基础知识，以帮助理解消息模式，解释如何处理 MT-MX 共存期间的数据截断，并通过端到端支付链的消息示例加深理解。 **面向人群：** * 支付领域业务分析师和顾问 * 支付领域从业者 **课程内容：** * ISO 20022 消息目录、SWIFT MX 消息目录和 SWIFT 支付组用法指南。 * ISO 20022 消息注册流程。 * SWIFT 支付组。 * MT 和 MX 消息共存及相关基础设施迁移的处理。 * MT-MX 共存中的数据完整性丢失处理。 * XML 在 ISO 20022 消息中的应用（基本结构、语法规则、XML Schema 及实例、数据类型、属性和复杂元素、限制和指示符）。 * ISO 20022 XML 消息模式理解。 * MX 消息中使用的代码。 * MX 消息验证。 * MX 消息相关重要概念（代理商与方、结算方法、消息元素的多重性）。 * PACS.008 消息的结构和要素（构建块 - 组头和贷记转账交易信息，贷记转账交易信息块，组头块）。 * PACS.009 消息的结构和要素 (PACS.009 Core, PACS.009 COV and PACS.009 ADV)。 * PACS.004 和 PACS.002 消息，以及 PAIN.001 和 PAIN.002 消息的结构（拒付与退回的区别，PACS.004 和 PACS.002 结构，PAIN.001 和 PAIN.002 结构）。 * 通过实际示例理解 MX 消息（PAIN.001、PAIN.002 示例；串联支付案例分析：第一个 PACS.008，第二个 PACS.008、PACS.002 及第三个 PACS.008，第四个 PACS.008）。 * 进一步探讨最终方（Ultimate Parties）和已识别的 MX 消息错误用法，包括正确识别、实践场景、错误声明的含义，以及如何纠正已识别的错误用法。 * 提供练习测试和作业。
**Part 2 of 3 courses**Are you someone who is searching for a reliable resource on ISO 20022 SWIFT MX messages?Confused about where to begin learning? What to learn? From where to learn?Then this course is your perfect match!!You will get -Full understanding of CBPR+ usage guideline and message structure and elementsPacs.008, Pacs.009, Pacs.004, Pacs.002, Pain.001 and 002 message structuresLearn creating MX messages - Assignments + Resources100+ questions to get you ready for interviewEssential background knowledge of XML to understand message schemasLearn how to handle data truncation during MT-MX coexistenceMessage examples of end to end payment chainThis course, the 'Advanced Guide - ISO 20022 SWIFT MX Messages', delves deeper into all the necessary concepts of SWIFT MX messages, starting from how the different working groups of SWIFT work and the inter-relations of the usage guidelines, how XML is used to build the ISO 20022 messages schema, how the important messages are structured - discussing element by element, and the logic behind each element's presence. It also provides real life message examples to understand the application of all that is learnt.Who is this course for?Business Analysts and Consultants of Payments DomainAspirants of Payments DomainWhat this course covers?What are ISO 20022 message catalogue, SWIFT MX message catalogue and SWIFT payment groups usage guidelinesISO 20022 Message Registration ProcessSWIFT Payment GroupsHandling of Coexistence of MT and MX messages and Other Related Migrations of InfrastructuresHandling data integrity loss in MT-MX coexistenceXML in ISO 20022 messagesBasic Structure of XML and Syntax RulesXML Schema and InstanceXML Data TypesXML Attributes and Complex ElementsRestrictions and IndicatorsUnderstanding the ISO 20022 XML Message SchemaCodes used in MX MessagesMX Message ValidationImportant Concepts Related to MX MessagesAgents and PartiesSettlement MethodsMultiplicity of Elements in MessagesStructure and Elements of PACS.008 Message Building Blocks - Group Header and the Credit Transfer Transaction InformationUnderstanding the Credit Transfer Transaction Information BlockUnderstanding the Group Header BlockStructure and Elements of PACS.009 MessagePACS.009 Core, PACS.009 COV and PACS.009 ADVBuilding Blocks - Group Header and Credit Transfer Transaction InformationStructure of PACS.004 and PACS.002 Messages, PAIN.001 and PAIN.002 MessagesDifference between Reject and ReturnPACS.004 and PACS.002 StructurePAIN.001 and PAIN.002 StructureUnderstanding MX Messages with ExamplesPAIN.001 Message ExamplePAIN.002 Message ExampleSerial payment - First PACS.008Serial Payment - Second PACS.008, PACS.002 and Third PACS.008Serial Payment - Fourth PACS.008More on Ultimate Parties and Incorrect usages of MX identified so farCorrect identification of Ultimate PartiesPractical scenarios involving Ultimate PartiesImplications of Incorrect Declaration of Ultimate PartiesTake corrective action - Incorrect usages of Ultimate Parties identified so farTake corrective action - Incorrect usages of MX messages identified so farPractice Test and Assignments
