Anchor
_Toc439930508 _Toc439930508

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:

1. From the ETL Center window, click Data in the left navigation.
2. Click Interfaces and Interfaces.
3. Double click Add Interfaces Detail.
   You see the Add source Interface panel.
4. Complete the options on the panel and click Submit.

The following table list examples of data sources used with cash activity reconciliation.

Anchor
_Toc439930509 _Toc439930509

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:

1. 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.
2. Right click New Rule.
   You see the Add New Rule dialog box.
3. In the Rule Name text box, enter the name of the new rule.
4. Click the Module drop down and select Cash as the type of reconciliation.
5. Specify whether you want the rule inactive or available for use.
   Options include:
   –  Is Active (Default). The rule is available for use.
6. Click OK to save the rule.
   You see the Assignment Rules window with the refreshed list of rules.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. When complete, click OK.

Anchor
_Toc439930510 _Toc439930510

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.

Define Entity Bank Relationships (Local only)

You must define entity bank relationships when Custodian cash activity records contain internal custodian account numbers requiring translation to the Eagle Accounting entity id values. For a given custodian bank code, the Entity Bank Relationship feature provides a unique mapping for a custodian account to an Eagle STAR entity id. The entity bank relationship mappings are required when using the local MSGCENTER tables when loaded by custodian message streams.

To define an Entity Bank Relationship:

1. From the Accounting Center window, click Accounts and then click Account Setup and Maintenance and Entity-Custodian Relationships.
2. Double click Add Entity Bank Relationship.
   You see the Add Entity Bank Relationships panel.
3. Complete the options on the panel.

4. Click Submit.

   Note
   The Code Values table stores custodian bank codes using code category CUSTODIAN_BANK.

Configure the MSGSERVICE.INI Parameters

The MSGSERVICE.INI configuration file sets key variables used by the Cash Recon console and associated message streams. The configuration file is located in the Eagle STAR Config Files/Configuration Files/msgcenter webserver folder and the Cash Recon parameters are located in the [CASHRECON] section of the file.

To view/edit the file MSGSERVICE.INI configuration file:

1. From the Accounting Center window, click Reconciliation.
2. Click Admin and Administration.
3. Double clickEngine Manager.
   You see the Engine Manager application window.
4. In the left pane, navigate to the folder path and filename with the MSGSERVICE.INI configuration file.
5. Open the file for editing.
6. Complete the options in the [CASHRECON] section of the configuration file.
7. Click Save.
   You must exit and then re-open the Cash Recon console to acquire the new configuration options.

[CASHRECON] Section Options

The following CASHRECON options configure the behavior of the Cash Recon console:

• DataSetOption. Specifies the mode of comparison for Cash reconciliation. Refer to the Decide on the Mode of Comparison section for additional information.
• LoadSTARActivityStream. Specifies the stream to load pre-settled activity.
• LoadCUSTActivityStream. Specifies the stream to load custodian CSV files.
• LoadSettledActivityStream. Specifies the stream to load settled activity.
• MatchStream. Specifies the stream to match cash records from two sources on local tables in the MSGCENTER database.
• ResultsStream. Specifies the stream to post exceptions and establish downstream messages to adjust settled cash.
• AddCashStream. Specifies the stream to add cash transactions equal to the custodian cash transaction amount.
• RecPayStream. Specifies the stream to load pre-settled cash activity.
• CashTranStream. Specifies the stream to load settled cash activity.
• MatchStreamWH. Specifies the stream to match cash records from two sources on the CASH_ACTIVITY tables in the CASH database or one source and the ESTAR database traded/settled cash activity tables.