To build a Michigan Medicaid ABA claim adjustment and void workflow, identify whether CHAMPS, a Medicaid health plan, or a PIHP controls the transaction and whether it is a claim or encounter. Preserve the original transaction, TCN, remittance or response, authorization, service record, correction reason, adjustment or void receipt, and financial result. Reconcile any overpayment promptly and use the current behavioral-health policy for the service date.

Define Michigan's correction episode

Dev defines one episode as the original claim or local hold plus every transmission, rejection, adjudication, remittance, payment, correction, void, replacement, appeal, recoupment, refund, and closure event tied to it. The episode preserves raw evidence and the author of each clinical, coding, billing, payer, and financial decision.

Use the current Michigan Medicaid behavioral health authority

Michigan's CHAMPS Claims and Encounters page provides resources to submit, find, adjust, or void claims and encounters. The broader CHAMPS page identifies claims status, adjustments or voids, payment status, prior authorization, enrollment, and eligibility as separate functions. Dev records the transaction type and responsible payer before action.

Choose the responsible Michigan receiver

Michigan's autism portal supplies public program resources. The behavioral-health billing page says its code charts are references and that the Medicaid Provider Manual controls discrepancies. Dev also checks the 2026 policy bulletin index for service-date changes. PIHP, health-plan, and direct CHAMPS routes remain distinct.

Classify the claim state before acting

Dev uses the register to classify CHAMPS fee-for-service claim, Medicaid health-plan claim, PIHP claim, encounter, front-end reject, adjudicated denial, adjustment, full void, partial adjustment, overpayment, appeal, or reconciled close. Staff save the artifact that proves the state and receiver. A portal label, clearinghouse message, authorization number, claim-frequency value, directory entry, or call note establishes only what that source actually reports.

Build the Michigan CHAMPS claim and encounter correction register

Capture member and delivery system; claim or encounter; provider and affiliation; location; service and authorization; original TCN or plan reference; response and remittance; other insurance; correction reason; full or partial effect; route; receipt; new adjudication; credit balance or payment; owner; deadline; and closure. Structured fields drive routing, aging, and reconciliation. A short narrative records the source-record issue, permitted change, uncertainty, payer instruction, client impact, disagreement, and reason the accountable reviewer selected the action.

Keep clinical and billing authority distinct

Dev never changes clinical content merely to obtain payment. A qualified clinician makes any permitted late entry, addendum, or correction under the practice's documentation policy, preserving original content, authorship, dates, and reason. A qualified coding or billing reviewer maps verified evidence to the current receiver's route. Operations coordinates without authoring a clinical judgment or payer decision.

Run a source-to-claim comparison

Before release, Dev compares member and payer, provider identity, service location, authorization, completed record, actual date and time, code and units, prior claim state, requested change, reference identifier, attachment set, route, and deadline. The reviewer also states what should happen to the earlier claim and payment. Unknowns remain held with an owner and escalation path.

Preserve Michigan clocks and versions

Dev stores separate clocks for original filing, correction, adjustment, appeal, authorization, response, refund, and overpayment work. Each clock has a named start event, due event, source, timezone when relevant, and exception evidence. The register also keeps the manual, plan, form, portal, fee, code, and alert version used on the action date. Later guidance triggers review without erasing the earlier source.

Prevent duplicate action

Dev searches the complete Michigan episode before another transmission. The check covers clearinghouse controls, payer references, remittances, replacements, voids, disputes, appeals, refunds, recoupments, and manual workarounds. A valid release states whether the earlier claim should remain, reverse, replace, or await payer action. A pending reprocessing event is never treated as permission to submit another claim.

Protect clients and honest records

Dev separates financial follow-up from the family's care plan. A claim hold does not silently cancel clinically appropriate care, and a coverage decision does not become a clinical recommendation. The practice follows its lawful notice, continuity, record, collection, and emergency policies. Staff never shift a provider-correctable denial or prohibited charge to a member merely because correction is slow.

Work through Dev's fictional cohort

Dev locks 24 fictional Michigan episodes at a Grand Rapids network. Sixteen initially have delivery system, transaction type, provider, authorization, TCN, final state, route, receipt, and overpayment owner. One encounter is treated as a paid claim, one PIHP transaction enters CHAMPS, one void should be partial, one other-insurance result is missing, one provider affiliation is inactive, one episode cites an obsolete bulletin, and two lack remittance evidence. Six repair. Two remain held. The example is synthetic. It tests workflow and denominator logic and establishes no coverage, authorization, claim, appeal, compliance, legal, or payment conclusion for a real practice or member.

Calculate Dev's measures

Initial readiness is 16 of 24, or 66.7%. Twenty-two episodes reach valid action or accountable hold, or 22 of 24, or 91.7%. Report local holds, front-end rejects, adjudicated denials, paid claims, adjustments, voids, replacements, disputes, appeals, recoupments, refunds, and final payments as separate cohorts. Every held or failed episode remains in its declared denominator.

Address the central Michigan failure mode

Michigan behavioral-health reporting can involve claims and encounters. Treating them as interchangeable can produce a financially meaningless adjustment or remove required utilization reporting. Dev assigns separate acceptance and reconciliation evidence to the claim and encounter paths before closure.

Test Dev's workflow

Dev tests a CHAMPS paid claim, PIHP encounter, MHP denial, full void, partial credit balance, other-insurance update, provider-affiliation problem, and policy-bulletin change. Each test preserves its starting state, expected route, evidence, observed result, owner, correction, retest, and disposition. A successful submission passes the transmission check only. Adjudication, remittance, payment, and reconciliation require their own artifacts.

Reconcile remittance and cash

Dev links each payer decision to the remittance and each remittance to the actual deposit, debit, recoupment, refund, or accounts-receivable balance. Partial effects remain open. A new payment does not erase an unresolved earlier overpayment, and a zero-dollar remittance still needs review. Finance records claim-level allocation before closing the episode.

Run independent acceptance

Dev gives an independent reviewer the locked cohort, official sources, original claims, source records, authorizations, payer artifacts, routes, receipts, remittances, and cash reconciliation. The reviewer reproduces one correction and one hold. A changed cohort, missing failure, unsupported route, or unexplained financial difference fails acceptance.

Maintain the Michigan CHAMPS claim and encounter correction register

Dev reviews sources monthly and after program, plan, manual, code, form, portal, contract, authorization, fee, edit, appeal, or contact changes. Each source retains owner, effective and checked dates, scope, supersession, and next review. This Michigan page remains draft and noindex until the named reviewers clear it.

Related resources

Sources