Inside PPC | Map & Corridors | 3 - USD to CNY

Inside PPC | Map & Corridors week | 3 ,Asymmetric corridor: USD ↔️ CNY 🧭 When one side mandates purpose and the other doesn't, STP lives or dies on sender...

Inside PPC | Map & Corridors week | 3 ,Asymmetric corridor: USD ↔️ CNY 🧭
When one side mandates purpose and the other doesn't, STP lives or dies on sender discipline.
* US side: No universal purpose‑code mandate; focus stays on originator/beneficiary data. Many US payments go out with vague "Payment" narratives.
* China side: Cross‑border RMB (and much FX) requires a declared purpose category; banks often need invoice/contract support. Missing/unclear purposes are held or queried before credit.
* Pattern in the wild: China→US credits smoothly (purpose is already captured); US→China gets stuck when "why" is thin ,an RFI later, you've lost days and goodwill.
* Simple playbook: 1. Treat China‑bound wires as purpose‑mandatory even from the US.
4. Include a clear category (goods, services, capital, charity, other current account) plus invoice/contract refs in remittance info.
9. Where supported, populate ISO 20022 <Purp> so the receiving bank can auto‑classify.
12. Save a China‑bound template in your portal with pre‑filled purpose structure for repeat payees.
* Impact: Fewer compliance holds, fewer back‑and‑forths, and far fewer cases that drift into 5-10 working day investigations.
Why it matters: If only one end requires purpose, act as if both do ,your beneficiary's SLA (and supplier trust) depend on it.

Inside PPC - Week 1 Wrap: Map & Corridors
Post 1: We mapped the mandates - APAC/Gulf = , Europe/UK = , Americas = . If either end is , treat the whole corridor as such. Roughly 1-3 % of cross‑border flows trigger enquiries; fixes take 5-10 days and investigations cost ~$1.6B annually.
Post 2: UAE→India runs on two rulebooks. PoP codes mandatory in the UAE; RBI purpose codes pre‑credit in India. Mismatched codes & MT free‑text create the 1-3 % enquiries club. Fix it: carry both codes, use ISO fields, template & pre‑validate.
Post 3: USD↔CNY is asymmetric. US wires often lack purpose, but China requires clear categories & docs. Treat China‑bound wires as purpose‑mandatory; include goods/services/capital labels + invoice refs; use ISO & templates. The result? Fewer holds & RFIs, better supplier SLAs.
What to do next: Document your red corridors & purpose fields; put ISO / & validation rules in place; train teams & set KPIs (RFI rate, STP %).

Topics: ISO 20022, Payments, Compliance, Data Quality, Purpose Codes