Dunning Count vs Statement Count

Dunning Count vs Statement Count

Dunning Count vs Statement Count


What is the Dunning Message Count?

Dunning Message Counts are used as a measure of the delinquency of a Patient balance and to drive collection activities based on the level of delinquency.

  • The Count is based on the unpaid Encounter Balance that has the highest Dunning Count.
  • Example:
  • Encounter 10 (DOS 01/25/2025) has an unpaid Patient Balance and has Dunning Count 2 (Two Statements have been sent with no Payments received).
  • Encounter 23 (DOS 03/01/2025) has an unpaid Patient Balance and has a Dunning Count of 1 (One Statement has been sent with no Payments received).
  • The next Statement will display Dunning Message 3 based on Encounter 10 because it has an unpaid Balance with the highest Dunning Count.
  • Dunning Counts are much more effective than an aging-based process for managing Patient Collections.
  • Example: A balance that is 180 days old where regular payments are being made may be considered acceptable, while a 90-day balance where no payments have been made is a problem.
  • This nuance is handled effectively using Dunning Message Counts.


Difference between Statement Count and Dunning Message Count

What is the Difference between the Statement Count and Dunning Message Count?

  • Statement Count: The physical number of Statements that have been sent to the Guarantor to collect a balance.
  • Dunning Message Count: Represents the current Dunning Level and may not be the same as the Statement Count.
  • This determines the dunning message printed on the Statements, and drives the letters and Pre-Collections processes.
  • Each time a Statement is sent and a Payment is received that meets the Payment Rules, the Dunning Count is set back by 1 or zero.
  • Example: Statement and Dunning Count is 0.
  • A Statement is sent
  • The Statement Count and the Dunning Count are now 1 (Dunning Message 1 displays on the Statement).
  • A Payment is received and posted that met the Payment Rules, but is not paid in full.
  • The Statement Count is 1, and the Dunning Count is set back by 1, which still makes it zero again.
  • A Second Statement is sent for the remaining balance.
  • The Statement Count is now 2, but the Dunning Message Count is 1, which means the second Statement displays Dunning Message 1 (the same as the first Statement).


Learn More

Reset the Dunning Count

    • Related Articles

    • Reset the Dunning Count from the Pre-Collections Worklist

      From the Pre-Collections Worklist, choose the Encounters. Select Set Action. From the Choose Action dropdown list, select Reset Statement Counter to X. Select Run. Select Apply Action. Select Run. Learn More What is the Dunning Count ...
    • Statement/Invoice FAQs

      Statement/Invoice FAQs Balance Forward on Statements/Invoices How do I show/exclude Balance Forward on Statements? How do I show/exclude Balance Forward on Invoices? Batch Why did a Statement not Batch? Statements/Invoices Troubleshooting Delete a ...
    • Reset the Dunning Count

      Reset the Dunning Count from the Receipt Posting Screen On the Receipt, choose Manually Post to manually update the Dunning message count. Select Save [F2]. Reset the Dunning Count for the below Encounters to: Choose the new Dunning Count from the ...
    • Statement Batch Overview

      Statement Processing Statement files are processed after 1:00 PM Eastern. Any Statement files received after this time will be processed the following workday. Statement Files are NOT processed over the weekend. Statement Batch Dashboard Details: ...
    • Statement Exception Batches

      For the System to create Exception Batches, the System Setting must be set to Yes, which is the Default. (To change: Admin > System Settings > Statements > EXCEPTIONSBATCH) The Exception split option provides easy accessibility to Statements that ...