You are on page 1of 11

Format Payment Rule Download Document - User Guide

This guide describes the various aspects of the download document and how to read its content.

This document contains 3 sheets.


1. User Guide
2. XML Structure
3. Glossary

Index.html

This file within the zip file contains a index of all of the documents within. If you wish to use all functions of the files. You MUST export the
and open the index from that point. This will always for the the automatic opening of hyper-link files within the spreadsheets to be opened.
Within the zip file you will fine "FORMAT"_FormatRules_GOLD.xls, this file is the main file used, as it contains the format MIG (Left side) and

User Guide
This tab contains instructions to user on how to read the format rules.

Glossary:
This tab contains an alphabetical list of legal terms and acronyms the users are likely to come across in the file format, payment types and fo
/ meanings or Citibank interpretations of such terms.

The Format Payment Rule document


The Format Payment Rule document follows the naming convention of <Format>_FormatRules_GOLD.xls. This document contains the Forma
and PIUID
The document has the below structure.
Fig 1.

Columns A - K
These columns contain the format MIG information. All information contained here is reference to the standard used by the for
maximun number of characters that the standard allows within the element. However this does not mean that all the character
processing. You must refer to the FieldName and Properties columns to understand the processing requirements.

Column L,M,N (and each group of 3 columns if multiple Payment Types & Countries are used.
These group of 3 columns explain the individual elements used to execute the payment. If an element is not used, then it will b

FieldName and Properties


This shows the field name and the properties of the field:
Field Name:Format:MinLength:MaxLength:Status
1. Field Name: This is the data element name.
2. Format: Format specifies the correct type of data that field should contain. The various allowed formats are Numeric, Alphanumeric
3. Min Length: This denotes the minimum allowed length for the transaction field.
4. Max Length: This denotes the maximum allowed length for the transaction field.
5. Status: This denotes whether the data element is mandatory or optional or conditional

NOTES:
This denotes additional notes for data element. It can also contain a hyper-link reference to a file attached in the zip file. These hyper-lin
include in a single column. Please open and reference these links.

SplMappingNotes
This contains additional information at the format level, like exact values used vs the values used within Citi. It can also contain additional
informaiton that is possible to store within the cell.
Citi Information Xchange
Citi File Xchange Country Payment Rules Documentation

ISO 20022 XML STRUCTURE

Scope
The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It
is used to request movement of funds from the debtor account to a creditor.

Usage
The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions.
The CustomerCreditTransferInitiation message is used to exchange:
• One or more instances of a credit transfer initiation;
• Payment transactions that result in book transfers at the debtor agent or payments to another financial institution.
• Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque.

The message can be used in a direct or a relay scenario:


a) In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor.

b) In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It
agent.

The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example
large corporate

The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios.


The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s).

If it is agreed to include the payment information related to the debit side only once (i.e. Grouped mode), the PaymentInformation block wil

If it is agreed to repeat the payment information related to the debit side (i.e. Single mode), the PaymentInformation block must be present

The CustomerCreditTransferInitiation message also allows for a Mixed mode where the PaymentInformation block can be repeated and each
CreditTransferTransactionInformation block(s).
Single:
It indicates that for each occurrence of the Payment Information block, exactly one occurrence of the payment transaction block is present.
When grouping is set to Single, information for each individual instruction is included separately. This means the PaymentInformation block
TransactionInformation block.

Grouped:
It indicates that there is only one occurrence of the Payment Information block and several occurrences of the payment transaction block.
When grouping is set to Grouped, the PaymentInformation block will be present once and the Credit Transfer TransactionInformation block
Mixed:
It indicates that there are one or several occurrences of the Payment Information block where each of the occurrences might contain one or
When grouping is set to Mixed, the PaymentInformation block may be present once or may be repeated. Each sequence of the PaymentInfo
TransactionInformation block(s).

Outline
The CustomerCreditTransferInitiation message is composed of 3 building blocks:

A. Group Header
This building block is mandatory and present once. It contains elements such as MessageIdentification, CreationDateAndTime, Grouping ind

B. Payment Information
This building block is mandatory and repetitive. It contains, amongst others, elements related to the debit side of the transaction, such as D

C. CreditTransfer Transaction Information


This building block is mandatory and repetitive. It contains, amongst others, elements related to the credit side of the transaction, such as C

Rules
Grouping1Rule
If GroupHeader/Grouping is present and equals GRPD, then one and only one occurrence of PaymentInformation must be present.

Grouping2Rule
If GroupHeader/Grouping is present and equals SNGL, then each occurrence of PaymentInformation must contain one and only one occurre

General

Example: <?xml version="1.0" encoding="utf-8"?>


<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03" xmlns:xsi="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03">
The first line of XML is the XML declaration. It defines the XML version (example: 1.0) and the encoding used (example: utf-8).
The second line may specify the XML Namespace and XML Schema Instance Namespace before the start of root element.

