Specifying the Properties of the Match Process

Match process properties include an ID, name, and data sources.

See About Defining Match Process Properties.

To specify the properties for a new match process:

  1. Navigate to the Properties tab of the match process. See Defining the Match Process.
  2. Enter an ID for the match process and Name.
  3. Select the Number of Data Sources.
  4. Select the Source System data sources and the Sub System data sources.
  5. In Set Adjustment Accounting Date, select the option that determines the period to which the adjustment must be accounted:
    • Match Date

      The date on which the adjustment is created is set as the Adjustment Accounting Date. For example, transactions have accounting dates of 27th June and 30th June, and the adjustment is created on 3 July. The Adjustment Accounting Date is set to 3rd July.

      This is the recommended option and also the default setting. This setting ensures that users cannot create an adjustment with an accounting date related to a closed GL period. Use this option if your organization wants adjustments to be recognised at the time the reconciliation is done and if adjustments must be recorded in the current open period.

    • Latest Accounting Date in the Match Group

      The latest accounting date among the transactions included in the match group is set as the Adjustment Accounting Date. For example, match group contains a source transaction dated 26th June and subsystem transactions dated 30th June and 2nd July. This option sets the Adjustment Accounting Date to 2nd July.

      Use this option when the adjustment should be accounted for at the completion of a multi-step or cross-period transaction. It is also useful when reverse adjustments are created because the reverse adjustment will retain the accounting date of the original adjustment. Users should not match transactions that only have old accounting dates in a match group that is related to closed GL periods.

    • Earliest Accounting Date in the Match Group

      The latest accounting date among the transactions included in the match group is set as the Adjustment Accounting Date. For example, the GL posts a cash balance of $1000 on 31st May and the bank deposit posts $990 on 1st June. This option posts the adjustment to May period.

      Use this option when the adjustment must be reflected in the period of the original transaction during period-end reconciliation. Users must always match only the most recent accounting dates for the entire match group from a GL period that is currently open.

  6. (Optional) Select Allow Edit to enable users to set the adjustment accounting date to a user-defined value. This is applicable when creating manual matches and adjustments.
  7. Click Save.
  8. The default attribute mapping displays the attributes from your defined data sources and shows the relationship between attributes in Source System and Subsystem data sources. See About Default Attribute Mappings.
  9. Use the + (Plus sign) under Default Attribute Mapping to add a new attribute mapping.

    The New Attribute Map dialog is displayed. It contains the attributes from your defined data sources. Use this dialog to map the Source System attributes to the Sub System attributes and define match process limits.
    1. Select the attributes from the source system and the sub system that must be mapped.
    2. In the Default Tolerance Limit section, specify the tolerance limits for matching the source system and sub system attributes.

      See About Setting Tolerance Levels.

    3. Click Save to save the attribute map definition.

    See Default Attribute Mapping Example.

  10. Use the + (Plus sign) under Bucket Attribute Mapping to configure a bucket attribute mapping. See Configuring Buckets in Administering Account Reconciliation.

    When a currency is configured for the data source, a bucket attribute mapping is automatically created for the currency attribute. In this case, the maximum number of bucket attribute mappings that you can configure is 7. If a currency is not configured, the maximum number of bucket attribute mappings that you can configure is 8.