- A timely filing limit is set by each payer contract, plan or program rule, and it is often measured from something other than the date of service, so keep a table per payer and confirm it against the contract.
- Most claims that miss filing limits do not sit in billing; they age upstream, waiting on a signature, an authorization, an enrollment or a primary payer's decision.
- A claim that was rejected before the payer accepted it may not count as filed, so a rejection is a warning that the clock is still running.
- Corrected claims, new claims and appeals are different instruments with different clocks; sending the wrong one can produce a duplicate denial and burn the time you had left.
- Proof of timely filing is the acceptance record from the payer or clearinghouse, kept with the claim, not a screenshot someone remembers taking.
A timely filing denial is the most frustrating line on a remittance because nothing was wrong with the care. The patient attended, the note was signed, the authorization covered the day. The claim simply reached the payer after the payer stopped accepting it. In most cases the program cannot bill the patient for it either, so the service becomes a write-off. Picture a hypothetical IOP day delivered in March: the note was signed in April, the claim was held while a new clinician's payer enrollment was pending, the enrollment cleared in June, and the claim went out in July. Every person in that chain did their part. Nobody owned the date. This guide is about owning the date.
Why timely filing is a workflow problem, not a calendar problem
Ask a billing team about timely filing and they will usually describe the submission step: claims go out daily, the clearinghouse accepts them, nothing is late. That is generally true of claims that reach billing in good shape. The claims that miss filing limits are the ones that did not reach billing, or reached it and were sent back out to someone else to fix.
A claim's age is set by the date of service, or whichever event the payer measures from. Its progress is set by every hold placed on it. When those two are tracked in different places, the claim can be technically "in progress" in five departments while its filing window closes in none of them.
- Documentation holds. The note is unsigned, a co-signature is missing, or the group note was never individualized. The claim waits for the clinician.
- Authorization holds. The authorization was pending, exhausted or covered a different level of care. The claim waits for utilization review.
- Enrollment holds. The rendering clinician is credentialed internally but not yet enrolled with this payer. The claim waits for credentialing.
- Coordination of benefits holds. A second plan appeared mid-episode and nobody is sure which is primary. The claim waits for the patient, the payer or both.
- Rejection loops. The claim went out, came back rejected, and is sitting in a portal or a spreadsheet until someone has time.
Each hold is reasonable on its own. The failure is that none of them carries a deadline derived from the payer's filing limit. Fixing timely filing means pushing that deadline back upstream to whoever is holding the claim.
Know the clocks you are actually working to
There is no single timely filing limit. Each payer sets its own, and it can differ by plan, by product line, by whether you are in or out of network, and by the terms of your specific contract. Medicaid programs and their managed care plans set their own rules. Medicare is the one case where the rule sits in federal regulation: under 42 CFR 424.44, Medicare claims generally must be filed no later than one calendar year after the date of service, with limited exceptions set out in the same section. For every other payer, the source of truth is the contract, the provider manual it incorporates, and any amendments since.
More important than the number of days is what the clock is measured from and which transaction it applies to. A single payer relationship usually has several clocks running at once:
- Initial filing. How long you have to submit the first claim. It may be measured from the date of service, from the discharge date for an inpatient-style or residential stay, or from the end of a billing period. A program that bills residential stays on interim claims needs to know which date applies to each interim period.
- Corrected or replacement claims. How long you have to correct a claim the payer already adjudicated. Some payers measure this from the original date of service, some from the date of the original remittance. They are not always the same window as initial filing.
- Appeals and reconsiderations. How long you have to dispute an adjudication. Usually measured from the date of the remittance or denial notice, and often with more than one level, each with its own clock.
- Secondary claims. How long you have to bill a secondary payer, often measured from the date of the primary payer's remittance rather than the date of service. Some contracts have no secondary-specific rule, which means the initial filing limit applies even while you wait on the primary.
- Retroactive eligibility or enrollment. Some payers allow a window from the date retro coverage or provider enrollment was granted. Many do not. Know which before you hold a claim on the assumption that one exists.
Filing limits change with contract renewals, plan transitions and provider manual updates, and they are not always where you expect them. Before relying on any limit in this guide's framework, confirm it against your current contract and the payer's current provider manual, and record where you found it and on what date.
Build a timely filing table you will actually use
Most programs have this information somewhere: a payer grid from a former billing manager, a binder of contracts, a sticky note on a monitor. What they rarely have is one table that is current, sourced, and used to calculate deadlines. Build one row per payer and plan, and include these columns:
- Payer and plan or product line, including each Medicaid managed care plan separately.
- Initial filing limit, and the event it is measured from.
- Corrected claim limit, and the event it is measured from.
- Appeal limit for each level, and the event each is measured from.
- Secondary claim rule, if the contract has one.
- Retroactive eligibility or enrollment rule, if any.
- What the payer accepts as proof of timely filing.
- Whether a rejected claim counts as filed, if the payer states it.
- Source document, section, and the date someone last verified the row.
The last column is the one that keeps the table honest. A limit nobody has checked since the contract renewed is a guess with formatting. Assign one person to re-verify every row at each contract renewal and whenever a payer publishes a provider manual update, and put the next review date on the table itself.
Then use it. A filing deadline per claim, calculated from the table at the time the service is recorded, is what lets you sort work by days remaining rather than by days old. Those two orderings are different, and only one of them tells you which claim to work first.
Where the days go: claims age before they are ever submitted
Run one exercise before changing anything. Pull every timely filing denial from the last six months and, for each one, reconstruct the dates: service, note signed, claim created, first submission, any rejection, final submission. You are looking for where the gap opened. In most programs it opens before billing touches the claim.
The unsigned note from the clinician who left
A clinician resigns in March with a handful of unsigned notes. The notes cannot be signed by someone else, and the claims behind them sit. By the time anyone decides what to do, some of those services are close to a payer's limit. The fix is upstream: a documentation deadline that triggers escalation within days, not a monthly report, and an offboarding step that checks the departing clinician's open documentation before their last day. How to handle late entries properly is covered in late entries, addenda and amendments.
The enrollment that was "almost done"
A new clinician starts seeing patients while payer enrollment is pending. Their claims are held, reasonably, because submitting under an unenrolled provider invites a denial. But a pending enrollment has no fixed completion date, and the held claims are aging the whole time. Before anyone schedules a clinician whose enrollment is pending, decide with the payer contract in hand whether retroactive billing will be allowed and from when. If it will not, the scheduling decision is a financial decision and should be made as one. The credentialing piece covers tracking enrollment by payer with effective dates.
The authorization that came back late
Utilization review requested an extension; the payer took weeks to decide; the claims for those days were held pending the decision. If the approval comes back retroactive, the claims can go out. If the decision drags long enough, they go out late. Holds for pending authorizations need their own filing-deadline flag so that the UR coordinator, not just billing, sees the date approaching.
The second insurance plan nobody confirmed
A patient reports new coverage in week three. The claims stop while billing tries to establish which plan is primary. Meanwhile, both payers' filing clocks are running, and the secondary payer's clock may be running from the date of service rather than from a primary remittance that does not exist yet. The coordination of benefits piece covers the order-of-benefits work; for filing purposes, the point is that a COB question needs an owner and a deadline the day it is raised.
A hold without a deadline is not a pause. It is a write-off that has not been dated yet.
Rejections do not stop the clock
There is a practical difference between a claim that was rejected and a claim that was denied. A rejection generally stops the claim before the payer accepts it for adjudication: a missing subscriber ID, an invalid NPI, a format error. A denial generally means the payer accepted and adjudicated the claim and decided not to pay. Terminology varies by payer and clearinghouse, but the consequence for filing is the same in most cases: a rejected claim may not count as received, so the original submission date may not protect you.
That makes rejection handling a filing-deadline task, not a cleanup task. Specifically:
- Work clearinghouse and payer front-end rejections daily, not weekly. A claim that sits rejected for two weeks has lost two weeks of its window.
- Distinguish clearinghouse acceptance from payer acceptance. A claim can pass the clearinghouse and still be rejected by the payer's front end. Your proof of filing is the payer's acknowledgment, not the clearinghouse's.
- Check for claims that were never acknowledged at all. A claim with a submission record and no acceptance or rejection is not filed; it is missing. Reconcile submitted claims against acknowledgments on a fixed schedule.
- Ask each payer whether it treats a rejected claim as timely if resubmitted within some period. Some state a position in their provider manual. Record the answer in your table.
Corrected claims, new claims and appeals: choosing the right path
When a claim needs to change after the payer has it, there are generally three instruments. Choosing the wrong one is one of the most common ways programs burn their remaining window, because the payer responds to the wrong instrument with a duplicate denial or a rejection, and the clock keeps running while that round-trip happens.
A new claim
Use a new, original claim when the payer never accepted the first one: it was rejected at the front end, or it never reached the payer. There is nothing on the payer's side to correct. Sending a corrected claim for a claim the payer has no record of usually produces another rejection.
Do not send a new claim for a service the payer already adjudicated, even if it was adjudicated wrongly. The payer will typically deny it as a duplicate, and you will have spent time and possibly days of your window learning something you already knew.
A corrected or replacement claim
Use a corrected claim when the payer accepted and adjudicated the original and the original contained an error on your side: the wrong units, a missing modifier, the wrong rendering provider, the wrong date of service. The corrected claim tells the payer to replace the original. It needs the claim frequency indicator your payer requires for a replacement and the payer's original claim number, and it should carry the full corrected claim, not only the changed line. Payers also have a separate mechanism to void or cancel a claim that should not have been billed at all. Check your payer's billing guidance for the exact codes and fields; they are specified in the claim standards and payers apply them with their own variations.
Before sending a corrected claim, confirm the documentation supports the corrected version. A correction that adds units or changes a service code after payment is exactly what a reviewer will look at later, and the record has to show why the original was wrong.
An appeal or reconsideration
Use an appeal when the claim you sent was right and the payer's decision was wrong, or when you disagree with the payer's determination: a medical necessity denial, an authorization dispute, a contract rate dispute, or a timely filing denial you can rebut with proof. An appeal does not change the claim; it asks the payer to change its decision. It runs on its own clock, usually measured from the remittance date, and usually requires supporting documents.
A frequent mistake is sending a corrected claim to dispute a denial when nothing on the claim was wrong. The payer adjudicates the corrected claim the same way, denies it again, and the appeal window has kept running the entire time. If the claim is accurate, appeal. If the claim is wrong, correct it.
A quick decision sequence
- Did the payer accept the original claim for processing? If no, send a new claim, and check how much of the initial filing window remains.
- If yes, was anything on the claim wrong on your side? If yes, send a corrected or replacement claim, within the corrected claim window.
- If nothing on the claim was wrong, do you disagree with the payer's decision? If yes, appeal, within the appeal window, with documentation.
- If the service should not have been billed at all, void it, and document why.
Proof of timely filing: what holds up
Eventually a payer will deny a claim for timely filing that you believe you submitted on time. Sometimes the payer lost it. Sometimes the original was rejected and nobody noticed. Either way, the appeal turns on evidence, and the evidence has to exist before you need it.
Generally, the strongest proof is a payer-generated acknowledgment showing the payer received and accepted the claim on a specific date, such as a claim acknowledgment report (the 277CA transaction in electronic claims) or the payer's own acceptance report. A clearinghouse acceptance report showing the claim was forwarded to the payer is often accepted as supporting evidence, though some payers want proof the payer itself received it. A printout of your own claim screen showing a submission date is usually weak, because it shows what you intended to send rather than what the payer received. What each payer accepts varies; record it in your filing table.
- Keep acknowledgments attached to the claim, not in a clearinghouse portal you may stop using. When you change clearinghouses, export the history first.
- Keep the original claim number and any payer claim control number with every resubmission, so you can show the chain from first submission to final.
- Keep a record of any payer correspondence that extends or waives a deadline, including phone calls, with the date, the representative's name, and any reference number.
- Keep proof for as long as an appeal or audit could ask for it. Your record retention policy should cover billing records, not only clinical ones.
Secondary claims and coordination of benefits
Secondary billing is where timely filing quietly fails most often, because the secondary claim cannot go out until the primary pays or denies, and the primary can take a long time. Three habits help.
First, know each secondary payer's rule. If it measures from the primary remittance date, the clock starts when the 835 arrives, and secondary billing should be triggered by remittance posting, not by someone remembering. If it measures from the date of service, a slow primary can push the secondary claim past its limit no matter how quickly you act after the primary pays. In that case, ask the secondary payer whether a claim submitted with evidence of a pending primary will be held or whether you should submit and expect a pending or denial you can later correct.
Second, treat a primary denial as a secondary trigger, not just a primary problem. When a primary denies for a reason that means the secondary should pay, such as non-coverage, the secondary claim should go out with that remittance attached while you decide whether to appeal the primary.
Third, when COB is unresolved, set a decision deadline. A patient with two plans and no confirmed order of benefits is a filing risk for both payers. Someone should own getting the answer, with a date that leaves time to bill both.
Exceptions, extensions and how to ask for them
Some payers allow exceptions to filing limits in defined circumstances: retroactive eligibility granted after the service, administrative error by the payer, or delays outside the provider's control. Medicare's exceptions, for example, are listed in 42 CFR 424.44 and described in CMS's claims processing guidance. Commercial and Medicaid managed care exceptions, where they exist, are in the contract or provider manual and are usually narrower than providers hope.
When you ask, ask specifically. Identify the claims, the dates of service, the event that caused the delay, the date that event was resolved, and the documentation that proves each date. A request that says "our biller left and claims were delayed" describes an internal problem; payers rarely treat that as an exception. A request that shows the payer's own retroactive eligibility notice dated after the service, followed by a claim filed promptly after it, is the kind that tends to succeed.
Do not plan around exceptions. They are a remedy for the rare case, not a strategy for a backlog.
Running an aging-by-deadline worklist
Traditional accounts receivable aging sorts claims by how old they are. That is useful for cash forecasting and nearly useless for preventing timely filing denials, because a claim that is old for a payer with a long limit is less urgent than a younger claim for a payer with a short one. Add a second view: every unsubmitted, rejected, or held claim sorted by days remaining until its filing deadline, with the hold reason and the owner beside it.
Then run it weekly, the same way every week:
- Pull every claim with a filing deadline inside your warning window, including claims not yet created because documentation is incomplete. Set the warning window per payer, long enough to resolve the slowest hold you typically see.
- Group by hold reason: documentation, authorization, enrollment, COB, rejection, other.
- Send each group to the team that owns the source: clinical leadership for notes, UR for authorizations, credentialing for enrollment, admissions or billing for COB and demographics. Each claim gets a named owner and a due date that leaves time to submit.
- Review the claims closest to their deadline in a short meeting with those owners present. The question for each is what has to happen, by whom, by when.
- Record any claim that missed its deadline and why, and feed it into the monthly root-cause review.
This is also the point to decide, explicitly, when to submit a claim that is not perfect. If a hold cannot be resolved before the deadline, the contract terms and your compliance policy decide whether to submit what you can stand behind and correct later, or accept the loss. That is a decision for the billing manager and compliance lead together, made with the deadline in view, not something that happens by default when the date passes. Never submit a claim the documentation does not support to beat a deadline.
When a timely filing denial arrives anyway
Some will. Handle each one the same way.
- Check whether it is rebuttable. Do you have a payer acknowledgment showing receipt within the limit? Was the claim a corrected claim the payer measured from the wrong date? Was there retroactive eligibility? If yes, appeal with the proof.
- Check the patient balance rule before touching it. Many contracts prohibit billing the patient for amounts denied because of provider filing failures. Confirm against the contract and your financial policy before moving anything to patient responsibility; usually it is a provider write-off.
- Code the write-off distinctly. A timely filing write-off should be identifiable in reporting, separate from contractual adjustments and other denials, so you can count it and see whether it is shrinking.
- Find the hold that caused it. Every timely filing write-off had a cause upstream. Record it in one of the hold categories, so the monthly review can see whether the problem is unsigned notes, enrollment, UR, COB or rejection handling.
Who approves the write-off matters too. A timely filing write-off is a loss the organization chose not to prevent, and it should be visible to the person accountable for revenue, not absorbed silently at the posting step. The broader approach to routing denial causes back to their source is in denial prevention.
A hypothetical worked example
Say a 30-bed residential program with an attached IOP runs the six-month exercise described above and finds a small cluster of timely filing write-offs. Reconstructing the dates shows three patterns. Several IOP claims were held for a clinician whose enrollment with one plan took far longer than expected, and the plan did not permit retroactive billing to the start date. Several residential claims were secondary claims that went out late because secondary billing depended on one biller noticing primary payments. And a few were rejected at the payer's front end for a subscriber ID mismatch and sat in a clearinghouse portal for weeks.
The program makes three changes. Scheduling now requires credentialing to confirm, per payer, whether a pending clinician's services will be billable, and patients covered by plans without retroactive enrollment are scheduled with an enrolled clinician until enrollment clears. Remittance posting now creates a secondary billing task automatically whenever a primary payment or denial posts for a patient with secondary coverage, with the secondary payer's deadline attached. Front-end rejections are worked daily by a named person, and a weekly reconciliation checks that every submitted claim has a payer acknowledgment. None of these is a billing heroics project. Each one moves the deadline to where the hold actually lives.
Where the system can carry some of this
Everything in this guide can be run with a spreadsheet and discipline, and many programs do. The parts that are hardest to sustain by hand are the per-claim deadline calculation, the daily rejection handling, and the routing of each hold to its real owner. In Unisona Health, front-end rejections come back through the included clearinghouse connection with the failing field identified, and claim scrubbing checks authorization windows, credentials and modifiers before the claim leaves, so fewer claims enter the rejection loop at all.
Once claims are out, denials and partial payments land in the denials queue during remittance posting, each with the reason, the dollars at risk, the deadline and a named owner, so an appeal window does not close in a shared tab. Whatever tool you use, the test is the same: for any held claim, can someone tell you today how many days it has left and who is responsible for it?
Frequently asked questions
What is the timely filing limit for behavioral health claims?
There is no single limit. Each payer sets its own, and it can vary by plan, product line, network status and contract. Medicare generally requires claims to be filed within one calendar year of the date of service under 42 CFR 424.44, with limited exceptions. For other payers, confirm the limit against your current contract and provider manual and record where you found it.
Does a rejected claim count as timely filed?
Often not. A rejected claim generally stopped before the payer accepted it for processing, so the payer may have no record that it was received. Treat every rejection as a sign the filing clock is still running, work rejections daily, and check each payer's stated position on resubmitting rejected claims.
Should I send a corrected claim or an appeal?
Send a corrected or replacement claim when the payer adjudicated the original and something on your claim was wrong. Send an appeal when the claim was accurate and you disagree with the payer's decision. Sending a corrected claim to dispute a correct claim's denial usually produces the same denial while the appeal window keeps running.
What counts as proof of timely filing?
Generally the strongest proof is a payer-generated acknowledgment showing the payer received and accepted the claim on a specific date, such as a 277CA claim acknowledgment. A clearinghouse acceptance report is often accepted as supporting evidence. A screenshot of your own claim screen is weak. Keep acknowledgments attached to the claim and export them before changing clearinghouses.
Can we bill the patient for a timely filing denial?
Usually not. Many payer contracts prohibit billing the patient for amounts denied because the provider filed late. Confirm against your contract and financial policy before moving anything to patient responsibility, and code timely filing write-offs separately so you can track them.
How do we prevent timely filing denials?
Keep a sourced timely filing table per payer, calculate a filing deadline for every claim, and sort held and rejected claims by days remaining rather than days old. Route each hold, whether documentation, authorization, enrollment, coordination of benefits or rejection, to the team that owns it with a named owner and a due date.
