Rules

 

Use the Rules feature to have ACH Universal test individual transactions to:

--1. Classify transactions (ie. ACH, Wires, AMEX, etc...)

--2. Assign site numbers from Merchant Numbers (via data extraction / SIte Lookup).

 

 

While this is ideal for credit card transactions - it can be used on less complex scenarios as well.

 

 

Getting Started

Open the Rules form from the Home tab:

 

 

 

1. Classify transactions (ie. ACH, Wires, AMEX, etc...)

Use the rules to classify transactions based on text within the description (or any) field.

 

Remember to enable the feature by checking the check box at the top of the form.

 

Below is the G/L tab.

As an example - you can see that if the Description contains the text 'MC/V', the system will classify the record as MC/Visa.

 

 

When these rules are applied against the imported data, such as below - the records will be correctly classified:

 

 

 

Add you own rule:

--Bank or G/L - select one of the tabs.  If a rule is to apply to both, enter it in each tab.

--Click on the 'Add a Row' button above the grid.

--Enter the rule as appropriate.  Note: Some fields will contain a default value even if they are not used - this is okay.

 

 

 

2. Assign site numbers from Merchant Numbers (via data extraction / SIte Lookup).

 

Very often, when importing bank statements, the merchant number will be embedded within the text description.

 

The Rules feature can help you extract the merchant number - and convert it to a site number.

 

Below is the Bank tab from our sample data.

Looking at rule #1, the system will test the Description field and look for the text 'Credit Card Des' anywhere within the field.

 

 

 

 

 

If it does not find that text, the system will attempt the next rule, rule #2.  Note: The system will continue for all active rules.

If the system does find the text, it will take an action, and copy the rightmost 12 positions of data to the 'Lookup_Site' field.  The system will then stop processing rules for this record.

 

Once all of the records have been passed through the rules, the system will then take the value of the Lookup_Site field and look this up in the Site Index table - against the external merchant numbers.

 

If there is a match, the system will populate the record with a site number and transaction type (MC/Visa, etc...).

If not, the record will retain it's core matching type (Check, Misc +, Misc -), and it will not be included in the User Defined Matching Rule.

 

 

 

As an example, let's look at the data, which led to the first rule in the sample data.

 

 

 

 

 

Populate fields other than Lookup_Site

If you notice that in the 4th rule in the Bank sample above, exports the ACH Trace number to the Text1 (Matching Field).

This Trace Number, along with amount are used in an Alphanumeric text field match (Amount to Amount, Text1 to Text1).

 

We have elected to run the 'Alphanumeric Match' rule on the Matching Rules form.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

ssign Site numbers from Merchant Numbers (via data extraction / SIte Lookup).