CRO invoice management for biotech

A €70,000 invoice arrives from your CRO. The arithmetic is correct, the study team confirms the work is under way, and the amount is not obviously wrong. None of that tells you whether you should pay it.

The difficulty is not that CRO invoices are inaccurate. The difficulty is that the agreement an invoice should be checked against is rarely one document. It is a statement of work, plus whatever change orders have been approved since, plus a purchase order that may or may not reflect those changes, plus everything already billed against the same scope. Each of those lives somewhere different, and often with a different person.

This guide covers how to match a CRO invoice to what was actually agreed: which document governs, how to check rates and milestones, how to handle pass-through costs, and what to do when the invoice and the contract disagree. It assumes you already have a view of your contract values and commitments. If you do not, start with the companion guide on tracking CRO commitments, change orders and invoices, then come back here.

The five checks

To match a CRO invoice correctly, work through five questions in order. Each one depends on the answer to the one before it.

1. Which document governs? Identify the applicable statement of work and every approved change order that affects the invoiced scope.
2. Are the rates and units right? Compare what is billed against the agreed budget, line by line.
3. Has the billing event occurred? Confirm with the study owner that the milestone was reached or the work was performed.
4. Are the pass-through costs documented? Check third-party costs against receipts and agreed limits, separately from CRO fees.
5. Does it fit what remains? Check cumulative billing against the purchase order and the remaining contract value, not just this invoice in isolation.

The order matters: checking a rate is pointless if you are reading the wrong version of the budget.

1. Find the document that governs

The master agreement sets the commercial frame: payment terms, dispute handling, audit rights, termination. What it rarely tells you is whether a specific invoice is correct. That answer sits in the statement of work for that study, as amended by every change order approved since it was signed.

This is where most matching errors start. Finance checks the invoice against the SOW on file; the study team approved a change order three months ago that revised the monitoring schedule and the budget with it; nobody told finance. The invoice is correct and gets queried anyway, or it is incorrect and gets paid.

Before checking a single number, establish:

• Which SOW the invoice falls under, by study and by protocol version
• Which change orders have been approved, and which are still proposed or under review
• Whether any of those change orders revised the rates, not only the scope
• The currency and whether amounts are stated with or without VAT

A change order that is still under review does not authorise billing. If an invoice includes work covered only by a proposed change order, that is not a payment question yet. It is a scope question for the study owner.

2. Check the rates and the units

Once you know which budget applies, compare the invoice against it line by line. Two things go wrong here, and they look similar on paper.

The rate has moved. A monitoring visit priced at €1,800 in the SOW appears at €2,200. Sometimes there is a good reason: an approved change order revised the rate, or an annual escalation clause was triggered. Sometimes nobody noticed. Keep the agreed budget open beside the invoice and treat any difference as something to be explained, not absorbed.

The unit has changed. This is harder to catch. The rate per visit is unchanged, but visits are now billed per site rather than per subject, or project management has shifted from a fixed monthly fee to a percentage of the study cost. The individual numbers look familiar; the basis underneath them has moved. Check what each line is measured in, not only what it costs.

For time-and-materials work, also check the seniority mix. A budget built on a given split of senior and junior hours can be billed at the same hourly rates and still come in well above plan if the mix shifts.

3. Confirm the billing event actually happened

Finance cannot verify this one alone. Whether a milestone has been reached is a question for the person running the study, and it is a common reason a correct-looking invoice should not be paid.

Milestone contracts. Payment is tied to defined events: first patient in, a percentage of sites activated, database lock. The invoice asserts the event occurred. Someone has to confirm it did. "Database lock" invoiced in the month it was scheduled rather than the month it happened is an ordinary and easily missed error.

Time-and-materials contracts. There is no event, only effort. Here the check is whether the effort is plausible against study activity. A month with no enrolment and no site visits that carries full project management hours is worth a question.

Unit-based lines. Monitoring visits, queries resolved, samples analysed. These should reconcile against an operational record the study team already has. If no such record exists, you have no way to verify the line, and that is worth fixing before the next invoice rather than arguing about this one.

