Skip to main content

Barclays - Claims Manager - Inter Company Matching - ICM

Pitpit Mohammed Dadapeer
Updated

1. Inter Company Matching - ICM

1.   Intercompany match rules set up (MER-8451, MER-8450)

Change the matching rules in the Matching utilities tree to include the rule on which Claims the Client wants to be considered as Intercompany (ICM).

Static Data -> System Options-> Matching Strategies -> Matching Utilities

Click AMEND button

Click OK, once the matching strategies are created. Then Click 'OK'

Sample for Barclay to understand how the data values moves through the tree and the values generated:

Intercompany match rule will apply the below claims

  1. Interco = IN
  2. Entity = BCSL,BCIL,BCSI and BBPLC
  3. Trade type=Open Stock Borrow OR Open Stock Loan.

Claims with above values, are needed to be handled as ICM. Also, Matching has to be done between the claims with below Entity-A/c no combination

BCSL - 102012 with BCSI / BCIL– 699999
BCSL – 102017 with BBPLC – 802000
BCSL – 109022 with BBPLC – 802020
BCSL – 103823 with BBPLC – 899319

ie, for BCSL - 102012 with BCSI – 699999, the values of Matched by and SEC has to be populated as below. 

Matched by                                                                           SCE
Intercompany=IBL-IBCSL-102012 Intercompany=IBL-IBCSI-699999
Intercompany=IBL-IBCSI-699999 Intercompany=IBL-IBCSL-102012

1.   Intercompany match strategy set up (MER-8450, MER-8451)

Change the matching strategy tree too include matching strategies rule the Client wants.

Barclays requirement - Matching fields are CCY, Security Name, Pay Date. Match on Nominal, Cash

How to do Static Data -> System Options-> Matching Strategies -> GLOBALMATCH.

1.   Changes while DIVIDEND claims import by DIVIDEND Service (MER-9086).

Dividend Service has to do the below activities after import. After running DIVIDEND service , the claims will be available in CM, with the Matched By and CLE populated correctly.

  1. Import Dividend Claims
  2. For ICM claims, Populated Matched by and CLE as per Matching Rules.
  3. Add a new stage in DIVIDEND service to set up a Nudge to invoke Matching Service. Details are below.
  4. Add a new stage in DIVIDEND service, from Daily import.
  5. Update the service custom to have a custom function.
  6. This custom function should add a nudge ‘MNL_TRIGGER_ICM'
  7. This will be checked by MSGS/MATCH ( whichever service doing ICM) based on its value the ICM will be triggered.

Note: Make sure the Matched By, CLE, are having same field width. For Barclays it was different.

