Specimen Collection and Accession Reconciliation: Connecting Laboratory Work to Claims

The direct answer: reconcile events, not just totals

Laboratory reconciliation should connect the clinical order, specimen event, accession, finalized result, charge, and claim. Comparing only total specimens with total billed tests will miss important differences because one specimen can support multiple tests, an accession can contain canceled work, and a charge can be duplicated. Build an event-level crosswalk that explains what happened to each ordered service. CMS laboratory documentation guidance requires support for ordered services and accurate order processing and claim submission. Reconciliation turns that requirement into an operational control, but it does not mean every collected specimen or completed administrative task is separately billable.

Preserve identifiers and meaningful status changes

Use stable links among the ordering-system identifier, collection record, accession number, reference accession when applicable, and billing transaction. Retain collection, receipt, cancellation, recollection, and result-finalization events with their actual meanings. Avoid overwriting a canceled accession so completely that the history disappears. Document how merged patient records and corrected demographics propagate through the systems. When a test is added or removed, preserve the authorized change and its relationship to the original order. Clear identifiers let staff distinguish a legitimate additional service from an interface resend, while meaningful statuses explain why an ordered test did not become a completed reportable service.

Treat collection and testing as separate billing questions

The existence of a collection event does not establish separate payment for collection, handling, transport, or travel. Chapter 16 addresses specimen collection and related payment circumstances, and the applicable setting and payer rules matter. Review the actual service, eligible entity, claim instructions, and any restrictions before generating a charge. Do not infer a payable collection service from the presence of a phlebotomy note alone. Conversely, do not allow legitimate collection documentation to disappear simply because testing occurs elsewhere. Maintain the evidence needed to evaluate each potential service independently, while avoiding duplicate charges between the collection organization and the performing laboratory.

Hypothetical scenario: a recollection creates two charge records

A hypothetical laboratory receives an unsuitable specimen and creates a replacement accession after recollection. The first accession remains canceled, but both order messages generate charges in the billing interface. A daily reconciliation report identifies two proposed test charges linked to one completed result. The analyst reviews the order history, specimen rejection, and replacement accession before releasing any claim. The canceled testing charge is removed through the documented correction process. Any collection-related billing question receives its own payer-specific review rather than being assumed payable because a second draw occurred. The team then adjusts interface logic so canceled work no longer produces an active testing charge.

Use a reconciliation checklist with accountable owners

Assign exceptions according to the missing event. Laboratory operations should resolve specimen and result-status questions; ordering teams should address unclear authorized changes; interface staff should investigate missing or repeated messages; billing should reconcile claim creation and submission. Avoid a single unresolved bucket that hides the source of the problem. Record the accession, exception type, responsible owner, next action, and resolution evidence. Review unbilled completed services alongside billed canceled services, because both signal broken handoffs. A claim should not be created merely to make totals balance, and a charge should not be deleted without preserving why it was unsupported or duplicated.

• Match orders with collected and received specimens.
• Compare finalized results with active charge records.
• Investigate cancellations, recollections, and added tests.
• Reconcile reference laboratory and local accessions.
• Confirm each released claim reflects supported services.

Check dates and payer-specific collection requirements

Specimen collection date, receipt date, performance date, and result date are not interchangeable. Apply the relevant laboratory date-of-service instructions, including any applicable exceptions, instead of automatically selecting the date most convenient for billing. Payers may differ in their collection, transport, network, and claim requirements. Verify those rules for the actual product and setting, and retain the policy version used for disputed cases. Do not create a universal rule that every recollection is payable or that every courier event supports a separate charge. Reconciliation establishes the facts; coverage and coding review determine how those facts should be reported.

Turn reconciliation findings into system improvements

Use exception patterns to identify failed interfaces, confusing status definitions, and charge rules triggered too early in the laboratory process. Test configuration changes against completed, canceled, referred, and recollected cases before relying on them. Keep an audit trail connecting the original transaction with any correction. Cyber Sense can help assess the revenue cycle side of specimen-to-claim reconciliation and establish clear follow-up queues. Request a consultation to review where accession events stop matching billing records. Laboratory personnel should retain authority over specimen acceptability and clinical testing decisions, while the billing workflow accurately reflects those decisions and the payer requirements that apply.

Frequently asked questions

Related articles

• CLIA Number and Test Complexity: Laboratory Claim Checks Before Submission
• Laboratory Orders, Diagnosis, and Medical Necessity: Building a Supported Claim
• Laboratory ABN Workflow: Addressing Expected Medicare Noncoverage Before Testing