GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
12 / ISO 20022 & CBPR+12 MIN

Cover announcements and reimbursement agents

In a cover payment, the announcement and the money take different paths — reimbursement agents are the named correspondents that carry it, and there can be more than one.

NOT STARTED

L0 Explain simply

Analogy: calling ahead, and a separate delivery. Imagine you call a friend abroad to say "a parcel is coming for you, here is everything about it" — then the parcel itself travels through one or two courier depots you never mentioned on the call, before it reaches your friend's local depot. The call went straight to the destination; the parcel took its own route through whichever depots could actually carry it. A cover payment works the same way: the pacs.008 announcement goes directly to the creditor's bank, while the money travels separately through however many correspondent banks it takes to get there — and those correspondents have their own name in the message: reimbursement agents.

L1 Core concepts

A reimbursement agent is a correspondent bank that carries the cover value between the debtor agent and the creditor agent — distinct from the creditor agent itself, which only receives the announcement. The instructing reimbursement agent is the correspondent the debtor agent's cover payment goes to first; the instructed reimbursement agent is the correspondent that ultimately credits the creditor agent's account, completing the reimbursement. When one bank happens to serve both roles — the debtor agent's and creditor agent's shared correspondent — a single reimbursement agent is enough. When it does not, the cover has to pass through more than one.

L2 Practitioner view

The reimbursement agent role exists because the announcement and the cover are not required to travel the same path. The creditor agent needs to know, from the announcement alone, which correspondent to expect the cover value from — otherwise a credit notification arriving from an unnamed bank is just money with no context. Naming the instructing and instructed reimbursement agents in the pacs.008 gives every bank that later reads the message the same answer to "who is actually carrying the funds", independent of whichever bank happens to be the creditor agent for this payment.

L3 Technical details

Illustrative chain: Asha Traders pays a supplier who banks with Nordbank. Asha Traders' bank, Bank Alfa, has no shared correspondent with Nordbank in the transfer currency, so the cover has to pass through two correspondents: Meridian Bank first, then Cassia Bank, which holds an account for Nordbank. Bank Alfa's pacs.008 announcement names Meridian as instructing reimbursement agent and Cassia as instructed reimbursement agent — telling Nordbank exactly which two correspondents to expect the value from, even though neither of them is the creditor agent. Where a chain needs a third correspondent, the message adds a third reimbursement agent element — but only alongside the first two, never instead of them.

L4 Standards & sources

ISO 20022's pacs.008 Group Header carries InstructingReimbursementAgent, InstructedReimbursementAgent and ThirdReimbursementAgent as distinct elements, with a cross-element rule: if a third reimbursement agent is present, the first two must both be present as well — a chain cannot skip straight to naming a third correspondent without naming the two it necessarily passes through first. Presence of any reimbursement agent element is itself a signal that this pacs.008 is travelling the cover method, and CBPR+ usage guidance ties this to the settlement method element carrying the value COVE. The worked flow linked below uses a single shared correspondent, so it shows one reimbursement agent playing both roles at once — the simplest case, not the only one.

Sources & standards2
  1. Official requirement

    ISO 20022 Catalogue of messagesISO 20022 Registration Authority · pacs.008 GroupHeader InstructingReimbursementAgent, InstructedReimbursementAgent, ThirdReimbursementAgent elements and their cross-element presence rule

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Scheme-specific rule

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelinesSwift (CBPR+ working group) · reimbursement agent usage and settlement method COVE for the cover method

    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-18

    Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.

SEE THE PAYMENT MOVE

ISO 20022 cover payment (pacs.008 + pacs.009 COV) — swimlane diagramThe instruction reaches the creditor agent directly as a pacs.008 while the funds travel the correspondent route as a pacs.009 COV. The two must meet and match before the payee is paid. The full step-by-step description follows this diagram as text.
MESSAGECLEARING OBLIGATIONSETTLEMENTPOSTING
ISO 20022 cover payment (pacs.008 + pacs.009 COV). One correspondent carries the cover. Real flows may involve correspondents on both sides, foreign-exchange conversion, and charge deductions along the chain. PLAY IT STEP BY STEP →
Read the steps as text
  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 AlfaUSD 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. 08Posting
    The creditor is creditedCassia Bank (creditor agent)

    With instruction and funds matched, Cassia credits its customer. The cover method gives the creditor agent the details sooner, but the credit still waits for the money to actually arrive.

    • CR Creditor's account at CassiaUSD 1,250,000.00

MESSAGES INVOLVED

EVIDENCE AT ARM'S REACH

IMPLEMENTATION RESOURCES

Apply the base message definition first, then the scheme or infrastructure profile that governs this topic.

An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.

XSD + definitionBase ISO 20022

ISO 20022 message definitions and XSDs

Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.

OPEN OFFICIAL SOURCE
Usage guidelineCBPR+

CBPR+ usage guidelines

The network profile that restricts how ISO 20022 payment and reporting messages are used for cross-border traffic.

OPEN OFFICIAL SOURCE
Usage guidelineHVPS+

