The Batch Report That Proves Nothing
A 12-provider orthopedic group bills a regional commercial payer under a contract with a 90-day filing limit from date of service. A $8,420 claim, DOS March 3, went out electronically on March 10. The clearinghouse's batch-accepted report shows the file leaving that day, and the biller marked the account clean. On August 14 the payer denies it: "time limit for filing has expired - no record of receipt." The billing manager then pulls the claim-level file and finds the claim was rejected at the clearinghouse with "payer not enabled for this clearinghouse ID" and never transmitted. A paper claim was mailed June 5 and the payer logged receipt June 12 - day 101. A wider search turns up 212 more claims in the same window with the identical rejection, $391,000 total, roughly half still inside the filing limit. The payer-ID enrollment lapsed in February when the group onboarded two new providers and re-filed its EDI paperwork.
1. Is the $8,420 recoverable? Walk through what documentation actually establishes timely filing and what does not.
Read the worked answer
Start by separating three different events that all get called "accepted." A clearinghouse batch report only proves the file left your system; it says nothing about payer receipt. The claim-level payer acknowledgment (277CA) is the document that establishes receipt, and here the claim never produced one because the clearinghouse blocked it before transmission. So the electronic submission date of March 10 is not evidence of anything the payer will accept.
The paper claim is the remaining argument. It was received June 12, day 101 against a 90-day limit - facially late. The only openings are: (1) whether the contract measures the limit from postmark or proof of mailing rather than receipt, which would make the June 5 mailing day 94 and timely if it was sent certified; (2) whether the payer will grant an administrative good-cause exception for a documented clearinghouse enrollment failure, which is a provider-relations request, not an appeal; and (3) whether any intervening primary payer remittance resets the clock, which applies only on secondary claims.
Absent a certified-mailing provision, the $8,420 is a write-off. Do not file a formal appeal claiming timely filing on the strength of the batch report - a losing appeal burns the account and signals weak internal controls.
2. You have 212 claims and $391,000 at risk. How do you sequence the work, and what must you avoid?
Read the worked answer
Sequence by clock, not by dollar. Sort all 212 by remaining days in the filing window and treat anything still inside the limit as today's work - resubmit those through a correctly enrolled payer ID, with the original date of service intact, and log the new acknowledgment. That recovers the portion of the $391,000 that is still salvageable at full value.
For the claims already outside the limit, do not mass-resubmit. They will come back as duplicates or as late filings and you will have muddied the record. Instead, assemble one consolidated administrative request to the payer's provider-relations or network representative: a spreadsheet of claim numbers, DOS, rejection code, and the effective date the enrollment lapsed, with a request for a retroactive enrollment or good-cause adjustment. A single documented systemic-failure package at $391,000 gets executive attention in a way that 212 individual appeals will not.
What to avoid: don't let staff submit corrected claims with altered dates or a new "current" date of service to slip under the limit. That is a false claim, and it converts a revenue problem into a compliance problem. Also avoid writing anything off until the provider-relations decision is in writing.
3. What process changes would prevent a recurrence, and which one would you implement first?
Read the worked answer
The failure had a 60-day fuse and nobody was watching the fuse. The batch report looked green the whole time, which is exactly why this recurs in practices that "check" their submissions.
First and cheapest: a claim-level 277CA reconciliation worklist. Every claim submitted must have a payer acknowledgment within five business days; anything without one lands on a human's desk with the rejection code attached. That single control would have caught this on March 17 instead of August 14.
Second: treat certain rejection codes as alerts rather than routine corrections. Codes indicating the claim never transmitted - payer not enabled, invalid payer ID, trading-partner mismatch - are systemic by nature and should escalate to the billing manager automatically, because if one claim hit it, others did too.
Third: tie EDI enrollment maintenance to provider onboarding. Adding a provider or re-filing enrollment paperwork can silently break payer-ID mappings; make a post-change test claim with confirmation of acknowledgment part of the onboarding checklist.
Fourth: quarterly review of the payer-ID table against active contracts. Enrollment lapses are boring, invisible, and expensive - this one cost $8,420 outright and put $391,000 in play.