Medical device companies rarely sell the same way twice. A single capital asset can move under a purchase order, a lease, a hybrid usage fee, or a financing arrangement depending on what the customer needs. When your ERP treats all of those the same way, something eventually breaks.
Consider a company selling a capital device into outpatient clinics. One customer wants to own the equipment outright. Another prefers an operating lease at a lower monthly commitment. A third wants the device placed at no upfront cost with a per-procedure fee billed every time it is used. A fourth negotiates a hybrid arrangement with a reduced monthly base and a per-use charge above a volume threshold. All 4 are selling the same device. All 4 create different obligations, different recognition timelines, and different invoicing requirements. Finance has to track each one discretely, accurately, and on time.
This is not an edge case. It describes how a growing number of medtech and capital equipment companies go to market, particularly those selling into physician practices, outpatient facilities, or health systems where procurement preferences vary and deal competition is high. The commercial team needs flexibility to close. The finance team needs structure to report. The ERP has to support both.
The commercial models you actually encounter
Before getting into the system design, it helps to name the models clearly. Medical device companies typically operate some combination of the following:
01. Outright sale
Customer purchases the device. Revenue recognized at delivery or upon acceptance depending on contract terms. Simplest model operationally, but still requires performance obligation mapping under ASC 606 when support or training is bundled.
02. Operating lease
Customer pays a monthly or quarterly lease fee. Device stays on the seller's books as an asset. Revenue recognized straight-line over the lease term. Many agreements include a purchase option at end of term, typically at a heavily discounted residual price. That option changes the accounting treatment, the asset disposition path, and what finance needs to track from day 1 of the contract.
03. Per-use or per-procedure fee
Device is placed with the customer at no upfront cost or a nominal fee. Revenue accrues each time the device is used. Common in capital equipment where adoption barriers are high and the manufacturer wants to align its economics with clinical utilization. Requires usage data collection, metered billing, and variable revenue recognition.
04. Device plus service contract
Customer buys or leases the device and also pays for an annual service or maintenance agreement. Two distinct performance obligations under ASC 606, each with its own recognition schedule. Allocation of the bundled transaction price is required.
05. Hybrid capital and usage
Customer pays a reduced upfront or monthly fee combined with a per-use charge above a volume threshold. Increasingly common as device companies seek to lower adoption barriers while protecting long-term revenue. Most complex to model and invoice correctly.
06. Commercial partnership
Device company makes a strategic investment in or loan to a customer in exchange for an exclusive usage commitment. Revenue flows through procedure fees rather than capital. Requires tracking against contract minimums, exclusivity terms, and milestone dates.
Each of these creates a distinct contractual relationship. The problem is that most ERP configurations are built around 1 or 2 of them, and the rest get handled through workarounds, side spreadsheets, or manual journal entries that accumulate error over time.
"The commercial team closes a deal. Finance finds out at invoice time that the structure does not exist in the system. That gap is where revenue leaks."
What NetSuite can actually do here
NetSuite has the native architecture to handle this correctly when it is configured with intention. The relevant capabilities span several modules that need to work together rather than independently.
Advanced Revenue Management
NetSuite's ARM module handles multi-element arrangements directly. A single contract can contain a device sale element, a service element, and a usage element, each with its own standalone selling price, recognition rule, and deferral schedule. ARM automates the allocation of the total transaction price across those elements based on configured fair value methods, producing compliant ASC 606 treatment without manual journal entries.
SuiteBilling for recurring and usage models
SuiteBilling handles subscription-style and consumption-based billing natively. For a per-use model, usage records feed into a rating engine that calculates the invoice amount at the end of each billing cycle. For a hybrid model, a base fee and a variable usage charge can appear on the same invoice. Change orders manage mid-contract modifications such as volume threshold changes or term extensions, with automatic proration.
Fixed asset management and end-of-term buyouts
Devices placed under operating leases must remain on the lessor's balance sheet as assets. NetSuite's fixed asset module tracks each device, applies a depreciation schedule, and ties the asset record to the lease contract and customer. When a purchase option exists, the contract needs to capture the option price, the eligibility window, and the residual value the lessor is carrying. If the customer exercises the option, NetSuite generates the buyout invoice at the agreed discounted price, closes the lease revenue schedule, reverses any remaining deferred amounts, and removes the asset from the fixed asset register. If the option price is low enough to make exercise reasonably certain at contract inception, the arrangement may also need to be evaluated as a finance lease under ASC 842 rather than an operating lease, which changes the revenue recognition treatment entirely. Getting that classification right at deal entry, not at audit time, is what a properly configured ARM and fixed asset setup enables.
Revenue arrangements and performance obligations
ARM creates revenue arrangements as containers for performance obligations, mirroring the structure of the customer contract. Each performance obligation carries its own recognition start and end date, allocation amount, and recognition method. When a contract is modified, the arrangement absorbs the change order without requiring a new sales order or manual reconciliation of the old one.
Multi-book accounting
Companies that report under both US GAAP and IFRS 15, or that carry investor reporting requirements alongside statutory books, can use NetSuite's multi-book architecture to maintain parallel treatment for the same contract without duplicate data entry.
Deferred revenue management
Upfront payments under a usage or subscription model create a contract liability until the service is delivered. NetSuite moves revenue from deferred to earned automatically based on the recognition plan, with real-time GL impact and a clean audit trail for each period.
A note on ASC 606
Any contract that bundles a device with a service, a lease with a usage fee, or a capital sale with ongoing support contains multiple performance obligations under ASC 606. Each obligation requires a standalone selling price allocation, its own recognition timeline, and its own deferral treatment. Companies that handle this in spreadsheets or with manual journal entries are carrying significant financial statement risk, particularly as deal volume grows or audit scrutiny increases.
A note on ASC 842 and purchase options
When a lease agreement includes a purchase option at a heavily discounted price, that option is a material contract term that affects classification from the start. Under ASC 842, if the option price is low enough that exercise is reasonably certain, the arrangement is a finance lease, not an operating lease. That changes how the lessor records the transaction: instead of recognizing straight-line rental revenue over the lease term, the company derecognizes the asset at lease commencement and recognizes a net investment in the lease. Revenue recognition, balance sheet presentation, and the depreciation treatment of the device all shift. NetSuite's fixed asset and ARM configuration needs to reflect the correct classification at contract entry. Reclassifying midstream or at audit is materially more complex than getting it right on day 1.
Where automation changes the equation
Getting the configuration right is the foundation. But even a well-configured NetSuite environment still requires human decisions at key points in the contract lifecycle: when a deal structure is new, when contract terms change mid-cycle, when usage data comes in from an external system, and when something is off in the revenue waterfall. That is where automation and AI have real leverage.
Automated deal classification
Contract intake. An AI layer reading inbound contracts or deal notes can classify the commercial model, identify performance obligations, and pre-populate the NetSuite sales order with the correct items, recognition rules, and billing schedules, eliminating manual translation from the sales agreement to the ERP.
Usage data processing
Usage billing. Devices typically generate usage data in formats that do not match NetSuite's usage record structure. An automated integration with AI-assisted validation can ingest raw device telemetry or facility-reported procedure counts, clean them, flag anomalies, and push billing-ready usage records into SuiteBilling without a human touching the file.
Recognition exception monitoring
Revenue ops. ARM produces a lot of data. An AI monitoring layer can review recognition plan status across the contract portfolio, surface arrangements that are off-schedule, flag deferred revenue balances that have not moved in an unexpected pattern, and route exceptions to the right person before the period closes.
Renewal and modification routing
Contract lifecycle. As leases approach end of term, automated workflows can trigger alerts for both renewal and purchase option windows, assemble a briefing for the account team showing the option price, remaining asset value, and customer utilization history, and pre-draft the appropriate transaction in NetSuite for finance review. No option window lapses because it was buried in a contract folder.
Revenue waterfall analysis
Reporting. Finance teams at device companies regularly need to explain to leadership and investors how revenue is flowing across commercial model types. AI-assisted reporting can pull ARM data, segment it by deal structure, and produce a clean waterfall showing recognized, deferred, and expected revenue by model, region, or customer cohort.
Audit trail generation
Compliance. Auditors want to trace a specific revenue recognition entry back to the original contract term. An AI-assisted documentation layer can assemble that chain automatically, pulling the sales order, ARM arrangement, recognition event, and GL posting into a single thread without manual reconstruction.
Where Archer fits into this
Archer has worked with life sciences and healthcare companies across enough deal structure variation to know where the real complexity lives. It is rarely in the ERP itself. NetSuite can handle these models when it is configured correctly. The breakdown happens at the seams: between what sales puts in a contract and what finance sees in the system, between a usage data feed and a billable record, between a contract modification and a revenue arrangement update.
Our work in this space draws on several capabilities we have built specifically for the healthcare and life sciences segment.
Our Contract Lifecycle Management module gives commercial and finance teams a shared record of every customer agreement, its key terms, its milestone dates, and its current status. That shared record is what makes automated recognition rule assignment and billing schedule creation possible: you cannot automate what you cannot see.
The Accruals App addresses a related problem specific to usage models: when usage data lags the period end, you need to accrue revenue based on estimates and then true up when actuals arrive. Doing that manually across a large device fleet is slow and error-prone. We built the app to automate that cycle inside NetSuite, with full period-over-period traceability.
For companies operating under SOX or preparing for audit, the SOX Approvals module adds a structured approval workflow to revenue-affecting transactions, ensuring that contract modifications, recognition plan changes, and usage billing adjustments clear the right reviewers before they post to the GL.
What to do before the next deal closes
The best time to design the commercial model architecture in your ERP is before the sales team signs a deal structure the system cannot handle. In practice, most companies come to us after the fact, when a particular deal type has created a billing backlog, a deferred revenue mess, or an audit question they cannot answer cleanly.
If your device company is offering or considering more than 1 commercial model, the questions worth answering now are:
Does your NetSuite sales order structure have a line item type and recognition rule for each model you sell? Can you produce a report right now showing recognized versus deferred revenue by commercial model across your active contract portfolio? When a customer switches from a lease to a per-use arrangement mid-contract, does your system handle the modification or does finance rebuild the arrangement by hand? Is usage data moving from device to billing record automatically, or does someone have to touch it?
If any of those questions do not have a clean answer, the gap is worth closing before deal volume makes it harder.
Build the architecture before the complexity builds itself
Archer works with medical device and medtech companies to design and implement NetSuite configurations that handle multiple commercial models from the start, not as an afterthought.