After a protocol amendment, each site moves to a new budget on its own effective date, and visits completed around that date may need to be paid at the old or new rate. Without version history, teams can't tell which rate applied to which visit. Cloudbyz CTFM keeps every budget version with its effective date and links it to the agreement amendment, so payments, adjustments and accruals use the version in force for each visit. It is used by large pharma, global multinationals, biotechs, CROs and device companies.
Why version history matters
- Amendments take effect on approval. In the US, protocol changes generally need IRB approval before they are implemented (21 CFR 312.30), and in the EU substantial modifications must be authorised first. Each site's new budget should apply from its own effective date.
- Accruals must be right. Under US GAAP, clinical trial costs are expensed as incurred (ASC 730), so accruals need the rate that actually applied to each visit (G-Squared CFO).
- Payments must match signed terms. ICH E6(R3) expects financial terms to be documented in agreements (ICH E6(R3), EMA Step 5).
Situations that need adjustment
|
Situation
|
What happens without version history
|
With versions and effective dates
|
|
New procedure added mid-study
|
Missed on visits before the budget was updated
|
Paid from the effective date
|
|
Fee increased by amendment
|
Visits paid at old rate, site disputes
|
Difference identified and adjusted
|
|
Agreement signed after effective date
|
Unclear which rate applies
|
Rate follows the agreed effective date
|
|
Fee reduced or removed
|
Overpayment found at close-out
|
Visible before payment
|
|
Audit question on a past payment
|
Reconstructed from files
|
Version in force shown on the record
|
For large pharma and global multinationals
One amendment can mean hundreds of sites moving to new budgets on different dates across countries. What matters is seeing, at any time, which version each site is on, which sites are still waiting for an agreement amendment, and the total adjustment due across the portfolio, before accruals are booked.
For biotechs and emerging sponsors
Early protocols often change several times. For a small team, keeping each budget version and its effective date in the system avoids rebuilding payment history by hand, and gives auditors and CROs a clear answer about what was paid and why.
How Cloudbyz CTFM does it
Cloudbyz CTFM, built natively on Salesforce with Cloudbyz CTMS and EDC, builds budgets against the study visit plan and applies amendments to the affected visits and procedures as new versions. Agreement amendments are tracked and attached, the Financial Navigator can compare budget versions, and the forecasting module shows the cost of the change by region and site. Book a demo or visit cloudbyz.com.