To build a South Carolina Medicaid ABA void and replacement claim workflow, verify that Healthy Connections fee for service adjudicated the original claim, then preserve its Claim Control Number and remittance. Follow the current billing guide for a void or void-and-replace packet, including Form 130, the required original-claim evidence, corrected claim, reason, and attachments. Use each MCO's current route for managed-care claims and reconcile recoupment and replacement payment separately.

Define South Carolina's claim-correction episode

Samir 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 Healthy Connections Medicaid authority

The April 1, 2026 Provider Administrative and Billing Guide explains the paper void or void-and-replace route using Form 130. It calls for the original remittance, replacement claim and relevant documentation, and identifies the original CCN, reimbursed provider, member, adjustment type, and one reason as packet fields. Samir uses the current guide version and records any newer portal or EDI instruction before action.

Choose the correct South Carolina payer route

The ASD provider-manual change record and provider resource page anchor service-specific versions. The enrollment page distinguishes individual and group enrollment and later MCO contracting. A fee-for-service Form 130 packet cannot establish an inactive provider or correct a claim that an MCO adjudicated.

Classify the current claim state before action

Samir uses the register to classify fee for service versus MCO, then rejected claim, denied claim, paid claim requiring void, paid claim requiring void and replacement, plan correction, appeal, recoupment, or reconciled close. 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 Healthy Connections void and replacement packet register

Capture member and payer; reimbursed provider and location; service and authorization; original claim, CCN and remittance; claim state; void or void-and-replace intent; one adjustment reason; corrected claim; Form 130 fields; attachments; submission receipt; recoupment; replacement payment; owner; deadline; and closure. 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

Samir 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, Samir 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 South Carolina clocks and source versions

Samir 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 Healthy Connections void and replacement packet 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

Samir searches the full South Carolina 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 Samir's fictional example

Samir locks 19 fictional South Carolina episodes. Twelve initially have the correct payer, paid-claim evidence, CCN, remittance, route, reason, packet, and financial owner. One MCO claim uses Form 130, one CCN is truncated, one replacement claim omits an authorization number, one packet lacks the original RA, one lists two reasons, and two have no recoupment plan. Five 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 Samir's measures honestly

Initial readiness is 12 of 19, or 63.2%. Seventeen episodes reach valid action or documented hold, or 17 of 19, or 89.5%. 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 South Carolina risk

A void-and-replace packet can be administratively complete while pointing to the wrong payer, provider, CCN, or authorization episode. Match every Form 130 field to the remittance.

Test Samir's workflow against hard cases

Samir tests a pure void, a void and replacement, an MCO claim, a missing RA, a wrong CCN, two competing correction reasons, a group-versus-individual provider mismatch, and a recoupment followed by replacement payment. 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

Samir 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

Samir 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 Healthy Connections void and replacement packet register

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

Related resources

Sources