GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
CBPR+ (ISO 20022 CROSS-BORDER)

Whose money is this? A request for information before crediting

Trigger: Cassia Bank cannot confidently apply the credit — the creditor name in the pacs.008 does not match the account holder on record.

What operations sees first: The payment shows as delivered to the creditor agent but never confirms; then an investigation request referencing the transaction arrives at Bank Alfa.

WHERE IS THE MONEY?

Settled to Cassia early on, but parked in Cassia's suspense account until the information arrived; then credited to the creditor.

DID SETTLEMENT HAPPEN?

Interbank settlement completed before the investigation began — only the final customer posting waited.

WHO ACTS NEXT?

Cassia Bank (creditor agent) The debtor uses the beneficiary's registered legal name on future instructions; Cassia monitors its unapplied-funds queue by age so held items cannot be forgotten.

PLAY THE EXCEPTION

Trigger: Cassia cannot confidently apply the credit — the creditor name does not match the account holder on record.

STEP 1 / 11MESSAGE

The debtor initiates the cross-border payment

Debtor (payer) → Bank Alfa (debtor agent) · pain.001

A corporate treasury sends a pain.001 with structured party and remittance data — the structure survives the whole journey because every hop speaks ISO 20022.

Step 1 of 11: The debtor initiates the cross-border payment

  1. 01Message
    The debtor initiates the cross-border paymentDebtor (payer) → Bank Alfa (debtor agent) · pain.001
  2. 02Processing
    Bank Alfa validates, screens, and debitsBank Alfa (debtor agent)
  3. 03Message
    The pacs.008 leaves with a BAH and UETRBank Alfa (debtor agent) → Meridian Bank (intermediary agent) · pacs.008
  4. 04Processing
    Meridian screens in the middle of the chainMeridian Bank (intermediary agent)
  5. 05Settlement
    The correspondent settles across its booksMeridian Bank (intermediary agent)
  6. 06Message
    The pacs.008 continues to the creditor agentMeridian Bank (intermediary agent) → Cassia Bank (creditor agent) · pacs.008
  7. 07Processing
    Cassia validates the incoming paymentCassia Bank (creditor agent)
  8. 08 · EXCEPTION PATHProcessing
    The credit is held pending informationCassia Bank (creditor agent)
  9. 09 · EXCEPTION PATHMessage
    Cassia asks the debtor agent for clarificationCassia Bank (creditor agent) → Bank Alfa (debtor agent)
  10. 10 · EXCEPTION PATHMessage
    Bank Alfa confirms the beneficiary detailsBank Alfa (debtor agent) → Cassia Bank (creditor agent)
  11. 11 · EXCEPTION PATHPosting
    The credit is applied from suspenseCassia Bank (creditor agent)
  12. OUTCOME
    Funds
    Sat in the creditor agent's suspense account until the information arrived, then credited.
    Settlement
    Interbank settlement completed before the investigation began — only the customer posting waited.
    Who acts next
    Cassia Bank (creditor agent)The debtor uses the beneficiary's registered legal name on future invoices and instructions.
