Pain Point, Solved 4.9 ★★★★★ Google Rating

Why Do Dentrix eClaims Attachments Keep Rejecting and How Do You Keep Payer IDs Current?

All Pain Points

Ask AI about this page

Dentrix eClaims attachments keep rejecting because the payer ID on the claim is stale: Henry Schein One updates its payer list periodically, and several IDs were deactivated after the Change Healthcare cyber incident, so a claim built against an old ID rejects at the attachment layer and the x-ray or perio chart never reaches the carrier. It is rarely the attachment itself; it is that the ID you submitted against either never supported attachments or was retired, and the system could not map it to a supported one. The fix has four moves: read the rejection to the actual payer ID it names, audit your Dentrix payer table against the current Henry Schein One list on a schedule, correct the ID before the batch goes out, and re-send the rejected attachment claims the same day so nothing ages. We run those moves inside the Dentrix workflow you already use, so the image you attached actually reaches the payer. The table of contents maps the whole method; the moves after it are the detail.

How to Stop Dentrix Attachment Rejections and Keep Payer IDs Current
Key Pain Points and Discussions by Providers
Why This Keeps Happening
The Solution
How We Permanently Fix the Process
The Whole Thing in Four Sentences
Frequently Asked Questions
Where the Claims on This Page Come From

How to Stop Dentrix Attachment Rejections and Keep Payer IDs Current

The goal is simple: every attachment claim reaches the carrier the first time, with the x-ray and perio chart intact, and no crown claim ages waiting on a payer ID nobody updated. Here is what does that, move by move.

1. Read the Rejection to the Actual Payer ID It Names

An attachment rejection that reads the payor does not support attachments is naming a specific payer ID, not the whole carrier. Before anyone resubmits, pull that ID off the rejection and compare it to what is sitting in your Dentrix insurance table. Often the ID in your table was deactivated on the Henry Schein One end, or it was mapped to a supported ID that your practice never updated. You cannot fix an attachment claim by re-attaching the same image against the same dead ID; you have to find the ID first.

2. Audit Your Dentrix Payer Table Against the Current List

Payer IDs change periodically, and a batch of them changed after the Change Healthcare cyber incident when legacy IDs were deactivated. Set a standing monthly pass that compares every payer ID in your Dentrix table against the current Henry Schein One payer list through the payer search tool, flags the ones that no longer support attachments or were retired, and corrects them at the source. An ID audited once a month is an attachment that lands; an ID nobody has checked in a year is a rejection waiting to happen.

3. Correct the ID Before the Batch, Not After the Denial

The cheapest place to fix a stale payer ID is before submission. Once the corrected IDs are in the Dentrix table, the claims built against them carry the right ID into the batch, and the attachment reaches a payer that actually accepts it. Logging each payer’s attachment requirements per procedure code, which carriers want an x-ray, which want a perio chart, which want a narrative, means the claim is built right the first time instead of bouncing and coming back for rework nobody scheduled.

4. Re-Send Rejected Attachment Claims the Same Day

The clock that matters is the claim’s aging date, not the payer’s. A rejected attachment claim is only lost if it sits. The moment the rejection lands, the corrected claim goes back out the same day with the right payer ID and the image reattached, so a crown claim does not quietly age six weeks while three identical resubmissions bounce off the same dead ID. Tracking every rejection and payer ID change in one place is what keeps a stale ID from turning into a claim that never gets paid.

5. Hand eClaims and Attachments to a Dedicated Team

Practices that stop losing attachment claims to stale IDs do it by handing Dentrix eClaims and attachments to a dedicated team: remote billers who audit the payer table, correct IDs before the batch, and re-send rejections the same day, live in 1 to 2 weeks. The front desk goes back to the patients in the chair, a trained backup covers every gap, and the attachment rejection queue stops being the thing nobody owns. Below is what it sounds like when nobody owns it yet, in practice teams’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“We resent the same crown claim with the x-ray three times before anyone thought to check the payer ID against the current list. The fix took two minutes, and by then the claim had aged six weeks for nothing.” – billing lead, general dentistry practice

