Why revenue isn't product revenue for biotech
Most ERP financial modules operate on a simple pattern: Ship a product or provide a service, recognize revenue. That pattern is rarely available to biotech companies in the clinical stage. Any revenue that does occur prior to commercialization is derived from license and collaboration agreements, government or foundation grants, and cost-sharing arrangements with development partners.
Each revenue type has its own recognition logic and none of them map cleanly to the standard order to cash flow that NetSuite ships with. Organizations that generate collaboration revenue via a standard sales order process wind up with recognition schedules that don't align with the substance of the agreement, and finance teams that reconcile the gap in spreadsheets every quarter.
ASC 606 Customer contracts vs. ASC 808 Collaborative arrangements
The initial configuration decision is classification. In general, a collaborative arrangement where both parties are active participants in a joint research effort and share in the risk and reward of that effort is accounted for under ASC 808, not ASC 606. ASC 606 generally considers a licensing arrangement in which a partner is a customer of the company’s IP to be a contract.
This is no academic distinction. This affects the applicable NetSuite revenue recognition engine, the income statement presentation (revenue or contra-expense for cost reimbursements), and disclosures the arrangement requires. This classification is incorrect at the start of the contract and necessitates a rebuild of the recognition schedule later, often after a question is asked by an auditor that the finance team cannot answer cleanly.
Recognition of upfront payments, milestones and royalties
For arrangements within scope of ASC 606, the performance obligations will need to be identified and the transaction price allocated across the performance obligations. Upfront payments are rarely recognized on the spot, but are deferred and recognized over the period that the company is expected to perform underlying obligations such as ongoing research services.
Milestone payments must be analyzed for constraints. Payments related to events that are highly susceptible to factors outside of the company’s influence, such as regulatory approval, are generally excluded from the transaction price until the constraint is resolved. Royalties on licensed IP are recognized on the underlying sales rather than receipt. Each of these patterns can be supported using NetSuite’s native revenue recognition engine but would require configuration specific to the arrangement type and not a generic subscription or milestone template.
Grants: government and foundation revenue
NIH, BARDA, foundations and other sources of funding tend to be on a cost-reimbursement or cost-plus basis rather than a performance-obligation model. Revenue is generally recognized as allowable costs are incurred, subject to the terms of the individual award.
It requires the chart of accounts and project structure to track allowable vs. unallowable costs by grant, cost category limits where specified in the award and the application of indirect cost rate. Organizations managing multiple concurrent grants are left reconciling grant draws in Excel, creating audit risk and causing a delay in reporting at each close, without project-level cost tracking in the ERP.
Taking into account the cost-sharing and reimbursement between the partners
There are many collaboration agreements that have cost-sharing provisions where each party pays some percentage of the costs of joint development, and then the parties true up the numbers and pay each other back from time to time. That means that the ERP has to be able to track actual costs per program, apply the sharing formula and automatically generate the reimbursement invoice or bill.
Organizations that do this manually typically only find out about cost allocation errors months later when doing a partner audit or internal review to reconcile a shared cost pool with what was actually billed. Using the built-in sharing formula to configure project accounting closes this gap and provides defensible support for each reimbursement transaction.
Good project accounting as a by-product of R&D tax credit tracking
When project accounting is properly set up for collaboration and grant purposes, it produces a valuable by-product for the organization: the tracking of qualified research expenses needed to support R&D tax credit claims. That’s all a tax credit study requires: time tracking by project, expense categorization by qualifying activity, and documented allocation methodologies.
Biotechs that build this structure retroactively, at tax credit study time, spend a lot more on the study and often leave credit on the table because contemporaneous documentation does not exist. Designing this into the ERP from the start means that an annual scramble becomes a report that is already there.
NetSuite configuration with no spreadsheet shadow system
Organizations that are good at managing collaboration, grant and license revenue in NetSuite have one thing in common: revenue arrangements are classified and documented at the start of the contract, project structures match the actual cost-sharing and reporting requirements of each agreement, and the revenue recognition engine is configured based on the arrangement type rather than being forced to fit into a single generic template.
The alternative is a shadow system in Excel that re-calculates recognition every quarter, isn’t connected to the general ledger in a way that an auditor can trace, and depends on institutional knowledge that leaves when a team member does. For a company preparing for a Series C, a partnership, or an eventual IPO, that gap is a diligence finding in waiting.