5 Reasons Your SaaS Gross Margin Looks Better Than It Is

5 Reasons Your SaaS Gross Margin Looks Better Than It Is

A clean 85% gross margin is the number that gets you a meeting. It's also the number most early SaaS books get wrong.

Here's the uncomfortable part: a SaaS gross margin overstated by sloppy expense coding doesn't just flatter your deck. It misleads you. You price wrong, you forecast wrong, and the first sharp investor who reads your financials backs out of diligence quietly.

The good news is that an overstated margin is almost always a categorization problem, not a real-economics problem. The cash already left your account. Someone just parked it in the wrong row. Find the five usual suspects below and your "true" gross margin shows up — usually 10 to 20 points lower than the headline, which is exactly the number you should be running the business on.

Reason 1: SaaS gross margin overstated by a hosting bill hiding in operating expenses

This is the big one. Your AWS, Google Cloud, or Azure invoice is the cost of delivering the product your customer pays for. Under cost-accounting logic, the cost of delivering revenue belongs in cost of revenue — your COGS — not down in operating expenses next to rent and software subscriptions.

When founders lump infrastructure into "OpEx" because that's where the bill landed in their accounting software, gross margin inflates. On a company spending 15% of revenue on hosting, moving that line where it belongs can drop reported gross margin by roughly 15 points overnight.

It's not a loss. It's the truth catching up. ASC 350-40 governs how SaaS hosting and internally-developed software is treated for accounting, and it exists precisely because "where the invoice landed" is not the same as "where the cost belongs."

Reason 2: Support and onboarding salaries that quietly live under G&A

Here's the rule of thumb that trips up generalist bookkeepers: if a salary is required to deliver the service the customer is paying for right now, it usually belongs in COGS.

Customer support that keeps existing accounts running and onboarding teams that get a new customer live are both delivery costs. A SaaS COGS what-to-include checklist almost always puts the fully-loaded cost of those people — salary, benefits, payroll tax — in cost of revenue.

A generalist parks all headcount under G&A because that's tidy. The result is a gross margin that looks like a pure-software business when you're actually running a high-touch one. Sales and marketing salaries stay in OpEx — those win future revenue, they don't deliver current revenue. The line matters.

Reason 3: Payment processing fees nobody bothered to reclassify

Stripe, Adyen, and the rest take their cut before the money ever hits your bank. Two to three percent of every dollar of revenue, gone, every month.

Because the fee is netted out automatically, it's easy to never see it as a cost at all — or to dump it in "bank charges" under OpEx. Either way, your gross margin reads a couple points too high.

For a SaaS business doing $4M in revenue, processing fees at 2.5% are $100,000 a year of cost of revenue that frequently never gets coded as such. That's a real two-and-a-half-point swing in the number your board stares at every quarter.

Reason 4: Capitalized software development that never gets amortized back

This one is subtle and it's where good intentions go sideways. Under ASC 350-40, qualifying software-development costs for the product you sell can be capitalized — moved off the income statement and onto the balance sheet as an asset, instead of expensed immediately.

So far so good. The problem is what happens next, which is often nothing. Once that asset is in service, it's supposed to be amortized over its useful life, and for a product you're selling, that amortization is a cost of delivering the product.

When the capitalized cost sits on the balance sheet and the matching amortization never flows through, current expenses look artificially low and margin looks artificially high. You've turned a real cost of building your product into an asset that quietly never depreciates on paper. Auditors notice. So do diligence teams.

Reason 5: Annual prepaid plans you booked all at once

A customer pays $24,000 upfront for an annual plan in January. The cash is fantastic. The accounting is a trap if you recognize all $24,000 as revenue the day the invoice clears.

Under ASC 606, subscription revenue is recognized ratably as you deliver the service — in this case $2,000 per month over the twelve-month term, not $24,000 on day one. Recognize it at invoice and you pull a full year of revenue into a single month, which means you also pull future margin into the present.

Get this wrong and your gross margin in the signing month looks heroic, then craters in the months after as the costs to serve that customer keep landing with no matching revenue. ASC 606 isn't bureaucratic busywork here. Matching revenue to the period you actually earn it is the only way the margin line tells you anything true.

When a SaaS gross margin overstated by miscoding finally tells the truth

Add these five up and the pattern is the same every time: cash already spent, just filed in the wrong drawer. Fixing them doesn't make your business worse. It makes your decisions better.

A real SaaS gross margin tells you how much each new dollar of revenue actually contributes after the cost to deliver it. That's the number that determines whether you can afford to spend on growth, what you should charge, and how long your runway really is. An inflated one tells you a comforting story right up until it doesn't.

The reason these errors persist isn't that founders are careless. It's that a general-purpose bookkeeper has never had to learn where a hosting bill belongs or why ASC 606 matters for an annual plan. Those rules are specific to SaaS, and so is the person who should be applying them.

Find a bookkeeper who actually knows where your hosting bill goes

If reading those five reasons made you want to open your own financials and check, that's the right instinct — and it's a sign your books deserve a specialist's eye.

The SaaS Bookkeeper works specifically with software businesses, which means COGS composition, ASC 606 revenue recognition, and hosting-cost accounting are the daily job, not an edge case they look up. The categorization mistakes above are exactly the ones a SaaS-focused bookkeeper is built to catch before they reach your board deck or a diligence room.

Read The SaaS Bookkeeper's verified reviews on Sam's List, then book an intro call and ask them one question: "What does my gross margin look like once the hosting bill is in the right place?" If the answer surprises you, you found the right problem — and the right person to fix it.