Filtering and Grouping Transactions in AutoMatch Rules

AutoMatch rules in Transaction Matching support grouping and filtering the transactions in the rules, which will be used by the match engine to match transactions. A tab called Filters and Groups displays on the Edit Rule dialog for a single data source and for two data sources.

Filtering Transactions in AutoMatch Rules

Automatch will include only the transactions that is specified by the filter while executing the rule. Other transactions are excluded for the matching.

Note the following about filtering transactions:

  • It is optional to define filtering for each rule.

  • Filters are defined for each data source.

  • Only one filter per data source can be selected for each rule.

All the different types of rules will allow filtering

Two Source Match Process - in a two source match process, one filter can be selected for source system and one for subsystem

Single Source Match Process - in a one source match process, the filter selected for subsystem can be the same as the one selected for source system.

Grouping Transactions for Auto Matching

  • It is optional to define grouping for filtering for a rule.

  • You can choose one ore more attributes for grouping.

  • Grouping is allowed for "Many" types rules only: One to Many, Many to One, or Many to Many.

One to Many

Grouping can be done only for Sub System data source:

  • In a two source match process, only the Sub System data source and its attributes display.

  • In a single source match process, only the data source and its attributes display.

Many to One

Grouping can be done only for Source System data source:

  • In a two source match process, only the Source System data source and its attributes display.

  • In a single source match process, only the data source and its attributes display.

Many to Many

Grouping can be done for both Source System and Sub System data source

  • In a two source match process, both the Source System data source and its attributes and Sub System data source and its attributes display.

  • In a single source match process, the data source and its attributes display.

Attributes

The following conditions apply to grouping attributes:
  • You can choose one ore more attributes for grouping.

  • Grouping attributes can be in any order.

  • Grouping attributes can include calculated attributes.

  • The balancing attribute is not allowed to be a grouping attribute.

  • For Many to Many rules, all attributes defined in the rule conditions must be part of the Group By query, except for the Balancing Attribute.

Rule Conditions

If grouping is enabled for a Many type rule, only the attributes chosen for grouping are considered during rule creation. The rule conditions filter the attributes and show only the attributes selected for grouping in the drop down. It is optional to create the rule conditions using these attributes.

How Auto Matching is Performed Using Groups

The grouped transactions behave as single transaction. Grouping can be applied only on the Many side. Once the grouping is applied on the Many side in a One to Many or Many to One rule, the rule behaves as if it is a One to One rule on the Many side as well, so that grouped transactions will be considered as single transaction.

In a Many to Many rule, grouping can be applied on both sides or only on one side. When grouping is applied on both sides, it behaves as if it is a One to One rule with grouped transactions behaving as a single transaction. However, when the grouping is applied only on one side, it behaves as if it is a One to Many or Many to One rule depending on the source the grouping is applied to.

Example

To help you understand how the matching is done, let's look at this example of Bank Transactions and GL Transactions:

In the below One to Many Rule example, GL Transactions are grouped by: Transaction (Tran) Date, Payment Type (PymtType), and Batch ID. The order of the attributes does not have any effect on matching.

Rule condition: Credit Amt Matches Exactly Total Amt

Balancing attributes: Credit Amt in BANK and Total Amt in GL

Table 9-7 Example of Bank Transactions

Number As-Of Date Bank ID Acct No Credit Amt

1

9/17/2018

121000248

4129965265

1000

2

9/19/2018

121000248

4129965265

400

Table 9-8 Example of GL Transactions

Number Tran Date PymtType Batch ID Total Amt

1

9/18/2018

Bank Draft

CS18091802

200

2

9/18/2018

Bank Draft

CS18091802

200

3

9/18/2018

Bank Draft

CS18091802

600

4

9/20/2018

Bank Draft

CS18091802

200

5

9/20/2018

Bank Draft

CS18091802

200

This rule will create two matches.

Table 9-9 Match 1 - Example of Matching Bank Transactions

Number As-Of Date Bank ID Acct No Credit Amt Match Set #

1

9/17/2018

121000248

4129965265

1000

1

Table 9-10 Match 1 - Example of Matching GL Transactions

Number Tran Date PymtType Batch ID Total Amt Match Set #

1

9/18/2018

Bank Draft

CS18091802

200

1

2

9/18/2018

Bank Draft

CS18091802

200

1

3

9/18/2018

Bank Draft

CS18091802

600

1

Table 9-11 Match 2- Example of Matching Bank Transactions

Number As-Of-Date Bank ID Acct No Credit Amt Match Set #

1

9/19/2018

121000248

4129965265

400

2

Table 9-12 Match 2- Example of Matching GL Transactions

Number Tran Date PymtType Batch ID Total Amt Match Set #

4

9/20/2018

Bank Draft

CS18091802

200

2

5

9/20/2018

Bank Draft

CS18091802

200

2

In the above rule, if we added another rule condition As-Of Date Matches Exactly Tran Date, no matches would get created.