Lockbox Variance, Failed 835, and an Unclaimed Refund

The manager should tie the variance to specific items, not force the deposit to balance.

1. Match the deposit total to the lockbox batch and ERA control totals. The $3,175 variance equals the $3,150 commercial payer payment plus the $25 patient copay check. That is a strong indicator that both items are in the deposit but not in posted payments.
2. Reprocess the failed 835 after validating the trailer count. If the file cannot be loaded, post the 14 claims from the payer portal or a corrected 835, using the claim-level detail. Do not post the $3,150 as a lump sum to one account.
3. Post the $25 patient copay to the correct patient account and apply it to the patient responsibility.
4. Clear the $3,175 suspense entry only after the underlying items are posted. The suspense entry should not remain as a plug. Document the reason, the posting references, and the person who cleared it.
5. Investigate the $1,900 refund separately. A check that has not cleared may be lost, stolen, or undeliverable. Do not net it against the deposit variance.

The manager should avoid the tempting journal entry that debits cash and credits a generic adjustment. That hides the problem and makes the next reconciliation harder.

The immediate cause of the variance is a failed 835 and an unposted copay, but the underlying causes are control gaps:

• No same-day file balancing. The failed 835 should have been detected when it arrived, not during a Monday reconciliation. A control should compare the 835 trailer count and dollar total to detail before acceptance, and alert the posting team on rejection.
• No daily bank-to-posted-cash reconciliation. A daily or next-day reconciliation would have isolated the $3,175 immediately and prevented a three-week-old suspense entry.
• Suspense aging. The $3,175 suspense entry was three weeks old with no owner. A weekly suspense aging report with assigned owners and escalation at 10 days would have forced resolution.
• Refund address verification. The refund was mailed to an old address, suggesting no address confirmation before check issuance. A control should verify the patient's address, stop payment on the stale check, and reissue after contact.
• Manual posting capacity. If the team is relying on manual posting because files reject, cross-train staff and document the manual workaround, including a second-person review.

Controls should focus on prevention and detection, not on faster plugging.

The stale refund requires its own process. The manager should:

• Verify whether the check was cashed. If it was not, place a stop payment and confirm the patient's current address by phone or patient portal before reissuing.
• Document the stop-payment date, check number, and reissue date in the refund log. If the patient cannot be reached, follow the organization's unclaimed-property and escheatment policy rather than leaving the check outstanding indefinitely.
• Do not take the $1,900 back into revenue simply because the check has not cleared. The liability remains until the refund is resolved.

For the payer, the manager should notify the payer that the 835 failed to load and that the payment is being posted from portal detail, if the payer requires confirmation. For the patient, the $25 copay should be posted and a receipt or statement should reflect it. If the patient calls about the refund, staff should have a clear status and expected reissue date. The manager should also review whether other refunds went to old addresses in the same batch, since one bad address often signals a data-quality issue.