A dental billing SOP is less about creating paperwork and more about making reimbursement predictable. When every handoff is defined, claims go out faster, fewer items get stuck in pending status, and patients get clearer answers about what they owe and why.
For most practices, the billing “system” lives partly in the practice management software and partly in people’s habits. An SOP pulls those habits into a single, teachable playbook so performance does not depend on one experienced team member being in the office.
What a dental billing SOP should accomplish
A useful SOP does three things at the same time: it standardizes the work, assigns ownership, and builds in checks that catch mistakes before they become write offs.
It also creates a shared definition of “done.” In billing, “done” is rarely “claim sent.” It is “claim accepted, adjudicated correctly, paid, posted accurately, and any balance resolved.”
A well-built SOP is also an accountability tool. If the team is seeing rising denials, slower cash, or more patient disputes, the SOP helps you locate the exact step that is failing.
How to structure the document so people will actually use it
Most SOPs fail because they read like a policy manual instead of an operating guide. Keep each workflow self-contained, with clear start and stop points, and write to the role doing the task.
After you decide the format, define your standard “modules” so every section feels familiar. Many practices keep each module to one to two pages plus checklists and screenshots.
A strong baseline structure includes:
- Purpose and scope
- Systems used (PMS, clearinghouse, payer portals, payment tools)
- Step-by-step procedure
- Required documentation and attachments
- Timelines (same-day, within 48 hours, weekly cadence)
- QA checks and escalation steps
- Metrics to monitor
Workflow 1: patient intake, insurance capture, and eligibility verification
Your SOP should start before the patient arrives. Billing outcomes are largely determined by data quality at scheduling and check-in.
Spell out exactly what front desk or scheduling must collect, where it goes in the PMS, and what is considered complete. Include rules for scanning or attaching insurance cards, entering subscriber details, and recording coordination of benefits when a patient has dual coverage.
Then define your verification cadence. Many practices verify benefits 48 to 72 hours before the visit and confirm again at check-in, because coverage can change mid-month and because simple entry errors are common.
After a paragraph like this, the checklist becomes actionable:
- Minimum insurance fields: subscriber name, DOB, subscriber ID, group number, payer phone, payer address
- Eligibility timing: pre-visit verification and day-of-service confirmation
- Estimate method: document deductible remaining, annual maximum remaining, and coverage percentage assumptions
- Pre-auth trigger: identify procedures that require prior authorization and start requests immediately
Also include a script standard for financial conversations so patients hear consistent language about estimates versus guarantees.
Workflow 2: clinical documentation and CDT coding rules
A billing SOP has to connect clinical documentation to coding standards. If documentation is inconsistent, even excellent billing teams cannot keep claims clean.
Define what “billable documentation” means for your practice. Many offices use a SOAP-style note requirement, plus radiographs, periodontal charting, intraoral photos, and narratives when payer policies call for them.
Your SOP should explicitly require current CDT usage and annual code updates. It should also specify who is allowed to select and edit codes, and what happens when documentation does not support the code selected.
Keep this section short in the SOP body, then attach detailed coding job aids for high-risk categories (implants, sedation, periodontal therapy, build-ups, and frequent downgrades).
Workflow 3: charge entry, claim creation, and same-day submission
The clean-claim standard belongs in writing. “We try our best” does not survive staff turnover.
Define when charges are entered (often same day), what must match the clinical note, and which fields must never be left blank. Include payer-specific requirements you see repeatedly, like tooth numbers, surfaces, quadrant, narrative prompts, and attachment types.
This is also where the SOP should name the technology path: PMS claim module, clearinghouse edits, payer portal submission rules, and how attachments are sent (electronic, portal upload, secure fax).
A simple, repeatable pre-submission quality gate helps prevent avoidable rejections:
- Run a claim edit report in the PMS and resolve all warnings that affect payment.
- Confirm provider identifiers, treating provider, and billing provider are correct for the plan.
- Validate attachments are present and legible, with correct date of service references.
- Submit electronically when allowed and confirm acceptance status within 48 hours.
Add your timely filing rules here. Even if limits vary by payer, the SOP should set an internal deadline that is tighter than the payer’s limit so the team has room for rework.
Workflow 4: claim follow-up, denial management, and appeals
Most practices do not need more follow-up effort, they need consistent follow-up. The SOP should define how the team finds aging claims, how often they work them, and how they document actions.
A claim log is one of the simplest controls. Whether it is inside the PMS, a spreadsheet, or a clearinghouse worklist, define required fields (submission date, last touch, next action date, owner, notes).
Denial work needs a standard path. Include denial category mapping (eligibility, missing info, documentation, bundling/downgrade, frequency, coordination of benefits) so trends can be measured, not guessed.
Also define escalation. If a claim is stuck after a set number of touches or exceeds a certain aging threshold, the SOP should state who reviews it next and what options exist (correct and resubmit, appeal, request reconsideration, patient re-estimate, or provider documentation addendum).
Workflow 5: payment posting, reconciliation, and secondary claims
Payment posting is where small errors quietly become large losses. Your SOP should require posting the same day or next business day when possible, and it should require line-by-line reconciliation against the original claim.
Define exactly how your team posts:
- Allowed amount
- Insurance paid amount
- Patient responsibility (deductible, copay, coinsurance)
- Contractual adjustment codes
- Non-covered amounts and narrative reasons
Then define what happens when payment is not as expected. Underpayments should go into a named queue with a time limit for action, and the SOP should provide appeal templates and documentation checklists.
Include a rule for secondary claims: submit the secondary claim immediately after primary posting, with the primary EOB attached when required, so secondary benefits are not lost in end-of-month catch-up.
Workflow 6: patient statements, digital payments, and collections steps
Patient billing should be written to reduce confusion. Clear statements, predictable timing, and easy payment methods reduce inbound calls and speed cash.
Your SOP should specify statement cadence (for example, first statement within X days of insurance posting), delivery methods (mail, email, text), and minimum statement content (itemized services, dates, insurance payment summary, and balance explanation).
It should also define how disputes are handled: where notes are stored, what the team can adjust without approval, and when a manager must review.
A short list of standardized collection actions often works better than an overly complex policy:
- Courtesy reminder
- Second notice
- Phone outreach
- Payment plan offer
- Final notice
Keep it respectful and compliant with state rules, and require documentation of every patient contact attempt.
Roles, handoffs, and authority levels
Even a perfect workflow fails when ownership is unclear. Write roles in terms of tasks, decision rights, and metrics, not job titles, since many practices combine roles.
EZDDS Billing often sees the strongest results when practices assign a clear “single owner” per revenue cycle segment and then use defined handoffs, rather than having everyone touch everything.
Here is a practical role map you can adapt:
| Role | Owns these steps | Can approve | Key metrics to watch |
|---|---|---|---|
| Insurance Verification Coordinator | Eligibility, benefits entry, pre-auth initiation, COB capture | Updating plan details in PMS | Verification accuracy, pre-auth turnaround, coverage-related denials |
| Coder or Coding-Qualified Biller | CDT selection, documentation checks, coding corrections | Code corrections that match documentation | Coding error rate, first-pass acceptance rate, downgrade frequency |
| Claims Specialist | Claim creation, attachment management, submission, rejection fixes | Resubmissions and corrected claims | Days from DOS to submission, rejection rate, clean claim rate |
| A/R Follow-up Specialist | Work aging claims, payer calls/portals, appeals packets | Appeal submission within payer rules | Insurance A/R aging, appeal success rate, denial rate by reason |
| Posting and Patient Billing Specialist | ERA/EOB posting, adjustments, patient statements, payment plans | Small courtesy adjustments within policy | Posting timeliness, patient A/R aging, patient collection rate |
| Billing Manager or Practice Manager | Oversight, compliance checks, payer escalations, SOP updates | Write offs and refunds above threshold | Net collection rate, >90-day A/R %, audit findings, training completion |
Add one paragraph in your SOP that states approval thresholds plainly (example: “refunds over $X require manager approval”) and list who can change the fee schedule and insurance plan tables.
QA checks that catch errors early
Quality assurance works best when it is built into daily work instead of saved for month-end. Put QA checks directly inside each workflow section, then repeat the highest-impact checks in a single QA page.
After you explain the philosophy, make the checks specific:
- Before submission: confirm subscriber data, provider identifiers, tooth and surface details, and required attachments
- After submission: review clearinghouse rejections within 48 hours and correct the same day
- During posting: reconcile each line item to the EOB or ERA and route underpayments to a defined queue
- Weekly: run an aging report, work oldest or highest-dollar claims first, and document the next action date
- Monthly: sample-audit a set of paid and denied claims for documentation support and coding accuracy
Add a trend review requirement. If denials increase for a code family or payer, the SOP should require a root-cause note and a documented process change or training assignment.
Compliance requirements to write into the SOP (HIPAA and billing integrity)
Compliance language should be operational, not generic. State exactly how PHI is handled, transmitted, and accessed.
Your SOP should require role-based access in the PMS, unique logins, secure transmission methods for attachments, and a minimum necessary standard for sharing patient information. Include where audit logs live and who reviews them.
Billing integrity needs equal clarity. Prohibit upcoding, unbundling, and billing for services not rendered, and require documentation support for every billed code. Add a simple corrective-action process when an error is found: correct, refile if needed, document the fix, and track it so repeat issues get addressed.
Also include record retention rules and a policy for refunding identified overpayments within required timeframes, based on applicable payer and legal requirements.
Implementation: turning the SOP into daily behavior
Rollout works best when the SOP is treated like a production system, not a one-time project. Assign an owner, set a review cadence, and keep version control.
A practical approach is to implement in phases (verification first, then claims submission, then posting and A/R) so the team can stabilize one area before changing the next.
Training should be role-based and scenario-driven. New hires should have an SOP-based onboarding checklist, and existing staff should have short refreshers tied to denial trends and audit findings.
If you want the SOP to stay current, require an annual review plus updates whenever you change software, switch clearinghouses, or see payer policy shifts. Add “last revised” to every page footer so staff can trust they are using the right version.
For practices that prefer to keep clinical teams focused on patient care, an outsourced billing partner can maintain these workflows, monitor QA, and report performance trends back to leadership on a steady cadence, while keeping the practice in control of policies and approvals.