Short answer: An Early Intervention claim is only billable when the session matches the child’s active Individualized Family Service Plan (IFSP). Most generic EHRs can’t check that match. EI billing software can, before a claim ever goes out.
If a rejected claim has ever eaten up your afternoon, you’re not alone. Tracing a denial back to a unit count or an IFSP date is frustrating work, and it pulls your team away from the families you serve.
The good news? It usually isn’t a people problem. It’s a software problem, and that’s fixable.
Why do generic EHRs fall short in Early Intervention billing?
Early Intervention doesn’t follow the same billing rules as other healthcare settings. Here are three of the biggest differences.
It runs on a different payment model. Under Part C of IDEA, EI services are publicly funded, and how payers are billed (Medicaid, private insurance, and state or local funds) varies by state.
The IFSP is the authorization. A session is billable only if it matches the plan exactly: service type, frequency, duration, location, and units.
Small mistakes add up. A mismatched claim can be rejected right away. If it’s paid and found later in an audit, state auditors may apply that error rate across your billing history.
What is pre-billing validation in EI billing software?
Pre-billing validation checks each session against the child’s active authorization before a claim is created. In ProviderSoft, it happens during daily billing validation, so you catch issues while they’re still easy to fix.
Here’s what ProviderSoft checks:
- Dates and units: The session falls within active IFSP dates and stays within the authorized units.
- Rendering provider: The provider matches the therapist assigned on the authorization.
- Employment status: The provider was active with your agency on the date of service.
- IFSP status: The IFSP isn’t in Draft or Suspended status.
- Documentation: Signed session notes are on file, plus a physician prescription or order for any service type flagged as Prescription Required (like OT, PT, or Speech).
In New York, these checks line up with common EI Hub rejections, including F28, F24, F22, and F30.
How does EI billing software handle overlapping session times?
An overlap happens when two providers bill for the same child at the same time, beyond what’s allowed. In New York, that’s an F51 rejection. ProviderSoft checks start and end times in Case Management before claims are billed.
Of course, some overlaps are planned. When a co-visit is approved for both service authorizations and claimed as a co-visit, ProviderSoft recognizes it, so your team isn’t chasing sessions that are fine.
Duplicates get handled separately too. When a claim is flagged as a duplicate (F7 in New York), ProviderSoft suppresses the extra F51 flag, so you work one issue instead of two.
How do EI agencies create 837 claims and reconcile 835 remittances?
Once sessions pass validation, ProviderSoft turns them into claim files and helps you see what came back. Both steps live in the Billing module.
Sending claims (Billing > File Creation): Verified session notes become HIPAA 837/837P claim files for your state clearinghouse or State Fiscal Agent. A single file can hold thousands of claims, and each batch is saved under Billing > File History, so you always know what went out and when.
Reconciling payments (Billing > Remittance and Billing > Reconciliation): Where your state supports electronic delivery, ProviderSoft imports 835 remittance files and automatically matches payments to the claims you billed. Each result is sorted by Collection Result Status:
- Collected
- Valid A/R / Expected
- Ineligible Write-off
- Other Write-off
- Subsequent Claim
- Previous Claim
You can also track pending Medicaid reimbursements and payment discrepancies, which makes resubmissions easier. No more piecing it together in spreadsheets.
Does EI billing software work across different states?
It should, because every state does EI billing a little differently. ProviderSoft supports state-specific workflows, so you can follow your state’s rules without workarounds.
- New York: Exchanges 837, 835, and 277 files with PCG / EI Hub and eMedNY.
- Texas and New Mexico: Supports agencies acting as the local municipality or EIOD, including referral tracking, HCFA 837 exports, and municipal reporting.
- Pennsylvania: Supports PROMISe 837/835 workflows and lets agencies run EI and ABA services in one platform.
- California: Supports California Early Start agencies.
Frequently asked questions
Why do Early Intervention claims get rejected? Most EI rejections come from a mismatch between the session and the active IFSP, such as units over the authorized cap, a date outside IFSP dates, the wrong rendering provider, or overlapping session times.
Can a standard EHR handle EI billing? Most generic EHRs aren’t designed to validate sessions against an IFSP or support state-specific EI payer workflows. Agencies using them often rely on manual checks to fill the gap.
What is an F51 rejection in Early Intervention? In New York’s EI Hub, an F51 edit means a claim’s start and end times overlap with another claim for the same child beyond allowed thresholds.
What is 835 reconciliation? 835 reconciliation matches the payer’s Electronic Remittance Advice against the claims you originally billed, so you can see what was collected, what’s still expected, and what was written off.
Does ProviderSoft support EI billing in multiple states? Yes. ProviderSoft supports state-specific EI billing workflows, including New York, Pennsylvania, Texas, New Mexico, and California.
Billing that starts with the IFSP
Your team entered Early Intervention to help children and families, not chase rejected claims. The right software lets them get back to that.
Agencies like 365 Kids have used ProviderSoft to streamline workflows as the agency scaled, without adding administrative overhead.
Built for Early Intervention. Not adapted to it.
We’d love to show you how it works. Schedule your demo today.
by Mackenzie McIntyre