G20 Cross-Border Payments Targets: The 2027 Reporting Countdown

ByOfficer

On 8 July 2026, the Financial Stability Board’s Deputy Secretary General, Martin Moloney, told an OMFIF audience that the G20 Roadmap for Enhancing Cross-border Payments is approaching its finish line without having reached its destination. The G20 cross-border payments targets on cost, speed, transparency and access were set in 2021, and most of them fall due at the end of 2027. On current data, the FSB says satisfactory global improvement in line with the 2027 timetable is unlikely. For a payment institution, that gap carries operational weight: it shapes which parts of your messaging and reporting stack a supervisor, a scheme operator, or a correspondent bank will expect to see working over the next eighteen months.

His remarks, titled “Cross-Border Payments: Towards the Next Chapter”, are worth reading for where they point the supervisory pressure. When the headline targets slip, attention shifts to the concrete building blocks meant to deliver them: harmonised ISO 20022 message data, Legal Entity Identifiers, structured transparency information, and the data quality that sanctions and anti-money-laundering screening depend on. Those are the things a payment institution builds, files, and gets audited against.

One distinction runs through everything that follows. The G20 cross-border payments targets are a global yardstick, monitored through key performance indicators, and they place no direct filing obligation on any individual firm. The obligations that do land on a payment institution reach it through messaging standards, scheme rulebooks, and regional law built to hit those same targets. Treating the two as one thing is where preparation tends to go astray.

Related reading: ECB Project Agora: Tokenised Cross-Border Settlement

The cross-border payments calendar that matters

The programme has a long timeline, but only two dates on it create firm build obligations for a payment institution. The rest are monitoring milestones and policy checkpoints. Keeping the calendar scannable helps a reporting team separate the deadlines that move a system-change budget from the ones that move a press release.

  • November 2020: G20 Leaders endorse the roadmap for enhancing cross-border payments (the FSB’s Stage 3 roadmap report, developed in coordination with the CPMI, was published on 13 October 2020).
  • 13 October 2021: the FSB finalises the quantitative targets for cost, speed, transparency and access.
  • 23 February 2023: the FSB publishes priority actions to achieve the targets by the 2027 date.
  • October 2023: the CPMI sets out its harmonised ISO 20022 data requirements for cross-border payments.
  • 22 November 2025: Swift’s CBPR+ MT/ISO 20022 coexistence period for cross-border payment instruction messages ends.
  • 9 October 2025: the FSB publishes its consolidated progress report for 2025, integrated with the key performance indicators.
  • 26 February 2026: the CPMI publishes an updated report on the harmonised ISO 20022 data requirements.
  • End-2027: target date for most of the G20 targets, and the date by which the CPMI encourages alignment with the harmonised ISO 20022 data requirements.
  • 2030: the target date for the remittance cost goal, aligned with UN Sustainable Development Goal 10.c.

The two operational dates to track are 22 November 2025 and end-2027. The first is the Swift CBPR+ end of MT/ISO 20022 coexistence for cross-border payment instruction messages. The second is the CPMI’s encouraged alignment date for the harmonised ISO 20022 data requirements; those requirements are not regulatory requirements. A firm should treat end-2027 as a practical data-quality and interoperability benchmark unless a scheme rule, correspondent requirement or local law makes it binding for that firm.

What the G20 cross-border payments targets actually measure

The targets sit across three market segments and four dimensions. The segments are wholesale payments between financial institutions, retail payments made by people and businesses, and remittances. The dimensions are cost, speed, transparency and access. Each cell of that grid carries a measurable goal, and the FSB measures progress at the global and corridor level from aggregated data.

On cost, the targets are specific for the two consumer-facing segments. For retail, the goal is a global average cost of a cross-border payment of no more than 1 per cent by end-2027, with no corridor higher than 3 per cent. For remittances, the goal is a global average cost of sending a USD 200 remittance of no more than 3 per cent, with no corridor above 5 per cent, by 2030, matching the UN Sustainable Development Goal. Wholesale payments carry speed and access goals but no headline cost figure; the FSB set no wholesale cost target because average costs are difficult to estimate in a market where transactions are typically not individually priced.

On speed, the 75 per cent target applies across all three segments by end-2027, but the formulation differs. Wholesale payments should be credited within one hour of initiation, or within one hour of the pre-agreed settlement date and time for forward-dated transactions, with the rest within one business day and reconciliation by the end of the day credited. Retail and remittance payments should make funds available to the recipient within one hour, with the rest within one business day. On access, the remittance goal is that more than 90 per cent of individuals who wish to send or receive a remittance should have a means of doing so electronically, with parallel access options set for the retail and wholesale segments.