Build the confirmation into the approval route rather than chasing it by email. If the study owner has to be asked each time, the answer will eventually be a reflexive yes.

4. Treat pass-through costs as their own problem

Pass-throughs are third-party costs the CRO incurs on your behalf and bills on to you: investigator grants, central lab work, courier and shipping, imaging, IRB and ethics fees, translations, travel. They are the part of a CRO invoice most likely to produce a surprise, for three reasons.

They are usually estimates, not fixed fees. The pass-through section of a SOW is typically a budget rather than a price. Whether that budget acts as a spending limit depends on the contract: on any cap, prior-approval requirement or change order provision attached to it. Establish which of those applies before anyone treats the total contract value as a ceiling.

They often arrive with a lag. Site invoices reach the CRO months after the work, then reach you a billing cycle later. An invoice in October can carry site costs from June. If you are reconciling period by period, they will never line up.

The documentation standard is weaker. CRO fees are defined by the budget. Pass-throughs are defined by someone else's receipts, which you may or may not receive.

Four things to settle in the contract, not at invoice time:

• What level of backup documentation accompanies pass-through billing, and in what format
• Whether any handling fee or markup applies, and whether it applies to the gross or net amount
• Whether a pass-through budget can be exceeded without a change order, and by how much
• Which costs are pass-throughs at all – some CROs classify items such as translations or courier charges as direct costs

Track pass-throughs separately from CRO service fees in your own records. Combined into one contract total, a service fee overrun and a pass-through overrun look identical, and they call for entirely different conversations.

5. Check it against what remains, not against itself

An invoice can pass every check above and still be wrong, because the question is never whether this invoice is reasonable. It is whether this invoice plus everything already billed fits inside what was agreed.

That means checking two balances, and they are often not the same number.

This is the €70,000 invoice from the opening. It sits inside both balances, so the amount is not what will stop it. That is not the same as saying it should be approved: checks one to four still have to pass, and a quiet invoice is not a verified one.

What should draw attention is that the two remaining figures differ by €85,000. That gap is the July change order, approved against the contract and never reflected in the purchase order.

Nothing goes wrong this month. It goes wrong in four months, when cumulative billing passes €620,000 and legitimate invoices start failing a PO check for a reason nobody can immediately explain. By then the change order is old news and the investigation starts from scratch.

So the fifth check has a second half: when a change order is approved, the purchase order covering that scope is revised at the same time. If your approval route does not connect those two events, it will produce this gap repeatedly.

One caution on the arithmetic. A purchase order raised under an existing contract is not an additional commitment. If both the €705,000 contract and a PO covering the same scope appear in your commitment total, you have counted the same obligation twice. The commitment tracking guide covers how to keep contracts and POs linked rather than added together.

Where three-way matching fits

Three-way matching compares the purchase order, the invoice and a record that the goods or services were received. It is the standard control in accounts payable, and it works well for what it was designed for: catching an invoice for something that was never ordered or never arrived.

For complex CRO engagements it verifies that the purchase order, invoice and recorded delivery are consistent. It does not replace checking the applicable SOW and approved change orders, because the purchase order is a downstream document. If the PO was raised against a superseded version of the budget, a three-way match will confirm the invoice agrees with the wrong number.

The practical consequence for a small biotech: receipt confirmation is the part worth putting in place first. Knowing that a named person confirmed the work was delivered, and having that recorded against the invoice, is the check the numbers cannot do for you. A formal three-way match becomes worthwhile once purchase order volume is high enough that confirming each one by hand stops being realistic.

When the invoice and the contract disagree

Most discrepancies are not disputes. They are missing context, and they resolve in a day once the right person sees them. Treat them that way by default.

Separate the clear part from the disputed part. If €62,000 of a €70,000 invoice matches and €8,000 does not, holding the entire payment is rarely the only option. Where your contract and your own procedures allow it, process the undisputed portion and keep the disputed amount documented and open. Some agreements and some accounts payable systems do not permit a split invoice. If yours does not, the reason for the hold has to be visible somewhere other than inside the blocked invoice.

Record why, not just that. A disputed line needs the reason, the amount, who raised it and what resolves it. Six weeks later, in a credit note or a renegotiation, the reason is the part everyone has forgotten.

