Why a milestone payment is not always revenue in the books

A $2.5M pharma milestone hits your bank and your bookkeeper records it all as revenue. Here is why that is often wrong and how to split it correctly.

A biotech CFO we work with received a $2.5 million milestone payment from their pharma partner in October. The collaboration agreement had been in place for eighteen months. The bookkeeper recorded the full $2.5 million as collaboration revenue when the wire cleared. Four months later, during a Series B audit, $1.8 million had to be reclassified as deferred revenue. The board presentation had shown the wrong number for an entire quarter.

Nothing fraudulent happened. The books had simply missed a step.

Milestone payments and earned revenue are not the same thing

In life sciences partnerships, milestone payments arrive in a single wire. But what triggered the payment and what the company still owes the partner are separate questions. A milestone payment often funds future work as much as it compensates for past work. The portion attached to completed obligations belongs in revenue. The portion covering future obligations sits in deferred revenue until that work is done.

The standard accounting method auditors expect is called ASC 606 under Generally Accepted Accounting Principles (GAAP). It requires companies to identify their promises in a contract and match revenue to when those promises are fulfilled. The payment date is not the revenue date. The obligation completion date is.

Four reasons milestone payments get recorded incorrectly

Collaboration agreements contain multiple performance obligations. Most pharma partnership agreements include more than one deliverable. A company might agree to provide preclinical data, supply drug substance for clinical trials, participate in joint steering committee meetings, and share manufacturing know-how. Each is a separate promise with its own revenue timing. When a milestone payment arrives, the question is which promises the payment relates to, not when the wire arrived.

Not all milestone triggers are completion events. Some milestones are tied to work already finished, like delivering a Phase 1 data package. Others fund work that comes next, like providing manufacturing guidance through Phase 2. A payment that covers future work is a prepayment, not earned income. Recording it as revenue before the work is done overstates the Profit and Loss report (P&L) and understates the company’s liabilities.

The payment amount rarely maps to a single obligation. A $2.5 million milestone might include $700,000 for completed work and $1.8 million for future consulting and data-sharing commitments. Splitting it correctly requires reading the agreement and assigning value to each obligation. A quick entry to collaboration revenue skips that step entirely.

Deferred revenue is a real liability. When a company books a milestone payment as revenue before the work is done, it is reporting income not yet earned. If the partnership terminates early, money may be owed back to the partner. During due diligence, an audit adjustment reclassifying revenue into deferred raises immediate questions about financial controls, even when the cause is a timing error.

What one milestone looked like correctly split

Here is what the $2.5 million milestone looked like after the collaboration agreement was reviewed and obligations were separated.

Obligation	Status at payment date	Amount
Phase 1 data package	Complete, final report submitted	$700,000
Technology transfer support	In progress, 8 months of consulting remaining	$1,100,000
Manufacturing process advisory	Not started, Phase 2 guidance pending	$700,000
Total milestone received		$2,500,000
Revenue recognized in October	Data package obligation complete	$700,000
Deferred revenue as of October	Future obligations not yet met	$1,800,000

The $700,000 went to the P&L in October. The $1,800,000 sat on the balance sheet as a deferred revenue liability and moved to income each month as the consulting and advisory work was completed.

Why the error compounds

Three problems follow from recording the full milestone as revenue before obligations are met.

Board reporting shows the wrong number. A board deck showing $2.5 million in collaboration revenue for the quarter, when only $700,000 was earned, overstates income by $1.8 million. When the correction happens in audit fieldwork, it reads like a restatement even when it is a bookkeeping fix. Board members who tracked that number through the year will have questions.

Due diligence complications. Series B investors and pharma acquirers examine revenue quality. An audit adjustment shifting $1.8 million from revenue to deferred raises concerns about controls, even when the underlying cause is a timing error in the books.

Grant income becomes harder to verify. Life sciences companies often hold federal grants alongside partnership revenue. Grant program officers expect clean separation between income types. A lump milestone on the revenue line obscures that separation and can slow grant compliance reviews.

What correct milestone accounting looks like

For life sciences clients we work with, every collaboration agreement is reviewed before any milestone payment is recorded.

First, list every performance obligation in the agreement. Common obligations in pharma partnerships include data package deliveries, clinical supply of drug substance, technology transfer consulting, manufacturing guidance, and joint committee participation.

Second, assign a value to each obligation based on what it would cost as a standalone deliverable.

Third, determine what is complete and what is not. Finished obligations are recognized as revenue. Obligations in progress or not started remain in deferred revenue.

Fourth, maintain a monthly recognition schedule showing the opening deferred balance, amounts recognized that month, and the remaining obligation. The schedule is updated each time work on an obligation is completed.

Best practices for life sciences companies

A few practices that keep milestone accounting clean:

Review the collaboration agreement before recording any milestone payment. Listing obligations takes less than an hour and prevents audit adjustments later.
Set up a separate deferred revenue account for each pharma partner. A single catch-all deferred revenue line for multiple partnerships makes it impossible to track which obligation belongs to which agreement.
Maintain a monthly recognition schedule and update it each time an obligation is completed, not at quarter-end.
Align recognition with actual deliverables, not the calendar. Revenue moves to income when an obligation is met.
Review the recognition schedule before each board meeting so the revenue figure in the board deck matches the books.

Three questions worth asking

If you are not sure how milestone payments have been handled in your books, three questions to ask whoever manages your finances:

For each milestone received in the last twelve months, which specific obligations in the collaboration agreement were complete on the payment date, and which were still in progress?
Does the company maintain a deferred revenue schedule for each partnership, updated monthly as work is completed?
Have auditors ever proposed an adjustment to collaboration revenue timing, and what process change followed?

If those answers are uncertain, milestone payments may have been booked as 100 percent revenue regardless of whether the underlying obligations were finished. A one-time agreement review and a monthly recognition schedule going forward will correct it.

If your company has received a milestone payment in the last two years and is not sure how much belongs in deferred revenue, send us the collaboration agreement summary and the milestone amounts received. We review milestone accounting for life sciences companies and can confirm whether the books match what the agreement requires.