On transparency, the target is a minimum list of information that a payment service provider makes available to payers and payees. That list covers the total transaction cost, including all charges and fees plus the applicable currency-conversion rate and its cost, the expected time to deliver the funds, the ability to track the payment’s status, and the terms of service. Transparency is the dimension that reads most directly as a data-production requirement, because each item on that list has to be generated, populated and surfaced by a firm’s systems.

Here is the point a reporting team should hold onto. None of these figures is a return that a firm files. They are outcome metrics that the FSB and the CPMI compute from aggregated data. What a firm is actually accountable for is different: its systems must produce the message content, the disclosures and the settlement behaviour from which those aggregate outcomes are built.

Why the end-2027 deadline is slipping

The 2025 consolidated progress report gave the honest reading. The key performance indicators, first calculated in 2023, show only slight improvement at the global level. The speed of wholesale payments has improved, and remittances have sped up, so families relying on money from relatives abroad receive it faster. Average cost has stayed sticky, with gains concentrated in the most expensive regions. Transparency improved a little, though the FSB flagged that the quantitative data is still too thin to form a full picture. The report concluded that satisfactory global improvement in line with the 2027 timetable is unlikely.

Moloney’s speech offered four reasons the market has resisted the roadmap’s push. Cross-border payments are marginal to the business model of most firms that provide them, so the usual competitive pressure to innovate is weak. The service leans heavily on foreign exchange markets, which sit outside the roadmap’s reach. Technology adoption is dominated by participants who often seem to prefer second- or third-mover advantage. And the political and regulatory authority needed to force change is spread across central banks, finance ministries and standard setters, with no single body holding the mandate.

For a compliance function, the useful takeaway is a negative one. The slippage does not soften any firm-level obligation. The messaging cutover already happened. The harmonised data requirements still point at end-2027. The regional transparency and instant-payment rules run on their own statutory clocks. A missed global target changes the FSB’s next chapter, and not a supervisor’s expectation that your ISO 20022 fields are populated correctly. Reading a slow KPI as breathing room is the mistake this section exists to head off.

ISO 20022 is where the reporting readiness test really sits

The messaging standard is the part of the roadmap that most directly touches a payment institution’s plumbing. ISO 20022 was first introduced in 2004, and adopting a harmonised version of it for message formats is building block 14 of the roadmap. By Moloney’s figures, implementation now covers 77 per cent of fast payment systems and 53 per cent of real-time gross settlement systems. For Swift CBPR+ payment instruction messages, the MT/ISO 20022 coexistence period ended on 22 November 2025. That ended coexistence on the Swift CBPR+ network; it did not mean every payment rail or participant globally had completed full ISO 20022 implementation.

Migration is the floor, not the finish. In October 2023 the CPMI set out twelve harmonised ISO 20022 data requirements for cross-border payments, and it published an updated version of that report on 26 February 2026. The requirements standardise how key data elements are structured so that payments interoperate and pass straight through without manual repair. Market participants are encouraged to align with them by end-2027 at the latest, with flexibility to move at their own pace until then. That end-2027 date is the one a reporting officer should carry into a project plan.

The common failure here is treating ISO 20022 as a message-conversion exercise and stopping there. I have seen migrations delivered on time at the wire level, with the richer structured fields left unmapped to the downstream engines that are supposed to consume them. Moloney made the same point in policy terms: the value of the standard comes from consistent usage, from embedding the data into screening, reconciliation, fraud analytics, supervision and reporting. A structured remitter address that never reaches the screening engine is a field a firm populated and then wasted.

Turning the transparency target into disclosure data

The transparency dimension is where the global target and hard regional law line up most closely. In the European Union, the transparency of charges and the currency-conversion disclosure obligations for cross-border transfers sit in Regulation (EU) 2021/1230. The instant payments reforms in Regulation (EU) 2024/886, adopted on 13 March 2024, amended that regulation and the payment services framework, and they push euro credit transfers toward instant execution with payee verification. Those instruments turn the abstract transparency target into concrete disclosure content a firm must generate and stand behind.

The reporting-readiness question is whether the systems that quote a price and settle a payment can also produce the four transparency data points the roadmap lists. Total cost including the conversion rate, expected delivery time, tracking status and terms of service each has to be captured, stored and, in a dispute or a supervisory review, reproduced. A firm that discloses a headline fee but cannot reconstruct the applied exchange-rate margin for a specific historical transaction has met the marketing form of transparency without the evidentiary substance. For the EU instant-payments detail, our guide to the SEPA Instant Payments Regulation walks through the execution and verification obligations that now sit on top of the transparency rules.

Legal Entity Identifiers and the data the messages carry

Two building blocks push identity and data quality into the payment message itself. One promotes common message formats and the use of Legal Entity Identifiers; another establishes unique identifiers with proxy registries. The point of both is that a payment which carries clean, structured party data is cheaper to process, faster to clear, and far easier to screen. Poor data quality and weak standardisation are, in the FSB’s own framing, a direct drag on speed, price and transparency.

