Support for NetSuite’s Multi-Subsidiary Customer feature
If you use NetSuite OneWorld, prior to the 2018.1 release, NetSuite allowed users to assign a customer record to only one subsidiary. With the 2018.1 release, NetSuite is introducing the Multi-Subsidiary Customer feature that permits you to share a customer or sub-customer record with multiple subsidiaries.
With this release, CAM has been enhanced to also support the Multi-Subsidiary Customer feature. The following scenarios explain the CAM functionality in different situations:
- When the subsidiary information is present in the bank file and identified by the connector
In this scenario, the payment will be created for a subsidiary coming from the bank file regardless of whether it is a primary or a secondary subsidiary.
- When subsidiary information is not present in the bank file but exists in invoice pertaining to a customer
In this scenario, the payment will be created for a subsidiary mentioned in an invoice regardless of whether it is a primary or a secondary subsidiary.
- When subsidiary information is not present in either the bank file or if there are no invoices in the transaction
In this scenario, the payment will be created against the primary subsidiary associated with the customer.
Note: When the FIFO auto-application of payments to invoices feature is enabled, CAM will create a payment for a subsidiary coming from the bank file and the payment will only be applied to the invoices belonging to the bank file subsidiary in a FIFO manner. When subsidiary information is not present in the bank file, a payment will be created against the primary subsidiary associated with the customer and auto-applied to the invoices belonging to the primary subsidiary only.
Customer deposits and write-offs will be created against the subsidiary for which the payment is being created regardless of whether it is a primary or a secondary subsidiary.
New advanced search logic to improve match-rate
Prior to this enhancement, the customer name from the bank file was only considered for payment creation when the exact customer match was found in NetSuite. In real-world user may not enter the customer's name that exactly matches with the name of a customer in NetSuite. For example, the customer name in the bank may be “ABC LTD” while in the NetSuite it may be “ABC INC”. This impacted the customer identification match rate to identify the customer in NetSuite.
To improve the customer match rate between the bank file and NetSuite when the customer name is not exactly matching, a new advanced search algorithm has been introduced in CAM. This new search logic helps in identifying the possible customer in NetSuite when the customer name in bank file does not exactly match. A threshold value determines the degree of search results with 0.1 being highest and 1 being lowest.
Increased limit for customer advanced search
The customer advanced search uses fuzzy logic to identify customers by name. If a direct match is not found, the search algorithm searches for customer records with similar names, and the limit for returned results increases from 2000 to 8000.
Note: This search is applicable only for the Customers that have an Invoice open for the last 90 days (from the date of processing). The results returned are approximate matches, so you should carefully review the matches found using fuzzy search logic.
Limitation: This search is limited to get the details of the Customers that have an Invoice open for the last 90 days (from the date of processing).
Navigate to Bank File to NetSuite > Settings > Advanced Settings > Advanced Search for Customer to enable or disable the advanced search, and set the threshold value. By default, the threshold is set to the recommended value of 0.1.
Note: The results returned are approximate matches and we recommend users to review the matches found using this advanced search logic.
Scenario 1: Exact Match
The advanced search logic is used by CAM when the connector is unable to find a matching customer mentioned in the bank file with the customer in NetSuite. The connector will not look for another possible matching customer in NetSuite when the exact match is available. The following screen demonstrates the same in NetSuite:
In this case, the Customer Identification Method populates as Exact Match, and no Approximate Matches for Customer fields information returns. The matching NetSuite customer is added to the Celigo Cash App Transaction record.
Scenario 2: One match found using customer advanced search
If there is no exact match on the customer name between the bank file and NetSuite, and you get only one search result using the advanced search, the connector automatically sets that customer as the NetSuite customer.
In this scenario, the connector doesn't populate the Approximate Matches for Customer field, but the customer identified using fuzzy logic is added into the Celigo Cash App Transaction record and the Customer Identification Method field populates as Approximate Match.
Scenario 3: Multiple matches found using customer advanced search
In the case when there is no exact match between customer name in the bank file and NetSuite, and you get multiple search results using the fuzzy search then the connector only displays possible matches in the Approximate Matches for Customer field.
In this scenario, as you can see in the following image, no information is populated by the connector in the NetSuite Customer and Customer Identification Method fields. When multiple results are found, the results are displayed in Celigo Cash App Transaction record > Celigo > Approximate Matches for Customer. You can manually edit the transaction and add the right customer based on fuzzy search suggestions.
Support for ignoring transactions with zero amount
A new checkbox, Skip Zero Amount Transactions, has been added to the Bank File to NetSuite > Settings > Advanced Settings. When enabled, this checkbox allows you to filter out any zero amount transactions from the bank file to be processed in NetSuite.
Note: The checkbox is enabled by default.
You can disable the checkbox, to create payments for transactions with zero amount in NetSuite.
View Bank Name at the Batch level
The Celigo Cash App Batch record in NetSuite has been enhanced to display the bank name associated with the Lockbox/Account Number. This will enable the user to easily sort or search batches across Banks and is helpful when multiple users in an AR team audit or verify the transactions.
Option to provide the absolute or percentage amount for Write Off/Customer Deposit threshold
Prior to this release, the Write Off Threshold Amount and Customer Deposit Threshold Amount fields in the File Processing tab for the Bank Transactions to NetSuite flow only accepted absolute amount as the threshold amount.
With this release, these fields have been enhanced to also accept percentage amount along with the absolute amount for which customer deposit/write off needs to be generated. For percentage, provide a number followed by the % character. For example, 10 %.
Note: You can still provide an absolute amount in this field.
Support for entering a range of transaction codes to be skipped or included for processing
In the previous CAM release v1.11.0, a new setting, Enter Transaction Codes, was introduced in the Settings> Advanced Settings section of the Bank File to NetSuite flow. This setting allowed you to enter the transaction codes that you wanted to skip for processing. For more details see, the New setting to skip transaction from bank file based on transaction codes section in Cash Application Manager | November 2017 (version 1.11.0).
In this release, the Enter Transaction Codes field has been enhanced to also support ranges of transaction codes. Enter individual transaction code(s) or range(s) separated by a comma. Based on your choice, corresponding transactions will either be skipped or included for processing from the bank file. Use '-' to indicate a code range. For example: 100, 201-299, 305.