NetCash - Implementation overview

Overview

A typical NetCash implementation goes live in about 6-8 weeks, followed by 30 days of post-go-live support. A Direct API bank connection adds about 2-4 weeks. This article lists the milestones in the project, what happens on each call, and what your team does between calls, so you can plan the time.

Netgain runs weekly one-hour working sessions with your team to walk through bank connection, run training, and answer questions. Between sessions, your team completes configuration steps and user acceptance testing (UAT).

Project at a glance

Kickoff and discovery

On the kickoff call, Netgain welcomes your team, covers introductions, reviews the scope of the products you purchased, and explains project governance and implementation methodology. The call also covers best practices and the next steps, including planning and discovery sessions.

Discovery work that follows:

• • Complete the Product Discovery Questionnaire if you haven't already returned it.
  • Set a go-live date. The go-live date is the beginning of the first month NetCash will be fully functioning.
  • Confirm whether you will use a sandbox.
  • Bookmark the Netgain Knowledge Center.
  • If you are new to NetSuite, configure your subsidiary structure, chart of accounts, NetSuite segments (Department/Class/Location), and user and role permissions before bank connections start. Define and build any customizations.
  • Give the Netgain implementation lead administrator access to your sandbox and production accounts, if needed.

Setup and configure

Netgain requests the app provision. Your team then completes setup.

• • Install NetCash. See NetCash Installation.
  • Fill out the roles and permissions template. NetCash permissions take two steps: adding NetCash users, and configuring permissions by role. See NetCash Roles and Permissions. Netgain updates roles in your sandbox. You update roles in production.
  • Bank connection
    • If using a Netgain direct API, Netgain will share the steps to kick off this process with your bank. See NetCash Direct API Connection.
    • If using a third-party provider to connect, Netgain will walk through the Bank Connect portal. See Automatic Bank Feed Connection Setup.
    • If connecting to a bank feed manually, Netgain will walk through those steps. See Manual Bank Connection Setup.

Bank connections and configuration

This phase runs through the weekly working sessions.

• • Connect and configure bank accounts. Once your bank institution is connected, the accounts then appear in NetCash > Setup > Bank Accounts, where you add the required information to each bank account record. With many accounts, complete the NetCash Bank Account Template and send it to your implementer to upload.
  • Upload CSV bank data (if applicable). If a bank feed connection is unavailable, Netgain can load transactions with the NetCash CSV import tool.
  • Create automation groups and rules. Netgain and your team create rule groups, then automation rules.
  • Create cutover items. For any bank account where the bank balance and the GL balance differ on your cutover date, such as outstanding checks or deposits in transit, create cutover items. This is a one-time process for the first month. See Cutover items.
  • Test and activate automation rules. Your team and Netgain test the rules before activating them.

Training

Netgain runs a training call and a reports training call.

Training call topics

• • Navigation overview
  • System settings
  • Bank dashboard
  • Confirming rule matches
  • Match Assist
  • Manual match bank transactions
  • AI tools
  • Match history
  • Reconcile (confirm cutover items exist for the first month)

The reports training call covers the reports that come with NetCash, including Bank Activity, Proof of Cash, Reconciliation Detail, and Direct Cash Flow.

User acceptance testing (UAT)

Netgain recommends UAT before the implementation is completed. All mapping, permissions, and configuration must be done before UAT begins. See NetCash User Acceptance Testing (UAT).

Go-live

If you configured in a sandbox, Netgain sets up production to match it.

• • Update production roles and permissions. Netgain's policy doesn't allow consultants to edit role permissions in a live NetSuite environment, so your consultant guides you through the updates.
  • Review data in production. Check bank accounts, bank transactions, and automation rules. Plan about 2 hours.
  • Review the access tokens. Netgain and your team confirm that a member of your team created the access tokens for both sandbox and production.
  • Go-live call. Netgain confirms NetCash is live in production and your team is using it.
  • Complete your first reconciliation. See NetCash Reconcile and the Bank Reconciliation Playbook.

Netgain schedules the closure call during or right after the go-live call, so everyone has a date set.

Post-go-live support and project closure

For 30 days after go-live, your implementation team stays available through your first NetCash close. They answer questions and explain any process that didn't come up in training. By the end of your first close, bring any leftover implementation tasks so the consultant can address them.

The closure call usually happens after your first month-end close in NetCash. It covers:

• • A recap of the work completed by both teams
  • Final steps toward closure and sign-off
  • Your Netgain contacts going forward
  • A product review and implementation survey
  • Other Netgain products that pair with NetCash

Your project sponsor provides sign-off, live on the call or by email afterward. Netgain removes its access to your NetSuite account as part of closing the project. For ongoing help, email support@netgain.tech.

Related links

• • Intro to NetCash
  • NetCash User Acceptance Testing (UAT)
  • NetCash Go-Live Process