pacs.009 COV financial institution transfer
A fictional cover transfer in ISO 20022: the institutional leg plus the underlying customer credit transfer block that keeps the real parties visible.
Illustrative, non-production example. Values are fictional and the message is not validated for any specific network, scheme, or implementation guide.
<?xml version="1.0" encoding="UTF-8"?> <!-- Illustrative non-production data --> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.009.001.08"> <FICdtTrf> <GrpHdr> <NbOfTxs>1</NbOfTxs> <SttlmInf> <InstgRmbrsmntAgt><FinInstnId><BICFI>DEMOUS33XXX</BICFI></FinInstnId></InstgRmbrsmntAgt> <InstdRmbrsmntAgt><FinInstnId><BICFI>DEMOGB2LXXX</BICFI></FinInstnId></InstdRmbrsmntAgt> </SttlmInf> </GrpHdr> <CdtTrfTxInf> <PmtId> <InstrId>DEMO-COV-001</InstrId> </PmtId> <IntrmyAgt1><FinInstnId><BICFI>DEMOUS33XXX</BICFI></FinInstnId></IntrmyAgt1> <UndrlygCstmrCdtTrf> <Dbtr><Nm>Demo Trading Ltd</Nm></Dbtr> <DbtrAgt><FinInstnId><BICFI>DEMODEFFXXX</BICFI></FinInstnId></DbtrAgt> <CdtrAgt><FinInstnId><BICFI>DEMOGB2LXXX</BICFI></FinInstnId></CdtrAgt> <Cdtr><Nm>Example Supplies Ltd</Nm></Cdtr> <InstdAmt Ccy="EUR">1250.00</InstdAmt> <RmtInf><Ustrd>DEMO INVOICE 1001</Ustrd></RmtInf> </UndrlygCstmrCdtTrf> </CdtTrfTxInf> </FICdtTrf> </Document>
EVERY ANNOTATED FIELD
GrpHdr/MsgIdMessage identification — mandatoryA unique reference for this message, assigned by the instructing agent for this hop.
GrpHdr/CreDtTmCreation date and time — mandatoryWhen this message was created.
GrpHdr/SttlmInf/SttlmMtdSettlement method — mandatoryHow this transfer settles between the agents — on an account one of them services (INDA, INGA), through a clearing system (CLRG), or via a separate cover (COVE). In a COV cover the reimbursement agents below name where the cover funds move.
The pacs.009 COV carries the cover leg; the reimbursement agents are the ISO equivalent of the MT202 COV's sender's/receiver's correspondents (:53a:/:54a:).
GrpHdr/SttlmInf/InstgRmbrsmntAgtInstructing reimbursement agent — conditionalIn a cover arrangement, the agent that reimburses the instructed agent — where the cover funds come from (the sender's correspondent). A third reimbursement agent extends the chain when needed.
This is field :53a: in an MT202 COV; the instructed reimbursement agent below is :54a:.
GrpHdr/SttlmInf/InstdRmbrsmntAgtInstructed reimbursement agent — conditionalThe agent that receives the reimbursement — where the cover funds are paid (the receiver's correspondent).
Reimbursement agents only appear with the COVE settlement method; a plain interbank pacs.009 does not carry them.
CdtTrfTxInf/PmtId/EndToEndIdEnd-to-end identification — mandatoryThe reference the first instructing party assigned to this institutional transfer, passed on unchanged.
In the COV usage, market practice ties the cover's references to the underlying customer payment so the creditor agent can match the two — follow the usage guideline in force for exactly which reference goes where.
⚠ A cover whose references do not line up with the underlying pacs.008 leaves funds unapplied in a queue while investigations run.
CdtTrfTxInf/PmtId/UETRUnique end-to-end transaction reference — mandatoryThe globally unique tracking identifier for the transfer.
Tracking and matching of cover payments leans heavily on the UETR — it is the strongest link between a pacs.009 COV and its underlying pacs.008.
CdtTrfTxInf/IntrBkSttlmAmtInterbank settlement amount — mandatoryThe amount and currency settling between the institutions.
⚠ In the cover method, a cover amount that differs from the underlying pacs.008 settlement amount (beyond agreed charging) is a classic mismatch investigation.
CdtTrfTxInf/IntrBkSttlmDtInterbank settlement date — mandatoryThe value date of the transfer between the institutions.
Cover timing matters: if the cover settles later than the beneficiary bank expects, the customer credit may be withheld until the funds actually arrive.
CdtTrfTxInf/DbtrDebtor — mandatoryThe financial institution whose funds move. In pacs.009 this element identifies an institution (typically by BIC), not a customer — that is the structural difference from pacs.008.
If a customer appears anywhere in the business content, pacs.009 core is the wrong message — the payment belongs in pacs.008, possibly with a pacs.009 COV as cover.
CdtTrfTxInf/IntrmyAgt1Intermediary agent 1 — optionalThe first intermediary institution between the agents, when the transfer routes through more than one correspondent.
⚠ Routing data that names an intermediary with no account relationship to the next party pushes the transfer into manual repair.
CdtTrfTxInf/CdtrCreditor — mandatoryThe financial institution receiving the funds.
CdtTrfTxInf/UndrlygCstmrCdtTrfUnderlying customer credit transfer — conditionalA copy of key details of the underlying customer payment — its debtor, debtor agent, creditor agent, creditor, and remittance information — carried inside the cover so every bank moving the money can see whose payment it funds.
This element exists because cover payments historically hid the customer parties from the banks moving the funds. Its content must be copied faithfully from the underlying pacs.008 and left unchanged in transit.
⚠ Sending a plain pacs.009 core where the transfer actually funds a customer payment removes exactly the data sanctions screening needs — a payment-transparency failure, not a formatting nuance.