NetCash Transaction CSV Import Tool
Overview
The NetCash CSV Upload Tool allows users to manually upload bank transactions in cases where the bank feed connection is unavailable. Users can download bank transaction data as a CSV file from their banking institution and easily upload it directly into NetCash, ensuring bank activities are recorded and up-to-date within the system. Below is a walkthrough of the CSV import tool, including instructions to make your import successful.
Temporary Manual Uploads
If transactions have already been imported by a bank connector (e.g., Finicity or Plaid) but you need to temporarily switch to manual uploads for a given period, you will need to do the following:
Navigate to the NetCash Bank Institution page by searching "NetCash Bank Institution" in your global search bar. Edit the appropriate institution and override the Provider field from "FINICITY" to "MANUAL." You may proceed with importing transactions. Later, when ready to switch back to the Connector, perform the following:
Navigate to the NetCash Bank Account record(s) by searching "NetCash Bank Account" in your global search bar. Edit the appropriate account(s) and update the "Last Manual Entry Date" to the last transaction date of the most recent import. Then, go back to the NetCash Bank Institution page to switch the Provider from "MANUAL" back to "FINICITY."Click here to view this walkthrough in full screen.
Key Assumptions
- The user has already downloaded a CSV file of bank transactions from their financial institution.
- The bank institution and associated bank accounts have already been configured in NetCash.
- The user making the input will need the correct permissions. The CSV Import uses the NetCash Import and NetCash Import Template Custom Record permissions.
Step by Step Process
- Navigate to CSV Upload
- Go to NetCash > Setup > Import Bank Activity.
- Select Bank Institution and Account
- Choose the relevant Bank Institution from the dropdown.
- Optionally, select the specific bank account, if uploading for a particular account. If you are uploading transactions across multiple bank accounts, leave this field blank.
- Optionally, select the Run Automation Rules checkbox if you would like your automation rules to run after the import is complete. By default, when using CSV imports, NetCash Automation Rules are not scheduled to run. Rules will run only if this checkbox is checked.
- Set Header Rows and Date Format
- Indicate if the file includes a header row, and if so, specify the header row number.
- Select the Date Format that your CSV import follows. Note that a dash "-" and a slash "/" are interchangeable. "DD/MM/YYYY" will work for "DD-MM-YYYY"
- Upload CSV File
- Click to drag and drop your file or browse and upload your CSV file.
- The tool will display the first few rows of the file for preview, allowing users to verify the columns they want to map.
- Map Fields
- Field mapping is a critical step to ensure complete and accurate data. Please read the following carefully.
- NetCash attempts to auto-map fields in the CSV file to NetCash fields. You may adjust field mappings by double-clicking any field to modify it to the correct field.
- NetCash will ignore any columns in the file where the header row field is blank.
- If additional fields are desired beyond the available NetCash fields, you can add them via these instructions.
Required fields include:
- Name
- Date
- Amount or Debit/Credit
- Account Name or Account Text (if a bank account is not selected from the dropdown list)
When mapping the header column in the NetCash CSV Import Tool, you will see a blue border appear in the cell you have double-clicked to edit, like the image below. After setting a field, in order to save, you need to click somewhere else in the table so that the blue border disappears.
6. Configure Transaction Details
- Transaction ID: If the CSV includes a transaction ID, map it accordingly. Otherwise, NetCash will assign a unique transaction ID to each transaction. If your bank does not give you a transaction ID in your CSV transaction download, then you will need to ensure you are not importing duplicate transactions as there will be no way for NetCash to know if something is a duplicate because each imported transaction will receive a different transaction ID if assigned by NetCash.
If a transaction is subsequently uploaded with the same transaction ID as a previously uploaded transaction, then NetCash will update the initial transaction with the new information and data from the subsequent transaction.
7. Template Setup (Optional)
- Templates streamline future uploads by saving mapping configurations. For repeat imports, create a template by selecting Import and Create New Template from the dropdown icon next to the import button.
- To update an existing template, choose Import and Update Template.
- If no templates are created, field mapping must be reconfigured for each new upload.
8. Finalize Import
- Click Import to upload the transactions into NetCash.
- After clicking import, the processing page will show as pending, then processing, then complete.
- Any transaction lines with errors will show in red with an error message.
- Please note that any transactions without errors import successfully, even if certain transactions error out. You will need to correct and re-upload any transactions that had errored out. Alternatively, you can delete the entire import and re-upload (see instructions below).
- To review imported transactions, navigate to the Manual Match page or Bank Activity Report.
Undoing a CSV Upload
If erroneous or duplicate data is imported, it can be removed.
Prerequisite: Please note that the user needs Full permission on NetCash Import to perform the following steps:
- Navigate to the Bank Imports Report
- Go to NetCash > Reports > All Reports > Bank Imports Report.
- Delete the Import
- Select the recent upload, click Permanently Delete Bank Activity, and confirm by typing CONFIRM when prompted.
- This deletion is irreversible, so please review the report before confirming.
If a transaction from a previous CSV import has already been matched and a user tries to delete that import, then the other transactions of the import that are not matched will be deleted, but the matched transaction will need to be unmatched before it can be deleted.