“The rejection just said the payor does not support attachments, so we kept re-attaching the radiograph like the image was the problem. It was never the image. The ID in our table had been deactivated and nobody knew payer IDs even changed.” – office manager, dental practice

“After the Change Healthcare mess a whole set of our payer IDs went stale, and our attachments started bouncing with no warning. We only caught it because a hygiene claim we knew was clean kept rejecting at the attachment layer.” – practice administrator, multi-provider dental group

“Nobody here owns the payer ID table. It gets set up once when we add a carrier and then never looked at again, so when an ID gets retired we find out from a stack of attachment rejections, not from anyone watching the list.” – front desk lead, general dentistry practice

“I have learned to check the payer ID against the current list before I even build the claim now. Half our attachment rejections disappeared the month we started auditing the table instead of trusting whatever was in there from two years ago.” – dental biller, general dentistry practice

Our Answer

Here is what we actually do. A dedicated remote biller reads the attachment rejection to the exact payer ID it names, audits your Dentrix payer table against the current Henry Schein One list on a monthly schedule, and corrects any ID that was deactivated or never supported attachments before the batch goes out. When a claim rejects at the attachment layer, they re-send it the same day with the right ID and the image reattached, so a crown claim does not age while identical resubmissions bounce off a dead ID. They also log each payer’s attachment requirements per code, so the claim is built right the first time. Our billers are credentialed professionals trained in US dental billing and Dentrix eClaims workflows, working inside the systems you already run, with AI drafting the first pass and a human verifying every submission. This is our dental billing support paired with an AI-first workflow, in one paragraph.

Why This Keeps Happening

If the claim is complete and the image is attached, why does it still reject? Because the attachment layer is checking one thing your front desk cannot see from the claim screen: whether the payer ID you built against is current and supports attachments. Henry Schein One maintains the payer list Dentrix eClaims routes against, and it changes periodically. When an ID is retired, the system tries to map your submitted ID to a supported one, and when it cannot, the attachment rejects. The image was never the issue; the routing target was.

The Change Healthcare cyber incident made this worse for a stretch of time. Several payer IDs were deactivated on the Henry Schein One end as connectivity was rebuilt, and practices that never audit their payer table kept submitting against IDs that had quietly gone dead. A claim built on a stale ID does not warn you at build time; it passes through and rejects downstream at the attachment layer, where it competes for attention with every other rejection in the queue. Keeping that table clean is exactly the kind of unglamorous, repeatable work an outsourced dental billing team is built to own.

And the cost is not just one bounced claim. The American Dental Association has long documented how attachment and documentation requirements slow dental claim adjudication, and a rejected attachment claim is worse than a slow one: it is a crown, a scaling and root planing, or a surgical extraction whose radiograph never reached the payer at all. It sits in unsubmitted or rejected status, aging quietly, until a 60 or 90 day report catches it. The lost days are real, and the write-off risk grows every week the ID stays wrong.

⚠️ The quiet one that hurts most: The quiet one that hurts most: an attachment rejection reads exactly like a claim that just needs the image re-attached. So the front desk re-attaches the same x-ray and re-sends against the same dead payer ID, and it bounces again, and again, and the claim ages the whole time it looks like it is being worked. Nobody sees that the ID itself is the problem, because the rejection blames the attachment. Unless someone compares the payer ID on the rejection to the current Henry Schein One list, the most fixable rejections are the ones that quietly age past their filing window.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

What you tried	What actually happened	Who ended up doing the work
Re-attached the x-ray and resent the same claim	Bounced again on the same dead payer ID, because the attachment was never the problem	Whoever had a free minute at the front desk
Called the carrier about the attachment rejection	Sent in circles, because the ID was retired on the software side, not the carrier’s	The front desk, on hold
Assumed the payer ID table was fine since it was set up once	IDs deactivated after the cyber incident sat stale for months until a stack of rejections surfaced them	Nobody; the table had no owner
Gave eClaims and attachments to a dedicated remote biller	Payer table audited monthly, IDs corrected before the batch, rejections re-sent same day	Someone whose whole job it is

The Solution

So what does “someone whose whole job it is” look like on a rejected attachment claim? The biller starts where the front desk usually cannot: reading the rejection to the actual payer ID it names, then comparing that ID against the current Henry Schein One payer list through the search tool. When it is stale or never supported attachments, they correct it in the Dentrix insurance table at the source, so every claim built after that carries the right ID. Most attachment rejections are a stale-ID problem, and that is exactly what dedicated dental billing support is built to catch before it ever becomes an aging claim.

Then comes the standing work that keeps it from coming back. Once a month the biller runs a full audit of your payer table against the current list, flags every ID that was retired or mapped to a supported one, and logs each payer’s attachment requirements per code so the next claim is built right the first time. When an attachment claim does reject, it goes back out the same day with the corrected ID and the image reattached, not three weeks later after it has aged. The rejection queue stops growing because someone is finally watching the list instead of the stack of bounces.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow reads the rejection, matches the payer ID, and flags the ones that changed; a person confirms the correction is right and owns the resubmission. Every security control that protects the radiographs and chart data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving patient images through a claims workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team keep your payer IDs current better than your own front desk? Because auditing payer tables and reading eClaims rejections is their entire day, not the thing they squeeze between check-ins and phone calls. The people working your Dentrix claims are credentialed professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US dental billing and eClaims workflows. They know that an attachment rejection is naming a payer ID, they know the Henry Schein One list changes, and they know how to correct the table at the source. That is not a task handed to whoever is free between patients; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a stale payer ID never sits because the one person who watches the table is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

✓ What stops happening: What stops happening: the crown claim resent three times before anyone checks the payer ID. The x-ray re-attached over and over against a dead ID. The batch of IDs that went stale after the cyber incident and nobody noticed. The attachment rejection that ages six weeks because it looks like an image problem. The payer table that gets set up once and then trusted for years while carriers quietly retire the IDs inside it.

2-Week Free Trial

Ready to Stop Losing Claims to Stale Payer IDs?

Book A Strategy Call Request Information

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented eClaims workflow: which payer IDs your practice submits against, which ones support attachments, which were retired or mapped after the cyber incident, and the exact monthly audit that keeps the Dentrix table matched to the current Henry Schein One list. Before we take a single claim for a new practice, we audit your payer table top to bottom so we can see which IDs are already stale, and we build the workflow against your real carrier mix, not a generic template.

From there the workflow becomes a living playbook rather than a table nobody owns. It records which carriers want which attachments per code, which payer IDs changed and when, how to read an attachment rejection to its true ID, and the schedule for re-checking the list as Henry Schein One updates it. It is written down, kept current, and owned by the team. When your biller is out, a trained backup runs the same audit the same way, so a crown claim never ages because the one person who watched the payer table came back too late.

That is the difference between reworking this month’s attachment rejections and fixing the process for good, and it is what a dedicated dental billing partner actually buys you. A biller leaving used to mean the payer table went stale again and attachments started bouncing. Under this model the audit keeps running, the playbook stays, the backup steps in, and a stale payer ID stops being the thing that quietly costs you paid claims.

The Whole Thing in Four Sentences

Dentrix eClaims attachments keep rejecting because the payer ID on the claim is stale: Henry Schein One updates its payer list periodically, several IDs were deactivated after the Change Healthcare cyber incident, and a claim built against a dead ID rejects at the attachment layer while the image never reaches the carrier. Re-attaching the same x-ray, calling the carrier, or trusting a payer table set up once all fail the same way. The fix is to read the rejection to the actual payer ID, audit the Dentrix table against the current list monthly, correct the ID before the batch, and re-send rejections the same day. A general dentistry group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop losing claims to stale payer IDs? Try us risk free: two weeks, your real Dentrix rejection queue, dedicated billers auditing the payer table and re-sending attachments the same day, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Transparent Weekly Pricing

One Flat Weekly Rate. 45 Hours of Coverage.

No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.

Single

$399/ week

One dedicated remote dental biller owning your Dentrix eClaims and attachment submissions end to end, single-location general practice

Clear Your Attachment Rejections This Month

You have seen the whole method. The pilot proves it on your own Dentrix rejection queue, with a tracker your team can watch every day.

Start My 2-Week Free Trial

Request Information or call directly: (800) 489-5877