Anti-money-laundering obligations ride on the same rails. FATF Recommendation 16, the travel rule, requires originator and beneficiary information to accompany a wire transfer, and ISO 20022 carries far more of that data than the legacy formats did. Moloney noted a recurring gap: a study found that many institutions still lean on screening methods designed for the old message types, even though the new standard offers a richer, more structured basis for sanctions and financial-crime checks. A firm that has migrated its messages but not rebuilt its screening logic around the structured fields is carrying travel-rule data it does not fully use. Our explainer on the FATF Recommendation 16 travel rule sets out the originator and beneficiary data expectations in more detail.

Speed, access, and the rails behind them

The speed and access targets are delivered less by any single firm than by the shared infrastructure firms plug into. Faster settlement depends on the interlinking of domestic fast payment systems, on wider adoption of payment-versus-payment settlement to remove foreign-exchange settlement risk, and on extending and aligning the operating hours of key payment systems so that a payment sent in one time zone is not stranded waiting for another market to open. Extending operating hours is building block 12, and payment-versus-payment coverage remains one of the frictions Moloney named as still unresolved.

Interlinking is the most visible lever. Cross-currency instant settlement arrangements let two domestic instant systems exchange value directly, compressing a chain of correspondents into a single hop. Our note on TIPS cross-currency settlement shows how one such arrangement works across euro and Nordic currencies. For a reporting team, the operational detail is that these arrangements change the settlement leg and the data a firm sees, which in turn affects reconciliation, liquidity monitoring and the timestamps a firm records against each payment. A new rail is a new data source before it is a faster service.

Stablecoins and the silver-bullet question

The speech was candid about the technology that gets the most attention. Total cross-border payments in 2024 ran at or around USD 200 trillion. By some estimates, stablecoins carried less than 0.2 per cent of that flow in 2025. The order of magnitude tells the story: stablecoins remain a very small share of cross-border value today. Moloney’s read is that their most immediate value may lie in hybrid models, integrated with bank money and interoperable foreign-exchange and settlement, as components rather than as stand-alone global rails, and even that remains uncertain.

The reporting-readiness implication is a matter of sequencing. A payment institution deciding where to spend its remaining pre-2027 budget has little reason to reprioritise a whole reporting roadmap around stablecoin rails that move a fraction of a per cent of volume. Where a firm does issue or handle tokens, the reporting obligations are already concrete under the crypto and e-money frameworks, and they stand apart from the roadmap. Our overview of stablecoin reporting obligations under MiCAR, EMT rules and PSD3 covers what applies when a token actually enters a firm’s flows.

What a payment institution should line up before 2027

The next eighteen months reward firms that treat the roadmap as a data agenda and not a policy debate. The work is unglamorous and specific, and most of it is already in flight somewhere in the organisation. The task is to connect the pieces so that the message, the disclosure and the report all draw on the same structured source.

  • Map every one of the CPMI harmonised ISO 20022 data requirements to a populated field in your outbound and inbound cross-border messages, and hold the internal alignment deadline at end-2027.
  • Confirm that the structured fields you now carry actually feed your screening, reconciliation, fraud and reporting engines, so migration converts into usage.
  • Check that Legal Entity Identifiers and structured party data are present and validated where the message and the counterparty support them.
  • Verify that your systems can reproduce the four transparency data points, including the applied conversion rate, for a specific historical transaction, and not only quote them at the point of sale.
  • Rebuild sanctions and travel-rule screening logic around the richer ISO 20022 data, instead of running new messages through checks designed for legacy formats.
  • Track any interlinking or cross-currency instant arrangement your firm joins as a new data source with its own timestamps and reconciliation needs.

None of these items is triggered by a specific G20 target being met or missed. Each is a firm-level obligation or good practice that survives the roadmap’s outcome, and each is testable against your own systems today. For payment institutions weighing the wider licensing and reporting picture, our guide to PSD3 for payment institutions and electronic money sets out how the EU framework is evolving around these obligations.

Frequently Asked Questions

Do the G20 cross-border payments targets create a reporting obligation for my firm?

No. The targets are outcome metrics that the FSB and the CPMI compute from aggregated data at the global and corridor level. No individual firm files a return against them. The obligations that reach a firm come through messaging standards such as ISO 20022, scheme rulebooks, and regional law like the EU transparency and instant-payment rules.

What actually happened at the November 2025 ISO 20022 cutover?

Swift’s CBPR+ MT/ISO 20022 coexistence period for cross-border payment instruction messages ended on 22 November 2025. After that point, firms using or receiving those messages should plan around structured ISO 20022 data, while recognising that some participants may still rely on contingency processing, in-flow translation or other rails outside CBPR+.

How is the CPMI end-2027 date different from the November 2025 migration?

