Research billing is one of the more reliable sources of compliance exposure in an academic medical centre or a health system with an active trials program. The error patterns are well known: billing a payer for an item the sponsor already funded, billing for a service that was not covered because the device or drug was investigational, or billing routine care as research and losing legitimate reimbursement.
The instinct is to treat this as a claims problem, and there is real work to do in the revenue cycle. But the determination of what may be billed to whom is made long before any claim is generated. It is made in the coverage analysis, encoded in the study budget, and committed to contractually in the clinical trial agreement. If those three documents disagree, no amount of downstream diligence produces a defensible claim.
This guide covers how the three documents relate, the points at which they drift apart, and the contract-side controls that keep them aligned across the life of a study, including the amendments that are the most common cause of divergence. The error rate is not a reflection of carelessness; it is what happens when four documents prepared by four teams have to agree line by line.
The three documents and what each fixes
Each document performs a distinct function, and confusion about which one governs a given question is itself a source of error.
- The protocol, defines what will be done to participants and at what visits, and is the source from which everything else is derived.
- The coverage analysis, classifies each protocol-required item and service as billable to a payer, funded by the sponsor, or not billable at all, with documented rationale.
- The study budget, prices the sponsor-funded items and sets the per-participant and milestone amounts the sponsor will pay.
- The clinical trial agreement, makes the budget contractually binding, sets invoicing and payment terms, and governs what happens when the protocol changes.
- The billing grid or calendar, operationalizes the classification in the clinical and billing systems so that charges route correctly at the point of service.
The chain only works if each link reflects the one above it. In practice the coverage analysis and the budget are often prepared in parallel by different teams under schedule pressure, the agreement is negotiated by a third, and the billing grid is built from whichever document the coordinator had to hand. By the time a claim is generated, the classification has been inherited three times and nobody remembers which document it came from.
A protocol amendment adding a visit, changing an assessment or extending follow-up changes what is protocol-required, which changes the coverage analysis, which changes the budget, which requires a contract amendment. Studies commonly execute the protocol amendment and defer the budget and contract work. Every participant seen in the interval is billed against a classification that no longer matches the protocol.
Where the control fails
These patterns appear in internal audits with enough regularity that they are worth checking specifically rather than waiting to find them.
- Coverage analysis is done once, at startup. Without a trigger to revisit it, the analysis ages against an amended protocol and nobody notices until a claim is questioned.
- Budget and coverage analysis are not reconciled. An item classified as sponsor-funded in the analysis but omitted from the budget will be performed, unfunded, and often billed to a payer by default.
- Contract amendment lags protocol amendment. The clinical work proceeds on the amended protocol while the financial and contractual documents describe the old one.
- Invoicing milestones are not tracked. Sponsor payments tied to enrolment, monitoring visits or database lock go uninvoiced, which is a revenue loss rather than a compliance problem but stems from the same gap.
- Reconciliation is never performed. Nobody compares procedures performed against sponsor invoices against payer claims, so offsetting errors persist indefinitely.
Five steps to keep billing defensible
Step 1, Make the coverage analysis a versioned artifact
Treat it as a controlled document with a version, an effective date and a link to the protocol version it analyses. An undated coverage analysis cannot answer the question that matters during an audit, which is what the classification was on the date of service rather than what it is now.
Step 2, Reconcile the budget against the analysis before execution
Run an item-by-item comparison before the agreement is signed. Every item the analysis classifies as sponsor-funded should appear in the budget, and every budgeted item should have a classification. Discrepancies found here cost nothing; discrepancies found later cost a refund and an investigation.
Step 3, Tie contract amendment to protocol amendment
Build an obligation that fires whenever a protocol amendment is executed, requiring a coverage analysis review and, where the classification changes, a budget and contract amendment within a defined period. Track it as a dated commitment with an owner rather than as a step in a workflow document.
Step 4, Track sponsor invoicing milestones
Extract payment triggers, enrolment milestones, invoicing deadlines and holdback release conditions from the agreement into dated obligations. Unbilled sponsor revenue is common and it is entirely a tracking failure rather than a negotiation one.
Step 5, Reconcile performed, invoiced and billed
Establish a periodic reconciliation comparing procedures documented in the research record, amounts invoiced to the sponsor and claims submitted to payers. This is the control that finds double billing and missed sponsor revenue, and it is the evidence an auditor will ask to see.
See study obligations tracked across the portfolio
Watch how invoicing milestones, amendment duties and reporting obligations become monitored records.
Why the contract record is the right home
Study agreements generate a stream of dated commitments on both sides: invoicing milestones, reporting deadlines, amendment obligations, record retention and audit cooperation. Holding them in study binders and spreadsheets is why they are missed. Treating them as obligations on the contract record with owners and evidence is the same pattern applied to provider agreements generally, described in Provider contract management for health systems. Consolidating clinical, payer and vendor commitments into one view is the approach set out in Obligation Management for Healthcare. It also gives research finance a view of unbilled sponsor revenue, which is usually the finding that funds the rest of the work.
Document, what it governs and its refresh trigger
Each artifact has a different owner and a different trigger for revision, which is precisely why they drift.
| Artifact | Governs | Typical owner | Refresh trigger |
|---|---|---|---|
| Protocol | What is performed | Sponsor and investigator | Amendment |
| Coverage analysis | Who may be billed | Research compliance | Protocol amendment |
| Study budget | What the sponsor pays | Research finance | Coverage analysis change |
| Clinical trial agreement | Binding terms and invoicing | Contracting office | Budget change |
| Billing grid | Charge routing at service | Research operations | Any of the above |
Research billing compliance is often described as a revenue cycle discipline, and the corrective action after a finding usually lands there. The more durable fix is upstream. If the coverage analysis is versioned, the budget reconciles to it, the contract follows the protocol amendment on a tracked deadline, and someone reconciles what was performed against what was invoiced and billed, most of the error patterns simply stop occurring. None of that requires new systems so much as treating the study agreement as a live set of obligations rather than a document filed at startup. Organizations that make this shift generally find the compliance improvement arrives alongside a measurable recovery of sponsor revenue they were entitled to.
For related guidance, see Value-based care contract administration, simplified, The compliance guide to BAA tracking across vendors and Staffing agency contract control for health systems.
