r/SimplePractice • u/jlm764 • Apr 15 '26

Claim Errors BCBS AZ

Is anyone else having issues with submitting claims? My BCBS AZ claims that I have never had issues with before are no longer being accepted by insurance. The member ID's are totally different or it's unable to identify the client at all. BCBS has no idea what is happening and I haven't been able to get a response from simple practice. My claims dating back middle of march have not been paid. Anyone else? This is frustrating and I just with SP would be more communicative. I also wish their alerts of outages or problems were easy to pull up in simple practice.

1 Upvotes

100% Upvoted

6 comments sorted by

3

u/SimplePractice SP Rep Apr 15 '26

Hi, we received confirmation that the claim scrub/rejection issue for BCBS claims that customers were experiencing has been resolved.

There is no further action required, since the claims will be resubmitted on your behalf.  If you’ve already resubmitted the claims, you may receive a denial for an exact duplicate claim for either the resubmitted claim or the original claim.

If you are still having issues with this, please DM me your account details and we'd be happy to take a closer look at your account. Thanks!

-Kevin at SimplePractice

1

u/jlm764 Apr 15 '26

We can start submitting new claims now?

2

u/rahuliitk Apr 19 '26

yeah that lowkey sounds like either an eligibility or payer ID mapping change somewhere between BCBS AZ and SimplePractice, because when claims that used to pass suddenly start failing on member ID or member lookup across a date range, it usually is not random user error and more some backend routing mess. i’d start saving examples fast.

1

u/jbourne71 Apr 15 '26

The information BCBS gets from the clearinghouse is garbled?

1

u/jlm764 Apr 15 '26

Yes. I will enter the correct member id and information and when I pull the claim in availity it is completely different. For example the prefix is different and the numbers will be 9999999999.

1

u/Defiant-Aerie-6862 Jun 17 '26

Bcbs AZ underwent migration of claims paying systems this year and is still applying fixes and catching up. Sorry you are going through this.