How to create an account-scoped bank matching rule in NetSuite

Create a bank matching rule for one credit-card account, compare transaction memos, add a fixed memo condition, and reopen the saved rule to verify it.

The quick answer

Open Transactions > Bank > Reconciliation Rules and click New Rule. Include one account on Accounts. On Conditions, compare the imported memo with the NetSuite memo, then add a second condition requiring the imported memo to equal a fixed value. Save the rule and reopen it to verify the account and both rows.

This example creates Office Subscription Match for Operating Credit Card. It is configured to require the imported memo to match the existing transaction's memo and equal Office Subscription. The walkthrough ends with the saved configuration. No bank line is imported or matched here. Account, company, and person names in the screenshots are fictional example data. This replay demonstrates configuration in a simulated account; no production rule save or matching result is tested.

Before you start

Use a role with permission to create matching rules and an eligible account with Use Match Bank Data and Reconcile Account Statement Pages enabled. The example uses Administrator and a USD account. Check the actual account name, type, and currency before including it.

A matching rule associates existing transactions. It doesn't create a new GL transaction. System rules run before user rules, and matching rules include an equal-amount or equal-amount-sum requirement by default. The number and wording of system rules can differ by account or version; inspect the list available to you.

01. Inspect the active system rules

Go to Transactions > Bank > Reconciliation Rules. Before creating a rule, read the active system rules. In this example, the transaction-number-and-amount rules and an amount rule with a previous-date window are active. Keep those alternatives in mind when reviewing later matches.

Inspect the active system rules before creating a user rule.

02. Name the user rule

Click New Rule. In Rule Name, enter Office Subscription Match. Use a name that tells a reviewer which recurring transactions the rule is intended to match.

03. Include only the intended account

On Accounts, select Operating Credit Card. Check that its type is Credit Card and its currency is USD. Leave other accounts unselected. Select Show Included Only and confirm that only this account remains visible.

The included-only view confirms the rule is scoped to one account.

04. Compare the imported and NetSuite memo fields

Open Conditions. In the first row, choose All Imported, Memo, and Equals. Leave Value empty. In the comparison columns, choose All NetSuite and Memo.

This row compares two fields. The blank Value cell is intentional because the comparison uses the existing transaction's memo.

The first row compares two memo fields; it does not use a fixed Value.

05. Add the fixed memo restriction

Click the plus control to add another condition. Choose All Imported, Memo, and Equals, then enter Office Subscription in Value. Leave the comparison transaction type and comparison field empty in this row.

06. Read the two conditions together

The first row requires the two memos to agree. The second requires the imported memo to equal Office Subscription. Both conditions apply, along with the default amount requirement shown above the grid.

Use a field comparison in row one and the fixed memo value in row two.

07. Save and reopen the rule

Click Save. Find Office Subscription Match under User Rules. Confirm its Active checkbox is selected and its Rule Type is Matching.

In this example, the saved rule is active and its type is Matching.

Reopen the rule. On Accounts, use Show Included Only to verify that Operating Credit Card is still the only included account.

Reopening confirms the saved account scope.

Open Conditions and verify both memo rows again. Click Cancel to close the inspection without making another change.

Both conditions remain on the saved rule.

08. Review later proposed matches

The saved name, active state, account, and two conditions are the success checks for this walkthrough. Saving the rule doesn't reconcile a statement or show that it caused a match.

When you later review an imported match, compare the bank line with the selected NetSuite transaction. An earlier system rule may already qualify on amount, date, or transaction number. Attribute a match to this user rule only after a controlled test rules out those alternatives.

Common questions

Can a matching rule include more than one account?

Yes. Each additional account must be included in the rule. This example deliberately includes only Operating Credit Card. Use Show Included Only to check which accounts are selected.

Does an empty Value mean the memo must be blank?

No. In the first row, Value is empty because the condition compares All Imported Memo with All NetSuite Memo. The comparison fields supply the other side of the condition.

What does the second memo condition do?

It requires the imported memo to equal Office Subscription. With both rows configured, the imported memo must equal that fixed text and agree with the NetSuite memo. Equals is the selected operator; the guide does not use a contains comparison.

Must the amounts match too?

Yes. The Conditions tab states that equal amount or equal amount sum is included by default. This example adds memo conditions without adding a separate amount row.

Do user rules run before system rules?

No. NetSuite tries active system rules first, then active user rules in their configured order. Moving a user rule higher in its list doesn't put it ahead of system rules. A later proposed match may already satisfy a system rule.

Does saving this rule create or reconcile a transaction?

No. It saves the rule configuration. This example verifies the active rule, selected account, and two conditions by reopening them. It doesn't import or match a bank line, create a GL transaction, or reconcile a statement.

Supporting sources

Oracle's Creating User Transaction Matching Rules documents account selection and condition entry. System Reconciliation Rules explains when matching proceeds from system rules to the first active custom rule.