Clinical Trial Charge Capture & Reconciliation

A finished Medicare Coverage Analysis (MCA) and a fully populated S/R/Q billing grid inside a CTMS tell a research billing office how a protocol item should be billed. They do not, by themselves, guarantee that the actual claim leaving the institution matches that determination. Between a coverage-analysis decision and a paid claim sits a separate operational chain — charge capture, charge routing into the electronic health record (EHR), claims editing, and reconciliation against the billing grid — and it is in that downstream chain, not in coverage analysis itself, that most real-world research billing errors and double-billing exposure actually originate.

This guide covers that downstream layer specifically. For how a billing designation gets assigned in the first place, see Medicare Coverage Analysis for Clinical Trials and OnCore CTMS Coverage Analysis: How S/R/Q Billing Designations Actually Get Set. This page picks up where those leave off: once S, R, and Q are set in the CTMS, how do those designations actually reach a claim correctly, and how does a billing office confirm they did?

Two different compliance problems, not one

Research billing compliance programs tend to treat coverage analysis and charge reconciliation as a single topic, but they are two structurally different problems with different failure modes:

Coverage analysis (upfront): a classification problem — deciding, for each protocol item, whether it is routine care, a research cost, or patient responsibility, under CMS National Coverage Determination (NCD) 310.1 or the applicable payer’s rules. This happens once per protocol (and again at each amendment).
Charge capture and reconciliation (downstream): an execution problem — making sure that every single visit, every single time it occurs, the charge that actually gets generated in the EHR, coded, edited, and submitted on a claim matches the classification the coverage analysis already assigned. This happens continuously, for every subject, at every visit, for the life of the study.

An institution can have an excellent coverage analysis and billing grid and still have significant billing exposure if the downstream execution layer does not reliably enforce it. That gap — between a correct determination on paper and a correct claim in practice — is what charge-capture and reconciliation controls exist to close.

Where the gap opens up: grid to claim

A typical path from a finished billing grid to a submitted claim runs through several handoffs, and each one is a place where the coverage-analysis determination can fail to carry through correctly:

Billing grid finalized in the CTMS — S/R/Q (or equivalent) designations are set per procedure, tied to the protocol’s schedule of events.
Visit occurs and is documented — a coordinator or clinician records the encounter, ideally against a study-specific visit template that carries the billing designation forward automatically.
Charge capture in the EHR — orders and documented services generate charges. Some EHRs (Epic’s research-billing tools are a widely deployed example at academic medical centers) route charges tied to a study record into a dedicated research charge-review queue rather than letting them flow straight to claims; other institutions rely on manual research-billing-office review of research-flagged encounters instead.
Coding and claims editing — charges are coded, and for a qualifying clinical trial, claim-level and line-level markers specific to research billing are added before the claim scrubber releases the claim.
Reconciliation — the billing office (or a delegated research-billing-compliance function) periodically checks what was actually billed against what the billing grid says should have been billed, for the same visit.

A break at any step — a coordinator using the wrong visit template, a charge that bypasses the research-review queue, a coder removing a research-specific modifier, a reconciliation step that never happens — can produce either of the two outcomes institutions are trying to avoid: a research-only item billed to Medicare or another insurer (double billing / overpayment risk), or a routine-care item left unbilled and absorbed as an unnecessary research-account cost (lost or misallocated revenue).

Getting research designations into the actual charge stream

Two mechanisms do most of the work of making sure a visit’s charges reflect its billing grid designation before a human ever reviews them:

Study-specific visit templates. Rather than relying on a coordinator to remember which items on a given visit are billable to insurance versus the study budget, many institutions build the billing designation directly into the order set or visit template tied to that protocol’s calendar in the CTMS/EHR integration, so the correct routing is the default rather than something applied after the fact.
Research charge-review queues. Charges generated against an encounter flagged as research-related are routed to a dedicated review step — staffed by the research billing office, patient financial services, or a hybrid compliance function — before they are released to a payer. This is the point where a charge that does not match the expected billing grid designation for that visit gets caught and corrected, rather than reaching a claim.

Neither mechanism is a substitute for the other. A well-built visit template reduces how often a charge shows up wrong in the first place; the review queue is the backstop that catches what still gets through wrong — protocol amendments not yet reflected in the template, an add-on order placed outside the standard visit, a coordinator overriding a default.

