5.1.1 Incoming Message Upload

The Incoming Message Upload refers to the process of receiving and processing incoming financial transaction messages automatically, without manual intervention.

The Incoming ISO messages with Business Application Header (BAH) are received via Electronic Messaging Service (EMS).
  1. Once the Incoming message is received, the message is logged in the incoming message tables.
  2. The header and payload are extracted from the incoming message. Based on the message version specified in the header, the system performs format validations according to the schema details stored in the File Parameter Detailed (PMDFLPRM) maintenance.
    Branch/Host Derivation:
    • Value received in <AppHdr> <To> <BICFI> field of TARGET2 business header is extracted.
    • Based on the BICFI the branch code is derived. Host Code is derived as the Host Code associated with the Branch Code.
  3. The transaction booking branch in Generic Wires ISO Inbound Booking Branch Derivation Detailed (PSDIBRDV) is resolved first based on the To BIC value received in the BAH of the Incoming SWIFT CBPRPlus/TARGET2 ISO messages.
    • To BIC is checked against the branch level SWIFT Address maintenance. The matched Branch code is considered as transaction booking branch.
    • If there are multiple branches having the same BIC, then the 1st matched branch is considered.
  4. The host code of the booking branch is picked up from the branch derived.

    The Media is resolved.

    • The Business Service <BizSvc> value of the Business Application Header (BAH) is checked.
    • If this tag is present and if the value contains cbprplus, then the media is considered as FINPLUS. Otherwise, the media is considered as RTGSMX.
  5. For the media and host code, in the newly introduced Generic Wires ISO Incoming Message Branch Derivation maintenance is referred.
  6. To BIC value of the BAH is checked against the new Generic Wires ISO Incoming Messages Branch Derivation for the Host code or Media or BIC combination.
    • If a record is found, then the Branch code maintained against that BIC is considered as transaction booking branch.
    • If there is no record found, then the default branch code is considered as booking branch.
  7. The branch derived in the initial step is retained as booking branch, if there no maintenance done in the Generic Wires ISO Incoming Message Branch Derivation maintenance for the media and host code combination.
  8. In case of incoming payments results in a pass-through message, Under Pass through Payment Information tab, Pass through Payment field is updated as Yes, The Clearing System Reference displays the value as received in incoming message on the below outgoing pacs.008/pacs.009 CBPRPlus/TARGET2 view screens:

Table 5-1 Payment Type

Sr No Payment Type Network Description
1 Pacs.008 CBPRPlus PSDOCBVW
2 Pacs.009 CBPRPlus PSDOCNVW
3 Pacs.008 TARGET2 PSDOT2CV
4 Pacs.009 TARGET2 PSDORBTV

Parent topic: Common Straight Through Processing