Watch for the pattern, not the instance. One retroactive change order is normal. A quarterly rhythm of work performed first and authorised afterwards is a process problem on one side or the other, and it will not be fixed invoice by invoice. Raise it at the governance meeting with the pattern in front of you.

Keep the disputed amount visible, and classify it correctly. A held amount is not automatically an approved commitment. If you are disputing it, the open question is precisely whether you agreed to it. Track it as potential exposure, separate from committed spend. Dropping it from the forecast understates your risk; counting it as agreed overstates your obligation.

The part that is not really about invoices

In a company of fifteen people, invoice matching rarely fails because nobody knows how to do it. It fails because the knowledge needed to do it is split across two people who are not in the same conversation.

The study team approves the change order, because the change is an operational decision about the trial. Finance owns the contract value, the purchase order and the payment. Between the approval and the invoice, the information has to cross from one to the other, and in most small biotechs that crossing is an email that someone remembers to send.

The practical fix is not a policy document. It is deciding three things explicitly:

• Who confirms delivery. One named person per study, not "the team".
• What happens when a change order is approved. Who updates the contract value and the purchase order, as part of the same step rather than as a follow-up.
• Which invoices never pay on a single signature. A threshold, or a rule that any invoice touching a change order gets a second look.

The point of writing these down is not control. It is that when the CFO asks in month nine why an invoice was approved, somebody can answer without reconstructing it.

When a spreadsheet stops being enough

With one or two CRO agreements and few change orders, a well-kept spreadsheet handles all of this. The signs that it no longer does are specific:

• Approved change orders are not consistently reflected in purchase orders
• Confirming that work was delivered happens in email threads
• Nobody can say quickly how much has been invoiced against a given SOW
• Pass-throughs and service fees sit in one undifferentiated total
• The answer to "why was this approved?" requires reconstruction

How biosuite helps

biosuite keeps vendor contract financials, change orders, purchase orders, approvals and invoices connected in one place, so the documents an invoice should be checked against are the ones in front of the person checking it.

The part most relevant to this guide is invoice receipt confirmation routing, which is included in the professional plan: an invoice is routed to the person who can confirm the work was delivered, and the confirmation is recorded against it. For teams that need a formal three-way match between purchase order, invoice and receipt, that sits in the advanced plan.

biosuite works alongside your accounting or ERP system rather than replacing it.

Your accounting system sees the invoice. biosuite sees the commitment behind it.

Start tracking your CRO contract financials for free →

Frequently asked questions

How do you match CRO invoices against contracts and purchase orders?

Check the applicable statement of work and approved change orders, confirm the rates and units match the agreed budget, confirm the billing event occurred, check pass-through costs against documentation, and check cumulative billing against the purchase order and remaining contract value.

What is three-way matching for CRO invoices?

Comparing the purchase order, the invoice and a record that the services were delivered. It confirms those three agree, but it does not confirm the purchase order reflects the current statement of work and approved change orders.

What are pass-through costs in a CRO contract?

Third-party costs the CRO incurs on your behalf and bills on, such as investigator grants, central lab work, shipping and ethics fees. They are usually budgeted estimates rather than fixed prices, so whether the signed contract value acts as a hard cap depends on the agreement.

Can a CRO invoice work that was not approved in advance?

It happens, usually as a retroactive change order. Whether it is payable depends on the contract. If it recurs, agree a process with the CRO for flagging out-of-scope work before it starts.

Should you pay an invoice while part of it is disputed?

Where the contract and your accounts payable process allow it, consider paying the undisputed portion and holding only the disputed amount. Record the reason, the amount and what resolves it, and track the held amount as potential exposure rather than as approved commitment.

Does an invoice need its own purchase order?

Not necessarily, but billing should be checked against a purchase order that reflects the current contract value. When a change order is approved, revise the purchase order covering that scope at the same time.

Related reading: How to track CRO commitments, change orders and invoices, which covers contract values, remaining commitment and the difference between a commitment and an accounting accrual.

The examples in this article are illustrative and do not constitute legal, accounting or financial advice.