The hardware-plus-service problem
A medical device company sells a product, services that product across its operational life, and generates recurring revenue from consumables, parts, software, and service contracts. The financial statements have to reconcile manufacturing economics with service economics, with each governed by its own ASC 606 treatment. Most ERP implementations are configured for one model or the other. Device companies need both.
As Archer's medical devices industry page describes, medical device companies operate at the intersection of regulatory intensity, distribution complexity, and growth pressure. UDI compliance, lot-level traceability, quality system integration, and multi-channel revenue recognition do not simplify as you scale. NetSuite, configured for medical device, supports the device lifecycle from raw material through end of life.
A medical device company is two businesses on one platform. ERP that treats it as one model loses the visibility CFOs need to manage either side.
Why generic ERP fails medical device operators
UDI compliance
Unique Device Identification (UDI) requires device-level identifiers carried through manufacturing, distribution, and post-market. Generic lot tracking does not satisfy UDI without configuration extensions.
21 CFR Part 820 quality system
The FDA Quality System Regulation requires document control, design controls, corrective and preventive action documentation, and complaint handling. The ERP supports parts of this if configured correctly. Bolt-on quality systems duplicate data and create reconciliation work at audit time.
510k cost tracking
510(k) Premarket Notification costs accumulate over months or years. The program cost basis matters for capitalization decisions, R and D credits, and CFO reporting. Generic ERP configurations lose the structure.
Service contract revenue
ASC 606 application to service contracts requires performance obligation analysis distinct from product sale recognition. Combining the two without configuration produces revenue numbers neither auditors nor investors can defend.
How Archer configures NetSuite for medical device
UDI is configured as a structural field on item records and lot transactions. Device identifier and production identifier components are both supported. GUDID submission data flows from NetSuite without secondary data entry.
21 CFR Part 820 configuration aligns NetSuite's approval workflows, audit trail, and electronic signature capabilities with the quality system documentation requirements. Archer's Quality Management System module handles design history file, device master record, and device history record references inside NetSuite without bolt-on systems.
510k program cost accumulates against a program record from project initiation. Internal labor, external service, prototype, and testing costs all flow to the program. Invoice OCR Capture reduces manual AP processing on the high volume of testing and external service invoices. The capitalization decision and the R and D credit calculation both run off the same data.
Service contract revenue is configured with separate performance obligations for stand-ready service, planned maintenance, and time-and-materials work. Contract Lifecycle Management tracks renewals, escalations, and modifications. Revenue recognition runs against each obligation independently.
Related on archerinsights.com
- Medical devices industry page. Archer's full configuration approach for medical device companies.
- Quality Management System. 21 CFR Part 820 quality workflows integrated with NetSuite.
- Contract Lifecycle Management module. Service contract management and revenue recognition.
- Invoice OCR Capture. AP automation for high-volume R and D and service spend.
- Material Requirements Planning for life sciences. Manufacturing planning for regulated device production.
- Approvals App for SOX-ready workflows. Design control and engineering change approvals.
External references
- NetSuite Life Sciences ERP
- FDA Unique Device Identification System
- FDA Quality System Regulation (21 CFR Part 820)
- FDA 510(k) Premarket Notification
Configure NetSuite for the device lifecycle, not just the sale
A discovery call with an Archer implementation lead. Bring your product mix and service model, and leave with a clear view of the configuration that supports both.