2.11 FX Confirmation Message Intraday Batch

This topic describes the systematic instruction to define FX Confirmation Message Intraday Batch.

The system runs an Intraday batch FXCONFRM for FX Confirmation message auto-matching. The upload activity in the incoming message browser will parse the message and upload it into an internal upload table, thus confirming that the format is correct. If this step is successful, the incoming browser will show the message as processed else the message marked for repair with an error code, which indicates the format error.

The auto-confirmation batch uses the data in the incoming message and executes the matching based on Confirmation rule set up. This batch will use the rules in the sequence defined and attempt to match the messages to a contract for fully/partially matched cases.

The matching of the incoming confirmation message details with the deal details is done based on the matching required fields maintained for the confirmation rule. The processing is done sequentially based on the rule codes maintained for the confirmation class for FX module.

During the auto-match processing, if the details of an incoming message match with a single existing deal in the system based on a Full Match rule, then the confirmation is marked for the deal by triggering CONF event. The message marks as Completely Matched.

If multiple contracts are matched with a single message while processing a Full Match Rule, then the message will be marked as Partially Matched. Even if the message matches while processing according to a Rule code not checked for Full Match, then the message will be marked as Partially Matched.

Partially matched deals should be manually matched from the 'Manual Matching' screen.

The system will match the Party detail fields based on BIC codes. The list of contracts against a message in case of full/partial matches will be stored and subsequently can be viewed from the 'Manual Matching of Confirmation Messages' screen

While doing an auto-matching, the system will match an incoming message with details of the latest outgoing confirmation message details of a contract.

The following fields of the FX deals match against the message field values:

Table 2-11 FX fields and the message values

MT 300 FX Confirmation Message field	FX Contract field
82A	Counterparty BIC
30T	Booking Date
22A	Events
30V	Value date
33B	Bought Currency
33B	Bought Amount
32B	Sold Currency
32B	Sold Amount
36	Deal rate
57a Settlement for Bought Leg	Settlement for Sold Leg
57a Settlement for Sold Leg	Settlement for Bought Leg
57a Account With Institution for Bought Leg	Account With Institution for Sold Leg
57a Account With Institution for Sold Leg	57a Account With Institution for BoughtLeg
58a Beneficiary Institution Pay Leg	Branch BIC Code
22C	Common Reference
56A Intermediary Bought Leg	Intermediary Sold Leg
56A Intermediary Sold Leg	Intermediary Bought Leg