NetCash Automation Rules - CSV Import
Overview
NetCash automation rules can be created, edited, and tidied up in bulk using a CSV file. This is useful when:
- Setting up many rules at once during implementation
- Editing fields on many rules at a time
- Moving a finished rule set from sandbox to production
We will walk through each use case below.
Prerequisites
- Bank accounts must be set up with the required fields.
- At least one automation rule group must be created.
- NetCash must be on version 2026.1.50 or later. To check which version you're on, visit this site. To request an upgrade, contact Netgain Support at support@netgain.tech.
Tip for Success
Before importing automation rules, the user should be familiar with how automation rules work in NetCash. If you haven't built a rule through the UI yet, do that first so that you have context for all the rows and fields in the CSV.
Importing rules for the first time
Consider Volume
We recommend the CSV import workflow only if importing 20 or more automation rules at once. Otherwise, it is more easily done in the UI directly.
To import rules, follow the instructions below.
- Navigate to NetCash > Setup > Import Automation Rules.
- Select Download CSV Template in the top-right corner. Save the template somewhere you can find again.
- Open the template.
Note
The CSV doesn't have one row per rule. Each rule becomes a small group of rows: one for the rule itself (its name, status, tolerances) plus one row for each filter, matching criterion, and template line on the rule. All the rows that belong to the same rule share the same rule name, and that's how the system knows they go together. Keep this in mind when you're looking at the CSV for the first time - the file looks longer than you'd expect.
4. Replace the example rules with your own. Keep the column headers exactly as they came; just change the values underneath. If a column doesn't apply to your rule, leave it blank.
5. Save the file as a CSV.
6. Back on the import page, drag and drop or select your file, and take a look at the preview. The preview shows what the import will create and lists any errors before anything is saved.
7. If the preview looks right, run the import.
Editing rules in bulk
To make changes to existing rules in bulk, the easiest path is to export, edit, and re-import rules.
- Navigate to NetCash > Reports > All Reports > NetCash Automation Rule CSV Export. This export contains all automation rules and associated criteria.
Note
The CSV doesn't have one row per rule. Each rule becomes a small group of rows: one for the rule itself (its name, status, tolerances) plus one row for each filter, matching criterion, and template line on the rule. All the rows that belong to the same rule share the same rule name, and that's how the system knows they go together. Keep this in mind when you're looking at the CSV for the first time - the file looks longer than you'd expect.
2. Download the file.
3. Make the desired changes and leave all other fields the same.
4. Save as a CSV file.
5. Navigate to NetCash > Setup > Import Automation Rules and import your file.
Note
The exported file already has each rule's child_id filled in. That ID is what tells the system you're editing existing rules, not creating new ones. Don't clear or change the rule ID column - if you do, the import will create duplicates.
Transferring rules from sandbox to production
Once you've finished building and testing your rules in sandbox, you can move them to production using the same CSV import.
- In sandbox, export the rules by navigating to NetCash > Reports > All Reports > NetCash Automation Rule CSV Export.
- Download the file.
- Check every NetSuite value in the file (accounts, vendors, customers, departments, classes, locations, tax codes, groups) against your production environment. Anything missing or named differently in production has to be fixed in the CSV before importing - the import does not create missing NetSuite records.
- Clear the rule ID column. Sandbox rule IDs don't match anything in production and leaving them in place will cause the import to fail or behave unexpectedly. Clearing them tells production to create fresh rule records.
- Save the file as CSV.
- Log into production, navigate to NetCash > Setup > Import Automation Rules, and import the CSV. Preview first to catch any leftover sandbox-specific values.
Do you already have rules in production?
If production already has automation rules and you're bringing more over from sandbox, decide first whether you're adding to or replacing the production set. The import doesn't deduplicate by rule name - running it as-is will create new rules side-by-side with the existing ones, even if the names match. If you want to replace the existing production rules, deactivate or remove them through the rule list first.
