NetCash Bank Connection via Skript - Bank Activity Retrieval

Overview

This article explains how NetCash retrieves bank activity from a Skript connection, why recent transactions sometimes take a day or two to appear, and what you can do to get activity sooner. It applies to any NetCash bank account connected through Skript, in any region.

If you are still setting up a Skript connection, see NetCash Bank Connection via Skript - Australian Banks first.

How bank activity is retrieved

NetCash pulls transactions from Skript on a scheduled background sync that runs once per day. By default the sync runs at 11:00 UTC, so the local time it lands depends on your time zone.

A few things about how the sync behaves are worth knowing, because they explain most of what you see on the Bank Activity page:

• NetCash only pulls transactions your bank has marked as posted. Pending transactions are not brought in until the bank posts them.
• Each run re-checks the last several days of history, not just the previous day. Any transaction that posts late still gets picked up on a later run without you doing anything.
• The account balance shown in NetCash refreshes with each daily sync.
• The sync matches each transaction on its unique bank-side ID and updates the existing record instead of creating a second one, so a transaction never gets duplicated across runs.

Why recent activity can take a day or two

There are two separate delays to keep apart:

1. Posting delay at the bank. The transaction has not yet been marked posted at your bank, so Skript does not have it yet and NetCash has nothing to pull. This is the usual cause of a one-to-two day lag.
2. Sync timing at NetCash. The transaction is posted and waiting, but the once-a-day sync has not run since. This gap is at most one day.

The difference matters because it tells you whether acting will help. If the delay is a posting delay at the bank, running the sync more often does nothing - there is nothing to pull until the bank posts. If the transaction is already posted and you do not want to wait for the next scheduled run, you can pull it in now.

Run the sync on demand

The sync already runs automatically once a day so in most cases you do not need to run it manually. A manual run is only for when you need posted activity before the next scheduled run.

If a transaction is posted at your bank and you do not want to wait for that next scheduled run, a NetSuite administrator can trigger the sync manually:

1. Go to Customization > Scripting > Script Deployments.
2. Open the deployment titled NetCash | Bank Tran - Skript | MR.
3. Select Save & Execute to run it immediately. View full size

This is a one-off catch-up. It is safe to run - because transactions are matched on their unique ID, an extra run will not duplicate any activity - but it only surfaces transactions that are already posted at the bank.

Need activity more than once a day

If you regularly need bank activity to land more than once a day, contact Netgain rather than changing the schedule yourself. We can adjust how often the sync runs for your account. More frequent syncing is safe for your data, but it adds load against your bank's Skript connection, so we will set a cadence that fits your account.

Keep the connection healthy

A broken or expired connection stops activity from arriving at all, which can look like a retrieval delay. On the bank institution record, set the Error Log Recipients so the right people are notified by email if the connection needs to be re-authenticated. See the Skript connection article for where that field lives.