Strip Tax from Every Revenue Metric. See What You Actually Earned.

Why Tax Distorts SaaS Metrics More Than Founders Expect

When you add Stripe Tax, enable VAT collection for EU customers, or start collecting US state sales tax, every revenue number in Stripe grows — even if your actual product revenue didn't change by a cent. That gap compounds fast. A SaaS business collecting 20% VAT from UK and EU customers and 6–10% sales tax from US states can see gross Stripe receipts run 12–18% above true net revenue. That is not a rounding error; it is a material difference in every metric you use to make decisions.

The problem is not that you are collecting tax — you are supposed to. The problem is that Stripe's default reporting surfaces total charge amounts. Without a dedicated tax-exclusion layer, every metric you derive from that data — MRR, ARR, LTV, average revenue per user — is inflated by the tax component. You are measuring a number you will never keep.

Dnoise reads directly from the raw Stripe event stream and identifies tax line items at the charge level, before any metric is calculated. Every number in the product reflects what your business actually earned. You can see exactly which Stripe events contributed to any figure — click any metric and trace it to the underlying charge and its tax breakdown. Learn more about how this works on the How Dnoise Works page.

What Stripe Reports vs. What You Actually Keep

Stripe's dashboard shows you the charge amount — the total the customer paid. That total includes your product price plus any tax Stripe collected on your behalf. Stripe does report tax amounts separately in its Tax reports and invoice line items, but those figures live in a different corner of the dashboard and do not flow into Stripe's revenue charts or your payouts metric automatically.

The practical result: founders reading the Stripe revenue dashboard are looking at a number that includes pass-through tax liability. That money is not revenue. It is collected on behalf of a tax authority and will be remitted. Treating it as revenue overstates MRR, understates churn rate (because the tax-inflated base makes losses look smaller proportionally), and produces an LTV that will not survive a financial audit or investor data room.

Dnoise calculates net revenue by reading the tax_amount field on every Stripe charge and invoice, subtracting it before any metric is aggregated. The formula is transparent and inspectable — no normalization layer, no proprietary algorithm deciding what counts. You can verify the math yourself against any Stripe charge. Browse the full formula reference in the Metrics Library.

Tax Across Jurisdictions: VAT, GST, and US Sales Tax

SaaS businesses selling internationally collect different tax types depending on customer location: VAT in the EU and UK (typically 20–25%), GST in Australia and Canada (10% and 5–15% respectively), and sales tax across US states that have enacted economic nexus laws since South Dakota v. Wayfair (2018). Stripe Tax handles the collection and rate calculation. Dnoise handles the exclusion from your metrics.

This matters beyond MRR accuracy. If your customer base is shifting toward higher-VAT regions — say, growing faster in Germany and the Netherlands than in the US — your gross Stripe receipts can grow even in months where your net revenue is flat or declining. Without tax-excluded metrics, that regional mix shift is invisible. You see revenue growing; the actual business is not.

Dnoise surfaces net revenue by region so you can spot exactly this pattern. If EU revenue is growing as a share of total receipts, you will also see whether net revenue is keeping pace or whether a higher average tax rate is inflating the gross number. This connects directly to understanding your true gross revenue retention — a metric that only means something if tax is stripped out of the base before you calculate it.

How Tax Inflation Quietly Skews GRR and NRR

Gross Revenue Retention and Net Revenue Retention are the two metrics investors scrutinize most in a SaaS data room. Both are calculated against a cohort's starting revenue base. If that base includes tax, both ratios are suppressed in expansion months (expansions are smaller relative to an inflated denominator) and flattering in contraction months (losses look smaller against the same inflated base). The error is not random; it is systematically misleading.

A concrete example: suppose your January MRR base for a cohort is $50,000 gross — but $6,000 of that is VAT collected from EU customers. Your true net base is $44,000. If that cohort contracts by $4,000 net in February, your true GRR is 90.9%. Calculated on the gross base, it looks like 92%. That 1.1-point difference in GRR compounds across twelve months into a materially different picture of retention. For a bootstrapped business making pricing and investment decisions on that number, the distortion matters.

NRR above 110% is generally considered top-quartile for B2B SaaS — see the 2026 SaaS churn benchmarks for current reference points. Calculating NRR on tax-inflated revenue can make a 104% business appear to be a 107% business. That is the kind of gap that changes how you read your own health and what investors see in your data.

Dnoise calculates GRR and NRR on net revenue from day one. The numbers are smaller than what a gross-revenue calculation would show — and they are accurate. You can click any cohort figure and see the exact Stripe events that make up the starting base and any expansion or contraction events, each with tax already excluded.

What Dnoise Shows You

Every metric in Dnoise is calculated on net revenue — the amount your business keeps after tax is stripped from each charge. Here is what that looks like in practice:

• Net MRR and ARR — calculated with tax excluded at the charge level, so the number reflects product revenue only. No manual export, no spreadsheet adjustment needed.
• Tax as a percentage of gross revenue — see the share of each period's Stripe receipts that was tax, broken down by currency and region. Spot when a shift in your customer geography is affecting your effective take rate.
• Cohort GRR and NRR on net revenue — retention ratios calculated on the correct base. Comparable to benchmarks that also use net revenue as the denominator.
• Per-customer tax visibility — click any customer's revenue figure and see the tax amount on each of their charges. Useful when a single large customer's tax situation is unusual.
• Traceable to the Stripe event — every net revenue figure links to the underlying charge and shows you the tax_amount that was excluded. No black box between your Stripe data and the number on screen.

This also interacts with other parts of the business you may be tracking. If failed payments are distorting your recovery picture, the Stripe failed payments guide covers how to think about gross vs. net amounts in a dunning context. And if you are evaluating payback period on customer acquisition, using net revenue rather than gross in your LTV calculation changes the CAC payback period materially — often adding two to four months to the true figure.

FAQ