Skip to main content
Looking for older announcements? See all past updates.

​
Bug fixes

​
Insurance claims are no longer auto-submitted while the Date of Service is still in the future

When a clinician created an OON Pay or Thrizer Pay charge with a Date of Service of tomorrow, Thrizer previously sent the claim to the clearinghouse right away. The clearinghouse rejects any claim whose service date is in the future, so the claim came back rejected and was left in a durable failed state that would not retry on its own — even after the session date arrived. Thrizer now holds these claims at creation instead of auto-submitting them. The claim is created normally and stays available for submission once the Date of Service is no longer in the future. Who this affects: clinicians who create OON Pay or Thrizer Pay charges for the next day. See Date of Service and payment type. Why it matters: these claims used to need manual intervention to un-stick. They now flow through the normal submission path on the day of service and no longer arrive in your queue as failed. What to do: nothing new for new charges. If you have a claim from the last two weeks that was rejected with “From Date is invalid, date is in the future,” contact Thrizer support at help@thrizer.com to have it resubmitted.

​
Clients page no longer crashes for practices with a legacy insurance record

A small number of clinicians saw a “Something went wrong” error when opening the Clients page. The crash was caused by a legacy insurance record on one client that carried a placeholder plan value; that single record was taking down the whole roster load. The Clients page now ignores placeholder plan values instead of crashing, so the roster loads even when one client has legacy data on file. Who this affects: clinicians who were unable to open their Clients page because of a repeated “Something went wrong” error. What to do: reload the Clients page. If you still see the error, contact Thrizer support at help@thrizer.com.