1.   Set up System parameters for invoking standard code to do ICM (MER-8452)

    1. Att.[ICM_MATFLDS] +AMOUNT|+NOMINAL
    2. Att.[YLE_MATDBFLDS] CCY|claimdept|_VALUEDATE|SECURITYNAME|AMOUNT|NOMINAL
    3. Att.[CLE_MATDBFLDS] CCY|claimdept|_VALUEDATE|SECURITYNAME|AMOUNT|NOMINAL
    4. Att.[ICM_PRQ_MATFLDS] CCY|claimdept|_VALUEDATE|SECURITYNAME
    5. Att.[SCSVR_MODE] - ICM - Runing SetClaim Server in Intercompany mode
    6. Att.[SCSVR_SERVICE_IDENTIFIER] - MSGS – (Different ICM stages will get attached to this service, during run time)
    7. Att[DEFAULT_MATCH_START]  =GLOBALMATCH
    8. Att.[ICM_PRQ_MATFLDS] - Prerequisite matching fields
    9. Att.[MATCHYLE_KEY_PRFX – C1
    10. Att.[ICM_EOD_STARTHOUR] - 

2.   Add the MATCHYLE in Field Equivalence

3.   Add the file Local_preprocess_matching.txt in local implementation script

4.   Move Intercompany Match processing to a new service MATCH (MER-9069)

  1. A new service is created so that it can be run independently and MSG service's load is readuced.
  2. With a new Service,  set up required sys params for the service.
  3. While creating the Release Instruction, include steps to Register the Services.

5.   How to setup data claims data and get it import into CM (MER-9102, MER-9117, MER-9190)

1.   Different Matching status

  1.  
    1. MAT
    2. UNM
    3. PRQ
    4. UNMM
    5. Initial status AWM not required

Sample data preparation: M:\REGRESSIONTEST\BARCAP\DIVCPN\DIVIDEND\20210610\InterCompany Match -Import data preparation Flow.xlsx

 

·         How to create sample data for ICM

  1. open the attached excel. (or take the same excel from M:\REGRESSIONTEST\BARCAP\DIVCPN\DIVIDEND\20210610\InterCompany Match -Import data preparation Flow.xlsx
  2. Copy any of the available group of records in the excel.
  3. Value to be confirmed or changed
    1. Column A - PAY/REC
    2. Column B - Value for uniqueref
    3. Column C - Security Name (same for a group) -> Prequisite
    4. Column I - Pay Date (same for a group) -> Prequisite
    5. Column M - Account Number ( it is related to Entity in Column V) – Prerequisite
    6. Column o - InterCo (should be IN)
    7. Column P - Nominal (same for a group) -> Matching Condition
    8. Column Q - Cash  (same for a group but - for pay record) -> Matching Condition
    9. Column R - CCY (same for a group) -> Prequisite
    10. Column T - current cash base (same for a group) 
    11. Column U- Trade Type (Open Stock Borrow / Open Stock Loan) 
    12. Column V - Entity (it is related to Account no in Column M)
    13. Save the file and Close it
      1. Create the import file

Sample data arranged in .tab file for import. Put this tab file in a folder names <COBDATE> in regression folder path. Here 20210610.

  1. open the attached excel “InterCompany Match -Import data preparation Flow.xlsx”. (or take the same excel from M:\REGRESSIONTEST\BARCAP\DIVCPN\DIVIDEND\20210610\InterCompany Match -Import data preparation Flow.xlsx
  2. Copy the records to the import file <file name>_<COBDATE>.tab (eg M:\REGRESSIONTEST\BARCAP\DIVCPN\DIVIDEND\20210610\claim_manager_exp_20210610.tab
  3. Save and put that file (.tab) in the folder named <COBDATE> in regression folder. Here the folder name should be “20210610”
      1. Reset data in CM/Delete the existing ICM claims from Claims table.

Delete all the existing sample data from UAT db. Sample query below.

  1. Query to clean the claims record

//Find all the ICM records

select * from mrt_bcclaims  where mrtacno in ('102012','699999','102017','802000','109022','802020','103823','899319')    --- AND mrt_valuedate not like '20210622'  –- include this if there is a pay_date filter needed

//Delete all the ICM records

delete from mrt_bcclaims where mrtacno in ('102012','699999','102017','802000','109022','802020','103823','899319')

-- AND mrt_valuedate not like '20210622' –- include this if there is a pay_date filter needed
  1. Query to clean the updpnd (Match Service tabkes data from this table to work)
    1. delete from mrt_bcclaimsupdpnd where MRT_CARDKEY like 'ICM%'
  2. Query to clean up Nudge (Match will start if there is a nudge entry added by DIVIDEND)
    1. delete from MRT_bcclaimsNUDGE WHERE (MRT_KEY LIKE 'MNL_TRIGGER_ICM%')
  3. Commit if you have run any of the above queries.
      1. Run the IMPORT in CM to populate Data in CM

In Barclays CM,

  • go to SM -> select DIVIDEND service -> Reset COB date to <COBDATE> . Here for the above same data prepared the COBDATE = 20210610
  • Execute DIVIDEND Service
  • Refresh DIVIDEND worksheet for Data.
  • Use Matched By =IBL* Group by Pay Date, Match ID.
  • Filter for 102012,699999,102017,802000,109022,802020,103823,899319
  • Verify the Data
      1. Run MATCH service (MER-9069)
  • select MATCH service -> Reset COB date to <COBDATE> . Here for the above same data prepared the COBDATE = 20210610
  • Execute MATCH Service
  • In first cycle, Match service will identity the MatchBy and CLE combinations to be matched
  • In later cycles, it will do matching, taking on MatchBy-CLE combination at a time.
  • Refresh DIVIDEND worksheet.
      1. Verify data
  • Go to Website - login as a user
  • go to DIVIDEND Worksheet
  • filter for A/c = 102012,699999,102017,802000,109022,802020,103823,899319
  • fitler for Matched By = IBL*
  • Group By paydate (Also Asc) & Match ID
  • Layout Select ‘uniqueref ‘, ‘Security Name’, ‘Match ID’, ‘Match By’.
  • In the Dividend Worksheet, the claims imported should be
    • open,
    • Match Status Should be same as the clue provided by the Security Name
    • Also, the grouping can be identified with the format of values for uniqueref.

Note : Refer EPIC 

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Related to

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk