Dental ERA format: understanding the ANSI 835 standard
If your front desk or billing team spends hours reconciling payments, chasing down missing EOBs, or fixing posting errors, you are not alone. Dental offices deal with a steady stream of payer formats, partial payments, and unclear adjustments. The ANSI 835 file, also called the electronic remittance advice or ERA, is meant to fix that. In practice, many teams still struggle to use it well.
This guide explains what the 835 is, how it works in dental billing, and how to use it to speed up payment posting and reduce mistakes.
What is the ANSI 835 ERA?
The ANSI 835 is a standardized electronic file that payers send to explain how they processed a claim. It includes payment details, adjustments, denials, and patient responsibility. Think of it as the digital version of an EOB, but structured so software can read and post it automatically.
Dental practices receive 835 files through clearinghouses or payer portals. Your practice management system or billing software then imports the file and applies payments to the correct claims.
In theory, this replaces manual data entry. In reality, many offices still review, fix, and rework these postings because of mismatches or unclear codes.
Why dental offices struggle with ERAs
The 835 format is standardized, but payer behavior is not. That gap creates real headaches:
Payers use different adjustment codes or group codes for the same scenario
Patient responsibility amounts do not match estimates given at the front desk
secondary insurance details are incomplete or missing
Claim lines do not map cleanly to procedures in your system
Payments arrive bundled across multiple claims with little clarity
This leads to rework. Teams open the ERA, cross-check with the claim, then compare against the patient ledger. If something does not line up, they dig into payer portals or call support. Hold times alone can eat hours each week.
Key components of an 835 file
You do not need to read raw EDI to benefit from ERAs, but understanding the structure helps you troubleshoot issues.
Claim payment information
Each 835 includes:
Claim identifiers like patient name, account number, and claim control number
Payment amount for the claim
Dates of service
Payer details
This section tells you which claim the payment applies to and how much was paid.
Service line details
Payments are often broken down by procedure code. Each line shows:
CDT code
Billed amount
Allowed amount
Paid amount
This is where you see partial payments or downgraded procedures.
Adjustment codes
Adjustments explain why the payer did not pay the full billed amount. These use standardized CARC and RARC codes.
Examples:
Contractual obligations
Deductibles
Frequency limitations
Missing information
If your team does not understand these codes, posting errors are almost guaranteed.
Patient responsibility
The ERA lists what the patient owes, such as:
Copay
Coinsurance
Deductible
If this does not match what you collected upfront, you are left chasing balances after the visit.
Payment method
The 835 also shows how the payment was made. This could be EFT, check, or virtual card. Matching this to your bank deposits is part of reconciliation.
How ERA posting works in practice
Most dental software supports auto posting from 835 files. The process usually looks like this:
Download or receive the ERA from your clearinghouse
Import it into your practice management system
The system attempts to match claims and post payments
Staff review exceptions and fix errors
The problem is step four. Exception queues can get large, especially if your claim data is inconsistent or your insurance verification process is weak.
Common ERA posting errors and how to fix them
Claim not found
This happens when the claim number in the ERA does not match your system.
Fix:
Use consistent claim control numbers when submitting claims
Avoid manual edits after submission
Check clearinghouse settings for mapping issues
Incorrect procedure mapping
If CDT codes in the ERA do not align with your system, payments can post to the wrong line.
Fix:
Standardize coding practices across providers
Audit your software’s code mapping settings
Adjustment misinterpretation
Staff may apply adjustments incorrectly, which distorts patient balances.
Fix:
Train your team on common CARC and RARC codes
Build internal cheat sheets for frequent scenarios
Patient balance mismatches
You collect one amount, but the ERA shows another.
Fix:
Improve insurance verification before the visit
Use real-time eligibility tools to estimate benefits more accurately
Bundled payments confusion
Payers often send one payment for multiple claims.
Fix:
Use detailed reconciliation reports
Match total payment amounts before posting line items
Best practices to get more value from 835 files
Standardize your claim data
Clean input leads to cleaner ERAs. Use consistent naming, coding, and claim identifiers. Small inconsistencies create big reconciliation issues later.
Tighten insurance verification
Many ERA issues start before the claim is even submitted. If your eligibility checks are off, your payment posting will be messy. Verify:
Coverage limits
Frequencies
Waiting periods
Coordination of benefits
Accurate estimates reduce surprises for both your team and your patients.
Build a clear adjustment policy
Do not leave adjustment decisions to guesswork. Document how your office handles:
Contractual write-offs
Denials
Patient responsibility
This keeps posting consistent across staff members.
Track denial patterns
Your ERA data is a goldmine for spotting trends. If you see repeated denial codes, there is a root cause. It could be coding errors, missing attachments, or eligibility issues.
Fixing the source reduces future rework.
Audit your auto posting rates
Do not assume your system is working perfectly. Track:
Percentage of payments auto-posted without intervention
Number of exceptions per batch
Time spent on manual corrections
If auto posting rates are low, investigate why.
Reconcile daily
Waiting until the end of the week or month creates a backlog. Daily reconciliation keeps issues small and easier to fix.
How ERAs impact cash flow and team workload
When ERAs are handled well, payments move faster and require less manual effort. When they are not, you feel it immediately:
Slower collections because payments sit unposted
More patient billing errors and complaints
Increased time on payer calls
Higher burnout for front desk and billing staff
For many practices, payment posting becomes a bottleneck. It is repetitive, detail-heavy work that still requires judgment.
When to consider outsourcing or automation
If your team is constantly behind on posting or spending hours fixing ERA errors, it may be time to change the setup.
Signs to watch:
Backlog of unposted payments
Frequent patient balance corrections
High denial rates tied to eligibility issues
Staff overtime focused on billing tasks
Automation can improve auto posting accuracy, but only if your underlying data is clean. Outsourcing can help if you do not have the bandwidth to manage exceptions internally.
Final thoughts
The ANSI 835 format is meant to simplify payment posting, but it only works as well as the processes around it. Clean claims, accurate verification, and consistent posting rules make a huge difference. Without those, ERAs turn into another source of confusion.
Many dental offices reduce posting errors and speed up collections by pairing better ERA handling with dedicated billing support. Teero’s revenue cycle management tools handle payment posting and reconciliation so teams spend less time fixing errors and more time running the practice.
