Articles / Learning brief
CGI-MP: Common ISO 20022 Practice for Corporates
Your notes
In simple terms / 01
What this means in plain language
Common Global Implementation – Market Practice (CGI-MP) is a multi-bank forum that agrees a shared way to use ISO 20022 for corporate-to-bank messages, so a company can build one payment profile instead of a different variant for every bank.
ISO 20022 is a flexible messaging standard, and flexibility has a cost. The same payment can be expressed in many valid ways, so without agreement each bank tends to ask a corporate customer for a slightly different version of the message. A company that banks with several institutions then has to build and maintain many near-identical variants. The Common Global Implementation – Market Practice (CGI-MP) forum exists to fix this. It is a group of banks, corporates, and vendors that publishes agreed usage guidelines narrowing the choices, so a corporate treasury can implement one profile of the payment initiation message and reuse it across its banks.
Complete lesson / 02
Understand the full idea, step by step
A company that keeps accounts at five banks would like to send all five the same kind of payment file. In theory one standard should make that possible. In practice, a standard flexible enough to serve everyone can be filled in five slightly different ways — and the company ends up building five files. This lesson is about the fix for that.
Flexibility without agreement
ISO 20022 lets the same business action be represented in more than one valid way — optional fields, different code choices, and varying levels of detail. When each bank makes its own choices, a corporate that uses several banks ends up building a separate message variant for each relationship. That multiplies development, testing, and maintenance, and it slows down every change. Nothing here is broken; the gap is a shared way to use the standard on the corporate-to-bank leg.
CGI-MP — Common Global Implementation – Market Practice
CGI-MP is a multi-bank forum — banks, corporates, and technology vendors — that agrees a shared convention for using ISO 20022 on corporate-to-bank messages. It publishes usage guidelines chiefly for payment initiation (pain.001), payment status report (pain.002), and account statements in the cash management (camt) family, narrowing the optional choices to an agreed set so a corporate can implement one profile and expect each participating bank to accept it. It is a market-practice layer on top of the standard, not a new standard.
You may be wondering: is CGI-MP just CBPR+ for companies?
It is the same idea — a usage-guideline layer that narrows ISO 20022 — applied to a different link. CBPR+ governs the bank-to-bank cross-border leg, between financial institutions. CGI-MP governs the corporate-to-bank leg, between a company and its banks. A treasury team cares about CGI-MP for the file it sends its banks; its banks care about CBPR+ for what they send each other. Same tool, different stretch of the road.
| CGI-MP | CBPR+ | |
|---|---|---|
| Which leg | Corporate to bank | Bank to bank, cross-border |
| Who uses it | Companies and their banks | Correspondent banks |
| Typical messages | pain.001, pain.002, camt statements | pacs.008, pacs.009, pacs.002, camt reporting |
| What it is | Market-practice layer on ISO 20022 | Market-practice layer on ISO 20022 |
ISO 20022 — ILLUSTRATIVE, NON-PRODUCTION
The pain.001 is the customer's initiation — the file a corporate sends its bank. CGI-MP is the agreement about how to fill in messages like this one so every participating bank reads it the same way. Riya never sees a message like this; a corporate treasury does.
Where CGI-MP sits
CGI-MP is central to corporate treasury connectivity precisely because it is a convention, not a replacement. It does not run any system and it does not change what ISO 20022 can express — it agrees which of the standard's valid choices everyone will use. That is why a treasury team can build one profile against CGI-MP and reasonably expect each participating bank to accept it, instead of hand-fitting a variant per bank.
FOR NOW, REMEMBER
- ISO 20022 allows several valid ways to express the same instruction, so without agreement a multi-bank corporate builds one variant per bank.
- CGI-MP is a multi-bank forum that agrees a shared convention for corporate-to-bank ISO 20022 — chiefly pain.001, pain.002, and camt statements.
- It is a market-practice layer on top of the standard, not a new standard, so a corporate can build one profile.
- CGI-MP covers the corporate-to-bank leg; CBPR+ covers the bank-to-bank cross-border leg — same kind of tool, different link.
TRY IT YOURSELF
Asha Traders' treasury wants to build a single payment-initiation file its banks will all accept, instead of one per bank. Which market practice is it building to, and why?
You have now seen both usage-guideline layers — corporate-to-bank and bank-to-bank. The topic behind CBPR+ pulls the cross-border interbank picture together in depth.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
CGI-MP is a market-practice layer that sits on top of ISO 20022; it is not a new standard and does not change the underlying schemas.
- 02
It targets corporate-to-bank flows — payment initiation pain.001, payment status pain.002, and account statements in the camt family.
- 03
By agreeing common usage, it lets a multi-banked corporate build one message profile instead of a separate variant per bank.
Practical use cases / 04
Where you would use this
A treasury team maps its enterprise resource planning system to a single CGI-MP pain.001 profile and sends the same format to all of its banks.
A bank documents its channel by pointing to CGI-MP guidelines, reducing the custom mapping work each new corporate client must do.
A software vendor builds CGI-MP-aligned templates so its product connects to many banks without bespoke rework for each one.
Worked example / 05
Put the idea into a real situation
Illustrative example: Meridian Foods banks with three institutions and used to maintain three slightly different payment files. It adopts a CGI-MP pain.001 profile: one file layout for outbound credit transfers, one pain.002 to receive status back, and camt statements for reconciliation. Now a single mapping from its accounting system reaches all three banks, and onboarding a fourth bank means checking that bank's CGI-MP conformance rather than writing a new format from scratch.
Evidence & review / 07
Evidence & review
Corporate-to-bank ISO 20022 messaging (payment initiation and cash management) using the CGI-MP market practice, contrasted with CBPR+ on the interbank leg.
What this brief simplifies: CGI-MP's scope is summarised at a teaching level; the agreed field choices are set by its published guidelines. Named parties are fictional teaching cast.
Sources for this brief3
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain.001, pain.002, camt message definitions
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Market practice
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · Contrast with the bank-to-bank cross-border leg
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.