How CDMOs handle phase-gate project accounting in NetSuite

The phase-gate accounting problem most CDMOs are still running on spreadsheets

A contract development and manufacturing organization runs a single sponsor program across multiple phases. Process development. Tech transfer. Phase I clinical batch manufacturing. Phase II expansion. Phase III process performance qualification. Commercial supply. Each phase has its own cost structure, its own deliverables, its own billing terms, and its own implications for the sponsor's books.

The CDMO bills under a single master services agreement, with work orders that release scope phase by phase. The ERP has to track cost at the phase level, recognize revenue at the milestone level, manage WIP versus expense classification at the item level, and produce sponsor-ready cost reports that survive audit. Most generic ERP implementations treat the sponsor relationship as a single project and reconcile the rest in Excel.

NetSuite supports phase-gate project accounting natively when configured for it. Per Oracle NetSuite Life Sciences ERP documentation, the platform handles milestone-based revenue recognition and project accounting on a single cloud platform. The configuration work is in mapping the CDMO's specific phase structure to NetSuite's project hierarchy without losing granularity.

Phase I is not Phase II. Different cost behavior, different billing trigger, different sponsor accounting treatment. ERP that treats them the same drops revenue and creates audit findings.

The 5 phases that matter for CDMO project accounting

Every sponsor program in a CDMO can be modeled with 5 phase types, even when sponsors use different naming conventions.

Phase 01 Process development and tech transfer

Cost-plus or time and materials billing. Sponsor expenses these costs as R and D in most cases. CDMO recognizes revenue as costs are incurred. The configuration needs visibility into hourly labor, lab consumables, and analytical services at the work order level.

Phase 02 Engineering runs and validation lots

Fixed price or hybrid billing. Engineering runs may or may not be billable depending on the MSA. Validation lots are billable when successful, sometimes at risk to the CDMO when not. WIP versus expense treatment becomes complex here: the sponsor may capitalize validation lots as pre-launch inventory if the BLA or NDA is reasonably assured.

Phase 03 Phase I clinical manufacturing

Fixed price per batch with quality release gating. Revenue recognition under ASC 606 typically runs at the point of GMP batch release, not invoice. Sponsor expenses the cost as R and D under ASC 730.

Phase 04 Phase II and III commercial-stage clinical

Same structure as Phase I but with higher batch sizes, longer runs, and tighter delivery commitments. Some sponsors begin capitalizing lots as pre-launch inventory once Phase III enrollment hits a defined milestone.

Phase 05 Commercial supply

Full COGS treatment for the sponsor. Take or pay contracts, minimum guarantees, and price escalators are common. Revenue recognition transitions to point-in-time at shipment or transfer of control, depending on contract terms.

How to model phase-gate projects in NetSuite

The recommended NetSuite project structure for a CDMO sponsor program uses a parent program record with phase-level subproject records underneath, each tied to one or more work orders.

Phase I versus Phase II cost buckets in practice

The financial difference between phases shows up in 4 places.

Direct labor

Phase I uses senior process development and analytical scientists at higher loaded rates. Phase II uses GMP manufacturing operators at standard rates. Same person can be on both, but the time has to be coded to the correct subproject for cost reporting to make sense.

Material consumption

Phase I burns through small-volume reagents, single-use plastics, and analytical standards. Phase II uses production-scale raw materials and GMP-released APIs. The bill of material on the work order has to match the phase.

Quality oversight

Phase I quality review is process development engineering. Phase II is full GMP batch record review, QA approval, and quality unit lot release. The labor allocation reflects the difference.

Documentation

Phase I generates development reports. Phase II generates batch records, certificates of analysis, and release documentation that flows to the sponsor's regulatory submission. The cost of documentation labor is meaningful and has to be captured.

Client billing triggers and how to configure them

The MSA defines billing triggers. The ERP enforces them. Common patterns for CDMO billing triggers:

Time and materials. Bills as costs are incurred. NetSuite project billing posts on a defined cadence, usually monthly. Configuration uses standard time entry and expense recording against the subproject.

Fixed price on milestone. Bills when a milestone is achieved. Milestones are tracked in Contract Lifecycle Management. Achievement is recorded as a discrete event, which triggers the billing schedule.

Per-batch fixed price. Bills on GMP batch release. Configuration ties the work order to the milestone, and the quality release transaction triggers the invoice through Approvals App.

Cost-plus with cap. Bills incurred cost plus a fixed margin, up to a cap. NetSuite project billing calculates the margin automatically and stops at the cap. Variance over the cap surfaces as a recovery risk on the project dashboard.

Hybrid. Fixed milestone payment plus time and materials for change orders. Configuration runs two billing streams against the same subproject, with the change order tracked separately.

WIP versus expensed R and D: the configuration that matters

The CDMO does not decide whether a sponsor capitalizes pre-launch inventory. The sponsor does. But the CDMO's invoicing and cost reporting has to support either treatment without rework.

The practical configuration:

1. Item records for clinical batches carry a default cost treatment field. Pre-approval batches default to expense. Validation and pre-launch lots default to WIP when the MSA specifies. Commercial batches default to COGS.
2. Cost roll-up posts to a project-specific COGS or R and D expense account based on the item's default, with override capability.
3. Sponsor reports run from the project structure and present cost by phase, with classification visible for each lot.
4. When the sponsor's accounting policy changes mid-program, the configuration accommodates the change through reclassification entries that preserve the audit trail through 21 CFR Part 11-compliant electronic records.

Reporting that survives sponsor audit

Sponsor audit teams ask for 4 reports during any CDMO review.

Cost by phase, by lot, with labor, material, overhead breakdown. Run from NetSuite subproject reporting. The data lives in the project structure.

Milestone history with achievement date, billing amount, and supporting documentation reference. Lives in Contract Lifecycle Management.

Change order log with cost impact and approval trail. Lives in the project change order records and Approvals App history.

Inventory reconciliation showing sponsor material in CDMO custody by lot, location, and status. Runs from NetSuite lot tracking.

None of these reports should require Excel reconstruction. If they do, the configuration is incomplete.

Related on archerinsights.com

1. CDMO industry page. Archer's purpose-built configurations for contract development and manufacturing.
2. NetSuite for CDMOs hub. The foundational configuration approach for CDMO operations.
3. Contract Lifecycle Management. Milestone, accrual, and obligation tracking inside NetSuite.
4. Approvals App for SOX-ready workflows. GMP batch release and change order routing.
5. Quality Management System. GMP quality workflows integrated with project records.
6. Case studies. Documented CDMO and life sciences engagements.

External references

1. NetSuite Life Sciences ERP
2. FDA 21 CFR Part 11: Electronic Records and Signatures
3. FASB ASC 606 Revenue Recognition Standard
4. ICH Quality Guidelines (Q9 Quality Risk Management)