Statements Improvements in 7.3.16+

With the latest release of MacPractice, we've made some leaps forward in resolving some standing issues with Statements that have surfaced in later 7.0 and early 7.3 builds of MacPractice. Many offices have reported several issues of varying severity, and we are optimistic that this latest build of MacPractice will vastly improve your experience with Statements.

However, for many offices, this will require reverting changes that had been made as temporary workarounds. This is also a good time for your office to evaluate how you want your statements configured to meet the needs of your office. This article is intended to assist you with this process. If you have any questions, concerns, or you would like some assistance you can always call MacPractice Support at 877-220-8418, or reach out to support via popping the bubble in MacPractice or clicking the "Have a question? Ask Now" link in the lower right of the HelpDesk.

New Help Desk Resources
With this new release, we also are releasing a few additional resources to assist with configuring Statements Manager, as well as a thorough list of all preferences that can impact how your statements print. Printing Statements from the Ledger is still straightforward; simply choose the desired option from the Print Menu.

New Preference added

In 7.3.16, we have added a new Preference called "Print Payments Applied to Charges Outside The Date Range" that has an impact on how the Previous Balance line item is treated when dealing with charges that fall outside the statement date range, but a payment applied to said charges is WITHIN the date range. Follow the link for more information.

Issues and Workarounds

This is not a comprehensive list. If you need assistance with an issue not listed below, please contact MacPractice Support.

Running Balance in Statement Forms
Issue: One of the larger issues was that the running balance included on several statement forms would often be disrupted by charges or payments made outside of the statement date range. This is the 'Balance' column often seen on several statement forms, such as...

  • Statement 5 Column (and variants)
  • Statement CC
  • Statement CC Tooth and Surface
  • Statement Code and Diagnosis (and variants)
  • Statement Expected Insurance
  • Statement FC CC
  • Statement Pending Insurance

The running balance in Statements is now corrected.

Workaround to revert: If you were previously using one of these forms, MacPractice Support likely instructed your office to utilize a Statement 4 Column form, as this style of form does not include a running balance. It is safe to switch back to one of the above listed forms. You can change the default form that prints in the ledger by navigating to MacPractice Menu > Preferences > Forms > Account Statement/Incident Statement. In the drop down menu, select the desired form.

To change the form that prints in the Statements Manager, navigate to Managers > Statements, and at the bottom middle of the window, there is a Forms drop down menu that will allow you to select your desired form.

Finance Charges 
Issue: Some offices have experienced MacPractice unexpectedly quitting when assessing finance charges via Statements Manager for outstanding charges or an unapplied amount outside of a statement's date range. MacPractice Support has been instructing offices to either disable Finance Charges, or to selectively ensure those accounts with charges or unapplied amounts outside of the date range did not have "Charge F.C." checked when printing statements.
This issue has now been corrected.
Workaround to revert: You can now enable Finance Charges by navigating to the Finance Charges tab in the Statements Manager and checking the Finance Charges checkbox. While you can still selectively choose which accounts receive Finance Charges now via the 'Charge F.C.' checkbox, you now do not NEED to exclude accounts that met the above criteria.

Incident Statements Printing Full Account Balance
Issue: When printing an incident statement, it is often desirable to only print a specific set of charges or to only print the current incident and have the total reflect the items printed, not the account balance. There was an issue that was causing the account balance to print on an incident statement, which was preventing offices from having that finer control in what balances printed on their incident statements.
This issue has now been corrected.
Workaround to revert: There was no easy workaround for this situation. One temporary solution for offices that absolutely needed to control the balance on a statement was to "hard-code" a statement form to print a custom number in the balance field. If your office needed this kind of workaround, please reach out to MacPractice Support to have them revert this change. Alternatively, you can simply switch back to one of the default forms, and they should perform as expected. 

Ledger Items Printing Out of Order on Statements
Issue: Oftentimes an office will want charges to print in a specific order, and a statement should reflect the order of the ledger. This way there is a relative amount of control in how items are listed, as you can adjust the order in which transactions are posted. However, there was an issue where statements would not necessarily reflect the order in which transactions are listed in the ledger.
This issue has been corrected.

Workaround to revert: None. 

Was this article helpful?
1 out of 1 found this helpful