Create a matching rule
Matching rules determine how to automatically match transactions from a bank feed or import file for reconciliation.
Create matching rules at the same level in which the bank account was created and the same level that you perform reconciliations. For example, if a bank account was created within an entity, you create rules at the entity level.
How it works
First, a rule filters for transactions (if there are filters defined). Then, it considers any grouping, and then considers the defined matching conditions.
For transactions to match, all conditions defined in the rule need to be met. If a transaction doesn't match exactly to the defined conditions, transactions will not automatically match for reconciliation.
See examples of matching rules that you can create.
If you are banking with an institution in a different time zone than where your business is located, create a matching condition to account for a difference in posting dates.
Video
Create a matching rule
| Subscription |
Cash Management |
|---|---|
| Regional availability |
All regions |
| User type |
Business |
| Permissions |
Bank transaction rules: Add |
-
Go to Cash Management > Setup > Reconciliation rules and select Add (circle) next to Matching and creation rules.
-
On the Rule page, in the Details section, add identifying information about the rule.
-
Give the rule an ID, a Name, and, optionally, Description.
-
Select the Type of rule that you're creating.
In this case, select Match rule. Learn how to create a creation rule.
-
-
Optionally, consider only a subset of transactions in the Filter transaction by section.
Filter transactions- In the Data source dropdown list select either Bank transactions or Intacct transactions.
-
Select the Field on which to filter.
Depending on your selection in the Data source list, the available fields vary.
-
Select the Operator.
Depending on your selection in the Field list, the available operators vary.
-
Enter the Value, or select an option from the dropdown list.
Depending on the field and operator you select, some values are case sensitive.
-
If you select any of the alphanumeric fields (such as Document number, Payee, Description, or any of the payee address fields) and select Equals as the operator, the Value field is case sensitive.
-
If you select any other operator, the Value field is not case sensitive.
For example, consider a bank transaction feed which contains a transaction where the Payee value is "Wexford Widgets Inc". If you select Equals as the operator and enter "Wexford Widgets INC" in the Value field (note the difference in capitalization), that transaction is not matched, so it is not included in the filter. However, if you select Contains as the operator and enter "Wexford Widgets INC" in the Value field, that transaction is matched and is included in the filter.
-
-
Optionally, determine how to group transactions.
For example, you might have multiple Intacct transactions that match to one bank transaction.
Keep in mind that the rule first considers filter results and then tries to group transactions.
-
Define Matching conditions.
All matching rules require a matching condition for Amount.
Matching conditions- Select the Bank transaction field.
- Select the Operator.
-
Select the Value.
This field is case sensitive.
- In the Match with this field in an Intacct transaction column, select which field to match to.
-
Select Save.
Next step: After you create the rule, create a rule set to contain it. Make sure that creation rules run last. Then, apply the rule set to an account.
When you reconcile, import a bank file, or refresh a bank feed for an account, matching rules run first. Then, creation rules run and create additional transactions from any remaining bank transactions.