Know Your Rule Types: System, User-Defined, and Auto-Create

07/15/2025

Fernanda Garcia

by Fernanda Garcia

Summary

Join our newsletter

Last updated: 2026-05-29

Executive Summary:

NetSuite's bank reconciliation engine uses three distinct rule types: System Rules for standard transaction matching, User-Defined Rules for custom matching logic, and Auto-Create Rules for generating GL entries from unmatched bank lines. Understanding the hierarchy in which these rules execute is essential for configuring a bank reconciliation setup that is both accurate and maintainable. Techfino explains how each rule type works, when it applies, and how to avoid common configuration mistakes.

NetSuite’s Bank Reconciliation feature offers powerful automation tools - but to make the most of them, it’s essential to understand how System Rules, User-Defined Rules, and Auto-Create Rules work together in hierarchy and function.

Here’s how to master the matching engine behind your bank data reconciliation - and how to avoid the most common missteps.

System Rules: Default Logic with Built-in Flexibility

System Rules are NetSuite’s out-of-the-box match criteria. Think of them as the platform’s first line of defense: they run automatically and attempt to match imported bank lines with GL transactions using broad patterns like:

  • Transaction Number + Amount
  • Amount + Transaction Number (without prefixes or leading zeros)
  • Amount only, when date is within 90 previous days

These rules are powerful and support one-to-many or many-to-many scenarios - particularly when a shared transaction number exists across lines. But they can’t create GL transactions, and they always run before any custom logic you define.

User-Defined Rules: Tailor Matching to Your Business Logic

User-defined rules let you define how NetSuite should match imported lines to GL transactions, based on your business-specific logic. These are typically one-to-one matches and should be used when you need precision - such as matching a Canadian checking account based on specific transaction IDs or custom memos.

You can define which accounts the rule applies to…

… and control the logic using custom conditions such as:

  • Matching by date range
  • Filtering by transaction type
  • Comparing GL dates to imported ACH lines

Pro Tip: Order matters. Always place your most specific user rules at the top of the execution list. This prevents incorrect matches that could be caused by broader rules running too early.

Bg Image

White paper

title-continuedsuccess-2

What if NetSuite support actually worked?

See the Continued Success difference.

Get the Whitepaper

Auto-Create Rules: Automatically Create and Match GL Entries

Auto-create rules are a special category of user-defined rules. They do more than just match - they generate GL transactions based on imported bank lines and then match them. This is particularly useful for:

  • Bank fees
  • Interest charges
  • Recurring charges that don’t originate in NetSuite

However, these rules have limitations:

  • They can’t create journal entries or bank transfers
  • They don’t support tax codes
  • They are only triggered from manual one-to-one matches

Tips for Creating Effective Matching Rules

Here’s what every NetSuite admin and accountant should keep in mind:

  • Start with Date, Amount, and Transaction ID. These are your most reliable matching anchors.
  • Memo field can be helpful, but keep in mind that NetSuite matches only on header-level memos, not line-level notes.
  • Understand transaction type mapping: A deposit in your bank might appear as a debit in NetSuite’s cash account. Misunderstanding this will break your matches.
  • Watch for complex groupings: System rules can sometimes resolve many-to-many matches automatically if transaction numbers align. Otherwise, manual grouping via the Match Bank Data page may be required.

Wrapping Up: Use the Rule Hierarchy to Your Advantage

Understanding the hierarchy is key:

  1. System Rules run first - broad but automatic
  2. User-Defined Rules bring in precision and override defaults
  3. Auto-Create Rules fill in missing GL data with matched entries

Use this structure intentionally. By combining default flexibility with tailored logic and auto-generated transactions, your reconciliation process can be dramatically faster, more accurate, and easier to maintain.

Want help reviewing your reconciliation setup? Our Techfino team can assess your current logic and recommend improvements that reduce manual intervention while maintaining full audit readiness.

Frequently Asked Questions About NetSuite Bank Reconciliation Rule Types

What are the three rule types in NetSuite's bank reconciliation?

NetSuite's bank reconciliation uses three rule types: System Rules (NetSuite's default matching logic that runs automatically before any custom rules), User-Defined Rules (custom business-specific matching logic you configure for precision matching), and Auto-Create Rules (rules that automatically create GL transactions, such as bank fees or interest, from unmatched bank lines).

What are System Rules in NetSuite bank reconciliation?

System Rules are NetSuite's out-of-the-box matching criteria that run automatically on every bank reconciliation before any custom logic. They match imported bank lines to GL transactions using broad patterns like Transaction Number + Amount, or Amount within 90 previous days. System Rules support one-to-many, many-to-one and many-to-many matching scenarios but cannot create GL transactions.

What are User Rules in NetSuite bank reconciliation?

Within the User Rules layer, NetSuite provides two rule types: custom matching rules and Auto-Create Rules. Custom matching rules allow you to define custom matching logic tailored to your specific business needs, for example, matching a Canadian checking account using transaction IDs or specific memo text. They run after System Rules, and like System Rules they can produce grouped matches as well as one-to-one. They give you precision control over how bank lines are matched when the default System Rules are insufficient.

What are Auto-Create Rules in NetSuite bank reconciliation?

Auto-Create Rules are a type of User Rule that handles eligible bank lines that don't match any existing GL transaction, such as bank service fees, interest income, or other bank-initiated charges. Instead of leaving these lines unmatched, Auto-Create Rules automatically generate the corresponding GL transaction and match it, keeping your reconciliation clean and eliminating the manual step of creating these entries separately. What it creates depends on the account type: for bank accounts, checks and deposits; for credit card accounts, credit card charges and credit card refunds.

What is the execution order of rule types in NetSuite bank reconciliation?

NetSuite always executes System Rules first, before any custom rules you define. User-Defined Rules run after System Rules for lines that weren't matched. Auto-Create Rules aren't a separate stage; they live inside User Rules alongside custom matching rules, and you can set the order the whole User Rules list runs by dragging them on the Reconciliation Rules page. Understanding this hierarchy is critical when debugging reconciliation issues, an unexpected System Rule match can prevent your User-Defined Rule from firing.

How can Techfino help optimize bank reconciliation rules in NetSuite?

Techfino helps clients configure and troubleshoot all three bank reconciliation rule types, from auditing System Rule conflicts to building User-Defined Rules for complex matching scenarios and configuring Auto-Create Rules for recurring bank charges. If your reconciliation has persistent unmatched items or incorrect matches, Techfino's consultants can diagnose the root cause and implement the right rule configuration to resolve it.

What should you do when no bank reconciliation rule type matches an imported bank line in NetSuite?

When no rule matches an imported bank line, NetSuite leaves it in an unmatched state in the reconciliation workbench. You can manually match it to an existing GL transaction, create a new journal entry directly from the workbench, or build a new User-Defined Rule to catch similar transactions automatically in future imports. Persistent unmatched lines are often a signal to review your overall rule set configuration.

Talk to a NetSuite Expert

Tell us what you're working on, and we'll help you figure out the next step.

Related posts