Client Based Duplicate Logic

Transcription

1 Set-up, Configuration, and Use Client Based Duplicate Logic Step 1 of this process is setting up the rule you will use on the client table for specifying its dupe logic. Navigate Impact-> Tables-> Company Table-> Client Duplicate Rule Table From here your options are Exit, Add, Edit, Delete. 1

2 We will select Add. A new rule table will display with options for declaring what will be considered a duplicate and what will be considered a suspected duplicate. 2

3 The Duplicate Rule Code is up to 5 characters in length and is alpha numeric. Ignore these status classes allows you to skip over specified status classes when looking for dupes with this rule. Duplicate and Suspected Duplicate rule options are identical and are as follows: Client Acnt 1 Matches Existing and new accounts both have the same Client Account 1 info. Client Acnt 2 Matches Existing and new accounts both have the same Client Account 2 info. Balance Matches Existing and new accounts both have the same Referral Amount. Date of Service Matches Existing and new accounts both have the same Date of Service. Last Charge Date Matches Existing and new accounts both have the same Last Charge Date. Statement Guarantor Matches Existing and new accounts both have the Statement Guarantor Number. Medical Record Number Matches Existing and new accounts both have the same Medical Record Number. Client Fields You are able to select up to 5 of the 24 client specific fields for matching in order to provide extended flexibility. Existing Account in Class and Days in Status. There are three options to select a grouping of status classes and the number of days in status must fall between the values in order to qualify. In all cases, the logic used for the Duplicates should contain more matching criteria than the Suspected Dupe criteria. Failure to do so would result in no accounts achieving a Suspected Dupe Status. Once your rule is configured, save it. 3

4 Now exit the screen and navigate to the main Impact Screen. From there, Navigate Impact->Tables->Company Tables ->Client Table Select the client you want to add the duplicate logic to. 4

5 Once on the client, select the Linking/Duping Tab 5

6 Your first task is to decide how the dupe logic will be applied against other clients in the system. Your options are: Dupe within this Client Only -> No This option sets the dupe check to occur across all clients according the system settings. Dupe within this Client Only -> Yes this option sets the dupe check to occur within this client code only. Dupe within this Client Only -> List this option allows you to add a listing of client codes below for the duplicate checking to occur 6

7 The last step on the client table is to select your Dupe Rule. Now save the client setup. 7

8 Application of the Rule Once the rule is configured, you will load or enter new business and then navigate to the New Business Batch Window Impact-> New Debtor Processing -> New Debtor Entry You will locate your batch, highlight it and close it. 8

9 9

10 If your batch needs to be balanced, you will be prompted to do so at this time. Once balanced, you will then close the batch. 10

11 At this point, the dupe checking will occur. If there are no duplicates, the batch will simply close. If there are duplicates and/or suspected duplicates, the following message will appear: This means accounts within the new business batch have now been flagged as either a Duplicate or a Suspected Dupe. At that point, re-open the batch and you will see accounts flagged as Cls Dup (Duplicate), Cls Sus Dup (Suspected Duplicate) or blank (non-dupe) 11

12 Within the batch, you now have the option to display Dupe, Suspected Dupes, or All accounts. Your next step is to Delete the duplicates by selecting Delete Cls Duplicates, which will give you the following prompt. 12

13 Your batch will now look something like this. Now you will go back and select Cls Suspected Duplicates from the Entry Type button. 13

14 Within the batch, you will now only see Suspected Duplicates. Start with Suspect #1. 14

15 To Review what accounts are either duplicate or a suspected duplicate to this account, select the account (highlight) and click on EDIT Select (highlight) the Client Account #1 field and right click or hit tab. 15

16 A list of possible duplicate accounts will appear. You can scroll over on the bottom to see additional address information, phone numbers, tax id, drivers license and date of birth. 16

17 You can also select a name on the list, right click and choose VIEW THE DEBTOR to see the actual workcard. From there you can view any part of the work card - history, trans history, etc. 17

18 When done, choose FILE - EXIT to return to the New Debtor Detail Batch Entry screen. 18

19 Reviewing each account, you have 2 options regarding advancing to the next account. If you select Save and Next, the Suspect Dupe flag will be REMOVED and it will be staged for posting. If you select the NEXT button, the account will remain in the batch WITH the suspected dupe flag still in place. Once you complete your batch review, choose the Delete Suspected Duplicates button. You will be prompted as follows. Selected Yes and the Suspected Duplicates are removed. 19

20 You now have a clean batch ready to post. 20

21 Close your batch as before. Balance the batch with your revised total. Close your batch. 21

22 Note: You may get a new Dupe message saying there are suspected dupes in the batch. These should be the accounts you approved for posting. If you want to go back in to the batch to see these accounts they will have the suspect dupe flag on them. It is not necessary to go back into this batch again. 22

23 Post your closed batch as normal. Reporting Within the Print Queue, you will have created 2 reports during your duplicate deletion process. 23

24 The first report will contain all accounts deleted when you selected the Delete Cls Duplicates button. The second report will contain all accounts deleted when you selected the Delete Suspected Duplicates button. 24

25 Your reports will look like this. End of Client Duplicate Logic Document 25