NetCash Bank Connection via NetSuite's Match Bank Data
Overview
NetCash can pull bank transactions from NetSuite's Match Bank Data instead of connecting directly to a bank's API. This option is for customers who already have a working bank feed in NetSuite's Match Bank Data and want NetCash to consume those transactions rather than establishing a parallel API connection.
Once configured, a scheduled script pulls transactions from Match Bank Data into NetCash on the cadence selected during deployment - typically nightly.
Not available for select banks
The following banks are not able to connect via this method; instead, they are connected via Netgain's Direct API.
- JP Morgan
- Wells Fargo
- Bank of America
- KeyBank
- US Bank
Bank feed troubleshooting is out of scope
Netgain does not troubleshoot data issues originating from the Match Bank Data connection. NetCash imports exactly what Match Bank Data provides. If transactions are missing, duplicated, or incorrect at the Match Bank Data level, the issue must be resolved through the bank feed or NetSuite Support before NetCash will reflect the corrected data.
Prerequisites
- A working bank feed connection in NetSuite's Match Bank Data.
- The internal ID of each NetSuite GL bank account that will sync to NetCash. Internal IDs can be enabled under Home > Set Preferences > General > Defaults > Show Internal IDs.
Set the Bank Institution Provider to NetSuite
- Search "NetCash Bank Institution" in your global search bar and access the "Page: NetCash Bank Institution."
- If the institution does not yet exist, create it first by selecting New NetCash Bank Institution.
- If not already shown, select Customize View to show the Provider field.
- In Edit mode, type NETSUITE (all caps) into the Provider field.
Set the Provider Account ID on the Bank Account Record
- Search "NetCash Bank Account" in your global search bar and access the "Page: NetCash Bank Account."
- If not already shown, select Customize View to show the Provider Account ID field.
- Enter the Internal ID of the corresponding NetSuite bank account (the GL account configured for Match Bank Data).
- To access the internal ID of the bank account, access the Chart of Accounts. If not already displayed, enable internal IDs via Home > Set Preferences > General > Defaults > Show Internal IDs.
- To access the internal ID of the bank account, access the Chart of Accounts. If not already displayed, enable internal IDs via Home > Set Preferences > General > Defaults > Show Internal IDs.
- Repeat the above steps to input the Provider Account ID for each Bank Account that should sync from Match Bank Data.
Verify the Connection
- Navigate to NetCash > Help > NetCash Help. The connected institutions/accounts should appear in the list of banks.
- Under Bank Providers, click NetSuite, then click Sync NetSuite Transactions. This kicks off a script to pull over transactions.
- Confirm imported transactions under NetCash > Reports > Bank Activity.
Run a manual sync at any time
The Sync NetSuite Transactions action on the NetCash Help page can be used at any time to pull the latest Match Bank Data transactions on demand - useful for verifying setup or catching up after a delayed bank feed.
Schedule the Sync Script
Once the manual sync confirms transactions are flowing, schedule the import to run daily.
- Navigate to Customization > Scripting > Scripts and select Deployments on the NetCash | Tran Sync - NetSuite Bank | MR script.
- Click New Deployment.
- Set the deployment Status to Scheduled and configure the schedule to run daily, at a time after the Match Bank Data bank feed completes. Match Bank Data typically refreshes overnight, so a deployment scheduled for early morning will pick up the prior day's activity.
How far back the script looks
- First sync (no transactions in NetCash yet for the account): pulls from the bank account cutover date through today.
- Subsequent runs: looks back 5 days from the latest existing transactions, to catch late-posting bank corrections.
- Need to pull further back? Set the deployment parameters (screenshot below) and populate the Date From or Day Count.
4. Save the deployment.
One deployment per environment
Only one scheduled deployment is needed. The script processes every Bank Account record whose provider is set to NETSUITE, regardless of how many institutions/accounts are connected through Match Bank Data.
Limitations and Callouts
Data troubleshooting
NetCash imports the transactions as they appear in Match Bank Data. Any data quality issue at the bank feed level - missing transactions, posting-date timing differences, incorrect descriptions - will carry through to NetCash. Resolve those issues at the Match Bank Data layer first.
Sync cadence depends on the bank feed
NetCash can only sync what Match Bank Data has already pulled. If the bank feed runs nightly, schedule the NetCash deployment to run after that window. Running the NetCash sync ahead of the bank feed will not pull in transactions that Match Bank Data has not yet received.
