NetCash Manual Bank Connection Setup
Overview
Bank accounts that do not support API connectivity through third-party services can be connected using a manual setup. This article outlines the steps required to complete a manual bank connection.
Step-by-Step Process
Bank Institution Configuration
Bank Institutions are automatically created in NetCash for all connections established via the API connection. The following instructions apply only to banks that do not support API connectivity.
Bank Institutions serve as containers for Bank Accounts and must be created manually.
To create a new Bank Institution:
- In the global search bar, enter NetCash Bank Institution, then select Page: NetCash Bank Institution to view the list of existing records.
- Select New NetCash Bank Institution to begin creating a new record:
- The only mandatory field for this record is Name. No additional fields are required. Once the name has been entered, select Save to complete the process:
Bank Account Configuration
For bank connections made through the API integration, NetCash will automatically create the bank accounts. The following instructions are only necessary for banks that do not support API connections.
Bank Account records can now be associated with the newly created Bank Institution.
To create a new Bank Account:
- Navigate to NetCash > Setup > Bank Accounts, where a list of all bank accounts in use will be displayed.
- Select New to create a new Bank Account record:
- In the side screen that appears, enter values in all required editable fields listed below:
Note: While some of the fields listed below may not be technically required by the system, they are functionally essential. Omitting them will result in limited or broken functionality.
| Field Name | Description |
|---|---|
| Name | This is the account name that will appear across all pages and fields when selecting an account. |
| Number | In many cases, the Number and ID fields contain the same value, as both typically represent the bank account number. However, there are instances where one field (e.g., Number) may contain only the last four digits, while the other (e.g., ID) holds the full account number, or vice versa. |
| ID | In many cases, the Number and ID fields contain the same value, as both typically represent the bank account number. However, there are instances where one field (e.g., Number) may contain only the last four digits, while the other (e.g., ID) holds the full account number, or vice versa. |
| Bank Institution | Select the Bank Institution associated with the Bank Account. The Bank Institution must be created manually before the Bank Account record can be added. |
| Currency | Enter the three-letter ISO currency code associated with the bank account (e.g., USD for US Dollar, AUD for Australian Dollar, EUR for Euro, GBP for British Pound, or JPY for Japanese Yen). This field will not be editable after the record is saved. |
| Initial Balance | This represents the bank account balance as of the end of the day prior to the cutover date. It enables the system to begin the bank reconciliation process at a specific point in time without accounting for historical transactions. |
| Cutover Date | This is the date when the bank reconciliation module will begin to be used. Transactions dated before this cutover date will not be imported. It is recommended to set this date to the beginning of a month. |
| GL Account | This is the GL account linked to the bank account. A GL account can only be associated with one bank account record. |
| Rounding GL Account | This account is used when a bank transaction is matched to a GL transaction and there is a difference in the amounts. The variance will be posted to this rounding GL account. |
| Offset GL Account | This account is optional but highly recommended. It serves as the default account for transactions created from the bank matching page. While it can be overridden during transaction creation, it will also be used by default when a Create Transaction automation rule is applied. |
- The following fields will also appear in the side screen and can be optionally populated, if applicable:
| Field Name | Description |
|---|---|
| Type | This field can be used to indicate the purpose of the bank account (e.g., checking or savings). Note that it is typically populated by the automated bank connection script and is not required for manual connections. |
| Current Balance | This field is system-generated and cannot be populated manually—as it is only applicable for bank syncs. |
| Cutover Date GL Balance | This field is automatically populated by the system and cannot be entered manually. It will display the balance of the selected GL Account as of the chosen Cutover Date. |
Segments Tab
| Field Name | Description |
|---|---|
| Class - Bank Line | This is the default class assigned to the bank line (transaction line affecting the bank account) of transactions created from the bank matching page or through automation rules. It can be overridden when creating a transaction. |
| Department - Bank Line | This is the default department assigned to the bank line (transaction line affecting the bank account) of transactions created from the bank matching page or through automation rules. It can be overridden when creating a transaction. |
| Location - Bank Line | This is the default location assigned to the bank line (transaction line affecting the bank account) of transactions created from the bank matching page or through automation rules. It can be overridden when creating a transaction. |
| Class - Offset | This is the default class assigned to the offsetting line (the line not affecting the bank account) of transactions created from the bank matching page or through automation rules. It can be overridden when creating a transaction. |
| Department - Offset | This is the default department assigned to the offsetting line (the line not affecting the bank account) of transactions created from the bank matching page or through automation rules. It can be overridden when creating a transaction. |
| Location - Offset | This is the default location assigned to the offsetting line (the line not affecting the bank account) of transactions created from the bank matching page or through automation rules. It can be overridden when creating a transaction. |
Reconciliation Tab
| Field Name | Description |
|---|---|
| Approver(s) | This is the user(s) responsible for approving the reconciliation record before it is marked as complete. |
| Balance Changed Date Variance | This field specifies the number of days a date on the matched transaction on the GL side can change before triggering a status update for a completed reconciliation. If the change exceeds the specified number of days, the reconciliation status will change from Completed to Balance Changed, indicating that further investigation is needed. For example, if the variance is set to 3 days and the transaction date changes by only 2 days after the match, no action will be taken. However, if the date changes by 3 or 4 days, the reconciliation status will be updated. |
Validations Tab
| Field Name | Description |
|---|---|
| Department - Validations | Used to specify that a GL transaction matched to a bank transaction from the designated bank account must be associated with a specific department(s). |
| Class - Validations | Used to specify that a GL transaction matched to a bank transaction from the designated bank account must be associated with a specific class(es). |
| Location - Validations | Used to specify that a GL transaction matched to a bank transaction from the designated bank account must be associated with a specific location(s). |
- After completing all required and optional fields, click Create at the top of the side screen. Make sure to review and complete these fields for each bank account record individually:
Upload Bank Accounts via CSV Import
If several bank accounts need to be uploaded, the user may consider uploading via CSV import.
Download the NetCash Manual Connection Template for a list of required fields. This template also includes a tab for uploading bank transactions to manual bank connections. Instructions can be found here for uploading transactions.
- Fill out the Bank Account tab in the NetCash Manual Connection Template
- Delete any informational or example rows
- When finished updating, save it to a known location as a .csv file
- Delete any informational or example rows
- Navigate to the Import Assistant by accessing Setup > Import/Export > Import CSV Records
- With the Import Assistant open, update the Import Type to Custom Records and the Record Type to NetCash Bank Account
- Then, select your .csv file
- On Import Options, make sure Add is selected (or Update if doing a bulk update to NetCash Bank Account) and "Run Server SuiteScript and Trigger Workflows" is checked
- On Field Mapping, note that NetSuite tries to directly map all fields it can recognize. When fields are not recognized, they must be manually matched between the .csv upload file and NetSuite fields
- The recommendation is to match based on Internal ID for applicable fields. You can click the pencil to the left of the mapping to change to internal ID, if you included that information on the import
- The recommendation is to match based on Internal ID for applicable fields. You can click the pencil to the left of the mapping to change to internal ID, if you included that information on the import
- Then, run the import.
- To view the status of the upload, select "Import Job Status" in the Confirmation banner or navigate to Setup > Import/Export > View CSV Import Status
- When complete, the status will change to complete and show the records imported successfully
- In the event of a failed upload, review the logs for the specific reasons, make necessary updates, and repeat the above steps
- You can review your NetCash Bank Accounts via NetCash > Setup > Bank Accounts or alternatively, to see it in a list view, you can type in NetCash Bank Account into your global search bar and navigate to Page: NetCash Bank Account