The November 2025 migration was a cutover to the message format. The end-2027 date is the CPMI’s encouragement to align message content with its twelve harmonised data requirements, so that the same data elements are structured consistently across systems. A firm can be migrated to ISO 20022 and still not be aligned with the harmonised data requirements.

What are the exact cost targets?

For retail cross-border payments, a global average cost of no more than 1 per cent by end-2027, with no corridor above 3 per cent. For remittances, a global average cost of sending a USD 200 remittance of no more than 3 per cent, with no corridor above 5 per cent, by 2030. Wholesale payments carry speed and access goals but no headline cost figure.

Which EU instruments turn the transparency target into hard law?

In the European Union, Regulation (EU) 2021/1230 governs the transparency of charges and currency-conversion disclosure for cross-border transfers. Regulation (EU) 2024/886, adopted on 13 March 2024, amended it alongside the payment services framework and pushed euro credit transfers toward instant execution with payee verification.

Does the FATF travel rule connect to the ISO 20022 work?

Yes. FATF Recommendation 16 requires originator and beneficiary information to travel with a wire transfer, and ISO 20022 carries more of that data in structured form than legacy messages did. The practical risk is that a firm migrates its messages but keeps screening logic built for the old formats, so the richer data is present but underused.

Should stablecoins change my reporting priorities before 2027?

For most payment institutions, no. Stablecoins carried an estimated fraction of a per cent of cross-border flows in 2025, against total volumes of around USD 200 trillion in 2024. Where a firm issues or handles tokens, the crypto and e-money reporting obligations apply in their own right, separate from the G20 roadmap.

Related Articles

Key Takeaways

  • The G20 cross-border payments targets on cost, speed, transparency and access were set in 2021, and most fall due at end-2027; the FSB’s 2025 progress report judges the global targets unlikely to be met on time.
  • The targets are outcome metrics measured through key performance indicators. They place no direct filing obligation on any individual payment institution.
  • The firm-level work arrives through a mix of binding and non-binding channels: ISO 20022 network and scheme requirements, CPMI harmonised data requirements where adopted, Legal Entity Identifiers where required or supported, EU transparency-of-charges rules, and FATF travel-rule data.
  • The November 2025 ISO 20022 migration was a hard cutover; the CPMI’s twelve harmonised data requirements ask for alignment by end-2027, which is the date a reporting team should plan to.
  • Migration is only the floor. The value comes from feeding the structured fields into screening, reconciliation, fraud analytics and reporting, which many firms have not yet done.
  • In the EU, Regulation (EU) 2021/1230 and Regulation (EU) 2024/886 turn the transparency and speed goals into hard disclosure and instant-execution obligations.
  • Stablecoins carried an estimated fraction of a per cent of cross-border flows in 2025, so they are worth watching without reprioritising a reporting roadmap around them.

Sources and References

  • Financial Stability Board, “Cross-Border Payments: Towards the Next Chapter”, opening remarks by Martin Moloney, 8 July 2026: fsb.org
  • Financial Stability Board, “G20 Roadmap for Enhancing Cross-border Payments: First consolidated progress report”, 13 October 2021: fsb.org (PDF)
  • Financial Stability Board, “Targets for Addressing the Four Challenges of Cross-Border Payments: Final Report”, 13 October 2021: fsb.org
  • Financial Stability Board, “G20 Roadmap for Cross-border Payments: Consolidated progress report for 2025”, 9 October 2025: fsb.org
  • CPMI (BIS), “Harmonised ISO 20022 data requirements for enhancing cross-border payments, updated report”, 26 February 2026: bis.org
  • CPMI (BIS), “Harmonised ISO 20022 data requirements for enhancing cross-border payments, original report”, October 2023: bis.org
  • Swift, “ISO 20022 for Financial Institutions” (CBPR+ MT/ISO 20022 coexistence period, ended 22 November 2025): swift.com
  • Regulation (EU) 2024/886 of 13 March 2024 as regards instant credit transfers in euro: EUR-Lex
  • Regulation (EU) 2021/1230 on cross-border payments in the Union: EUR-Lex
  • FATF Recommendations (Recommendation 16 on wire transfers): fatf-gafi.org

The next chapter is a data agenda

Moloney closed on coordination as the scarce resource, and asked who will champion a second roadmap after 2027. That is the right question for policymakers. For a payment institution, the more useful reframing is quieter. Whatever the FSB decides about the shape of the next chapter, the data obligations that were supposed to deliver this one are already sitting in your messaging and reporting stack. The structured ISO 20022 fields, the identifiers, the transparency records and the travel-rule data do not wait for a global target to be met. A firm that spends the run-up to 2027 making those fields real, and making sure the engines downstream actually read them, will be ready for the next chapter whatever it turns out to say.

Last updated: July 2026

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts