VeriDent Implementation Playbook (DSO)

Executive Summary

VeriDent is a revenue cycle management platform built for dental DSOs managing claim submission, adjudication, and payment posting across multiple locations. This playbook assumes you're running 10+ practices with decentralized billing operations and want to consolidate processes while maintaining location autonomy.

What you're actually solving: Claims sitting in inbox limbo for 30+ days, claim denials nobody tracks, payment posting delays that break AR aging, and zero visibility into why location A collects 65% and location B collects 42%.

Timeline to full activation: 12-16 weeks (phased by location, not all-at-once).

Expected outcome: 3-5% revenue recovery within 90 days post-go-live at pilot locations; 7-12% improvement in Days Sales Outstanding (DSO) across the network within 6 months.

Pre-Implementation Checklist

Week -4 to -2: Organizational Readiness

• Designate a single revenue cycle leader (DDS or business manager) as the executive sponsor—someone who owns AR and claim denials. Not IT. Not a consultant. Someone who benefits from faster payment.

• Identify billing operations lead at each location (typically office manager or billing coordinator). These are your implementation champions. Budget 8-10 hours/week from them for 12 weeks.

• Audit your current claim submission workflow. Document:

  • Which locations use which practice management systems (PMS)
  • How many claims submit daily (total across DSO)
  • Current claim denial rate (pull from your PMS reports—usually 8-15% for dental)
  • How long between claim denial and resubmission (this will shock you)
  • Who handles claim follow-up at each location

• Obtain read/write access credentials for each location's PMS. VeriDent integrates via API with Dentrix, Eaglesoft, Open Dental, and others. If a location uses something obscure, you'll need a manual workaround—flag this now.

• Create a data export schedule. Your PMS generates patient eligibility, claim history, and payment data. VeriDent needs clean, daily feeds. Assign ownership.

• Confirm payer connectivity. VeriDent submits claims to insurers electronically. Verify each location has active clearinghouse credentials (837 claims format). If any location still faxes claims, that's a pre-implementation problem.

Week -2 to 0: Technical Readiness

• Run a small-scale API test between your largest PMS and VeriDent (typically 50-100 claims). Look for:

  • Dropped fields (patient names, plan codes, procedure codes)
  • Date format mismatches
  • Eligibility data lag (eligibility should sync daily; if it's monthly, you're already behind)

• Map your claim denial codes to VeriDent's taxonomy. Dental uses ~200 denial reasons (missing tooth, endo not covered, frequency limits, etc.). VeriDent auto-categorizes these, but you'll customize the rules per payer per location.

• Set up user access tiers:

  • Level 1 (Corporate): Revenue cycle director sees all locations, trending, benchmarking
  • Level 2 (Location): Office manager sees their location only, can request claim resubmission
  • Level 3 (Back-office): Billing coordinator submits claims, posts payments

• Establish a testing environment. Don't go live in production on day 1. Test at one location for 2 weeks before going DSO-wide.

Implementation Timeline

Phase 1: Pilot (Weeks 1-4)

Select 1-2 "best-in-class" locations (high volume, organized billing, experienced staff).

• Week 1: VeriDent administrator trains the local billing team (4 hours). Walk through: claim submission, denial review, payment posting workflow.
• Week 2: Parallel run—both VeriDent and your old system run simultaneously. All claims go through VeriDent; verify accuracy. Run a 50-claim audit (compare to PMS records).
• Week 3: Cutover to VeriDent as the primary system for claim submission and denial management. Continue posting payments in PMS for now (we'll integrate this later).
• Week 4: Review pilot results. Expected metrics:
  • Claim submission time: < 2 hours end-to-day
  • Denial identification: same-day vs. "we noticed it 3 weeks later"
  • Resubmission turnaround: track this obsessively

Phase 2: Secondary Rollout (Weeks 5-10)

Roll out to 3-4 locations monthly (not all at once—you'll break support capacity).

• Weeks 5-6: Train locations 2-4. Lean on your pilot location's billing lead to co-train.
• Weeks 7-8: Locations 2-4 go live in parallel run.
• Weeks 9-10: Cutover. Repeat the audit process.

Phase 3: Full DSO Activation (Weeks 11-16)

• Weeks 11-12: Remaining locations launch.
• Week 13: Payment posting integration. Move from posting in PMS to posting in VeriDent (less double-entry, cleaner AR). This is a big move—do it after all locations are comfortable with claim submission.
• Week 14-16: Stabilization, reporting, and optimization.

Key Metrics to Track

Real-time (Weekly Reports)

• Claim submission volume & timing: Are all claims submitting daily? Flag locations with backlogs.
• Claim acceptance rate (CAR): Should be 85%+ on first submission. Anything lower means dirty data or payer issues.
• Days to claim receipt acknowledgment: Industry standard is 2-3 business days from submit to payer ACK. If you're seeing 5+, payer connectivity is broken.

Monthly (Operational Review)

• Denial rate & categorization: Break down by payer and denial reason. "Frequency limits" vs. "missing tooth" require different appeal strategies.
• Denial rework time: From denial receipt to resubmission. Target: < 5 business days. If you're at 15 days, your denial queue is out of control.
• Collection rate by payer: Which payers are slowest? Which locations are worst at follow-up?

Quarterly (Financial Impact)

• Days Sales Outstanding (DSO): Measure this before VeriDent and monthly after. You're targeting a 10-15 day reduction DSO-wide.
• Revenue recovery: Identify all claims denied in the prior quarter that were successfully appealed post-implementation. This is your ROI story.
• Claim variance by location: Which locations collect 70%+ vs. 55%? Use VeriDent to identify root causes (payer mix, coding issues, follow-up discipline).

Common Pitfalls

Pitfall 1: Treating VeriDent as a "set it and forget it" tool

Reality: VeriDent flags problems; your team fixes them. If denial rules aren't updated quarterly, you'll keep resubmitting the same claims to the same payers. Assign one person at each location as the "denial lead." They own the weekly denial review.

Pitfall 2: Skipping the eligibility sync

Many DSOs treat eligibility verification as "nice to have." Wrong. If VeriDent can't see that Mrs. Johnson switched from Delta to Cigna, your claims will deny. Ensure your PMS pulls eligibility daily from your clearinghouse. No exceptions.

Pitfall 3: Going live across all 10+ locations simultaneously

You'll overwhelm your support team. Your billing staff will panic. Train in waves. Accept slower adoption in the first 8 weeks to avoid chaos.

Pitfall 4: Not automating payment posting

Your billing coordinator shouldn't manually post EOB checks into the PMS while VeriDent sits idle. Integrate VeriDent's payment posting with your PMS API. Yes, it takes an extra 2 weeks of setup. Yes, it's worth it.

Pitfall 5: Ignoring location-level variance

One location's denial rate is