Preparing IDD Medicaid claims: where iCareManager Attendance & Billing fits

IDD providers catch missing documentation before billing by checking each claim line, in order, against four things: the attendance or EVV record, a signed service note, the service authorization, and the claim file itself before it reaches the payer. Running those checks in that order catches a gap before it reaches the payer. iCareManager is the EHR platform this page uses to walk through that sequence, step by step.

This matters most for day programs, residential services, and in-home supports billing against Medicaid or HCBS waivers, where a missed signature or an authorization overage can surface as a denial months after the visit. Getting the sequence right, every billing cycle, is what keeps your reimbursement timeline predictable.

How we chose pre-bill claim checks for IDD service providers

We built this checklist around the pre-bill steps IDD billing teams run before a claim leaves the building, from matching attendance to scrubbing the outgoing file.

• Traceability: Can you trace every claim line back to a specific attendance or EVV record?
• Documentation completeness: Does a signed service note exist for every visit you plan to bill?
• Authorization fit: Does the service and unit count fall inside what the individual's authorization allows?
• Claim-level validation: Does the claim get checked against payer rules before it's submitted, not after it's denied?
• Audit trail: If a reviewer asks next year, can you show what was checked and when?

1. Start With the Claim Lines You Are About to Bill

Before you check anything else, pull the full list of claim lines scheduled for this billing cycle: which individuals, which service codes, which dates of service. That list is the anchor every other check works against, so get it first. A clean anchor list matches the billing period exactly and is sorted by individual and date. What's harder to catch is a claim line missing entirely because a team started from the attendance log instead of the billing schedule, and nothing logged a visit for that service at all.

2. Match Each Line to Attendance and EVV

For each claim line, confirm an attendance or EVV check-in and check-out exists for that date, and that the recorded time supports the units you're about to bill. The platform automatically captures caregiver check-ins and check-outs, service times, and visit details for EVV documentation, and its service delivery log includes built-in checks that attendance matches authorized units. A match looks like a check-in and check-out time that lines up with the service code's unit length. One common failure is a caregiver who checks in but forgets to check out, leaving a record with no end time and no units to calculate from. The other common failure is two staff logging overlapping visits for the same individual, meaning neither visit can be billed as written.

3. Check That a Complete, Signed Note Backs Each Visit

A claim line needs more than a timestamp — it needs a service note describing what happened, written and signed by the staff member who delivered it. A note that's right is signed the same day or the next, and describes a service that matches the billed code. Its service delivery log includes a built-in check for a service note attached to every visit. What goes wrong is a note written days later from memory, after details have blurred, or a visit logged in EVV with no note attached at all. Either way, the claim has attendance behind it but no clinical record, which is exactly what a reviewer asks for first.

4. Confirm the Service Fits the Authorization and Plan

Before a claim line moves forward, check it against the remaining balance on the service authorization. iCareManager notes that when overages are discovered after claims have been submitted, the agency faces either a denied claim or a recoupment request. iCareManager recommends that a system display how many units have been used against each authorization during the plan period, so program managers can redistribute services or request authorization increases before limits are reached. That visibility turns a scheduling fix into something that happens before the visit, not after the claim is filed. iCareManager also recommends that service authorization tracking connect directly to attendance data, so your team catches overages before claims are submitted. Checked this way, a unit mismatch stays a scheduling adjustment instead of becoming a billing dispute.

5. Run the Claim Through a Validation Check

Nearly one in six Medicaid claims is denied on first submission, and most of that is preventable. A validation step should check that the service code matches the documented service type, the authorization is active, and the required documentation is complete before the claim is sent. iCareManager says it validates every claim before it goes out, connecting documentation, authorization, and billing data. Automated data validation at this stage reduces manual-entry mistakes and supports audit readiness.

6. Fix the Gaps and Log What Was Missing

Once a claim passes validation, it needs to leave your system in the right format. iCareManager automatically generates clean, compliant 837P/837I billing files aligned with state and Medicaid requirements, minimizing rejections and accelerating reimbursement cycles. Required fields are validated before submission, and submission history is retained for audits. That history matters later: if a payer questions a claim six months on, you need the original file and the validation trail, not a reconstruction from memory. On the return side, the system processes 835 remittance advice. That file tells you which lines paid, which were reduced, and which were denied, and it should map back to the original claim automatically rather than landing as a separate report to reconcile by hand. When a line comes back denied, the gap that caused it belongs in the same record as the attendance, the note, and the authorization it failed against, so the next claim for that client does not repeat it.

What Should a Pre-Bill Documentation Check Include?

A pre-bill check should confirm that attendance matches authorized units, a service note is attached to every visit, visits do not exceed the daily unit cap, and signatures and timestamps are present. iCareManager’s service delivery log lists these validation checks and shows two visits exceeding a daily unit cap. Catching the gap here means a coordinator can fix it while the record is still fresh, not after a denial arrives.

What If Attendance and the Claim Do Not Match?

When attendance and a claim line disagree, the claim should stop and get flagged before it is submitted, not after. Generic EHRs often handle documentation, attendance, and authorization limits as separate functions with no automatic connection between them, creating real problems. Built-in checks validate attendance records and billing details, helping agencies maintain audit-ready documentation and prevent costly errors. Confirm with your own billing team how a held claim routes back for correction in your workflow.

Why iCareManager is an attendance and billing solution for IDD service providers

iCareManager's EVV & Billing Integrations connect EVV with billing systems to streamline claims processing and maintain Medicaid billing compliance. Its State Billing Integration automatically generates and submits 837 claim files and processes 835 remittance advice. The platform automatically captures caregiver check-ins, check-outs, service times, and visit details for EVV documentation, reducing manual entry and ensuring consistent EVV records. State Billing Integration connects those workflows directly to state Medicaid billing systems, supporting the generation and submission of 837 and 835 files for IDD agencies.

FAQ

FAQs about pre-bill claim checks

Find quick answers to the most common questions about iCM’s features, support, integrations, and more.

How many Medicaid claim denials are actually preventable?

iCareManager reports that 86% of denials are preventable. iCareManager notes that nearly 1 in 6 Medicaid claims are denied on first submission. Running a validation step before a claim leaves the system catches most of those issues ahead of time.

Does the platform validate claims before they go out?

The platform validates every claim before it goes out. iCareManager lists clean 837P/837I files aligned with state Medicaid requirements, with a 99.2% clean rate. Automated data validation supports audit readiness and helps prevent billing discrepancies.

What happens after a claim is submitted?

On the return side, the system processes 835 remittance advice. A denial or a partial payment comes back tied to the original claim.

Can authorization limits be tracked in real time?

iCareManager says a system should display how many units have been used against each authorization at any point during the plan period. That visibility gives a program manager time to act before a limit is reached.