GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

GET IN TOUCH
CBPR+ (ISO 20022 CROSS-BORDER)

Cover missing: an ISO 20022 cover payment that does not match

Trigger: The creditor agent holds a pacs.008 announcing a payment, but no matching cover (pacs.009 COV) has arrived on its nostro.

Contributor Shubham Mathure

What operations sees first: The beneficiary cannot be paid because the announced payment has no funds behind it yet — the direct message was information, not money.

WHERE IS THE MONEY?

Debited from the customer on day one; the creditor was credited only after the cover was repaired.

DID SETTLEMENT HAPPEN?

The cover settled late; the direct pacs.008 was never money, only information.

WHO ACTS NEXT?

Bank Alfa (debtor agent) Bank Alfa reviews why the rejected cover sat unnoticed in the repair queue.

PLAY THE EXCEPTION

Trigger: Cassia holds a pacs.008 announcing USD 1,250,000.00 — but no matching cover has arrived on its nostro.

STEP 1 / 13MESSAGE

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 same starting point as a serial payment — what differs is how Bank Alfa routes the instruction and the money.

Step 1 of 13: 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 goes directly to CassiaBank Alfa (debtor agent) → Cassia Bank (creditor agent) · pacs.008
  4. 04Message
    The cover transfer goes to the correspondentBank Alfa (debtor agent) → Meridian Bank (correspondent) · pacs.009 COV
  5. 05Settlement
    Meridian settles the cover across its booksMeridian Bank (correspondent)
  6. 06Processing
    Cassia sees the cover arrive on its nostroCassia Bank (creditor agent)
  7. 07Processing
    Cassia matches the instruction against the coverCassia Bank (creditor agent)
  8. 08 · EXCEPTION PATHProcessing
    Cassia holds the payment unappliedCassia Bank (creditor agent)
  9. 09 · EXCEPTION PATHMessage
    Cassia queries the debtor agentCassia Bank (creditor agent) → Bank Alfa (debtor agent) · camt.026 (unable to apply)
  10. 10 · EXCEPTION PATHProcessing
    Bank Alfa finds the cover leg failedBank Alfa (debtor agent)
  11. 11 · EXCEPTION PATHMessage
    The cover is repaired and reissuedBank Alfa (debtor agent) → Meridian Bank (correspondent) · pacs.009 COV
  12. 12 · EXCEPTION PATHSettlement
    The cover settlesMeridian Bank (correspondent)
  13. 13 · EXCEPTION PATHPosting
    The creditor is credited lateCassia Bank (creditor agent)
  14. OUTCOME
    Funds
    Debited from the customer on day one; the creditor was credited only after the cover was repaired.
    Settlement
    The cover settled late; the direct pacs.008 was never money, only information.
    Who acts next
    Bank Alfa (debtor agent) — Bank Alfa reviews why the rejected cover sat unnoticed in the repair queue.
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 same starting point as a serial payment — what differs is how Bank Alfa routes the instruction and the money.

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

    After checks and screening on the structured fields, the customer account is debited and the bank chooses the cover method: announce directly to the creditor agent, and fund through correspondents.

    • DR Debtor's account at Bank Alfa — USD 1,250,000.00

    Screening checkpoint: Outbound cross-border screening — Both the direct instruction and the cover leg are screened by every bank that touches them.

  3. 03Message
    The pacs.008 goes directly to CassiaBank Alfa (debtor agent) → Cassia Bank (creditor agent) · pacs.008

    The creditor agent learns the full payment details immediately — who is paying whom, how much, and why — carried in structured fields under a Business Application Header. But this message alone brings no money.

  4. 04Message
    The cover transfer goes to the correspondentBank Alfa (debtor agent) → Meridian Bank (correspondent) · pacs.009 COV

    The pacs.009 COV moves the money along the account chain. Its underlying-customer block repeats the debtor and creditor so every bank in the chain can screen the real parties, and it shares the same UETR as the pacs.008.

  5. 05Settlement
    Meridian settles the cover across its booksMeridian Bank (correspondent)

    As in the serial flow, settlement is a book transfer between the two banks' USD accounts held at Meridian, the shared correspondent.

    • 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. 06Processing
    Cassia sees the cover arrive on its nostroCassia Bank (creditor agent)

    A credit notification tells Cassia the money side is complete on its account at Meridian. Now it has both halves of the payment: the instruction and the funds.

  7. 07Processing
    Cassia matches the instruction against the coverCassia Bank (creditor agent)

    The creditor agent pairs the pacs.008 with the incoming cover by UETR, references, and amount. Crediting on the pacs.008 alone would be paying before being paid.

  8. 08 · EXCEPTION PATHProcessing
    Cassia holds the payment unappliedCassia Bank (creditor agent)

    Without the cover, crediting the creditor would put Cassia out of pocket. The pacs.008 waits in an unapplied-funds queue until the money is confirmed.

  9. 09 · EXCEPTION PATHMessage
    Cassia queries the debtor agentCassia Bank (creditor agent) → Bank Alfa (debtor agent) · camt.026 (unable to apply)

    An unable-to-apply investigation message referencing the pacs.008 asks where the cover is. Investigations like this consume real operations time on both sides.

  10. 10 · EXCEPTION PATHProcessing
    Bank Alfa finds the cover leg failedBank Alfa (debtor agent)

    The pacs.009 COV was rejected for a structured-address error and never reached Meridian. The repair queue caught nobody's eye — a classic operational miss.

  11. 11 · EXCEPTION PATHMessage
    The cover is repaired and reissuedBank Alfa (debtor agent) → Meridian Bank (correspondent) · pacs.009 COV

    Bank Alfa re-sends the corrected cover, quoting the same UETR and underlying parties so the creditor agent can match it to the waiting instruction.

  12. 12 · EXCEPTION PATHSettlement
    The cover settlesMeridian Bank (correspondent)

    Money finally moves across the correspondent's books between the two banks' accounts.

    • 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
  13. 13 · EXCEPTION PATHPosting
    The creditor is credited lateCassia Bank (creditor agent)

    With the cover matched, the credit is applied. The delay and the investigation are the cost of the failed leg.

    • CR Creditor's account at Cassia — USD 1,250,000.00
  14. OUTCOME
    Funds
    Debited from the customer on day one; the creditor was credited only after the cover was repaired.
    Settlement
    The cover settled late; the direct pacs.008 was never money, only information.
    Who acts next
    Bank Alfa (debtor agent) — Bank Alfa reviews why the rejected cover sat unnoticed in the repair queue.

THE TIMELINE

  1. 01Cassia Bank (creditor agent)
    Holds a pacs.008 announcing USD 1,250,000.00 but finds no matching cover on its nostro.pacs.008
  2. 02Cassia Bank
    Sends an investigation message and queries the missing cover.camt.026
  3. 03Meridian Bank (cover route)
    Repairs and re-sends the cover (pacs.009 COV) so the funds actually arrive.pacs.009
  4. 04Cassia Bank
    Once the cover settles on its nostro, credits the beneficiary — the direct pacs.008 was never money, only information.

Resolution: In a cover payment the direct pacs.008 announces the payment while a separate cover moves the money. A missing or mismatched cover is investigated and repaired before the beneficiary is paid.

MESSAGES INVOLVED

LEARN THE CONCEPTS

Sources for this scenario2
  1. Official requirement

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cover payments

    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 models — Payments Signal

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

    What this simplifies: Single-cycle teaching model; participant-specific handling and exact timings vary.

    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.