Full step-by-step text (works without JavaScript)
  1. 01Message
    The debtor initiates the cross-border paymentDebtor (payer) → Bank Alfa (debtor agent) · pain.001

    A corporate treasury sends a pain.001 with structured party and remittance data — the structure survives the whole journey because every hop speaks ISO 20022.

  2. 02Processing
    Bank Alfa validates, screens, and debitsBank Alfa (debtor agent)

    Checks and screening run on rich, structured fields — one of ISO 20022's main gains. The customer account is debited on acceptance.

    • DR Debtor's account at Bank AlfaUSD 1,250,000.00

    Screening checkpoint: Outbound screening on structured data Structured names and addresses screen more precisely than free-text lines, cutting false positives.

  3. 03Message
    The pacs.008 leaves with a BAH and UETRBank Alfa (debtor agent) → Meridian Bank (intermediary agent) · pacs.008

    The interbank message travels with a Business Application Header and a UETR — the end-to-end reference every bank keeps unchanged, making the payment trackable.

  4. 04Processing
    Meridian screens in the middle of the chainMeridian Bank (intermediary agent)

    The intermediary agent screens the structured parties and checks cover on Bank Alfa's account.

  5. 05Settlement
    The correspondent settles across its booksMeridian Bank (intermediary agent)

    Settlement is a book transfer between the two banks' USD accounts at Meridian — same mechanics as the MT world; the message standard changed, the money movement did not.

    • DR Bank Alfa's USD account at Meridian (vostro)USD 1,250,000.00
    • CR Cassia's USD account at Meridian (vostro)USD 1,250,000.00
  6. 06Message
    The pacs.008 continues to the creditor agentMeridian Bank (intermediary agent) → Cassia Bank (creditor agent) · pacs.008

    The same UETR arrives at Cassia; anyone with the reference can see where the payment is in the chain.

  7. 07Processing
    Cassia validates the incoming paymentCassia Bank (creditor agent)

    Inbound screening and account checks before the credit is applied.

  8. 08 · EXCEPTION PATHProcessing
    The credit is held pending informationCassia Bank (creditor agent)

    Rather than crediting the wrong customer or returning good funds, Cassia parks the amount and investigates. Settlement has already happened — only the final posting waits.

    • CR Cassia unapplied-funds suspenseUSD 1,250,000.00
  9. 09 · EXCEPTION PATHMessage
    Cassia asks the debtor agent for clarificationCassia Bank (creditor agent) → Bank Alfa (debtor agent)

    An investigation request referencing the UETR asks for confirmation of the intended beneficiary.

  10. 10 · EXCEPTION PATHMessage
    Bank Alfa confirms the beneficiary detailsBank Alfa (debtor agent) → Cassia Bank (creditor agent)

    The debtor confirms the trading name on the invoice; the account is right, the name style differed.

  11. 11 · EXCEPTION PATHPosting
    The credit is applied from suspenseCassia Bank (creditor agent)

    With the ambiguity resolved, the funds leave suspense and reach the creditor.

    • DR Cassia unapplied-funds suspenseUSD 1,250,000.00
    • CR Creditor's account at CassiaUSD 1,250,000.00
  12. OUTCOME
    Funds
    Sat in the creditor agent's suspense account until the information arrived, then credited.
    Settlement
    Interbank settlement completed before the investigation began — only the customer posting waited.
    Who acts next
    Cassia Bank (creditor agent)The debtor uses the beneficiary's registered legal name on future invoices and instructions.

THE TIMELINE

  1. 01Bank Alfa
    Sends the CBPR+ payment; it settles leg by leg through Meridian Bank all the way to Cassia Bank.pacs.008
  2. 02Cassia Bank
    Validation stalls at the final step: the beneficiary name does not match the account holder. Rather than credit the wrong customer or return good funds, Cassia parks the amount in an unapplied-funds suspense account.
  3. 03Cassia Bank
    Sends an investigation request to Bank Alfa referencing the transaction's unique reference (UETR), asking for confirmation of the intended beneficiary.

    Shown generically here — institutions use different investigation channels and message types.

  4. 04Bank Alfa
    Checks with the debtor and confirms the beneficiary details: the account is right; the invoice used a trading name that differs from the registered name.
  5. 05Cassia Bank
    Applies the credit from suspense to the creditor's account.
  6. 06Cassia Bank
    Confirms completion so the debtor side can close its investigation case.pacs.002

Resolution: The credit posts once the ambiguity is resolved — held briefly in suspense rather than bounced back. Had no answer come, Cassia would eventually have had to return the funds instead.

MESSAGES INVOLVED

Sources for this scenario2
  1. Official requirement

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelinesSwift (CBPR+ working group)

    Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-12

    Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.

  2. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: Single-intermediary chain; investigation exchange shown generically; institution-specific handling varies.

    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.