Cash Application Manager (CAM) for NetSuite is built on the integrator.io iPaaS platform. Each bank/file format comes with two flows in the Integration App.
-
Environment tag: This tag identifies your environment if you have both sandbox and production environment Integration App tiles.
-
+Add Bank: Click +Add Bank to add a new bank to your existing Integration App. Use the drop-down menu to select any existing bank.
-
Associated flows list: This section holds the flows based on the file format you receive from the same bank. In this case, HSBC is sending files in both CSV and BAI2 formats.
-
Bank/file format flow list: The above image has two flows that are used by a single bank/file format. The first flow retrieves the file(s) from the bank server, and the second one creates custom data(Celigo Cash App Batch and Celigo Cash App Transaction records) in NetSuite. There are two other flows which are hidden as well.
The General tab has a Manual Upload Mode setting you can use to load the file as an input to the Cash Application Manager from your computer.
The Dashboard tab displays all jobs that ran for the last 30 days. You can use the CAM dashboard to troubleshoot any errors that occurred due to problems loading the file into NetSuite/Creating custom data.
The Connections tab displays the connections used to connect to the bank and NetSuite.
The Users tab displays the details of the users that have access to the Integration App tile along with their levels of permission.
The Notifications tab allows you to configure the notifications you’d like to receive on occurrence of following events:
-
One or more connections in the Integration App went offline.
-
An error occurred in the dashboard.
The Audit log tab displays all changes performed on the Integration App by any users at any given point of time.
CAM is an integration between the bank and NetSuite that automates the payment creation for the users abiding certain logic rules you set.
-
CAM is connected to the bank's SFTP server using the integrator.io platform and pulls the files from the server.
-
CAM then parses the files based on the parser settings you initially provide under Parser Settings, and creates custom records in NetSuite such as:
-
Celigo Cash App Batch
-
Celigo Cash App Transaction
-
Celigo Cash App Invoice
-
Celigo Cash App Credit Memo
-
-
Once these records are created in NetSuite, you create scheduled scripts in the NetSuite account that run every half hour (or whenever your customized schedule dictates).
-
These scripts retrieve all unprocessed Celigo Cash App transaction records and processes them to create customer payment records against the invoices available in the bank file.
-
Once the transactions are processed, each transaction is assigned a status according to the rules you've initially set.
-
The CAM dashboard in NetSuite allows you to validate and correct all the transactions that require attention. For more information, see Access the Cash Application Manager Dashboard.
CAM transactions can have any of the following statuses:
-
Error/Skipped
Customer identification is important when processing the transactions in CAM, especially for the transactions that do not have invoices underneath. Using the different settings available in CAM, you can easily apply the invoices to the transaction if the customer is identified.
In CAM mappings, the app looks for the exact customer name coming from the bank file to find the customer in NetSuite. Often, banks do not send the same name that is stored in NetSuite. For this reason, CAM comes with the following features to match the right customer.
-
Exact Match: A transaction gets this match method when the customer name coming from the bank file is exactly the same as the name of the customer in NetSuite.
-
MICR Match: In some cases, the bank file may not contain the customer information. In such cases, you can use this feature to match the customer with a transaction using the MICR number from the bank file. In addition to adding a customer, the Integration App also updates the MICR number for the customer of matching invoice in NetSuite if the MICR number is not present for any customer. For more details, see Match customer with a transaction using the MICR number.
-
Alias Match: This feature allows CAM to improve the match rate by learning from manual selections of customers on any unidentified transactions when a customer name is supplied in the bank file but not identified in NetSuite. For more details, see Cash Application Manager | August 2018 (version 3.0.0).
-
Approximate Match: To improve the customer match rate between the bank file and NetSuite when the customer name is not an exact match, an advanced search algorithm is available in CAM. This search logic helps identify the possible customer in NetSuite when the customer name in the bank file does not exactly match. For more details, see Cash Application Manager | August 2018 (version 3.0.0)
-
Manual Match: In cases where the customer information is either not provided by the bank or the customer name is not the same as the one in NetSuite, User updates the transaction with the right customer. These transactions are considered to fall under this category.
For more information, see Troubleshooting and FAQs.