NetCash - Tips and Troubleshooting

• NetCash > Help > NetCash Help - refresh the connection, then reauthenticate the affected account.
• Confirm the connection is still active (aggregator feeds drop and need re-auth; a sandbox refresh removes Plaid/Finicity setup).
• A single missing transaction is usually a bank-side posting hiccup - import that one line via CSV (see Importing bank activity) and monitor.
• For a direct API bank (JP Morgan, BOA CashPro, KeyBank, US Bank, Wells Fargo), a new account only flows once the bank enables it on the API reporting setup - contact your bank representative to confirm the account was added.

• Transactions dated before the cutover date - NetCash excludes pre-cutover bank transactions, so a bank line dated before cutover throws the balance off. Change its date to the cutover date, or create a cutover item for it (NetCash > Setup > Go Live > scroll right > mark the outstanding items > Submit).
• A changed cutover date removes existing matches and shifts balances - confirm the cutover date is correct before investigating further.
• Timing differences (entered one month, cleared the next) are normal reconciling items, not errors - leave them outstanding; they clear the following period.

• Is the rule's script deployment Scheduled? A Create/Match/Transfer rule that only runs when you click Execute has no scheduled deployment - set NetCash | Bank - Automate - Create/Match/Trans | MR to Scheduled, Daily, No End Date.
• Subsidiary mismatch: the bank account's subsidiary must be on the entity (vendor/customer) record, or Create Transaction fails with an INVALID/INVALID SUBSIDIARY error.
• Check/Deposit rules require a Merchant on the bank transaction (it maps to the required Entity field). If your bank feed has no Merchant, use the Journal Entry transaction type instead.
• Is the bank account included in the rule's Automation Group? A rule won't touch an account that isn't in its group.
• Grouped match not appearing in Confirm Rule Matches? A blank Date Tolerance defaults to 0 (exact-date match required) - set a tolerance value (auto-matching).
• Check the Script Execution Logs (see Viewing script errors) for the specific error.

• Overlapping schedules - the bank-sync job and the Automate-Create job running at the same time create duplicate JEs. Stagger them (sync first, create 1-2 hours later).
• Inactive approver in your JE approval workflow - the workflow errors after the JE is created but before it's matched, so the rule retries and duplicates. Replace or reactivate the approver.
• Transaction Type left blank on a Create Transaction rule batches multiple same-day transactions into one JE and can misfire - set the Transaction Type explicitly.
• Duplicates from a single bank transaction don't affect your reconciliation (only one match exists) - delete the extra JEs manually and continue.
• Duplicate imports on a direct-API account can occur if the same account is also connected via an aggregator - use one connection per account.

• Narrow the date filter. The GL side runs a live query that struggles at high volume; pulling all-time open items can time out. Filter to the period you're reconciling.
• Clear browser cache/cookies and retry; heavy concurrent NetSuite scripting can time the page out - retry when the account is quieter.
• Persistent slowness at very high transaction volume is partly a NetSuite database/query limit - open a NetSuite case if narrowing the filter doesn't help.

• This is almost always a browser caching issue - clear cache/cookies, disable browser extensions, or try a different browser (e.g. Edge).

• Open the employee record > NetCash subtab > set NetCash User Type = Full > Save.
• Check the user's role and that the role has the appropriate NetCash permissions under Permissions > Custom Record.

• Usually by design - see the Frequently Asked Questions below for how each is calculated.
• If the Detail report shows outstanding items that are actually cleared, the reconciliation was submitted before matching finished (the Detail report is snapshotted at submit). Reopen the reconciliation and resubmit.

• The file is delimited by something other than a comma (common with European/German/Swiss/Polish regional settings, which use semicolons). Open the file in Excel and do File > Save As > CSV to re-save it comma-delimited, or use Text-to-Columns to split it, then re-upload.
• Confirm the required columns (Name, Date, Amount/Debit-Credit, Account) are present.
• Native support for non-US regional CSV formats is a known limitation with an open enhancement request; the Save-As workaround is the reliable fix today.

