Every PE operator knows the feeling. The monthly report lands. ARR is up. The CRO is confident. And somewhere in the back of your mind a question forms that nobody in the room seems to be asking: is this number actually right?
Why Your Portfolio Company's ARR Number Is Harder to Trust Than You Think
Not wrong because of fraud. Not wrong because of bad intentions. Wrong because the systems that produce it weren't built to keep pace with how modern SaaS companies actually sell — multi-year commitments, mid-contract changes, bundled pricing, expanding customers. The most common of these, and the most quietly damaging, are ramps and swaps.
Ask the CRO and CFO to explain the delta between bookings and recognized revenue and watch what happens. Ask how swap credits are calculated. Ask whether ramp deals are configured for even recognition in NetSuite. The answers to those three questions will tell you almost everything you need to know about whether this business is built to scale its revenue operations — or whether it's one audit away from finding out it isn't.
What Are Ramps and Swaps, and Why Do They Distort ARR?
A ramp is a multi-year deal with pre-negotiated price increases each year. A swap is a mid-contract product exchange where a customer applies remaining credit toward something different. Both are legitimate and common. The problem isn't the structures themselves — it's what happens to the numbers after the deal closes.
In Salesforce, the booking reflects what was sold on the day it was signed. But in NetSuite, two things happen that change the financial picture entirely. First, revenue allocation: when a deal bundles a software license with professional services, NetSuite distributes value across each component based on standalone selling price. Second, recognition timing: a ramp deal can't be recognized as billed — the total contract value has to be spread evenly across the term under ASC 606.
What's visible in Salesforce and what finance is actually recognizing in NetSuite are separated by seven records. That's where the ARR story starts to drift.
Where Does the Margin Go When Swaps Go Wrong?
When a customer requests a swap, the account manager calculates the credit based on what they can see: the original invoiced amount, prorated for the remaining term. But after allocation, the actual remaining recognized value might be significantly less. The rep doesn't know this because the post-allocation position never made it back to Salesforce.
Across PE-backed SaaS companies, it's common to see 1 to 3 percent of ARR effectively donated each year — purely because swap credits are based on invoice math instead of recognized revenue.
Why Don't Portfolio Companies Catch This Earlier?
Because the signal is diffuse and delayed. There's no moment where the system throws an error or flags a discrepancy. The swap closes. The invoice goes out. Finance processes it weeks later, notices the numbers don't reconcile, makes a journal entry adjustment, and moves on.
The organizational dynamic makes it worse. Sales and finance operate in separate systems with separate priorities. The revenue position that matters for swap credits lives in NetSuite. The people who need it are in Salesforce. Bridging that gap requires a manual handoff that doesn't scale.
What Should PE Operators Be Asking Their Portfolio Companies?
- Can your account managers see the remaining recognized revenue position before they build a swap quote? If no, they're quoting from invoice math.
- Do your bookings, billings, and recognized revenue figures reconcile in a single system?
- How are mid-contract changes processed? If the answer involves someone calling finance, that's a workaround, not a process.
- How are ramp deals structured in NetSuite? If multi-year step-up pricing isn't configured for even recognition, you may have an ASC 606 compliance exposure.
How Does Continuous Fix the Revenue Operations Gap?
Continuous operates at the architectural boundary between Salesforce and NetSuite, tracking the full lifecycle of a deal from opportunity through allocation, recognition, and journal entry. For swaps, the account manager sees the actual remaining recognized value before they build the quote. For ramps, Continuous structures recognition correctly from the start and recalculates automatically when a contract changes.
For PE operators, the result is a portfolio company whose revenue reporting can be trusted — not because someone is manually checking it, but because the system closes the seven-record gap automatically.
Frequently Asked Questions
Why is ARR an unreliable metric at many mid-market SaaS companies?
ARR at most mid-market SaaS companies is based on bookings recorded in Salesforce at close. But bookings don't account for post-close revenue allocation, recognition timing under ASC 606, or the impact of mid-contract changes like swaps and amendments.
What is the financial impact of ramps and swaps being handled manually?
The most direct impact is margin leakage from swap credits calculated from invoice amounts rather than post-allocation recognized value. Across PE-backed SaaS, it's common to see 1–3% of ARR effectively donated this way each year.
How do ramps affect revenue recognition under ASC 606?
A ramp deal must be recognized evenly across the full contract term, because the same product is being delivered throughout. In year one, billing $20,000 while recognizing $25,000 creates an unbilled receivable. If ramp deals aren't configured correctly in NetSuite, RPO will be misstated.