What a clean qualifying-trial claim actually carries

Even after a charge is correctly routed, submitting it on an institutional claim (UB-04/CMS-1450, or the 837I electronic equivalent) for a Medicare qualifying clinical trial under NCD 310.1 requires claim-level and line-level markers that are specific to research billing and easy for a general claims-editing rule set to miss if it was not built with research billing in mind:

Condition Code 30 (“Qualifying Clinical Trial”) — entered at the claim level on institutional claims for a qualifying trial, regardless of whether every line item on that particular claim is trial-related. See CASRAI’s Condition Code 30 entry for the full field-level detail.
ICD-10 diagnosis code Z00.6 — reported alongside Condition Code 30 to identify the encounter as trial-related.
The trial’s 8-digit NCT number — reported in the designated claim field (UB-04 value code D4, or 837I loop 2300) so the payer can tie the claim back to a specific registered trial.
HCPCS modifiers Q0 and Q1 — applied at the line-item level on outpatient/professional claims: Q0 flags the investigational item or service itself, Q1 flags a routine service furnished in the course of an approved research study. These operate below Condition Code 30, which applies at the claim level, and neither marker substitutes for the other.

A claims-editing rule set that is not configured to expect these markers on research encounters can do real damage in either direction: it can reject a correctly coded research claim for looking incomplete, or — more consequentially — it can silently strip or fail to require a marker, releasing a claim that does not actually reflect the trial context the coverage analysis established. Confirming these fields are configured correctly in the claims-editing/scrubber layer, not just documented in the billing grid, is itself a reconciliation task.

Reconciliation: matching what was billed to what the grid says should have been billed

Reconciliation is the control that closes the loop: for a sample of visits (or, in a smaller study, every visit), someone compares the actual charges and claim markers generated against what the billing grid specifies for that visit, and resolves any mismatch before it compounds across the life of the study. In practice this usually means:

Pulling a charge/claim report for the study, by visit, by billing designation.
Comparing it against the billing grid’s expected designation for each procedure at that visit.
Flagging mismatches — a research-only item that generated a patient/insurance charge, a routine-care item that was absorbed by the study account instead of billed, a missing Condition Code 30/Z00.6/NCT-number/Q0/Q1 marker on a claim that should carry one.
Correcting the charge or claim before or shortly after submission where possible, and, where a claim has already been paid incorrectly, routing the finding into the institution’s standard billing-correction or credit-balance process.

Reconciliation cadence varies by institution and study risk profile — some run it visit-by-visit in near-real-time through the charge-review queue described above, others run a periodic (monthly or quarterly) retrospective audit across all active trials. What matters less than the specific cadence is that reconciliation is a defined, documented, recurring process with an owner — not an occasional spot-check — because the same charge-routing error, if the underlying visit template or order set is wrong, will otherwise repeat at every subsequent visit and every subsequent subject on that protocol.

Where double billing and missed revenue actually happen

In practice, the same handful of failure points recur across institutions:

Protocol amendments not propagated downstream. The billing grid gets updated after an amendment, but the CTMS visit template, the EHR order set, or the claims-editing configuration does not get updated to match — so charges keep generating against the pre-amendment designation.
Add-on or unscheduled orders. An order placed outside the standard visit template (an extra scan, an unscheduled lab) bypasses the automated routing entirely and depends on someone recognizing it as study-related at the point of charge review.
Coordinator or clinician override. A default billing designation gets manually changed at the point of care without going back to the billing grid to confirm the override is correct.
Coding-layer drift. A coder unfamiliar with research billing removes a Q0/Q1 modifier or Condition Code 30 as part of routine claim cleanup, not recognizing it as research-specific.
No reconciliation step at all. Some institutions build a strong upfront coverage analysis and CTMS billing grid but never close the loop with a recurring downstream reconciliation process, so errors in charge routing or claims editing are never caught unless an external audit or payer inquiry surfaces them.

Charging Medicare or another insurer for the same service the sponsor has already paid for under the clinical trial agreement is the fact pattern behind a large share of clinical-research billing enforcement activity; see False Claims Act Liability in Clinical Trial Billing for how that risk is assessed once it happens. The clinical trial agreement itself is typically what defines which party bears which research costs at the budget level — see Clinical Trial Agreement (CTA) — and reconciliation is the operational check that confirms the actual billing followed that allocation.

