The CDMO finance problem
A contract development and manufacturing organization runs 2 businesses at once. It is a manufacturer, which means GMP discipline, batch records, equipment qualification, and a physical inventory of raw materials, intermediates, and finished product. It is also a services business, which means project accounting, milestone billing, sponsor-specific cost tracking, and revenue recognition that follows the terms of every individual contract.
Most ERP systems are built for one or the other. A manufacturing ERP gets inventory and bills of material right and treats project accounting as an afterthought. A services ERP handles project costing and misses the GMP requirements that define how a CDMO actually operates. The gap shows up in the finance close. Month-end becomes a 10-day exercise in spreadsheet reconciliation between the production system, the project tracker, and the general ledger.
NetSuite, configured correctly, closes that gap. Per Oracle NetSuite's Life Sciences ERP documentation, the platform integrates finance, supply chain, quality, manufacturing, and R and D data on one cloud platform with validation-ready audit trails and Part 11-compliant electronic records and signatures. For a CDMO, the value is not in any single module. It is in the integration of project accounting, inventory, advanced manufacturing, and revenue recognition on a single platform of record. Archer's work centers on the configuration that makes that integration usable for sponsor-program reporting.
The CDMO finance problem is not that any single function is unsupported. It is that integration across functions is what generic ERP implementations consistently miss.
Why generic ERP fails CDMO operators
There are 4 places a generic NetSuite implementation, or a generic ERP of any kind, breaks down for a CDMO.
Project accounting at the program level
A CDMO sponsor program is not a single project. It is a portfolio of phases, each with its own cost structure, billing milestones, and deliverables. Phase 1 clinical manufacturing has different cost drivers than Phase 3 process performance qualification. An ERP that treats the entire sponsor relationship as a single project loses the granularity needed to manage margin, scope changes, and milestone revenue.
Inventory segregation by sponsor
Raw materials, intermediates, and finished product belonging to one sponsor cannot mix with another sponsor's material, even on a shared piece of equipment. Generic inventory configurations track lot and location. They do not enforce sponsor segregation as a hard constraint on transactions.
GMP-required documentation
FDA 21 CFR Part 11 requires audit trails, electronic signatures, and validated systems for any electronic record that supports a GMP decision. Most ERP implementations treat compliance as an external program. For a CDMO, the ERP is part of the validated environment, and the configuration has to demonstrate it.
Multi-entity consolidation
CDMOs operating in multiple countries, or with separate subsidiaries for clinical and commercial work, need consolidation that handles intercompany transfers, transfer pricing, and currency translation without manual journal entries at close.
How Archer configures NetSuite for CDMOs
Archer Insights has implemented NetSuite for contract manufacturers operating across clinical and commercial production, sterile and non-sterile fill finish, and biologic and small molecule modalities. The configuration approach is consistent across engagements.
Project structure is built as a parent program with phase-level subprojects. Each phase carries its own budget, milestone schedule, and billing terms. Costs collected at the phase level roll up to the program for sponsor reporting and to the subsidiary for financial reporting. Change orders are tracked as discrete project events with their own approval workflow, configured through Archer's Approvals App.
Inventory is configured with sponsor as a required dimension on lot records. Bin structures map to physical segregation in the warehouse. Material movements between sponsors are blocked at the transaction level, not flagged after the fact. The constraint lives in NetSuite, not in operator memory.
Revenue recognition is configured against the contract structure. Archer's Contract Lifecycle Management module tracks milestones, accruals, and obligations against the project. Time and materials work bills as costs are incurred. Fixed-price phases recognize revenue against milestone achievement or input-based percent complete per ASC 606. Royalty and milestone obligations surface in CFO reporting without manual tracking.
Multi-entity consolidation runs on NetSuite's OneWorld framework. Intercompany transfers between clinical and commercial subsidiaries are automated. Transfer pricing is applied at the transaction level. Foreign currency translation runs on the close calendar, not the spreadsheet.
Related on archerinsights.com
- CDMO industry page. Archer's purpose-built configurations for contract development and manufacturing.
- Contract Lifecycle Management module. Milestone, accrual, and obligation tracking inside NetSuite.
- Approvals App for SOX-ready workflows. Configurable approval routing with full audit trail.
- Quality Management System. GMP-grade quality workflows integrated with NetSuite records.
- NetSuite Implementation services. Life sciences specific implementation approach.
- Case studies. Documented CDMO and life sciences engagements.
External references
- NetSuite Life Sciences ERP
- Choosing the Right ERP for Life Sciences
- FDA 21 CFR Part 11: Electronic Records and Electronic Signatures
- ASC 606 Revenue Recognition Standard
Configure NetSuite for the way your CDMO actually operates
A discovery call with an Archer implementation lead covers your current state, the configuration gaps that matter most for your sponsor mix, and a realistic timeline from LOI to go-live.