To build North Dakota Medicaid ABA timely-filing and claim-correction controls, preserve the timely original claim, remittance, transaction control number, and reason for every later action. The current policy gives replacements, resubmissions, and voids a defined filing framework when the original was timely. Keep ABA approval, provider evidence, corrected record, receipt, appeal, overpayment, and final cash result in the same episode.

Define North Dakota's complete claim episode

Leander links the original local work item to every transmission, acknowledgment, rejection, adjudication, remittance, payment, correction, void, replacement, dispute, appeal, recovery, refund, and closure event. The record preserves the raw artifact and the author of each clinical, coding, billing, payer, and financial decision. A later transaction adds history; it does not overwrite the earlier state.

Start with current North Dakota Medicaid authority

North Dakota Medicaid's October 2025 timely-filing policy says replacements, resubmissions, and voids may be submitted within 365 days of the date of service when the original claim was filed timely. It calls for the RA date and TCN in the notes and identifies exceptions. It also says the limit does not restrict recovery of overpayments or mass adjustments.

Choose the responsible North Dakota receiver

The March 2026 provider newsletter tells providers to include a clear note explaining the reason for an adjusted claim. The ABA group application and exclusion form and behavioral-health policy keep provider, approval, and service requirements distinct from claim correction. Leander verifies the currently applicable ABA authority before a claim is released.

Classify the claim before choosing an action

Leander uses the register to classify local hold, timely original, late original, rejected file, denied claim, replacement, resubmission, void, appeal, overpayment recovery, mass adjustment, or reconciled close. Staff save the artifact that proves each state and identify its sender. A clearinghouse receipt, portal label, authorization number, directory entry, claim-frequency value, or phone note establishes only the fact it actually reports.

Build the North Dakota ABA timely-filing and correction register

Capture member and eligibility; provider and ABA approval; service, authorization and record; original submission date; RA date and TCN; claim state; correction reason; replacement, resubmission or void route; exception evidence; receipt; remittance; cash owner; 365-day clock; and closure. Structured fields drive routing, aging, duplicate prevention, and reconciliation. A short narrative states the source-record issue, proposed change, uncertainty, payer instruction, member impact, disagreement, and why the accountable reviewer selected the action.

Keep clinical and billing authority separate

Leander never edits clinical content to obtain payment. A qualified clinician makes a 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 route. Operations coordinates work without inventing a clinical judgment or payer decision.

Compare the record with every claim field

Before release, Leander compares member and payer, provider identity, location, authorization, completed clinical record, actual service date and time, code and units, earlier claim state, requested change, reference identifier, attachments, route, and deadline. The reviewer states the expected effect on the original claim and payment. Any unknown remains held with an owner and escalation path.

Preserve North Dakota clocks and source versions

Leander stores separate clocks for original filing, correction, adjustment, dispute, appeal, authorization, payer response, refund, and overpayment work. Each clock has a defined start event, due event, authority, and exception evidence. The register also keeps the manual, plan, form, portal, code, fee, alert, and contact version used on the action date.

Stop duplicate and competing transactions

Leander searches the full episode before another submission. The search covers clearinghouse controls, payer references, remittances, replacements, voids, disputes, appeals, refunds, recoupments, and manual workarounds. A release states whether the earlier claim should remain, reverse, replace, or await payer action. Pending reprocessing does not authorize another claim.

Protect clients and honest records

Leander separates financial follow-up from the person's care plan. A claim hold does not silently cancel clinically appropriate care, and a payer coverage action does not become a clinician's recommendation. The practice follows its applicable notice, continuity, record, collection, and emergency policies. A provider-correctable denial is not shifted to a member merely because correction takes time.

Work through Leander's fictional cohort

Leander locks 18 fictional episodes at a Fargo practice. Eleven initially contain timely-original evidence, provider and ABA approval, completed record, RA date, TCN, correction reason, route, receipt, remittance, and cash owner. One replacement lacks the original timely proof, one note says only 'corrected,' one void lacks the TCN, one late claim assumes an exception, two episodes confuse group status with an individual provider, and two recoveries lack a cash match. 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 Leander's measures

North Dakota correction readiness is 11 of 18, or 61.1%. Sixteen episodes reach supported action or accountable hold, or 16 of 18, or 88.9%. Report local holds, file rejects, adjudicated denials, paid claims, adjustments, voids, replacements, disputes, appeals, recoveries, refunds, and final payments as separate cohorts. Every failed or held episode remains visible in its declared denominator.

Address the main North Dakota failure mode

The 365-day rule needs a defined start event and proof that the original was timely; it is not a general promise that every correction will pay. Leander records the date of service, original receipt, RA date, TCN, action date, exception source, and payer result as separate facts.

Test Leander's workflow

Leander tests a timely replacement, denied resubmission, complete void, vague adjustment note, missing TCN, claimed exception, provider-approval mismatch, and open overpayment recovery. Each test records its starting state, expected route, evidence, observed result, owner, correction, retest, and disposition. Successful transmission passes only the transmission check. Adjudication, remittance, payment, and reconciliation require separate proof.

Reconcile the remittance and cash

Leander links every payer decision to its remittance and each remittance to the actual deposit, debit, recoupment, refund, or accounts-receivable balance. Partial effects stay open. A new payment cannot erase an unresolved earlier overpayment, and a zero-dollar remittance still needs review. Finance records the claim-level allocation before closure.

Run independent acceptance

Leander gives an independent reviewer the locked cohort, official sources, original claims, 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 North Dakota ABA timely-filing and correction register

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

Related resources

Sources