HVPS+ usage guidelines

The common high-value ISO 20022 market-practice layer used as a starting point by T2, CHAPS, Fedwire, CHIPS, and other payment infrastructures.

OPEN OFFICIAL SOURCE
Usage guidelineCBPR+

PMPG correspondent-payment and reporting market practice

Non-binding market practice for structured party data, cover payments, investigations, and the transition between MT and ISO 20022 reporting.

OPEN OFFICIAL SOURCE
RulebookSEPA SCT

SEPA Credit Transfer rulebook

The current scheme obligations, datasets, time cycles, and exception rules for a SEPA Credit Transfer.

OPEN OFFICIAL SOURCE
Usage guidelineSEPA SCT

SEPA Credit Transfer implementation guidelines

The EPC profile describing how the ISO 20022 messages implement the SCT rulebook between payment service providers.

OPEN OFFICIAL SOURCE
RulebookSEPA SCT Inst

SEPA Instant Credit Transfer rulebook

The current scheme rules for round-the-clock euro instant credit transfers and their exception handling.

OPEN OFFICIAL SOURCE
Usage guidelineSEPA SCT Inst

SEPA Instant Credit Transfer implementation guidelines and XSDs

Customer-to-PSP and Inter-PSP profiles for SCT Inst. EPC XSDs are technical validation subsets, not production artefacts or proof of full scheme compliance.

OPEN OFFICIAL SOURCE
Usage guidelineT2

T2 functional specifications, validation rules, and binding XSDs

The ECB release library for T2 RTGS and central-liquidity messaging, including public user specifications, business validation rules, and binding schemas.

OPEN OFFICIAL SOURCE
Usage guidelineTIPS

TIPS release specifications and professional-use documentation

The ECB release library for TIPS UDFS/UHB specifications, message examples, implementation guidance, and MyStandards message-version links.

OPEN OFFICIAL SOURCE
Usage guidelineCHAPS

CHAPS and RTGS ISO 20022 handbook and schema access

The Bank of England handbook for CHAPS message scope, enhanced data, returns, testing, and the MyStandards location of controlling schemas.

OPEN OFFICIAL SOURCE
Usage guidelineFedwire

Fedwire Funds Service ISO 20022 implementation and technical documents

Fedwire message versions, usage guidelines, implementation guidance, testing material, and the controlled route to proprietary schemas.

OPEN OFFICIAL SOURCE
Usage guidelineCHIPS

CHIPS ISO 20022 usage-guideline resources and rules

The public CHIPS ISO 20022 resource hub, legal notes, rules, change summaries, and participant material access points.

OPEN OFFICIAL SOURCE
MappingCBPR+

MT103 → pacs.008 implementation mapping

Field correspondence, transformation treatment, and data-loss notes for Cross-border customer credit transfer translation, in the spirit of public CBPR+ and PMPG translation guidance. Educational summary — the applicable usage guideline is the rule.

DOWNLOAD
Test packScheme-neutral teaching

Payment lifecycle test cases

Positive and negative test cases across validation, rejection, return, recall, reversal, investigation, reconciliation, migration, instant payments, and screening.

DOWNLOAD
Field matrixTIPS

TIPS instant-settlement implementation pack field and process matrix

Verified profile constraints with versioned evidence and explicit operating conditions.

DOWNLOAD
Coverage gapsTIPS

TIPS instant-settlement implementation pack restricted and release-specific gaps

Evidence that must be obtained from the owner before production readiness can be claimed.

DOWNLOAD
Coverage gapsCHAPS

CHAPS RTGS implementation pack restricted and release-specific gaps

Evidence that must be obtained from the owner before production readiness can be claimed.

DOWNLOAD
Field matrixFedwire

Fedwire Funds Service implementation pack field and process matrix

Verified profile constraints with versioned evidence and explicit operating conditions.

DOWNLOAD
Coverage gapsFedwire

Fedwire Funds Service implementation pack restricted and release-specific gaps

Evidence that must be obtained from the owner before production readiness can be claimed.

DOWNLOAD
Profile packSEPA SCT

SEPA credit-transfer implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

DOWNLOAD
Profile packHVPS+

High-value payments implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

DOWNLOAD
Profile packTIPS

TIPS instant-settlement implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

DOWNLOAD
Profile packFedwire

Fedwire Funds Service implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

DOWNLOAD
Sources for this topic3
  1. Official requirement

    ISO 20022 Catalogue of messagesISO 20022 Registration Authority · pacs.008 GroupHeader reimbursement agent elements

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Scheme-specific rule

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelinesSwift (CBPR+ working group) · reimbursement agent usage in the CBPR+ correspondent-banking profile

    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-18

    Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.

  3. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

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

    What this simplifies: The two- and three-correspondent chains are invented illustrations with no real institutions, references, or amounts; real reimbursement chains are set by whichever account relationships actually exist for the currency in question.

    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.

Deepest material on this page: L4 Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Public discussion

LOADING

Loading the discussion…