Barclays- Claims Manager - Swift Message

Sample Payment Message from Barclays

{1:F01BARCUS33AXXX0000000000}{2:I202SCBLJPJTXXXXN}{3:{108:2021071509101644}}{4:
:20:2021071509101644           // payadvice key
:21:adminAl1                          // user who initiated payment
:32A:210715JPY500,               // JPY is CCY and  500 amount
:53A:/02175541110
BARCUS33
:57A:JP409698900
JP798657
:58A:680685
JPYECGCT
:72:/BNF/ DIV ISIN RU0009029540,FR00000  // DIV mean claim type. For ICM, this section have IsICM =Y so as to identify it as Intercompany payment and ISIN will not be included.https://jira.cognizantproducts.com/browse/MER-9724
-}

ACK message

{1:F21BARCGB33AXXX0000000000}{4:{177:1110281218}{451:"&ack&"}{405:T30012}{108:"&pk&"}}{1:F01ZYAFGB30XXXX3026311635}{2:I202ZYAFGB30XXXXN}{5:{CHK:308FFD99259A}{TNG:}}

SETTLEMENT MESSAGE

If a payment have 3 claims, then there will be 3 settlement messages attached with this payment. 

1. Payadv table - 1 record per payment. payadvice key is used as the key for all the payment
2. Journal table - 1 record for payment and n settlement records, where n is number of claims considered in the payment.

Where to find these messages in CM

You can get the above message content,

1. either from Audit Trail in UI or from database,
2. refer table MRT_....CLAIMSJOURNAL and MRT_....CLAIMSPAYADV
3. A flow will be added in BRIDGE_TABLEs too

SWIFT MESSAGES

Below information are learned from Official SWIFT message website, while trying to understand the Barlcays Payment message

Main part of a swift message are 

{1:} Basic Header Block

{2:} Application Header Block

{3:} User Header Block

{4:} Text Block

{5:} Trailer Block

SWFIT MESSAGE FORMAT  Format and details

Details:

{1: – Identifies the Block – i.e. the Basic Header Block
F – Indicates the Application Id – in this case, FIN
01 – Indicates the Service Id
01 = FIN
21 = Acknowledgement (ACK) or Negative Acknowledgement (NAK)
YOURCODEZABC – The Logical Terminal Address – which is typically your BIC 8 (YOURCODE) + Logical Terminal Code (Z) + Branch Code
I know YOURCODE is an invalid BIC – but lets go with it…
1234 – Session Number – Ask SWIFT or your Service Bureau how they want you to populate this – this is not very interesting for corporates
567890 – Sequence Number – As above, ask your SWIFT people how they want this populated
} – Indicated the end of the Basic Header Block

{2: – Indicates the start of the Application Header block
I – Informs you that you’re in Input mode (i.e. the Sender), O would indicate Output mode – so you would be the recipient of the message
101 – Message type – in this case, an MT101
YOURBANKXJKL – The recipients BIC, consisting of their BIC (YOURBANK) + Recipients Logical Terminal Code (X) + Recipients Branch Code (JKL)
U – Message Priority:
U – Urgent
N – Normal
S – System
3 – Delivery Monitoring – Ask your SWIFT contacts or Service Bureau how you should populate this, if at all – Optional
003 – Non-delivery notification period – again, ask your SWIFT contacts how to populate this, if at all – Optional
} – Indicated the end of the Application Header Block

The User Header Block will always starts {3:

And will look something like: {3:{113:SEPA}{108:ILOVESEPA}} where:

{3: – Indicates the start of the User Header Block
{113:SEPA} This is an optional 4 alphanumeric bank priority code
{108:ILOVESEPA} – Indicates the Message User Reference (MUR) value, which can be up to 16 characters, and will be returned in the ACK
} – Indicated the end of the User Header Block