Skip to main content

Clinical Trial Site Payment Reconciliation: Common Questions

5 min read

How does clinical trial site payment reconciliation work? It compares the clinical trial agreement, approved budget, completed milestones, invoices, pass-through costs, amendments, and payment records to confirm that the right amount reached the right site at the right time. The review also explains every unresolved difference.

Invoice review checks whether an invoice meets submission and approval requirements. Payment processing sends funds. Reconciliation connects both activities to the governing contract and supporting evidence, then records the outcome.

FAQ: clinical trial site payment reconciliation​

What is clinical trial site payment reconciliation?​

Clinical trial site payment reconciliation is a traceable comparison of expected site payments with operational evidence and actual disbursements. The governing budget version comes first. Without it, a variance could be a genuine error, a valid timing difference, or a contract interpretation issue.

Discrepancies often appear when visit completion, enrollment, screen failures, holdbacks, tax treatment, currency conversion, or amendments sit in different systems. A site might complete a visit milestone under an amended budget, while the payment file still uses the previous rate. The reviewer should identify the amendment, confirm the visit date, calculate the difference, assign an owner, and document the adjustment.

Worked example: A site completes a visit after a per-visit rate changes. The payment file still applies the old rate. Finance verifies the effective date in the amendment, checks milestone evidence, and records a retroactive adjustment rather than treating the variance as an unexplained overpayment.

Which records should be compared during reconciliation?​

The clinical trial payment reconciliation process normally compares records that show what was agreed, what happened, what was approved, and what was paid. The exact set depends on the protocol, country, contract, and company procedure.

  • Clinical trial agreement, payment schedule, approved budget, and amendment history.
  • Visit, enrollment, screen-failure, milestone, and closeout data.
  • Site invoices, approved expenses, pass-through documentation, credit notes, and tax records.
  • Payment ledger, payment batch, remittance advice, holds, and returned-payment records.

Keep each approved budget version. Overwriting an earlier version removes the evidence needed to explain why a rate changed. Separate per-patient payments from startup fees, screen-failure payments, pass-through expenses, closeout fees, and retainage.

Worked example: A reviewer traces one visit line from completed milestone evidence to the approved rate, invoice number, payment batch, and remittance record. If the invoice number, site ID, study ID, and amount match, the reviewer can document the payment as reconciled.

Site IDMilestoneApproved amountPaid amountVarianceReason codeOwnerStatus
Site-001Visit completedPer approved budgetPayment batch amountApproved minus paidTiming, data, or disputeNamed reviewerOpen or resolved

A basic calculation is outstanding amount = approved amount − paid amount. Define separately how the organization treats credits, holds, taxes, and currency conversion.

How often should clinical trial site payments be reconciled?​

Reconcile before releasing a payment batch, after a material contract amendment, at study closeout, and whenever a dispute or unexplained balance appears. This risk-based cadence is operational guidance, not a universal regulatory schedule; sponsor and CRO procedures control the final frequency.

Waiting until closeout makes records harder to trace. Staff change, systems get replaced, and budget versions become less familiar. Each review should retain the site, study, country, budget version, milestone, approved amount, paid amount, outstanding amount, discrepancy reason, owner, and resolution status.

Worked example: A payment-cycle review finds the same approved invoice twice in the ledger. The reviewer matches invoice number, site, study, and amount, marks one entry as a duplicate, obtains the required approval, and records the correction before the next payment run.

What causes payment discrepancies at clinical trial sites?​

Clinical trial payment discrepancies usually come from mismatched data, contract changes, approval gaps, or payment timing. Common causes include:

  • Duplicate invoices or incorrect patient and visit counts.
  • Missing milestone data or outdated budget rates.
  • Unapproved expenses, incomplete pass-through evidence, or tax differences.
  • Currency conversion differences, payment holds, and system cutoff dates.

Classify each variance before correcting it. A data error needs a source-record correction. A timing difference needs a documented explanation and follow-up date. A contract dispute needs review by the responsible finance, clinical, legal, or site contact under the applicable procedure.

Worked example: The ledger shows an unpaid pass-through expense. Finance checks the invoice and finds that approval evidence is missing. The amount remains on hold with a reason code and owner; it isn’t recorded as a rejected invoice or a missed payment.

How should teams resolve and document reconciliation differences?​

Resolve differences in a fixed sequence so the final record explains why the amount changed.

  1. Identify the variance and preserve the original value.
  2. Verify the governing contract and budget version.
  3. Compare milestone, invoice, approval, and payment records.
  4. Confirm disputed facts with the responsible site or clinical contact.
  5. Approve the correction under sponsor, CRO, institutional, tax, and records policies.
  6. Record the final disposition and payment action.

The clinical trial payment audit trail should retain the original value, corrected value, reason code, supporting document, reviewer, approval, date, and resulting payment action. Keep disputed amounts separate from confirmed corrections, and document escalation when the parties interpret the contract differently.

Worked example: An amendment changes a per-visit rate and applies to eligible visits already completed. The reviewer links the retroactive adjustment to the amendment, lists affected visits, records the original and corrected amounts, and obtains approval before issuing the adjustment.

Can software support clinical trial site payment reconciliation?​

Clinical trial payment reconciliation software can match records, flag duplicate or missing entries, route exceptions, preserve review history, and show the status of each site. Automation works best around repeatable checks. A qualified reviewer still decides whether a disputed expense, contract interpretation, or protocol-specific exception is valid.

When assessing a tool, check for source-system connections, budget-version control, configurable matching rules, exception queues, role-based approvals, exportable audit history, and support for the currencies or payment structures used in the study. Confirm each capability in current product documentation rather than assuming that a general clinical operations platform handles payments.

Worked example: A system flags two entries with the same site, study, invoice number, and amount. The finance reviewer checks the source documents, assigns a duplicate-invoice reason code, approves the correction, and keeps the match history with the ledger record.

For research sites, the finance desk in Rightview's Navigator builds billing rules from the site's budget and clinical trial agreement, reconciles source activity against the invoiceable items in the site's CTMS, and finds billable work the site has not invoiced yet. Staff approve or dismiss each item.

For a longer walkthrough, see A Practical Guide to Site Budgets and Trial Finance Reconciliation.