NetCash - Switching Connection Providers

Overview

NetCash can pull bank activity through several methods. If you want to switch methods after going live with one method, this article covers how to make the switch without creating a gap in coverage or importing duplicate transactions.

Before You Switch

A different provider is not automatically faster or better

Sync speed and data quality depend mostly on how readily the bank itself shares its transaction data, not on the connector. Confirm the new feed is actually an improvement before switching a live account.

Test the new connection in a sandbox first. Sandbox testing is available for Plaid, Finicity, and GoCardless (not Skript). Connect the institution in your sandbox account and run the feed for a week or two to confirm it is viable before changing anything in production.
Some banks must use Netgain's Direct API. JP Morgan, Wells Fargo, Bank of America, KeyBank, and US Bank connect through Netgain's Direct API and cannot be moved to Plaid or Finicity.
Note the last transaction date on the account you are switching. You will use it to clean up any overlap after the switch (see Avoiding Duplicate Transactions and Coverage Gaps below).

How NetCash Routes a Connection

Every NetCash Bank Institution record has a Provider field that tells NetCash which sync engine to run for that institution. Common values are PLAID, FINICITY, NETSUITE, GOCARDLESS, SKRIPT, and MANUAL. Direct-API institutions use their own values (for example BOACASHPRO).

You only type the Provider value for NetSuite and Manual

For aggregator connections - Plaid, Finicity, GoCardless, Skript - the Provider field is set automatically when you establish the connection through Bank Connect, because those connections require a login. You type the Provider value by hand only for NETSUITE and Manual, which have no login flow. This is why switching to or from an aggregator is more than a single field change.

Switching the Provider

Regardless of where you're switching from, find where you're switching to in the table below and follow the matching procedure. The steps differ because some connections require a login (aggregators), some are a field change (NetSuite), and some are provisioned by Netgain (Direct API).

Switching to	Procedure
Plaid, Finicity, GoCardless, or Skript	To an Aggregator
NetSuite (Match Bank Data)	To NetSuite
Netgain Direct API	To the Netgain Direct API
Manual/CSV Imports	NetCash Switching to Manual Transaction Uploads

To an Aggregator (Plaid or Finicity)

Aggregator connections require a bank login, so you establish the new connection first, then move it onto your existing records.

Confirm the new feed in a sandbox first, as described above.
In production, go to NetCash > Setup > Bank Connect. Hover over New Bank Connection and select the new provider (Plaid is recommended first; use Finicity if Plaid is unavailable or unsuccessful for that bank).
Click Next, search for and select the banking institution, complete the bank's login flow, select the accounts to connect, and click Submit. This establishes the new feed and sets the Provider field automatically.
Move the new connection onto your existing records, then retire the new duplicates. Connecting in the previous step created a new Bank Institution record and new Bank Account records, because the new provider issues its own identifiers and NetCash cannot reuse the old ones automatically. To keep your existing accounts and their full transaction history visible in NetCash, copy the connection details from the new records onto your existing records, then inactivate the new ones:
1. Search for NetCash Bank Institution in your global search bar to access the institution page.
2. Select Customize View to include the following fields in your display.
3. In Edit mode, copy the connection fields - Provider, Token, Institution ID, and Cursor - from your new institution record onto your existing/old institution record, replacing the previous provider's values.
4. Search for NetCash Bank Account in your global search bar to access the bank account page.
5. In Edit mode, copy the Provider Account ID from your new bank account record onto the matching existing/old account record.
Once the values above are moved, inactivate the new (duplicate) records - both the institution and its accounts.

Inactivate the new duplicates, never your existing records

Keep your original accounts as the surviving records so their history stays in view. Inactivating existing accounts would hide those accounts from NetCash pages along with the transaction history. For this reason, we want to inactivate the new records.

To NetSuite (Match Bank Data)

NetSuite's Match Bank Data has no login flow, so you switch to it by editing the Provider field on your existing record - no new records are created, and your transaction history stays attached.

Confirm a working bank feed already exists in NetSuite's Match Bank Data for the account. NetCash imports what Match Bank Data provides; it does not establish the bank feed itself.
Search NetCash Bank Institution in the global search bar to access the institution page. If the Provider field is not shown, select Customize View to display it.
In Edit mode, change the Provider field to NETSUITE (all caps).
Search for NetCash Bank Account in your global search bar to access the bank account page. If the Provider Account ID field is not shown, select Customize View to display it.
On each NetCash Bank Account record, set the Provider Account ID to the internal ID of the corresponding NetSuite GL bank account.

See NetCash Bank Connection via NetSuite's Match Bank Data for the full setup, including how to verify the connection and schedule the sync.

To Netgain's Direct API

Netgain's Direct API is available for JP Morgan, Wells Fargo, Bank of America, KeyBank, and US Bank on their corporate platforms. It is not self-service - Netgain provisions the connection together with you and your bank, and the timeline runs several weeks, so start early.

See NetCash Direct API Connection by Netgain for the full process.
As the direct feed comes online, Netgain helps consolidate onto your existing accounts using the same principle as above - keep your original accounts as the surviving records so history stays visible.

Avoiding Duplicate Transactions and Coverage Gaps

This is the most common concern when switching a live account. Two behaviors of NetCash determine what to expect.

Dedup is per provider. NetCash recognizes an already-imported transaction by the connection provider's own transaction ID. Each provider assigns its own IDs, so the new provider will not recognize transactions the old one already imported as the same records. Where the two feeds briefly overlap around the switch, you may see a few duplicate transactions, or occasionally a missing one.

How the new feed resumes depends on the provider. Finicity and NetSuite (Match Bank Data) pull a recent window of activity, so they resume close to where the old feed stopped. Plaid resumes from the saved sync position (its Cursor) that you carried over in the steps above. Either way, switch promptly after the old feed's last sync so there is no gap to backfill, then clean up the small overlap:

Duplicate transactions: inactivate the duplicate bank transaction records left over from the old connection. See How to Delete/Inactivate Bank Transactions.
Missing transactions: create the missing transactions manually or pull them in via CSV import.

Is This Self-Service or Netgain-Led?

Switching between aggregators, NetSuite (Match Bank Data), or manual uploads is self-service with the guidance above. However, switching to the Direct API is always Netgain-led. Reach out to support if you are switching a large number of accounts or are not comfortable editing the connection fields yourself.

Was this article helpful?