Cloudbyz CTFM handles site payments in two ways. Payments for completed visits and procedures are generated automatically from study data, so sites don't need to invoice for them. Costs the site incurs on the sponsor's behalf, such as travel or local tests, arrive on a site invoice, which Cloudbyz CTFM checks line by line against the contracted budget, limits per unit and payee rules, routing only exceptions to a person before payment.
Site payments often run on terms of up to 90 days from receipt of a correct invoice (Applied Clinical Trials), so one wrong line can hold up a whole payment. Payment records also need a full audit trail, and in the US, payments to physicians and teaching hospitals are reportable under Open Payments.
|
Route |
What it covers |
How it is triggered |
|---|---|---|
|
Visit-based payments |
Per-visit and per-procedure fees, milestone fees |
Completed visits and milestones in CTMS and EDC |
|
Site invoices |
Pass-through and non-procedure costs, such as travel, stipends, local labs, imaging |
Site submits an invoice |
Built-in dashboards show invoices and payments at every level, from payee and site through to invoiced, approved and paid status, for one study or across the portfolio, together with accruals and outstanding amounts.
The same process works for an emerging biotech with a handful of sites and for large pharma or global multinationals with hundreds of sites, many payees and several currencies, because rules are set per site and agreement rather than handled by hand. Cloudbyz CTFM is built natively on Salesforce, on the same platform as Cloudbyz CTMS and EDC. How invoice routes, approvals and limits are set up depends on configuration.
The Cloudbyz team can walk through a site invoice from submission to payment. Book a demo or visit cloudbyz.com.