To build a Mississippi Medicaid ABA claim adjustment and void workflow, start from the finalized claim and remittance. A denied claim is corrected and submitted as a new claim, while an eligible paid claim may be adjusted or voided through MESA. Preserve the original transaction, current authorization and service record, reattach required documents, track any accounts-receivable recoupment, and use the member's MississippiCAN plan process when managed care controls the claim.

Define Mississippi's claim-correction episode

Luz 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 keeps raw evidence and preserves who made each clinical, coding, billing, payer, and financial decision.

Use the current Mississippi Medicaid and MESA authority

The November 2025 MESA job aid says portal adjustment and void actions apply to paid claims in Finalized Payment status. A denied claim cannot be adjusted and should be submitted anew after correction. The job aid also warns that original attachments do not populate automatically. A void can create an accounts-receivable recoupment when money was paid.

Choose the correct Mississippi payer route

The MESA FAQ supplies current fee-for-service filing and adjustment timing and the MESA provider page identifies portal functions for claims, corrections, remittance, prior authorization, and eligibility. MississippiCAN and CHIP claims follow the responsible plan's current instructions. Luz stores the member's delivery system and source date before choosing a correction path.

Classify the current claim state before action

Luz uses the register to classify each episode as unsubmitted hold, front-end rejection, denied claim requiring a corrected new submission, paid claim eligible for adjustment, paid claim requiring void, payer-initiated recoupment, appeal or review, or reconciled closure. Staff record the actual artifact and receiver. A portal label, clearinghouse status, authorization number, frequency code, or customer-service note cannot establish a later adjudication or payment state by itself.

Build the MESA claim-correction episode register

Capture member and payer route; billing and rendering identities; service date, code, units, modifier, place, diagnosis and charge; authorization number and span; original claim and MESA status; remittance and EOB; error source; clinical-record correction if permitted; chosen route; attachments; submission receipt; new control number; payment or recoupment; owner; due date; and final disposition. Structured fields support routing, deadlines, reconciliation, and reporting. Narrative fields preserve the source-record issue, permitted correction, uncertainty, payer instruction, client impact, disagreement, and why the accountable reviewer selected the route.

Keep the source record and claim change separate

Luz never edits 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 the verified record to the current payer route. Operations can coordinate evidence and status without authoring clinical judgment.

Run a pre-release comparison

Before release, Luz 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 checks what will happen to the earlier claim and payment. Unknowns stay held with an owner and escalation path.

Preserve Mississippi clocks and source versions

Luz records a separate start and end event for the original filing limit, corrected-claim window, adjustment period, appeal deadline, authorization span, response target, and any overpayment action. A generic age field cannot safely represent all of those clocks. The MESA claim-correction episode register also stores the manual or plan version that supported the route on the action date. When later guidance changes, open episodes retain the earlier evidence and receive a documented current-source review instead of a silent overwrite.

Control duplicate and financial effects

Luz searches the full Mississippi episode before another transmission. The check covers clearinghouse control numbers, payer claim references, remittances, earlier replacements, voids, appeals, refunds, recoupments, and manual workarounds. When a new submission is valid, the release record states whether the earlier claim should remain, reverse, replace, or await payer action. Finance receives the expected debit, credit, or zero-payment result and compares it with the later remittance and bank activity. Any difference remains open with a named owner.

Work through Luz's fictional example

Luz locks 16 fictional Mississippi claim episodes. Ten initially have a verified payer route, final claim state, source record, authorization comparison, correction route, required attachments, receipt, and reconciliation owner. Two denied claims were wrongly queued as adjustments, one paid claim lacks its remittance, one void omits the expected recoupment owner, and two managed-care claims use fee-for-service instructions. Four 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 Luz's measures honestly

Initial workflow readiness is 10 of 16, or 62.5%. After targeted repair, 14 of 16, or 87.5% reach valid submission or accountable hold. Report initial submissions, front-end rejects, adjudicated denials, paid claims, adjustments, voids, replacements, appeals, recoupments, refunds, and final payments as separate cohorts. Keep every held or failed episode in its declared denominator.

Address the main Mississippi risk

Copying an old claim and changing a value without classifying the current MESA state can create duplicate billing, discard attachments, or hide an expected recoupment.

Test Luz's workflow against hard cases

Luz tests a denied claim, a paid underpayment, a payment made to the wrong provider, a full void, an attachment-dependent claim, an expired authorization, a MississippiCAN member, and a correction that changes clinical-record content. Each test preserves the starting state, expected route, evidence, observed result, owner, correction, retest, and disposition. A successful portal submission passes only the transmission check; adjudication, remittance, payment, and reconciliation require their own evidence.

Reconcile remittance and cash

Luz links each payer decision to the remittance and each remittance to the actual deposit, debit, recoupment, refund, or accounts-receivable balance. Partial effects stay open. A new payment does not erase an unresolved prior overpayment, and a zero-dollar remittance is still a claim result that needs review.

Run independent acceptance

Luz gives an independent reviewer the locked episode list, sources, original claims, clinical evidence, authorization, payer artifacts, selected 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 MESA claim-correction episode register

Luz 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 Mississippi page remains draft and noindex until the named reviewers clear it.

Apply the additional Mississippi source 1

The ASD services page anchors the benefit and prior-authorization context. It does not replace current claim instructions. Luz compares the corrected claim to the authorization and completed record before release; a MESA transaction code cannot cure a service or documentation mismatch.

Related resources

Sources