Free Webinar Series: Part 1 of 8: Master the Basics, Tuesday Tuesday, September 11th, 2018 1-2PM PDT

Blog: Daisy News

News, data, & insights about workers' comp billing

header_illustration_blogDaisyBill

The Essential Guide to Correct e-Billing Processing

September 4, 2014 by Catherine Montgomery

In advance of today’s webinar on e-billing, I’m posting an example of e-bill processing that we will be using in the webinar.  This is the second time we’re giving this webinar because there’s been so much interest and because, let’s face it, e-billing is tough to get right unless you know what you’re doing.

The screenshots show the history of an actual original e-bill that we submitted to Sentry Insurance, which in this example did a great job of electronic claims processing.

This history shows what DaisyBill submitted, and when, as well as the deadline by which Sentry must send an electronic EOR.    

Next, the history shows Sentry’s clearinghouse, StoneRiver P2P, accepting the original bill submission, one day after DaisyBill transmitted the bill, and then forwarding it to Sentry.  StoneRiver and Sentry observed the mandated timeline of two days.

Finally, eight days after DaisyBill submitted the bill, Sentry sent back an electronic EOR.  This is fully nine days before the deadline of 15 working days, so good on them!  Note that if the original bill is electronic, then the EOR must also be electronic.

In a later post, I’ll dissect the electronic EOR and the subsequent electronic Second Bill Review.

For more information on e-Billing for work comp, visit the Webinar Library:

WEBINARY LIBRARY

Search results for:

About Us

DaisyBill is a trusted authority on workers’ comp billing. Thousands of work comp professionals attend our webinars and state agencies and professional organizations turn to us for our expertise. We created this blog to help everyone involved in workers’ compensation; sharing news, tips, and data of interest to the community.

Drop us a line with any news you would like us to share or any issue that concerns you.

intercom_chat_bubble_icon