Pending Void

Claims flagged as Pending Void in the Claim Submission Maintenance form:

• Are marked with an asterisk in the Remittance form.
• When a status of Paid or Partially Paid is applied manually or from an 835, and no action is selected, the Pending Void claim is automatically set with a Create Void Claim action.

A standard scenario for using Pending Void follows:

1. The claim is created and submitted, so the balance is on Revenue and A/R.
2. On the Claim Submission Maintenance form, the checkbox Is Pending Void is selected.
   • If that box is unchecked, WOJ GLs are deleted or reversed.
3. The claim is then paid, and the GL transactions are standard.
   • Debit Temp-Unallocated, resulting in a positive balance.
   • Credit A/R, resulting in a negative balance.
4. The Void claim is submitted, so no GL transactions are added.
5. The previous payment is withdrawn, which is recorded as Void Accepted.
   • Credit Temp-Unallocated, resulting in 0 balance.
   • Debit A/R, resulting in 0 balance.

A scenario when a claim marked Pending Void is later denied:

1. The claim is created and submitted, so the balance is on Revenue and A/R.
2. On the Claim Submission Maintenance form, the checkbox Is Pending Void is selected.
3. The claim is denied by the payor.
   1. Deselect the checkbox Is Pending Void.
   2. Remove or reverse WOJ GLs.
   3. The claim is left with a balance.

Download the PendingVoid.docx document to learn more about that feature introduced to myEvolv CS v 8.5.15