CAM (IO) - NetSuite v3.7.0 release notes, January 2021

What’s enhanced

Display dependent flows on the Integration App user interface

You can now find the dependent flows on the Integration App user interface that was previously available only in the backend code. These flows are auto-triggered and run in sequence by one of the existing integration flows. You can’t schedule, enable, or run the dependant flows. For more information, refer to Intro to Error Management. Following are the dependent flows:

• Bank invoice to NetSuite Cash App invoice (add)
• Bank credit memo to NetSuite Cash App credit memo (add)

For more information, refer to Understand the Cash Application Manager - NetSuite dependent flows.

Understand the MICR matching method

A new matching method “MICR” is introduced to match the customer with a transaction using the MICR number from the bank file. The MICR matched customers are shown in the “MICR match” method instead of the “Exact match.”

For more information, see Match customer with a transaction using the MICR number.

Set up email notifications for Cash App Manager

You can set up email notifications when a batch is created from the bank file and the transactions are processed. Two new saved searches are created to use the email notification functionality:

1. Celigo Cash App Batch Email Notification Setup: Using this, emails are triggered when a new batch is created from the bank file in the NetSuite.
2. Celigo Cash App Transaction Email Notification Setup: Using this, emails are triggered when all the transactions are processed into the NetSuite.

For more information, see Email notifications setup for Cash App Manager

Create transactions for inactive customers

You can now create and process transactions in NetSuite for Inactive customers. Processed transactions have ‘Error/Skipped’ status and payments are not created for these transactions automatically but you can create them manually.

For more information, see Create transactions for inactive customers.

What's fixed

Manually created payments of transaction record is not getting unlinked when transaction status is changed

When a customer creates the payments manually and if you change the status on the transaction record we are not deleting the linked payments.