Site Operations
Your clinical trial management system (CTMS) tracks invoices, not follow-ups: a site accounts receivable routine that actually collects
The gap: invoices recorded, follow-up not owned
The failure rarely starts as carelessness. A coordinator raises the invoice in the CTMS, the system records it, and the site assumes the payment cycle is now somebody's job. But the CTMS was built to manage trial operations — visits, enrollment, monitoring — not to chase money. It will tell you an invoice exists. It will not tell you that nobody has followed up on it in six weeks, that the sponsor asked for a corrected document and nobody sent it, or that the same invoice has been sitting past due while a newer invoice for the same study was issued on top of it.
Meanwhile, new visits are performed, new invoices are raised, and the unpaid pile grows quietly behind the active work. By the time someone looks, the oldest lines are months past due and hard to reconstruct. The money was earned correctly. The follow-up was never assigned. Collection needs its own tool and its own owner, and the tool should be deliberately simple.
One aging tracker outside the CTMS
Build one aging tracker outside the CTMS — a single list, in a format the owner can read in minutes, that pulls the same invoice data the CTMS holds and adds the fields the CTMS does not manage: date issued, due date, amount, study, sponsor, days outstanding, owner, last action taken, date of that action, and next action due.
One tracker, not one per study. A single list is the only way the owner can see the whole balance and spot patterns a study-by-study view hides: one sponsor repeatedly late, one study generating queries on every invoice.
The weekly routine: pull, flag, review at 30, 60, and 90 days
The routine runs once a week, on the same day, and takes the same shape every time.
First, pull the list. Refresh the aging tracker from the CTMS invoice records so it reflects every invoice issued, including any raised late or corrected since the last pull. Do not let the tracker become a separate truth that drifts from the CTMS — it is a working view of the same data, with follow-up fields added.
Second, auto-flag anything past 30 days. The flag is automatic and needs no judgment: every line past 30 days outstanding is flagged for review. The threshold is a working rule the site sets for itself, not a claim about payment terms or industry practice — it exists so that nothing slips from current to overdue without anyone noticing.
Third, review at 30, 60, and 90 days. Each band has a different question. At 30 days, the question is whether the invoice reached the right person in the right form: was it received, does it match the budget line, is any supporting document missing? At 60 days, the question is what is blocking payment and who owns removing the block: a query, a correction, a missing signature, a sponsor-side process step. At 90 days, the question is escalation: who at the sponsor needs to hear about it, and what does the site need to send to make payment possible? A line that sits in the same band for two reviews without a new action is a line the routine has failed, and the review should say so plainly.
One owner, one next action per line
A routine fails without a named owner. The owner is one person — not a department, not a shared inbox — who is accountable for the tracker being current and for every overdue line having a next action. Other people perform the actions; the owner makes sure the actions exist, are dated, and happen.
For each overdue line, the tracker records exactly one named next action: who will do what, by when. Not "follow up," which is an intention, but "send the corrected invoice with the signed visit log to the sponsor's accounts contact by Thursday." If the action cannot be written that precisely, the owner does not yet know what is blocking payment, and the next action is to find out. The history belongs in the record; the next action is what moves the line.
Standard follow-up by aging band, exceptions by hand
Most overdue invoices need the same short message, written once and reused. A 30-day follow-up confirms receipt and asks whether anything is needed. A 60-day follow-up names the blocker and the document being sent to clear it. A 90-day follow-up escalates, names the amount and the aging, and asks for a payment date. Each message is short, factual, and professional, and each one is sent with the evidence attached — the invoice, the supporting document, the budget reference — so the recipient does not have to ask for it.
Standard wording is what makes the routine sustainable. The owner only writes exceptions: the invoice with a genuine dispute, the sponsor with a process the site has to work around, the line where the amount itself is contested. Everything routine goes out in the standard form, on the standard day. A routine that requires fresh writing for every line will not survive a busy week, and a busy week is exactly when the oldest lines get forgotten.
Keep messages in writing. A call can move a blocked payment, but it should be followed by a short written note recording what was agreed, so the next review does not start from memory.
Automate the list, not the chase
Automation belongs in the pull, the flag, and the reminder. The weekly pull should be as close to automatic as the site's systems allow. The 30-day flag should fire without anyone deciding it should. The reminder that a next action is due should arrive before the date passes, not after.
Automation does not belong in the chase. A reminder that fires into a shared inbox and is read by nobody is worse than no reminder, because it creates the impression that follow-up happened. Escalation stays with the site: a named person deciding that this invoice, at this age, with this blocker, goes to this sponsor contact with this message. The judgment is the work; the list only makes it visible and repeatable.
How this works in practice
At Amavita Research, our Miami cardiovascular trial site, we care for more than 18,000 active cardiology patients, and our record includes zero United States Food and Drug Administration (FDA) Form 483 findings. A site with a population like ours generates invoices constantly, across many studies and sponsors, and the only way that volume stays collectible is a routine that does not depend on anyone remembering. One tracker outside the CTMS. One weekly pull. Flags past 30 days. Review at 30, 60, and 90. One owner, one named next action per overdue line, standard words for the routine cases, and a person — not a system — doing the chasing. That is how a site stops discovering unpaid invoices months late, and starts collecting the money its work already earned.
Julio G. Martinez-Clark is chief executive officer of Amavita Research Services, a Miami cardiovascular trial site, and chief executive officer of bioaccess, a first-in-human contract research organization.
Next step
Sponsors: see what Amavita Research can run
Amavita Research is a Miami cardiovascular trial site with 18,000+ active cardiology patients and zero United States Food and Drug Administration (FDA) Form 483 findings. See our site capabilities or talk with our sponsor team.