Credit Transfer Transaction, the single payment

The Credit Transfer Transaction Information block, often shortened to CdtTrfTxInf, is the third level in a pacs zero zero eight, and it describes a single payment to a single creditor. It includes the Payment Identification, which contains the Instruction Identification, the End to End Identification, and the Transaction Identification. The Instruction Identification is a reference assigned by the initiating party to identify the instruction, the End to End Identification is a reference that travels end to end from debtor to creditor and is used for reconciliation, and the Transaction Identification is a reference assigned by the debtor agent. The End to End Identification is particularly important, because it is the reference the creditor uses to match the payment to an invoice. The transaction block also includes the Amount, which is the Instructed Amount with its currency, and the Equivalent Amount if the payment involves a currency conversion. It includes the Charge Bearer if it differs at transaction level, the Creditor Agent, the Creditor, and the Creditor Account, which together identify who is to receive the payment and where it should be credited. It also includes the Purpose, which is a code that describes the reason for the payment, such as SUPP for supplier payment or SALA for salary, and the Remittance Information, which can be structured or unstructured and which tells the creditor what the payment is for. The transaction block is where most payment failures occur, because it contains the creditor details and the amount that must be validated. A wrong creditor account number, a missing creditor name, or an amount that does not match the Payment Information total can all cause rejection. An analyst must be able to read a transaction block, identify each element, and explain its business meaning. You should also understand the difference between the Instruction Identification, which is for the initiating party, and the End to End Identification, which is for the debtor and creditor, because confusing those two references is a common cause of reconciliation breaks. Take a worked example with real numbers. A Credit Transfer Transaction Information block carries payment identification with instruction identifier INSTR-2026-1187, end to end identifier INV-2026-1187 and transaction identifier TX-2026-1187-001. The instructed amount is EUR 25,000 and the equivalent amount is USD 27,250, because the payment is instructed in euros and converted to US dollars at a rate of 1.09. The charge bearer is SHAR, so the debtor and the creditor share the charges. The creditor agent is Bank B in Berlin, identified by its BIC, and the creditor is Rhine Metals GmbH with account DE89370400440532013000. The purpose code is SUPP for supplier payment, and the remittance information is unstructured with the text Invoice INV-2026-1187. Every field in this block is about one payment, and no field in this block applies to any other payment in the message. Failure and recovery: a transaction with an instructed amount that has three decimal places for EUR is rejected, because EUR allows only two decimal places, and the sender must correct the amount and resend. A transaction with a creditor account that is closed is returned by the creditor agent as a pacs.004 with reason code AC04, and the debtor is refunded. A transaction with a missing mandatory field, for example no creditor account, is rejected before it is processed, and the sender must add the field and resend with a new MsgId. A transaction with an end to end identifier that duplicates an earlier payment is flagged as a possible duplicate, and the operations team must check whether it is a genuine duplicate or a legitimate repeat payment, for example a monthly invoice with the same reference. A transaction with a purpose code that the scheme does not recognise is rejected with a pacs.002 and reason code AG01. The recovery depends on the failure: a format error is fixed and resent, a closed account is returned, and a duplicate is investigated before any action is taken. For a business analyst, product owner or subject matter expert, the test is to read a Credit Transfer Transaction Information block and to explain every field, its source, and what happens when it is wrong. The payment identification links the payment to the instruction and to the invoice, and the requirement must state which identifier is used for reconciliation. The instructed amount and the equivalent amount must both be present when there is a currency conversion, and the requirement must state the exchange rate source and the rate applied. The purpose code drives reporting and screening, and the requirement must state which codes are allowed for the product. Source: ISO 20022 pacs.008.001.08, Credit Transfer Transaction Information. Last reviewed 7 November 2026.