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?
Delete a Statement Batch
Description
Dunning/Statement Count
Dunning is the process of businesses communicating with customers in an effort to collect money owed for goods and/or services provided.
Example of Dunning: The Practice sends the Patient's Guarantor a Statement (paper or electronic) communicating the amount of money owed to the Practice with the expectation of payment from the Guarantor.
System Logic: The Dunning Message Count is determined by your Statement Profile setup and whether the Guarantor makes a Payment. The Dunning Message Count determines the Message that is sent on the Statement.
Example: The Dunning Count starts at zero and increases by 1 on each Statement Run. On the first run, the Guarantor gets Dunning Message 1; on the second run without receiving a payment, the Guarantor gets Dunning Message 2, etc.
- Select No Dunning Limit to continue to send Statements for Patient balances indefinitely.
- If you have set up Dunning Messages, the last Dunning Message will display on Statements that exceed the number of Dunning Messages set up.
- Example: You chose the option for No Dunning Limit, and three Dunning Messages have been set up. You have already sent three Statements and are now sending the fourth. The third Dunning Message will be sent on the fourth Statement and all subsequent Statements.
- If the No Dunning Limit option is not selected, the number of Dunning levels created on this screen will determine the maximum times a balance will be billed without an adequate payment (see the smart tip next to Payment Rules).
- Once the highest defined Dunning Level has been reached on an Encounter, when Statements are next batched the Encounter(s) will go into the Pre-Collections Worklist, instead of the Statement batch.
- See "Why is an Encounter Included on a Statement After Reaching Max Dunning?" below for more information on when Encounters may still be included in Statement Batches.
Why is an Encounter Included on a Statement After Reaching Max Dunning?
- An Encounter may still appear on a Statement after reaching its maximum Dunning Count due to how Statements are grouped during processing. After the Max Dunning is reached:
- The Dunning Count will not increase beyond that limit.
- It may still appear on a Statement when grouped with other Encounters that have a balance, but will not be sent as a standalone Statement.
- Additionally, the ability to reset a dunning level when partial payments are received means that the number of actual Statements sent can exceed the Maximum Dunning Level defined in the Statement Profiles.
History
Hold
Invoice Batch
Last Billed
Print/View Statements
Remit Address
Statement Batch
Statement Profile
Test Statement Batch
Upload