Closing the Claim Submission Batch
A claim submission batch closes when its released population and control totals reconcile to transmission evidence and expected responses, every claim has a known state, every exception has an owner, and closure evidence is retained. Closure does not mean adjudication or payment.
Updated 2 min read
On this page
Key takeaways
- Batch closure is an operational control, not payer adjudication.
- Every released claim must reach a known state or owned exception.
- Unresolved items remain visible after the routine batch closes.
What it controls
A claim submission batch closes when its released population and control totals reconcile to transmission evidence and expected responses, every claim has a known state, every exception has an owner, and closure evidence is retained. Closure does not mean adjudication or payment.
Closing after file generation or a positive batch response can strand individual rejections and missing acknowledgments. A formal closure test ensures the operational handoff to rejection, status, and follow-up queues is complete.
Design the work
Define expected response stages by channel and destination. Compare claim, line, and charge totals across release and transmission, then reconcile claim-level accepted, rejected, and unresolved states to the original population.
Set a documented cutoff and exception process for late or missing responses. Do not force unresolved claims into accepted status merely to balance the batch; transfer them with owner, deadline, next action, and evidence.
Minimum controls
- Released-to-transmitted control-total agreement.
- Expected response receipt and identifier matching.
- Claim-state reconciliation back to the released count.
- Authorized closure with an attached exception inventory.
Keep claim-specific information in the approved system
Put it into practice
Reconcile the population
Compare released, transmitted, accepted, rejected, and unresolved counts and amounts.Transfer exceptions
Assign each failed or missing response to a controlled owner and deadline.Approve closure
Retain reconciliations, report references, reviewer, timestamp, and open-exception inventory.
Review and improve
Review the control on a fixed cadence and after a material policy, payer, system, staffing, or workflow change. Compare the current process with its documented design, sample the evidence it produces, and record exceptions separately from completed routine work. A control that exists only in a policy but leaves no observable evidence cannot be evaluated reliably.
Use findings to change the upstream process, not merely to clear the current queue. Assign one owner, one next action, and one follow-up date. Preserve the definition and baseline used for the review so a later result can be compared without changing the measurement after the fact.
Frequently asked questions
Can a batch close with rejected claims?
Yes if rejections are completely identified and transferred to an owned exception workflow under the documented closure rule.
Should charge totals match accepted totals?
Not necessarily when claims are rejected or split; document which populations each total covers and reconcile the differences.
Operational terms
Authoritative sources
- Medicare Claims Processing Manual (opens in a new tab)
Centers for Medicare & Medicaid Services
- Medicare Billing: CMS-1500 and 837P (opens in a new tab)
Centers for Medicare & Medicaid Services