Define Data Sources
You must define the data sources to use before loading cash activity records for reconciliation. The data sources identify the origin of cash activity for any portfolio you want to reconcile. When cash reconciliation compares two sets of competing records, the cash match process filters records by data source on the left side and right side of the mathematical comparison.
To define data sources to use during Cash Activity reconciliation:
- From the ETL Center window, click Data in the left navigation.
- Click Interfaces and Interfaces.
- Double click Add Interfaces Detail.
You see the Add source Interface panel. - Complete the options on the panel and click Submit.
You can group a set of sources using the code value tables for a specific Code Category, such as CASHREC_SRCS. A set of custodians. such as CUSTODY1 and CUSTODY2, can be defined for use as a unified set of sources by adding the sources as code values under the category, along with a name to use as the name of the list. The set of sources is called a named list of sources and the data associated to the set of sources can be used as one side of the match. On the code values record serving as the name of the list, you must set the Code Value Description to L.
The following table list examples of data sources used with cash activity reconciliation.
Cash Activity Data Location | Source Code | Description |
|---|---|---|
Eagle data warehouse | CUSTODY1 | For warehouse to warehouse matching |
ESTAR Traded Cash Activity to Eagle data warehouse | ESTAR | For ESTAR to warehouse matching |
ESTAR Settled Cash Activity to Eagle data warehouse | ESTAR | For ESTAR to warehouse matching |
Custodian files | CUSTODY1 | For local to local work table matching |
Define Exception Assignment Rules
You can create exception assignment rules to simplify the workflow to automatically identify cash breaks based on entity or security attributes and then take the appropriate actions, such as, apply comments, categorize explained differences, and assign unexplained differences to team members for resolution. Once created, you can execute these rules from the Cash Recon console or execute in a message stream following the Run Match Now stream.
To define an exception assignment rule:
- From the Cash Recon console, click Assignment Rules.
You see the Assignment Rules pane with the current list of assignment rules and the Assignment Rule Details pane with the list of details for any selected rule. - Right click New Rule.
You see the Add New Rule dialog box. - In the Rule Name text box, enter the name of the new rule.
- Click the Module drop down and select Cash as the type of reconciliation.
- Specify whether you want the rule inactive or available for use.
Options include:
– Is Active (Default). The rule is available for use. - Click OK to save the rule.
You see the Assignment Rules window with the refreshed list of rules. - Select the rule from the list and in the Assignment Rule Details pane right click Add Rule Details.
You see the Add Rule Details dialog box. - Specify whether you want the rule applied conditionally or applied to all records.
Options include:
– Always (Default). Indicates that you want all records processed for assignment.
– Conditional. Indicates that you want to filter the records processed for assignment. When you select this option, you must click the Data Field drop down and select the database and column values used to qualify the selection of exceptions, including database filter logic using Boolean operators. You can select from the CASH, SECURITY, and RULES database tables. - Specify whether you want the rule to directly assign exceptions or evaluate exceptions for explained and unexplained differences before assignment.
Options include:
– Single Assignment (Default). Indicates that you want all breaks on a specific field assigned a specific break category, break sub category, and user/user group for handling. You can specify an expiration date for single assignments.
– Dependency Rule. Indicates that you want to break on a specific field after the evaluation of breaks on underlying fields. When you evaluate the underlying fields, the rule assigns each field a break category and subcategory, including a calculation field with the unexplained amount, if any, after considering the overall set of field differences. - For a single assignment election, click the Master Field drop down, select the field to inspect for breaks, and then assign a break category, break sub category, and user/user group for handling.
- For the dependency rule election, click the plus sign to add a record to specify an underlying field for evaluation, commenting, and assignment. On each record, you must click the Field Name drop down and select an underlying field to evaluate and then specify the break category, break sub category, user/user group assigned for handling, and a free form comment. You can specify an expiration date for each field supporting the dependency rule.
- Repeat Step 11 for additional underlying fields, as required to complete the dependency rule details.
NOTE: The UNKNOWN record exists as a permanent underlying field and displays the net unexplained difference, if any, that you can assign for research and resolution. - When complete, click OK.
Define the Mapping of Transaction Types (Local only)
You must map custodian transaction type to the Eagle STAR values, for proper comparison to the ESTAR and CASH databases. The transaction type mappings are only required when using the local MSGCENTER tables that are loaded by custodian message streams.
Fields on the incoming message you must establish include:
- TXN_ID (tag 1257)
- CASH_EVENT_TYPE (tag 53)
- LONG_SHORT (tag 15)
- CASH_CATEGORY (tag 62)
You must map the custodian transaction types using default mappings in the following figure.
Add Comment