Differences

This shows you the differences between two versions of the page.

--- eclaim_processes [2020/01/16 14:25] – lisa.maloney
+++ eclaim_processes [2020/06/22 11:24] (current) – lisa.maloney
@@ Line 2: / Line 2: @@
 This section of help will explain how to load an eclaim using the eclaim template, and the checks the system performs to prevent duplicate eclaim loads.
+Another feature of the eclaim process is the ability to have eclaims Auto Submit and/or Auto Approve.  This setting is done at the company level and companies with this setting enabled will flow through the eclaim process automatically.
+Auto Submit: if a company has this enabled, any eclaim loaded for this claimant will move from draft to submitted and then into a Pend, Hold, Evaluation status.
+Auto Approve: if a company has this enabled, any eclaim loaded for this claimant will be auto approved once the claim is submitted (either via auto submit or manually).
+Settings at the company level:
+{{:pasted:20200622-112349.png}}
 -----
@@ Line 150: / Line 159: @@
 {{:pasted:20200116-142434.png}}
+-----
+**__Eclaim Load Duplicate Checking__**
+Process to determine duplicates - Eclaim Load:
+. Check for possible Duplicate based on Header information (checks against both what is in the eclaim import tables and what is in the system for claims)
+  * Claimant
+  * Claimant Name
+  * Invoice Number
+  * Start Date
+  * End Date
+  * Total lines (Note: this is rarely if ever loaded as everything is calculated based on lines loaded)
+  * Total Requested Amount (Note: this is rarely if ever loaded as everything is calculated based on lines loaded)
+. Check line level for duplicates for those header rows that have been determined to be possible duplicates
+  * Each line is checked for duplicates within eclaim import to prevent loading of duplicates  - it requires that all lines match exactly to be considered a duplicate
+. Exact Duplicates are tagged and ignored preventing the load of the invoice from progressing any further
+Recap:  If we load (2) files they contain the same invoice, but they are not exact matches at the header level, they will not be flagged as a possible duplicate, add into that the change of the claimant to the invoice that you are doing, the second file would not see a possible duplicate in the system either because the claimant being loaded is not the one on the invoice that it should see as a duplicate.  Everything for eclaim is based at INVOICE level not claim level.
+-----

Telus TPM Documentation

User Tools

Site Tools

Differences

Page Tools