The Problem with Lump Sum Insurance Payments
One deposit. Forty-seven patients. $23,847.62. Which dollars go where?
The Lump Sum Problem
Insurance companies do not send individual checks for each claim. They batch payments together, sending one deposit that covers dozens or hundreds of patients. A single EFT might include payments for every claim they processed that week, regardless of service date or procedure type.
This batching creates the fundamental challenge of insurance reconciliation. You received $23,847.62. Your ledger needs to show exactly which patients that money applies to, in exactly the right amounts, with exactly the right adjustments. Getting any of it wrong means accounts show incorrect balances.
The information exists to match everything correctly. The ERA accompanying the payment lists every patient, every procedure, every payment amount, and every adjustment. But using that information requires systematic processes. Without those processes, lump sum payments become sources of persistent errors.
Why Insurance Companies Batch
From the payer's perspective, batching makes perfect sense. Processing individual payments for each claim would multiply their transaction costs. Banking fees, processing overhead, and administrative burden all favor consolidation.
Insurance companies typically batch by provider, payment period, and sometimes by product line. A dental practice might receive one weekly EFT containing all fee-for-service payments processed that week. PPO, HMO, and other product lines might come as separate deposits.
The batching schedule varies by payer. Some pay weekly. Others pay twice monthly. Some pay monthly. Understanding each payer's schedule helps you know when to expect payments and how much volume each deposit typically contains.
Larger deposits are not better or worse than smaller ones from a cash perspective. But larger deposits covering more patients create more reconciliation work. A deposit covering 10 patients is simpler to match than one covering 100.
The ERA Holds the Key
Every insurance EFT should include an Electronic Remittance Advice that details exactly what the payment covers. The ERA lists each claim paid, each procedure code, each allowed amount, each adjustment, and each patient responsibility amount.
ERAs arrive through your clearinghouse, typically as electronic files that can be loaded into your PMS. Some practices receive paper EOBs instead, which require manual processing but contain the same information.
The ERA is your roadmap for posting. Without it, a $23,847.62 deposit is just a number. With it, you know that $412 goes to Smith for crowns, $187 goes to Johnson for prophylaxis, and so on through every patient in the batch.
Posting from the ERA rather than just the deposit amount ensures accuracy. If you post $23,847.62 to a suspense account and allocate later, you risk misallocation. If you post each line of the ERA individually, each patient account gets exactly the right amount.
Common Matching Problems
Even with ERA data available, lump sum payments create matching challenges.
ERA totals sometimes do not match deposit amounts. Payers may hold back for previous overpayments, apply refund requests, or make other adjustments not detailed on the ERA. When the numbers do not match, investigation is needed.
Multiple ERAs might correspond to one deposit. If a payer batches across product lines but sends separate ERAs for each, you need all the ERAs to understand the complete deposit. Missing one ERA means missing part of the picture.
Timing differences create confusion. An ERA might arrive days before or after the corresponding deposit. Matching them requires tracking what is received but unmatched on both sides.
Patient information on ERAs sometimes differs from your records. Name misspellings, different ID numbers, or policy holder versus patient discrepancies make automated matching harder. Manual review is needed for items that do not match automatically.
Adjustments require proper interpretation. Contractual adjustments, withholds, and other deductions each mean something different. Posting them incorrectly affects patient balances and financial reports.
The Posting Process
Proper posting of lump sum payments follows a systematic approach.
Receive and import the ERA into your PMS. Most systems can read standard ERA formats and display the contents for review and posting. If your system requires manual entry, the ERA paper or file provides the source data.
Review the ERA before posting. Look for unusual adjustments, denied line items, or amounts that seem wrong. Catching problems before posting is easier than fixing them after.
Post each payment to the correct patient account. The ERA specifies patient, procedure, payment, and adjustment amounts. Your PMS should apply these to existing claims, matching by claim ID or procedure date.
Verify that ERA totals match deposit amounts. After posting everything on the ERA, the total should match what deposited. If it does not, find the difference before moving on.
Address any unmatched items. Payments for patients not in your system, denied claims that need appeal, or amounts that do not match expected payments all need investigation and resolution.
When ERAs Are Missing
Sometimes deposits arrive without corresponding ERAs. This happens when ERAs go to wrong addresses, get lost in clearinghouse processing, or simply never get sent.
Contact the payer if an ERA is missing. They can usually resend electronic remittances or provide payment details by phone. Getting the detail is essential for proper posting.
Bank deposit descriptions sometimes provide clues. ACH deposits often include trace numbers or payer identifiers that help track down corresponding remittance information.
Manual breakdown is a last resort. If you cannot obtain an ERA, you may need to review open claims for that payer and deduce what was paid based on amounts and timing. This is error-prone but sometimes necessary.
Never just post lump sums to generic accounts. Posting $23,847.62 to "insurance income" without patient-level detail leaves your ledger wrong and your patients incorrectly billed. The detail exists somewhere and is worth finding.
Reconciliation Requirements
Lump sum payments require specific reconciliation attention.
Verify that ERA totals match posted totals. After posting an ERA, confirm that your system shows the same total as the ERA document. Differences indicate missed line items or posting errors.
Verify that deposits match posted payments. The bank deposit should equal the sum of posted insurance payments for that batch. If your bank shows $23,847.62 but you posted $23,500, you are $347.62 short somewhere.
Investigate unallocated amounts immediately. Do not let unmatched insurance dollars sit in suspense accounts. Every dollar should reach a patient account within days, not weeks.
Review posting patterns for systematic errors. If the same type of error recurs across multiple batches, the problem is in the process rather than individual transactions. Fix the process.
Technology Solutions
Manual management of lump sum payments is time-consuming and error-prone. Technology helps.
PMS integration with clearinghouses automates ERA receipt. Rather than downloading files manually, ERAs flow directly into your system for review and posting.
Auto-posting features match ERA lines to open claims automatically. The system identifies which claim each payment applies to and posts without manual intervention for matching items. Only exceptions need manual handling.
Reconciliation tools compare ERA totals to deposits and flag discrepancies. Rather than manually comparing documents, software identifies mismatches that need attention.
Reporting shows unposted ERAs and unmatched deposits. Dashboards surface the exceptions rather than requiring manual tracking of what has and has not been processed.
These tools do not eliminate judgment. Someone still needs to resolve exceptions, investigate discrepancies, and verify that automation is working correctly. But they dramatically reduce the volume of routine work.
The Impact of Getting It Wrong
Errors in posting lump sum payments have cascading effects.
Incorrect patient balances generate wrong statements. Patients either owe more than they should (generating complaints) or show credits they do not have (generating refund requests for money not actually due them).
Incorrect insurance balances distort aging reports. Amounts posted to wrong patients or wrong claim periods make your receivables look different than they actually are.
Reconciliation discrepancies hide other problems. When your daily reconciliation is already off due to posting errors, detecting new problems becomes harder. The noise masks the signal.
Staff time is consumed by fixing errors. Every incorrectly posted payment needs investigation and correction. This detective work takes time away from current operations.
Clean posting of lump sum payments is not optional. The work will happen either when the payment arrives or later when someone cleans up the mess. Doing it right the first time is faster.
Building Better Processes
Practices that handle lump sum payments well share certain characteristics.
They have designated responsibility. Someone owns insurance posting and does it consistently. The work does not float between people based on who has time.
They process ERAs promptly. When remittances arrive, they get posted within a day or two, not queued for weeks. Prompt processing keeps accounts current.
They verify before moving on. After posting a batch, someone confirms that the posted total matches the ERA and the ERA matches the deposit. Verification catches errors immediately.
They escalate problems rather than ignoring them. When something does not match, they investigate rather than hoping it will resolve itself. Problems do not resolve themselves.
They periodically review the process. Are we keeping up? Are error rates acceptable? Are we finding issues that indicate systematic problems? Regular review drives improvement.
Zeldent automates lump sum payment matching by connecting to your ERA data and bank deposits simultaneously. We match each ERA line to deposited amounts and flag discrepancies for review. Schedule a demo to see how automated matching simplifies insurance reconciliation.
