FAQ ID # 127 |
Avoid duplicate data by matching download transactions before processing them Last Update : 2016/04/12 |
Print this FAQ |
Question / Issue |
How to avoid duplicate entries when processing downloads |
Answer / Solution |
Processing downloads (AL3 files) from carriers can be a very time saving task that can help you and your team keep your customer and policy data up to date. The problem is that duplicates can be made if you are not careful when processing your downloads. When processing downloads, you will see that the "Client" field will be either Green or Red.
To avoid duplicate entries in your database, look for the transactions with a red "Client". You can double-click on the red client name and search for a match if one was not found. In the image below (Fig. 1), double-clicking on "Velma Brown" will pull up the "Choose/Search Client" screen (Fig. 2). This will allow you to find the client by name. When you have found the client, select "OK". The screen should now have that transaction's "Client" in green (Fig. 3). When you process that download transaction, it will update the policy that you selected in the "Choose/Search Client" screen. Downloaded transactions that are of the type "Policy Change" or "Cancellation" implies that a policy already exists. These transactions should match with a record in InsurancePro in many cases. Processing "New Business" transactions when data does not match with information that may have been entered into InsurancePro as a quote or a prospect may create duplicate information as well. When processing "New Business" transactions, be aware of any information you may have already entered into InsurancePro prior to processing the download transaction. Matches are made using the following criteria:
There are nuances to matching each piece of data. This is how each piece of data is matched:
Fig. 1 Fig. 2 Fig. 3 |
Direct Link to This FAQ |
http://www.itcdataservices.com/support/IP6FAQ/?f=127 |
Tags |
Download Duplicates AL3 Match |