Where the Advance Beneficiary Notice fits — and where it doesn’t

Reconciliation sometimes surfaces a routine-cost item that is independently at risk of a medical-necessity or frequency denial under ordinary Medicare rules, separate from its trial-related classification. That is what an Advance Beneficiary Notice (ABN) is for — not a tool for resolving a charge-routing error. An ABN cannot lawfully be used to shift a sponsor-owed research cost onto the patient; doing so does not avoid double-billing exposure, it compounds it. See Advance Beneficiary Notice (ABN) in Clinical Trial Billing for the full mechanics, including the GA/GZ/GX/GY modifier set.

Who owns this in practice

Charge capture and reconciliation is rarely one person’s job. It typically spans:

The research billing office or research billing compliance function — owns the reconciliation process itself and is usually the point of escalation for a confirmed discrepancy.
Clinical research coordinators — execute the visit against the correct template and are often the first line of defense for catching an add-on order that needs manual routing.
Health information management (HIM) / coding staff — apply and preserve the research-specific claim markers (Condition Code 30, Z00.6, NCT number, Q0/Q1) rather than treating them as errors to clean up.
Patient financial services / the claims-editing (scrubber) team — configure and maintain the claims-editing rules so research markers are recognized rather than rejected or stripped.
Sponsor invoicing / clinical trial finance — bills the sponsor for the research-cost side of the same visit, and is a useful cross-check: a visit billed to the sponsor and to Medicare for the same item is the double-billing pattern reconciliation exists to prevent.

When reconciliation finds a problem

Not every discrepancy reconciliation turns up is the same severity. A charge caught and corrected before submission is a routine control working as intended. A claim that already went out, and especially one that was already paid, on an incorrectly billed item is a different situation: it typically needs to be routed through the institution’s standard claim-correction or refund process, and if it reflects a pattern rather than an isolated error, may warrant evaluation for the HHS-OIG Self-Disclosure Protocol. See OIG Self-Disclosure Protocol for Clinical Research Billing Overpayments for when and how that applies. A documented, working reconciliation process is itself evidence of a functioning compliance program if an error is ever found and needs to be explained to an auditor or the government.

For the broader orientation to clinical trial billing compliance — including the upstream steps this guide assumes are already in place — see the Clinical Trial Billing Compliance checklist.

Frequently asked questions

Is charge-capture reconciliation the same thing as coverage analysis?

No. Coverage analysis (MCA) is the upfront classification of each protocol item as routine care, research cost, or patient responsibility. Charge-capture reconciliation is the recurring, downstream check that confirms the actual charges and claims generated for real visits matched that classification. A study can have a correct coverage analysis and still have reconciliation failures if the downstream systems and processes don’t reliably carry that classification through to the claim.

How often should charge reconciliation happen?

Practice varies by institution and study risk. Some run reconciliation continuously through a research charge-review queue that checks every research-flagged encounter before the claim goes out; others run a periodic retrospective audit, commonly monthly or quarterly, across active trials. The important structural feature is that it is a defined, recurring process with a named owner, not an occasional or informal check.

What’s the difference between Condition Code 30 and the Q0/Q1 modifiers?

Condition Code 30 is a claim-level flag on institutional claims (UB-04/837I) indicating the claim relates to a Medicare qualifying clinical trial under NCD 310.1. Q0 and Q1 are HCPCS modifiers applied at the line-item level on outpatient/professional claims — Q0 flags the investigational item/service itself, Q1 flags a routine item/service furnished in the course of the study. They operate at different levels of the claim and neither replaces the other.

Can an unbilled routine-care item just be absorbed by the study budget instead of fixed?

No — that is itself a compliance and financial-management problem, not a safe default. Billing a routine-care item to the study budget instead of the correct payer misstates both the study’s cost basis and, depending on the funding source, can raise its own compliance questions; it should be corrected through the same reconciliation process as an overbilled item, not treated as the conservative choice.

Does an EHR automatically prevent double billing on a clinical trial?

Not by itself. An EHR’s research charge-review functionality (where available) reduces the risk by routing research-flagged charges to review before claims submission, but it depends on the encounter being correctly flagged as research-related in the first place, and on the visit template or order set reflecting the current billing grid. It is a control that supports reconciliation, not a replacement for it.