Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / SaaS Revenue Recognition Shifts in 2026
Transcript
- Lucas: So here is a question that usually comes up after earnings season, but lately it has been popping up in quiet conversations throughout the year: why does one company report twenty percent growth while another with similar product usage looks like it is flatlining? The answer often isn't about sales. It is about how they count their money. Luna: You mean revenue recognition? Because I have noticed some of these mid-cap software stocks looking weirdly stable even when their support tickets are spiking. Lucas: Exactly. We talk a lot about net dollar retention and churn, but we rarely discuss the mechanics of when that revenue actually hits the books. Today I want to dig into the shift toward smoothed revenue recognition models. Specifically, how some SaaS firms are moving away from recognizing revenue at the moment of consumption or spike, and instead locking it into predictable monthly buckets regardless of actual usage. Luna: That sounds like a way to hide volatility. Is that legal? Lucas: It is legal under current accounting standards, provided the contract terms allow it. But it changes the narrative completely. When you recognize revenue based on usage spikes, your financial statements look volatile. They go up and down with customer behavior. By smoothing that out, management can present a much cleaner growth curve to investors who are currently obsessed with predictability over raw volume. Luna: But doesn't that distort the truth? If a customer uses the platform ten times more in December than in January, shouldn't the revenue reflect that? Lucas: Ideally yes, but in practice, many B2B contracts are structured around annual commitments rather than pure pay as you go models. Even if the underlying technology tracks usage, the billing agreement might be a flat fee for unlimited access. The shift we are seeing is less about changing the contract and more about changing the internal accounting policy to align with those flat fees, effectively decoupling operational intensity from financial reporting. Luna: So you are saying they are prioritizing stability over accuracy? Lucas: I am saying they are prioritizing valuation stability. In this market environment, investors are paying a premium for predictable cash flows. A jagged revenue line suggests risk. A smooth line suggests a machine. And right now, machines trade at higher multiples than explorers. Luna: It feels like we are trading transparency for stock price comfort. Lucas: There is definitely an element of that. But let us look at the practical side. Consider a company that provides data analytics tools. Their customers tend to run heavy reports at the end of every quarter. If you recognized revenue based on compute hours, their third quarter would look massive and the other three quarters would look thin. That makes year-over-year comparisons messy. Luna: Right, because comparing March to September becomes meaningless if the usage patterns are seasonal. Lucas: Precisely. So by smoothing that revenue across twelve months, they make the quarterly comparisons valid again. It allows them to show consistent growth trajectory rather than seasonal noise. For a public company trying to justify a high price to earnings ratio, that consistency is worth a lot. Luna: But what happens when the usage actually drops? Does the smoothing mask a real decline in demand? Lucas: That is the danger. If usage drops permanently, the smoothed model delays the pain. You keep recognizing that same monthly amount even though the customer is barely logging in. It gives management time to fix the product or find new upsell opportunities before the financial statement reflects the loss. It buys them runway. Luna: Runway is exactly what everyone is chasing right now. Cash preservation is key. Lucas: It is. And this brings us to a specific case study that illustrates this perfectly. There is a mid-sized enterprise security firm that switched its recognition model last year. They moved from a usage-based trigger to a straight monthly amortization of their annual contracts. The result was immediate. Their reported revenue volatility dropped by forty percent. Investors reacted positively because the forward guidance became much easier to model. Luna: Did their actual cash collection change? Lucas: No. The cash came in exactly the same way. It was purely an accounting classification change. This highlights why you cannot just look at the top-line number. You have to look at the notes in the financial filing to see how they are defining that revenue. If they switch methods, the comparison to previous years breaks unless you adjust for it yourself. Luna: That seems like a trap for retail investors who just scan the headline earnings. Lucas: It is. And it gets more interesting when you consider mixed models. Some companies are now offering hybrid contracts where part of the fee is fixed and part is variable. Recognizing that split correctly requires sophisticated systems. Many smaller SaaS firms don't have those systems yet, which forces them to stick to simpler, sometimes less accurate, methods. Luna: So there is a technology barrier to doing this right too? Lucas: Absolutely. Your CRM needs to talk to your billing engine, which needs to talk to your general ledger. If those systems are siloed, you cannot implement complex recognition rules without hiring expensive consultants or buying expensive software. That is another reason why larger players are adopting these smoother models—they have the infrastructure to manage the complexity. Luna: Which reinforces the moat for big tech. Small guys get stuck with volatile numbers. Lucas: Exactly. It creates a feedback loop where size breeds accounting efficiency, which breeds better perceived performance, which attracts more capital. It is not fair, but it is efficient in the short term. Luna: Let me pause here for a second. If these conversations are useful for what you're building or running, remember that listener support keeps this show independent and ad-free. We deliberately don't run ads on these. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Thanks for keeping this space clean. Lucas: Appreciate it. Now, back to the accounting. Another angle to consider is the impact on taxes. Different jurisdictions have different rules for when revenue is taxable versus when it is recognized for book purposes. Luna: Does that create a lag in tax payments? Lucas: Sometimes. If you recognize revenue slowly for book purposes but collect cash upfront, you might have a timing difference. This creates deferred tax liabilities. Companies have to track those carefully. It adds another layer of complexity to the finance team's workload. Luna: It sounds like a headache for CFOs. Lucas: It is. But they view it as a necessary cost of doing business in the public markets. Private companies don't face this pressure. They can recognize revenue whenever they want, really. But once you go public, the scrutiny increases, and the demand for comparability drives these standardization efforts. Luna: So we are seeing a homogenization of financial language across the industry. Lucas: We are. And that makes it harder for unique business models to stand out. If everyone is smoothing their revenue, the outliers look strange. A company that genuinely relies on volatile usage might be penalized by the market simply because their numbers don't fit the new norm. Luna: Is there any pushback against this trend? Lucas: Some analysts are pushing for more granularity. They want to see the usage metrics alongside the smoothed revenue. They argue that if you smooth the revenue, you must disclose the underlying usage volume separately so investors can check the quality of that revenue. It is a call for more transparency, not less. Luna: That makes sense. Give me the raw data and I will trust your smoothing. Lucas: Exactly. Disclosure is the key. If a company hides the usage drop behind a smooth revenue line, that is fraud. If they disclose both, that is good governance. The line is fine, but it exists. Luna: How common is it for companies to fail that test? Lucas: Unfortunately, not uncommon. We have seen several high-profile cases where companies were accused of misleading investors by emphasizing the smooth revenue while ignoring the collapsing usage. These cases usually end in lawsuits and restatements. The restatement process is painful because it destroys credibility. Luna: Restatements are the nuclear option in finance. Lucas: They are. No CEO wants to announce a restatement. It signals that the previous numbers were wrong. So most companies err on the side of caution. They might even over-disclose usage metrics to protect themselves, which clutters the financial report but ensures safety. Luna: Clutter is better than lies, I suppose. Lucas: In the long run, yes. Short-term, clutter confuses people. But over a decade, clarity wins. The market eventually punishes opacity. It just takes time. Luna: Do you think this trend will reverse as interest rates stabilize? Lucas: I doubt it. The demand for predictability is structural now. Investors have learned hard lessons during the downturns. They prefer boring, steady growth to exciting, volatile growth. That preference is baked into the current valuation models. Luna: So SaaS companies are trapped in this smoothing cycle whether they like it or not. Lucas: Trapped is a strong word. Influenced is better. But yes, the incentive structure pushes them that way. Unless the market suddenly rewards volatility again, which seems unlikely given the current economic climate, we will probably see more of this. Luna: It reminds me of how housing prices are reported. Smoothed indices hide the daily chaos. Lucas: A great analogy. Indices are designed to show trends, not daily noise. Revenue recognition is becoming the index of corporate health, even if the underlying asset is noisy. Luna: Are there any emerging technologies that might complicate this further? Lucas: Blockchain and smart contracts could introduce real-time revenue triggers. Imagine a contract that automatically pays out every time a transaction occurs. That would force real-time recognition. It would kill the smoothing model entirely. But we are probably five to ten years away from that being mainstream in enterprise software. Luna: Five to ten years. Plenty of time for things to change. Lucas: Plenty of time. Until then, we are stuck with the spreadsheets and the smoothing. But knowing how the sausage is made helps you taste it better. Luna: I will keep my eyes on the footnotes next time I read an earnings report. Lucas: Good idea. The footnotes are where the real story lives. Most people skip them, but that is where the accounting decisions are hidden. Luna: It is funny how much power lies in a footnote. Lucas: Power and risk. They usually come together. What do you think will be the next big accounting controversy in SaaS? Luna: I bet it will be around AI compute costs. How do you allocate cloud spend when the model is trained on shared infrastructure? Lucas: That is a tough one. Allocation methodologies are always contentious. But I think you are onto something. As AI becomes central to SaaS offerings, the cost structure will change, and so will the revenue recognition challenges. Luna: Another layer of complexity added to an already complex system. Lucas: Always. But complexity is where the edge comes from. If you understand it, you win. If you ignore it, you lose. Luna: So the lesson is to read the fine print? Lucas: The lesson is to question the simplicity. If a number looks too smooth, ask who smoothed it and why. Luna: And how much truth got left behind. Lucas: Usually some. The question is whether it matters enough to change your decision. Luna: For most of us, it probably doesn't. But for the ones making the calls, it is everything. Lucas: True. And maybe that is the real takeaway. Transparency isn't just ethical; it is strategic. Luna: Strategic transparency. I like that phrase. Lucas: Stick with it. It might just become the new buzzword. Luna: Or the new standard. Lucas: Let us hope for the latter. I would rather live in a world where the numbers match the reality. Luna: Me too. Until next time, keep checking the footnotes. Lucas: Will do. Thanks for listening.