Enriched Bank Data Matching Improvements in NetSuite

Enriched Bank Data enhances matching of imported transactions to the general ledger, improving accuracy with AI-generated insights.

·2 min read·10 views·View Oracle Docs

TL;DR: The Enriched Bank Data feature enhances the matching accuracy of imported bank transactions to the general ledger in NetSuite by utilizing generative AI. This functionality is particularly useful for ambiguous transactions that have multiple possible matches.

What is Enriched Bank Data?

The Enriched Bank Data feature automatically extracts entity information from the memo and payee or payor fields of imported bank transactions. This process helps in resolving ambiguities when multiple matches are available for the same transaction amount. After applying existing system and custom matching rules, any unmatched transactions with identical amounts are subjected to enrichment-based matching during bank data import and reconciliation.

How Does It Work?

When importing bank data:

  1. System and custom matching rules are executed first to find potential matches.
  2. For any remaining unmatched transactions with the same amount, the enrichment process evaluates:
    • Exact transaction amount
    • General Ledger (GL) transaction date (up to 7 days prior)
    • Similarity in extracted entity information from the imported transaction compared to existing GL transactions.

This enrichment process is automatically run, and matched transactions are visually indicated by a multicolored vertical line on the Match Bank Data and Reconcile Account Statement pages, with details showing when a match is enrichment-based.

Important Considerations

  • The feature is enabled by default and can be adjusted in the Accounting subtab under Setup > Company > Enable Features by administrators.
  • Review Required: While this feature aims to improve matching accuracy, matches generated by AI should be reviewed for errors before finalizing reconciliation. Ambiguous matches could still lead to incorrect matches, thus thorough verification is essential.

Who This Affects

  • Administrators: Manage features and settings.
  • Accountants: Utilize bank transaction matching and reconciliation.
  • Developers: Integrate or enhance bank data processes within the system.

Key Takeaways

  • The Enriched Bank Data feature enhances matching accuracy for bank transactions.
  • It uses generative AI to extract relevant entity information for better matching.
  • Transactions that remain unmatched after standard rules may be enriched for a more accurate resolution.
  • Users must review automatic matches to confirm accuracy before reconciliation.

Frequently Asked Questions (4)

Does the on-demand data update feature support the Bank Feeds SuiteApp?
No, the on-demand data update feature does not currently support the Bank Feeds SuiteApp. Its support is anticipated in future releases by March 11, 2026.
What permissions are needed to access and manage the Enriched Bank Data feature?
To access and manage the Enriched Bank Data feature, you need the same permissions required to access the Match Bank Data page and to import bank data. Administrator role is necessary to change the feature's status.
How can I enable the Payment Date Prediction feature?
To enable the Payment Date Prediction feature, go to Setup > Company > Setup Tasks > Enable Features and open the Accounting subtab. The feature is disabled by default and requires the Administrator role for activation.
What methods should plug-in developers implement for on-demand data updates?
Plug-in developers should implement the refreshData(context) method to enable on-demand updates. For corporate card expenses, also implement getRefreshRequestStatus(context) to monitor the import status.

Weekly Update History (1)

Bankingadded

Added an entry for Dedicated Credit Card Refund Page and Menu Option.

View Oracle Docs
Source: Update Imported Data for Connected Accounts On Demand Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Integration

View all Integration articles →