A plan roster, your census, and the authorization list will never agree by accident. They update on different clocks. A monthly reconciliation finds terminations before the next visit, catches plan changes before the claim, and turns denials into exceptions instead of surprises.
Why the three lists drift apart
The plan roster reflects enrollment as the payer understands it. The census reflects whom intake admitted and scheduling is serving. The authorization list reflects what was approved for a service period. Each source changes independently.
Enrollment files lag. A discharge may not reach the plan until a retroactive termination is processed. A plan change can arrive with a new member ID while the old authorization stays open, which is why the authorization handoff workflow matters. Intake may use a nickname the plan never sees.
Federal standards shape how plans report enrollment and process changes, but they do not synchronize your local records. The Medicaid managed care overview and 42 CFR Part 438 explain the payer environment. Your state contract and provider manual control the correction paths.
Set a monthly cadence with a hard snapshot
Choose one reconciliation day, such as the third business day after month end, and pull all three sources that day. Record the timestamp, file name, and person who pulled each file. A Monday roster and a Friday census export will produce differences that are not real.
Compress the work into a short cycle: pull and save on day one, match and publish the log on day two, make plan calls on day three, submit corrections by day five, and escalate whatever remains on day ten.
Choose matching keys that survive real data
Use the plan member ID as the primary key and your internal client ID as the secondary key. Name and date of birth are fallback evidence, not a reliable key.
Normalize identifiers before comparing
Strip spaces, hyphens, and punctuation from member IDs, then preserve leading zeros, which spreadsheets often drop. Standardize suffixes and apostrophes without erasing the original value. Store both the raw and normalized strings.
When the member ID is missing
Match on last name, first name, and date of birth, then require a second check such as the last four digits of the plan ID or the service address. Never use a Social Security number as a matching field. If two clients share a name and birth date, send the pair to the lead rather than guessing.
Sort differences into four buckets
Every difference needs one bucket and one owner. Start with this table and adapt the labels to your systems.
| Discrepancy | What it usually means | First action | Owner |
|---|---|---|---|
| On roster, not in census | New enrollment or intake lag | Confirm admission and service status | Intake |
| In census, not on roster | Termination or enrollment pending | Call the plan before the next visit | Billing |
| Plan changed mid-month | Member moved products or MCOs | Verify effective date and new ID | Billing |
| Authorization missing | Service not requested or wrong dates | Compare order with plan record | Scheduling |
Separate eligibility from authorization
Eligibility answers whether the person is enrolled. Authorization answers whether a service is approved. A client can be eligible and still have no approved hours. A confirmed eligibility record cannot close an authorization gap.
Decide which items need a call and which need an adjustment
Call the plan when enrollment status, effective date, plan assignment, member ID, or waiver eligibility is unclear. Call when a termination looks retroactive or a plan change has no notice. Call when the portal and roster file disagree.
Adjust the claim when the plan has confirmed the facts in writing and the remaining issue is service linkage, units, or dates. Hold the claim when a retroactive termination is under review. Do not rebill under a different plan until the payer confirms the correct plan and effective date.
Assign one owner per queue
Intake owns demographic corrections and enrollment evidence. Billing owns claim impact and payer correspondence. Scheduling owns service continuity and the authorization request. The reconciliation lead owns the log, calendar, and escalation decision.
Name one accountable person per queue and a backup for the lead.
Keep a log and escalate on a clock
The log needs the discovery date, client, member ID, source files, discrepancy type, dollars or services at risk, owner, plan reference, status, resolution, and closed date. Add a next-action date so aging is visible. Use statuses such as open, awaiting plan, awaiting correction, adjustment submitted, resolved, and escalated. "Called the plan" is a note, not a status.
Escalate when a retroactive termination affects delivered services, a plan change leaves active visits without authorization, three contact attempts go unanswered, or exposure crosses a manager-set threshold. Send it to the operations director or compliance lead instead of making a fourth call. Keep the payer escalation list current, because a stale contact is how small gaps become write-offs.
Worked example
Client A appears on the plan roster with a first-of-month start date, but intake has no admission because the referral went to another branch. The coordinator verifies the address, creates the census record, and schedules the assessment. No claim moves until the start date is confirmed.
Client B was on Plan 1 at the start of the month and Plan 2 by the fifteenth. The authorization extract still shows Plan 1 units. Billing confirms the transition date, requests a Plan 2 authorization, and splits the claim. Scheduling learns which visits belong to each side.
Client C is terminated retroactively to the prior month. The plan confirms the date in writing. Billing holds the claims, checks whether services were delivered after termination, and routes the case to compliance for a billing or client-responsibility decision. The log stays open until the last claim closes.
Measure the process, then fix the causes
Track roster-to-census match rate, open discrepancy count and age, first-cycle closure, adjustment dollars, and intake-caused errors. Review the same three payer-specific patterns each month.
The failure modes repeat: matching on names only, pulling files on different days, letting scheduling improvise enrollment fixes, closing items without a plan reference, writing off small balances to clear the log, and saving the work for year end.
When the cycle consistently runs long, fix the upstream cause: require a plan ID at intake, maintain a controlled payer list, or block scheduling without an authorization. A virtual assistant can pull files, normalize identifiers, maintain the log, and prepare call lists. Eligibility decisions and claim approvals stay with authorized staff.
Bring your roster, census extract, and authorization report to a working session and map one cycle on your systems. Talk with our team about the support rhythm, or review the billing support scope and compliance boundaries before assigning ownership.

