Bank Reconciliation Now Auto-Submits Exact Matches by Default

What changed

NetSuite introduced the Automatically Accept Exact Matches accounting preference, enabled by default. When active, the system automatically accepts and submits eligible bank and credit card reconciliation match suggestions without requiring manual review on the Match Suggestions subtab.

Auto-submission triggers in two scenarios:

• During bank data import (CSV or bank feed)
• When reconciliation rules are manually executed

Eligible suggestions are limited to transaction-match and match-group suggestions generated by system or user-defined reconciliation rules. Auto-submitted matches appear on the Review subtab of the Reconcile Account Statement page with System in the Submitted by column.

What is excluded

The following suggestion types are not auto-submitted and remain on the Match Suggestions subtab for manual review:

• Entity-enriched suggestions
• Suggestions with multiple match options
• Transaction Matching Assistant suggestions (NetSuite Next only — phased rollout)
• Accounts payable or accounts receivable payment-application suggestions
• Auto-create suggestions
• Cash-in-transit suggestions

Permission requirement

Auto-submission only fires when the user performing the import or rule execution holds the Reconcile permission at Create, Edit, or Full level. If the permission is missing or insufficient, suggestions fall back to manual review on the Match Suggestions subtab — the same behavior as when the preference is disabled.

What to do

1. Audit your reconciliation workflow. Because this preference is on by default, exact matches are now silently accepted during import. If your team relies on reviewing every match before submission, an Administrator should navigate to Setup > Accounting > Accounting Preferences and disable Automatically Accept Exact Matches.
2. Review role permissions. Verify which roles have the Reconcile permission at Create/Edit/Full. Any user with that permission who imports bank data or runs reconciliation rules will trigger auto-submission. Tighten permissions if you want to limit who can cause automatic acceptance.
3. Update saved searches or scripts that report on match status. If you have SuiteScript or saved searches that key off the Submitted by field on reconciliation records, account for the new System value. Previously all submissions were user-initiated; now system-submitted rows will appear on the Review subtab.
4. Check custom reconciliation rule logic. If you have user-defined reconciliation rules, confirm that their match criteria are tight enough for unattended acceptance. Loosely configured rules could produce false-positive exact matches that get auto-submitted.
5. Monitor the Review subtab after your next import cycle to verify that auto-submitted matches are accurate before this becomes routine.

Notes

The source does not specify which SuiteScript modules or REST/SOAP endpoints expose this preference programmatically. If you need to toggle or read the preference via script, check the accountingpreference record or the companypreferences record in your sandbox. Oracle's documentation is vague on API-level access to this setting — verify in a non-production environment before automating.