• Ensure that the date format selected matches the format in the file. View full size
• Dates must use slashes or dashes. Dot or (in some locales) dash formats fail. Set the date cells to Text or reformat to slashes before saving.
• European Excel may auto-revert to dot format - re-check after saving.
• Confirm the latest SuiteApp version (import date handling has been broadened over time).

• For a scheduled/automated import (e.g. a SuiteScript that imports as -System-), confirm you're on the latest version; a past defect blocked system-run imports.
• Very large files can hit NetSuite governance limits - split the file into smaller batches.
• Check the Script Execution Logs (NetCash | Data Import | MR) for the specific error.

• NetCash > Reports > All Reports > Bank Imports report > select the batch > Permanently Delete Bank Activity > type CONFIRM. Unmatch any matched items in the batch first.
• To remove a single line, open NetCash Bank Transaction (global search) > Edit > Delete Record, or mark it inactive to keep the history.

They calculate the difference differently and on different dates. The Reconcile and Proof of Cash pages compute an adjusted bank balance (bank balance plus outstanding checks and deposits in transit) against the GL balance, so outstanding items net to zero by design. The Reconciliation Detail report is a period-based snapshot and does not classify an item as outstanding until the month *after* its transaction date. A December check isn't "outstanding" on the December Detail report - it appears once you advance to January. A zero Proof of Cash difference alongside outstanding items on the Detail report is normal.

Most often the transaction is dated before the cutover date (handle it as a cutover item), or was already picked up by a Create Transaction rule. Pre-cutover items live in the Go-Live cutover flow, not the Manual Match page.

The beginning balance on the Reconciliation Detail report is the cutover-date GL balance, not the Initial Balance field on the bank account. If there's no GL transaction before the cutover date, set the Initial Balance to 0 and bring the opening amount in as a bank transaction / cutover item on the Go-Live page.

There is no native "Cleared" flag like standard NetSuite bank rec. Use the Bank Activity report filtered to matched or not matched, and the Reconcile page per account. The All Reports page lists all available reports.

Credit card charges entered in one month but cleared the next are normal reconciling items - the statement-date vs. posting-date timing gap. Leave them outstanding in the current reconciliation; they clear the following period. NetCash uses the Statement Eligibility Date to handle this timing.

Yes, with the Mass Delete tool, deleting record types in dependency order: Match Items, then Match Groups, Transactions, Bank Accounts, Automation Rules, Automation Groups, Bank Institutions. Note that deleting a bank account also clears its reconciliation records - inactivate rather than delete if you want to keep history.

Only if the account number in the file matches the account number stored on the NetCash Bank Account record OR the account text column in the file matches the account name stored on the NetCash Bank Account record. Import templates otherwise upload to the account saved on the template.

NetCash pulls bank activity through open banking APIs, whether directly or using third-party providers. It does not use bank file transfers, file parsers, or screen scrapes. Where no API connection is available, you bring activity in through the CSV import tool (see Importing bank activity above).

NetCash does not connect to every bank. A bank has to allow third-party open banking API access, and many banks - and whole regions - have not adopted it. If a bank does not permit API connections, NetCash cannot pull its data and you would import activity by CSV instead. Availability varies by region:

• Australia: the Consumer Data Right (CDR) requires all banks to provide API access for all account types - the broadest coverage.
• UK and EU: open banking is regulated. We are not able to connect with any banks in the UK. Banks in the EU vary.
• US and Canada: there is no broad mandate, so API connectivity is available but limited, especially for business accounts.
• Latin America, Africa, and Asia: little to no API connectivity today.

If your bank is not connectable, use the CSV import tool, or ask Netgain whether a direct API connection is available.

Open banking lets you share your bank data with a third-party provider through APIs, replacing older methods: bank file transfers (data files such as the BAI2 cash-management format, which the bank has to send and which vary between banks), file parsers (programs that reformat a bank file for another system), and screen scraping (capturing data from the bank's website). APIs return data in a consistent format with minimal setup and support real-time access and automation, so NetCash uses them by default.