Customer Match Criteria

The Automated Cash Application feature matches customers to imported bank lines based on the following criteria:

Match Type	Conditions	Details
Exact Match	The imported bank line must specify either of the following in the appropriate fields: Customer name Customer ID Invoice number or numbers Note: In a CSV file, invoice numbers must be specified in the Invoice Number column. If there are multiple invoice numbers for a single bank line in a CSV file, certain formatting requirements apply. For details, see Preparing CSV Files for Import.	If the conditions for an exact match are met and the customer or invoice information in the bank line is correct, NetSuite displays the associated customer's name. If the bank line contains incorrect customer or invoice information, an exclamation mark icon displays next to the field in the Customer column. To see what's incorrect, hover over the icon. If the bank line specifies invoice numbers for different customers, the system identifies the customer of the first invoice and displays an exclamation mark icon. To view other invoices, select the appropriate customer. Note: The Automated Cash Application feature doesn't support multiple customers per bank line.
Preferred Match	You must have a customer mapping rule the system can use to identify a customer. The rule must contain values similar enough to the Payor and Memo fields in future imported bank lines for NetSuite to identify the right customer. The system compares rule values to future imported bank lines by removing white space, numbers, special characters, and capitalization. To create a customer mapping rule, see Adding or Changing a Customer. To view customer mapping rules, see Viewing Customer Mapping Rules.	When NetSuite can't achieve an exact match, it uses any existing customer mapping rules to try to identify a customer. Customer mapping rules let the system remember a customer selection for similar imported bank lines, based on the Payor and Memo field. In the bank line, NetSuite looks for payor and memo values similar to those in the rule to map to the right customer. NetSuite checks the payor value first and then the memo value.
Partial Match	You have a bank line with a payor or memo value similar enough to a customer name for the system to identify that customer as a potential match.	If NetSuite can't perform an exact or preferred match, it performs a partial match. A partial match uses a similarity algorithm to compare the Payor and Memo fields in incoming bank lines to customer names. The algorithm uses both characters and word length to try to identify a customer for the imported bank line. If the wrong customer is selected, which can happen if customer names are too similar, select the right customer and create a mapping rule.

Match Type

Conditions

Details

Exact Match

The imported bank line must specify either of the following in the appropriate fields:

Customer name
Customer ID
Invoice number or numbers

Note:

In a CSV file, invoice numbers must be specified in the Invoice Number column. If there are multiple invoice numbers for a single bank line in a CSV file, certain formatting requirements apply. For details, see Preparing CSV Files for Import.

If the conditions for an exact match are met and the customer or invoice information in the bank line is correct, NetSuite displays the associated customer's name.

If the bank line contains incorrect customer or invoice information, an exclamation mark icon displays next to the field in the Customer column. To see what's incorrect, hover over the icon.

If the bank line specifies invoice numbers for different customers, the system identifies the customer of the first invoice and displays an exclamation mark icon. To view other invoices, select the appropriate customer.

Note:

The Automated Cash Application feature doesn't support multiple customers per bank line.

Preferred Match

You must have a customer mapping rule the system can use to identify a customer. The rule must contain values similar enough to the Payor and Memo fields in future imported bank lines for NetSuite to identify the right customer. The system compares rule values to future imported bank lines by removing white space, numbers, special characters, and capitalization.

To create a customer mapping rule, see Adding or Changing a Customer.

To view customer mapping rules, see Viewing Customer Mapping Rules.

When NetSuite can't achieve an exact match, it uses any existing customer mapping rules to try to identify a customer. Customer mapping rules let the system remember a customer selection for similar imported bank lines, based on the Payor and Memo field.

In the bank line, NetSuite looks for payor and memo values similar to those in the rule to map to the right customer. NetSuite checks the payor value first and then the memo value.

Partial Match

You have a bank line with a payor or memo value similar enough to a customer name for the system to identify that customer as a potential match.

If NetSuite can't perform an exact or preferred match, it performs a partial match. A partial match uses a similarity algorithm to compare the Payor and Memo fields in incoming bank lines to customer names.

The algorithm uses both characters and word length to try to identify a customer for the imported bank line. If the wrong customer is selected, which can happen if customer names are too similar, select the right customer and create a mapping rule.

If NetSuite can't identify a customer, the Customer column field isn't populated. In this case, an exclamation mark icon always displays next to the field. Blank Customer column fields usually occur for non-payment bank lines that don't specify customer info, like deposits. To view error details, hover over the icon.

If the Customer column field is blank, select a customer. For details, see Adding or Changing a Customer.

If no customers are available from the list, see Troubleshooting Missing Records from the Customer.

Related Topics