NetCash Merchant to Entity Alias Mapping
Overview
A common rule that users create in NetCash is to match a transaction with the amount and date are the same and the Merchant on the Bank Transaction matches an Entity on the NetSuite Transaction. This rule is very helpful, however, the Merchant that appears on a Bank Transaction often does not exactly match the name of an Entity in NetSuite. NetCash solves this by using Entity Alias mapping.
Entity Alias Mapping
The Entity Alias Mapping can be found by navigating to NetCash > Setup > Entity Mapping. To create a new Entity Mapping, click New Row. On this row, select the NetSuite Entity that you would like to add mapping for. After selecting the NetSuite Entity, click into the cell in the Entity Alias column next to the NetSuite Entity. Here you will put in the variation(s) of values that the NetSuite Entity may appear on your Bank Transactions as Merchant.
In the example below, you can see that we have Entity Mapping for the NetSuite Entity "Zoom." On our Bank Transactions Zoom often appears as the Merchant "Zoom" or "Zoom Pro." This Entity Mapping ensures that if NetCash sees a Bank Transaction with the Merchant "Zoom Pro" it will treat that as if it is the NetSuite Entity Zoom for any NetCash Automation Rules.
Notice that for a few of the Entities in the screenshot below, we have multiple Entity Aliases. If a NetSuite Entity appears in many variations of Merchant on your Bank Transactions, you can add multiple Entity Aliases by separating each value in the Entity Alias cell with a comma.
An Entity Alias is only needed if the Merchant field differs from what is in the NetSuite Entity name. You do not need to setup an Entity Alias for every NetSuite entity, only for the Merchants that appear on Bank Transactions with values that do not exactly match the NetSuite Entity name.