Skip to main content

Troubleshooting Failed Insurance Eligibility Checks

Work through patient eligibility failure issues and resolve errors with common troubleshooting steps

If an eligibility check is failing or returning an unexpected result, it's typically caused by a mismatch between your practice management software (PMS) and what the payer has on file. Find the symptom that matches what you're seeing below, or work through all of them in order, most eligibility issues are resolved by the end of this article.

Eligibility check fails or returns wrong information due to a demographic mismatch

Cause: The Member ID, date of birth, name, or subscriber relationship in your PMS doesn't exactly match the payer's records. Payers match this information character-for-character, so even a small difference, ike a missing leading zero, will cause a failure.

Fix:

  1. Pull up the patient's insurance card or the payer portal and compare it against your PMS.

  2. Confirm the Member ID / Subscriber ID matches exactly, including any leading zeros.

  3. Confirm the Patient Name, Date of Birth, and Subscriber Relationship (self, spouse, dependent) are entered exactly as the payer has them.

  4. Check the Group Number. If the payer portal doesn't list one, remove it from the patient's profile in your PMS, an incorrect or unnecessary Group Number can cause a check to fail.

  5. Once you make the change, wait for the nightly sync to happen.

  6. Re-run the eligibility check.


Eligibility check fails on Delta Dental, BCBS, or another carrier with multiple state plans

Cause: Carriers like Delta Dental and BCBS operate as separate state-specific entities (for example, Delta Dental of California vs. Delta Dental of Nebraska). If your PMS has the wrong state entity or an outdated Payer ID selected, the check will fail even though the patient has active coverage.

Fix:

  1. Check the patient's insurance card for the exact state or regional plan.

  2. In your PMS, confirm the carrier selected matches that state-specific plan, not just the parent carrier name.

  3. Cross-reference the payer in our Supported Payer directory to confirm you're using the current, correct Real-Time Eligibility (RTE) Payer ID. Older or discontinued Payer IDs are a common cause of failed checks.

  4. Update the Payer ID in your PMS if needed.

  5. Once you make the change, wait for the nightly sync to happen.

  6. Re-run the eligibility check.


Eligibility check returns a "Provider Not on File" error

Cause: This error means the wrong NPI type is being submitted. Eligibility checks need the rendering provider's individual Type 1 NPI, not the practice's Type 2 organizational NPI.

Fix:

  1. In your Dental Intelligence or PMS eligibility settings, confirm you're submitting the rendering provider's individual Type 1 NPI.

  2. Update the setting if it's currently set to the Type 2 organizational NPI.

  3. Re-run the eligibility check.

  4. If the error persists after confirming your NPI type is correct, some payers (Aetna, for example) require providers to register their NPI directly with the payer or clearinghouse before Real-Time Eligibility will work. Confirm your NPI is registered for RTE with that specific payer.


Eligibility data in Dental Intelligence doesn't match what's in your PMS, or checks aren't running at all

Cause: A recent update in your PMS hasn't synced over to Dental Intelligence yet.

Fix:

  1. Once you make the change, wait for the nightly sync to happen.

  2. Re-run the eligibility check.

Using Vyne and checks won't run at all? Vyne must be installed on a PC running a local instance of your PMS, it is not compatible with RemoteApp environments. If Vyne is installed on a RemoteApp setup, eligibility checks will fail. Install Vyne on a local PC instead. Learn more.


Eligibility shows "Not Active" or "Not Eligible," but the patient has active coverage

Cause: Some employer or group plans opt out of sharing eligibility data through the standard EDI 270/271 request. When this happens, the payer is blocking automated eligibility data at the source, and it can't be resolved by Dental Intelligence.

Fix: This requires manual verification, it isn't something we can override on our end.

  1. Verify the patient's coverage directly on the payer's web portal, or by calling the payer.

  2. Document the active coverage details for your records.

If you'd like confirmation that this is what's happening (rather than a setup issue on your end), contact Dental Intelligence support.


Eligibility checks are failing with a gateway, connection, or HTTP error across multiple patients or payers

Cause: This typically indicates a clearinghouse or payer system outage rather than an issue with your setup.

Fix: This requires our support team to investigate. Contact support with the following ready to speed things up:

  • The patient's insurance card

  • A screenshot of the error

  • Any relevant payer portal screenshots


Contact Support

If you've worked through the steps above and your eligibility check is still failing, contact our support team, we're happy to dig in further.

Have this ready when you reach out:

  • Patient name and the payer involved

  • A screenshot of the error message

  • Confirmation of which steps above you've already tried


Common questions

Why does my eligibility check say "Provider Not on File"?

This means the wrong NPI type is being submitted, see the "Provider Not on File" section above.

Why is eligibility showing incorrect or missing benefit information for a patient I know has coverage?

This is usually either a demographic mismatch, an outdated Payer ID, or, if none of that applies, an employer plan that has opted out of sharing eligibility data. See the relevant sections above.

Can Dental Intelligence fix an eligibility check that's blocked by an employer's EDI opt-out?

No, this is a payer-side policy restriction, not a setup issue, and requires manual verification through the payer.

Why did my eligibility checks stop working for every patient at once?

This usually points to a clearinghouse or payer outage. Contact support so we can investigate.

Did this answer your question?