Request Information

Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.

Frequently Asked Questions

Why does my Dentrix attachment reject with the message that the payor does not support attachments?

Because the payer ID your claim was built against either never supported attachments or was deactivated on the Henry Schein One end, and the system could not map it to a supported ID. The attachment is fine; the routing target is wrong. Compare the payer ID named on the rejection to the current Henry Schein One payer list through the payer search tool, correct it in your Dentrix insurance table, and re-send. The image will land once the ID is current.

Why did our attachments start rejecting after the Change Healthcare cyber incident?

Because several payer IDs were deactivated on the Henry Schein One end while connectivity was rebuilt, and legacy IDs stopped being supported. Practices that never audit their payer table kept submitting against IDs that had quietly gone dead, so clean claims with valid attachments began rejecting at the attachment layer. The fix is to audit every ID in your Dentrix table against the current list and correct the retired ones.

How often should we audit our Dentrix payer ID table?

At least monthly. Payer IDs change periodically, and a batch of them changed after the cyber incident, so a table set up once and never rechecked drifts out of date. A standing monthly pass that compares every ID against the current Henry Schein One list, flags the ones that were retired or no longer support attachments, and corrects them at the source keeps attachment claims landing the first time.

Is the attachment itself ever the real problem?

Sometimes, but far less often than the payer ID. Before assuming the x-ray or perio chart is wrong, check whether the payer ID supports attachments and is current, because an attachment rejection names the ID, not the image. Once the ID is confirmed good, then look at whether the specific carrier wants a different attachment type for that procedure code, which is why logging each payer’s requirements per code matters.

How much does outsourced dental billing for Dentrix cost?

Staffingly charges a flat weekly rate per dedicated remote biller, with lower per-person rates for teams of 5 or more and 10 or more. Every plan covers 45 hours of coverage per week with a trained backup included, and there is no percentage of your collections. The pricing section on this page shows how the flat rate compares with typical US market rates for this work.

Will AI be making decisions on our claims?

No. AI drafts the first pass, reading the rejection, matching the payer ID, and flagging the ones that changed, and a credentialed human verifies every correction and owns the resubmission. The judgment stays with people. Automation removes the repetitive matching work so the biller spends their time on the claims that need a human, not on retyping the same corrections.

Do we have to change our practice management software?

No. Our billers work inside the Dentrix workflow you already use, so there is no migration and no new platform for your front desk to learn. They read your claims and rejections where they already live and submit through the eClaims connection you already have, which is why a typical practice is live in 1 to 2 weeks rather than months.

How fast will we see fewer attachment rejections?

Usually within the first two weeks. Once a dedicated biller audits the payer table, corrects the stale IDs, and re-sends the rejected attachment claims the same day, the claims that used to bounce on a dead ID start landing on the first submission, and the crown claims that used to age quietly start reaching the carrier with their images intact.

How does one flat weekly rate cover 45 hours every week?

Your dedicated specialist works a 9-hour day, Monday to Friday, which is 45 hours of coverage each week. The ninth hour is part of the flat weekly rate, not billed as overtime. Over a year that is 2,340 hours of coverage, against the standard US full-time work year of 2,080 hours (40 hours x 52 weeks, the same basis the U.S. Office of Personnel Management uses to compute hourly rates of pay). That is how $399 per week works out to $8.87 per hour.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From

Sources & References

Henry Schein One Claims Processing Updates. Vendor documentation of payer ID changes, attachment support, and IDs deactivated after the Change Healthcare cyber incident affecting Dentrix eClaims. henryscheinone.com
Dentrix Payer Search Tool. The current Henry Schein One payer list for verifying payer IDs and attachment support in Dentrix eClaims. dentrix.com
American Dental Association Dental Claims and Coding Resources. Guidance on dental claim submission, attachment requirements, and adjudication for dental practices. ada.org
MGMA Practice Operations and Revenue Cycle Resources. Benchmarks and guidance on claims processing, denials, and patient access for medical and dental group practices. mgma.com
HFMA Revenue Cycle and Denials Management Resources. Guidance on claim rejections, resubmission workflow, and the revenue impact of aged and lost claims. hfma.org