GTN in Generics

Executive Summary

Gross-to-Net (GTN) is one of the most underestimated risks in generic pharmaceutical finance.

For emerging and mid-market generics companies, the question is rarely whether GTN matters ; it is when complexity crosses the line from manageable to material.

Oracle NetSuite is often positioned as either a complete GTN solution or entirely insufficient. Both views are wrong.

Archer Insights’ point of view is simple:

1. NetSuite is an excellent financial foundation for Gross-to-Net
2. It is not a purpose-built GTN calculation engine
3. The winning strategy is phased, audit-first, and scale-aware

When implemented correctly, NetSuite can:

1. Support GTN accruals and controls
2. Serve as the system of record for revenue and liabilities
3. Provide a clean audit trail under ASC 606

As GTN complexity grows, NetSuite should not be replaced ; it should be paired with a specialized GTN platform such as Model N or Revitas.

Archer helps generics companies design this journey deliberately, avoiding over-engineering early and rework later.

1. What Makes GTN Hard in Generics

This section intentionally focuses on operational reality, not theory.

GTN complexity in generics is driven by:

1. Chargebacks (high volume, contract-driven, retrospective)
2. Government programs (Medicaid, Medicare Part D, 340B)
3. Channel mix volatility (wholesalers, specialty, direct)
4. Time lag between shipment, claim, and settlement
5. Auditor scrutiny under ASC 606

Any system supporting GTN must handle:

1. Accrual estimation at time of sale
2. Claim validation and reconciliation
3. Periodic true-ups
4. Transparent assumptions and controls

2. When NetSuite Is a Good Fit for GTN

NetSuite is a good fit when GTN complexity is real but still manageable.

Typical Company Profile

1. Early to mid-stage generics company

2. Limited product portfolio (generally < 20 SKUs)

3. Primary distribution through 1–3 wholesalers

4. Contract structures are relatively stable

5. Government exposure exists but is not dominant

6. Finance team is hands-on and process-driven

GTN Characteristics

1. Chargebacks are material but not overwhelming in volume
2. Accruals can be estimated using historical percentages
3. Rebates and returns are predictable
4. Quarterly true-ups are acceptable

Why NetSuite Works Here

In this scenario, NetSuite can:

1. Act as the system of record for revenue and accruals
2. Provide clean audit trails and SOX-aligned controls
3. Support GTN via:
4. Custom accrual logic
5. Contract and pricing masters
6. Chargeback validation workflows
7. Period-end true-up journal entries

The key is that GTN is engineered as a process, not expected to be “native.”

3. NetSuite’s Role When It Is a Good Fit

When NetSuite is a good fit, it typically plays three critical roles:

1. Financial System of Record

1. Books gross revenue
2. Holds GTN accrual liabilities
3. Posts adjustments and true-ups
4. Supports multi-book (GAAP vs management)

2. GTN Accrual & Control Framework

1. Accruals calculated at shipment or invoicing
2. Assumptions stored and version-controlled
3. Clear linkage between sales, accruals, and settlements

3. Audit & Compliance Backbone

1. Documented GTN methodology
2. Repeatable month-end process
3. Strong traceability from estimate → actual

In this model, NetSuite is not trying to outsmart GTN. It is enforcing discipline, consistency, and financial integrity.

4. When NetSuite Is Not As Good A Fit As The GTN Engine

NetSuite alone becomes insufficient when GTN complexity outpaces percentage-based estimation.

Typical Company Profile

1. Mid-to-large generics manufacturer
2. Large SKU count with frequent launches
3. Heavy Medicaid, Medicare Part D, and 340B exposure
4. Multiple GPO, PBM, and government contracts
5. High chargeback claim volumes
6. Aggressive pricing changes

GTN Characteristics

1. Accrual accuracy materially impacts earnings
2. Chargebacks are contract-specific and claim-driven
3. Government programs require statutory logic
4. Forecasting and analytics are critical
5. Auditors expect system-level controls

In this environment, GTN is no longer just accounting ; it is a core commercial operation.

5. NetSuite’s Role When It Is Not the GTN Engine

Even when NetSuite is not the GTN calculation engine, it still plays a central role.

NetSuite as the Financial Anchor

1. Remains the general ledger and AR/AP system
2. Receives summarized GTN results from a GTN platform
3. Maintains statutory and management reporting

GTN System as the Calculation Engine

1. Specialized GTN platforms handle:
2. Chargeback adjudication
3. Medicaid and 340B logic
4. Contract price validation
5. Forecasting and scenario modeling