NOTE
All files transmitted through any approved file based delivery channel shall be processed by Citibank in accordance with agreed security proc
of files and the Customer is fully responsible for file content and ensuring that files conform to any required formats.
Citi Information Xchange
Citi File Xchange Country Payment Rules Documentation

Term Comment
Customer This will always refer to a Citibank Customer who is using CFS to deliver Transactions.

The party to the Transaction whose account will be credited as the result of a successful Transaction. In a
Creditor
Payment this will be the Target or the Beneficiary.

The party to the Transaction whose account will be debited as the result of a successful Transaction. In a
Debtor
Payment this will be the Customer.

A Transaction where a Customer wishes to collect funds from an Account that the Target holds or has the
Direct Debit
necessary access rights, to an Account defined by the Customer.

A Transaction where a Customer wishes to transfer funds from an Account that the Customer holds or has
Payment
the necessary access rights, to an Account defined by the Target.

A business relation of the Customer to whom Transactions will be directed on behalf of the Customer. The
Target
Target will be the Customer's Counter Party in each successful Transaction.

A financial instrument that originates from a Customer and will be targeted at an entity with whom the
Transaction Customer has a business relationship. The Target entity does not require to have any relationship with
Citibank. Each transaction will either be a Payme

Originator The individual on institution that initiates the funds transfer. Also called the “By Order Party.”
Originator Bank The bank that is transmitting the payment on behalf of the originator
The Bank that is receiving the message instruction and the bank sending the message instruction (sent
Intermediary Bank
from the sending bank)
The bank that receives the funds intended for the recipient of the transfer. Also known as the payee bank,
Beneficiary Bank
the receiving bank, and the beneficiary institution.
Beneficiary The Individual or institution that receives the funds.
WorldLink Cheque A draft drawn on a bank to the order of a given person or organization or to the bearer.

WorldLink Remote Cheque A check issued by Citibank at the client’s direction.

Starting.with the origninator’s payment instructions, a series of transactions that are effected in order to
WorldLink Funds Transfer
make payments to a beneficiary. Also called electronic funds transfer, EFT or wire.

WorldLink Factory Draft A WorldLink cheque issued by a Citibank branch on behalf of their customer.
WorldLink Collections A conversion of foreign currency drafts to local currency payment
Electronic Data Interchange. The exchange of structured data messages to enable automated transactions
EDI
between application systems.

EDI For Administrations, Commerce and Transport. The international EDI standard messaging syntax
EDIFACT
under the responsibility of the UN, for trading transactions in all industries. Also known as UN-EDIFACT.

S.W.I.F.T. (or SWIFT) stands for Society for Worldwide Interbank Financial Telecommunication. It is a
SWIFT non-profit organization comprised of member financial institutions. It was established in 1973 by European
bankers who needed a more efficient and secure

Has a business relation with the Customer, and it is to him that the transactions will be directed on behalf
Third Party
of the Customer. The Third Party will be the Customer's Counterpart in each successful transaction.

Is a transaction where a Customer wishes to transfer funds to / from an Account that the Customer holds
from / to an account defined by the Third Party, or print a paper based payment instruction (checks) for
the Third Party to collect.Outgoing payments are transactions where the Citibank customer is debited and
a Third Party is credited. Incoming payments are transactions where a Third Party is debited and the
Payment Citibank customer is credited.
Citibank’s Destination system for payment instructions. It is the Backend system where the payments are
PayLink
processed and delivered to each correspondent country.
Transaction Reference: This reference number is used to individually identify each transaction within a file.
This code is used to indicate the transaction type. There can be different transaction types within each
Transaction Code country. By populating this the ACH (Automated Clearing House) in each country processes transactions in
the instructed format i.e. salary payments, pension payments etc.
Instruction Currency Code This indicates the currency in which the customer account is debited.
Transaction Currency Code This indicates the currency in which the transaction is paid.
Transaction Amount The amount to be paid.
Citibank Transaction Branch This field contains Citibank branch at which the customer's account is to be debited.
Ordering Customer Name and AddreThe name and address of the company issuing payments or collections.
Target Name and Address The name and address of the beneficiary or the debtor.
Ordering Customer Account This is the account number being used to debit funds from (in order to make payments) or credit funds to
Number (in order to make collections).
Transaction Method Code denoting the method by which the transaction will be routed.
Target Bank Details The name and other details of the bank of the beneficiary or the debtor.
Intermediary Bank Details The name and other details of the Intermediary Bank.
Transaction Details Additional information, in some cases this is passed to the beneficiary.
Target Account Number The bank account number of the beneficiary or the debtor.
Charge Code This indicates where the Bank charges are to be taken from.
Bank to Bank Details Details to be passed to beneficiary or beneficiary’s bank.
This will usually be the date that both the beneficiary account is credited and the customer account is
Value Date/ Transaction Due Date debited.

You might also like