Integration Model

1. GTN system calculates detailed deductions
2. NetSuite preserves audit traceability
3. NetSuite posts:
4. Accruals
5. Settlements
6. Adjustments

In this model, NetSuite governs the money, while the GTN platform governs the math.

6. Common Mistakes to Avoid

1. Expecting NetSuite to be a plug-and-play GTN solution
2. Overbuilding GTN logic too early
3. Underestimating audit expectations
4. Treating GTN as a one-time implementation
5. Letting GTN calculations live outside controlled systems (spreadsheets)

7. Practical Decision Framework

8. What Companies need to be aware of

1. NetSuite is a strong foundation for Gross-to-Net ; not a silver bullet
2. GTN success depends on controls, assumptions, and audit defensibility
3. The smartest approach is phased: NetSuite first, specialized GTN tooling later
4. Archer’s role is to design, implement, and govern this evolution end to end

The smartest approach is often phased: start with NetSuite-led GTN, then integrate a specialized GTN platform as scale and exposure demand it.

9. Archer Insights Point of View and Positioning

Archer Insights approaches Gross-to-Net not as a software configuration exercise, but as a commercial-to-finance operating model problem.

Most GTN failures do not come from the math. They come from:

1. Poor contract structure
2. Weak linkage between commercial strategy and finance
3. Accrual logic that auditors cannot follow
4. Over-engineering too early or under-engineering too late

Archer’s positioning is intentionally pragmatic:

1. NetSuite first, but not NetSuite forever
2. Design GTN as a scalable control framework
3. De-risk future GTN platform adoption

Archer’s GTN Philosophy

Archer believes:

1. NetSuite should always be the financial system of record
2. GTN logic should mature in phases
3. Specialized GTN platforms should be added only when economic and audit risk justify it

This avoids the two most common mistakes in generics:

1. Implementing a heavy GTN platform too early
2. Letting GTN live in spreadsheets for too long

Archer’s Phased GTN Roadmap

Phase 1: NetSuite-Led GTN Foundation

1. GTN accrual framework inside NetSuite
2. Contract and pricing master design
3. Chargeback intake and validation workflows
4. SOX- and audit-ready documentation

Phase 2: Hybrid GTN Model

1. Introduce Model N or Revitas for calculation complexity (Archer does not sell this)
2. NetSuite remains the GL and control layer
3. Clear ownership split between systems

Phase 3: Scaled GTN Operations

1. GTN platform becomes calculation engine
2. NetSuite becomes the financial authority
3. Archer governs integration, controls, and audit alignment

10. NetSuite vs Model N / Revitas Responsibility Split

The table below reflects Archer’s recommended system-of-responsibility model, not marketing claims.

11. How Archer Typically Positions This with Clients

We position the conversation around:

1. Risk (earnings volatility, audit exposure)
2. Timing (when complexity actually hits)
3. Control (who owns the numbers)

Our typical guidance:

1. If GTN errors are annoying, NetSuite-led GTN is sufficient
2. If GTN errors are material, a GTN platform is justified
3. In all cases, NetSuite remains the financial backbone

This keeps CFOs, auditors, and commercial leaders aligned, and avoids rework.

12. Key Implementation Takeaways

1. NetSuite is an excellent foundation for Gross-to-Net
2. It should never be treated as a silver bullet
3. The winning strategy is phased, intentional, and audit-first

Archer’s role is to:

1. Design the GTN operating model
2. Implement NetSuite to support it
3. Integrate GTN platforms when and only when they are justified

Appendix: Questions Auditors Will Ask (and How Archer Designs for Them)

1. How are GTN accrual percentages determined?

Expectation: Historical data, documented methodology, periodic review.

2. How do you validate chargebacks against contracts?

Expectation: System-based validation, not spreadsheets.

3. How do you ensure completeness of GTN liabilities?

Expectation: Controls tying shipments to accruals.

4. How are estimates trued up to actuals?

Expectation: Consistent, period-based true-up process.

5. Who owns GTN assumptions and approvals?

Expectation: Clear ownership and version control.

6. What happens when contracts or pricing change mid-period?

Expectation: Controlled updates with documented impact.

7. How does the GTN system integrate with the GL?

Expectation: Clear system-of-record definition.

8. Can you trace a dollar from gross sale to net revenue?

Expectation: End-to-end traceability.

9. How do you prevent management override of GTN estimates?

Expectation: Controls, approvals, and audit logs.

10. How does your GTN approach scale as volume grows?

Expectation: Roadmap, not heroics.