SaaS Pricing for Delaware LLCs: VAT & Tax

EU VAT (OSS) for EU consumers

B2C SaaS sales to EU consumers trigger VAT collection. Non-EU sellers register through One Stop Shop (OSS) in one EU country (typically Ireland) and remit VAT to all EU countries via single filing.

Rates: 17-27% depending on consumer's country. Pricing must include or display VAT correctly.

US sales tax: state-by-state

SaaS sales-tax treatment varies by US state. Some states tax SaaS (Texas, New York, Washington); some do not (California for most B2B). Economic-nexus thresholds typically $100K or 200 transactions.

Use TaxJar, Avalara, or similar service for automated multi-state compliance.

MoR vs direct Stripe

Direct Stripe (2.9% + $0.30 per transaction): you handle VAT, sales tax, and global compliance. Fits high-volume B2B SaaS with dedicated tax/finance team.

MoR services (Paddle 5-9%, Lemon Squeezy 5-7%): platform handles VAT, sales tax, chargebacks, compliance. Fits B2C SaaS, indie devs, and small teams.

Why pricing strategy and entity choice are connected

Most founders treat SaaS pricing as a marketing decision and entity formation as a legal one, but for a non-resident running a Delaware LLC the two are bound together.

The number you put on your pricing page determines how much tax you collect on behalf of foreign governments, how much you remit, and how much actually lands in your Mercury or Wise account at the end of the month.

If you set a flat price without thinking about whether VAT is inclusive or added on top, you can quietly lose 17% to 27% of European consumer revenue because the tax was baked into a price you advertised as the full amount.

A Delaware LLC formed for $110 in state fees gives you a clean US entity that customers and processors recognize, but the entity itself does not shield you from consumption taxes in the countries where your customers live.

The LLC is the legal seller, so VAT and local digital-services taxes attach to its sales regardless of where you personally sit.

That means your pricing model has to assume the role your home country tax authority would normally play, because no one else is collecting on your behalf unless you use a merchant of record.

Thinking about pricing and structure together early saves painful repricing later.

A founder who launches at $29 per month inclusive of all taxes and then discovers EU VAT obligations has to either eat the margin or raise prices on existing subscribers, both of which hurt retention.

Deciding upfront whether your headline price is net or gross, and which currencies you quote in, is part of the same planning exercise as forming the entity and opening the bank account.

Net pricing versus gross pricing on your checkout page

The single most consequential pricing decision for a non-resident SaaS seller is whether your listed price is the amount the customer pays before tax (net) or after tax (gross).

For B2B SaaS sold mostly to companies, net pricing is conventional because business buyers expect tax to be added at checkout and can usually reclaim it.

A buyer in Germany seeing $99 net understands VAT will be added and does not flinch.

For B2C SaaS sold to individual consumers, gross pricing is often expected because consumers compare the final out-of-pocket number, and a surprise tax line at checkout increases cart abandonment.

The tension is that a non-resident selling to many countries cannot show one gross price that is correct everywhere, because VAT rates differ from 17% in Luxembourg to 27% in Hungary.

If you advertise a single inclusive price of $20, your net revenue per sale silently varies by country, and your margin in high-rate countries shrinks.

Some founders solve this with location-aware pricing that displays a country-specific gross price, while others quote net and add tax at the final step.

Each approach is defensible, but you must choose deliberately rather than discover the consequences in your first quarterly reconciliation.

Whichever model you pick, document it in your records and reflect it in the figures you report on Form 5472 and the pro forma 1120.

The tax you collect and remit is not your income, so keeping collected VAT separate from revenue in your bookkeeping prevents you from overstating profit and from mixing other people's money into your operating balance.

Currency choice and its hidden margin effects

Quoting prices in US dollars is the default for a Delaware LLC because your bank account and most processors settle in dollars, but it shifts foreign-exchange risk onto your customers and can suppress conversion in price-sensitive markets.

A buyer in Brazil or Nigeria seeing a dollar price has to absorb both the exchange rate and any card-network conversion fee their bank charges, which makes your product feel more expensive than the sticker suggests.

Local-currency pricing improves conversion but introduces FX exposure for you, since the dollars you ultimately bank fluctuate with the rate at settlement.

Banks like Wise and Payoneer matter here because they let a Delaware LLC hold balances in several currencies and convert at close to the mid-market rate.

If you price in euros and collect euros, holding them in a Wise multi-currency balance until the rate is favorable beats forced conversion at a card processor's marked-up rate, which can run 2% or more above mid-market.

For a subscription business with thousands of small recurring charges, that spread compounds into real money over a year.

Be careful not to let multi-currency pricing turn into a reconciliation nightmare. Every currency you accept becomes a line you must track for revenue recognition and for your annual US filing.

Many non-resident founders settle on dollars plus one or two strategic local currencies for their largest markets, rather than offering a dozen currencies that complicate bookkeeping without proportional sales gains.

Trials, freemium, and the timing of tax obligations

Free trials and freemium tiers feel tax-neutral because no money changes hands, but they shape when your tax obligations begin.

A VAT obligation in the EU attaches at the point of a taxable supply for consideration, so a genuinely free trial generally does not trigger VAT until the trial converts to a paid subscription.

The moment the first charge lands, however, you are making a taxable B2C supply and the OSS registration discussed in the original post becomes relevant.

Founders sometimes assume their first few paid conversions are too small to matter, but the obligation exists from the first euro of consumer revenue.

Freemium complicates this further because a free tier alongside paid tiers means your tax footprint grows only with the paid cohort, yet your user base and support burden grow with everyone.

From a pricing standpoint, the free tier is a customer-acquisition cost rather than a tax event, so model it as marketing spend.

The taxable events are the upgrades, and your checkout flow needs to apply the correct VAT or sales tax at the upgrade moment, not at signup.

If you offer a paid trial at a reduced rate, such as $1 for the first month, remember that even a nominal charge is a taxable supply.

Many processors and merchant-of-record platforms handle this automatically, but if you run direct Stripe you are responsible for collecting the right tax on that $1 in each jurisdiction.

Cheap introductory pricing does not exempt you from collection duties.

Annual versus monthly billing and tax remittance cadence

Offering annual plans alongside monthly ones is a standard SaaS lever to improve cash flow and reduce churn, but it interacts with your tax remittance schedule.

When a customer pays for twelve months upfront, you collect the full year of VAT or sales tax in that single transaction even though you recognize the revenue over twelve months.

The collected tax is due to the relevant authority on its normal cycle, which for EU OSS is quarterly, so you may be remitting tax on revenue you have not yet earned in an accounting sense.

This is fine as long as you keep the collected tax segregated and do not spend it as operating cash.

For a non-resident founder managing the business from abroad, the discipline of separating collected tax becomes more important with annual billing because the sums are larger per transaction.

A single annual B2C subscription in a 23% VAT country bundles nearly a quarter of the headline price as tax you are merely holding.

Treating that as revenue inflates your sense of how the business is doing and risks a shortfall when the quarterly OSS payment comes due.

Annual billing also smooths your relationship with US federal filing.

Because the Delaware LLC reports its activity annually on Form 5472 and the pro forma 1120, having predictable annual subscription cohorts makes year-end reconciliation cleaner.

Just remember that the $25,000 penalty for a missed or incorrect 5472 applies regardless of billing cadence, so neither monthly nor annual pricing changes the underlying compliance deadline of April 15.

Per-seat, usage-based, and tiered models for cross-border sellers

The structure of your pricing model influences how complex your tax compliance becomes.

Per-seat pricing is straightforward because each invoice is a clear supply with a known value, which makes VAT and sales-tax calculation predictable.

Usage-based pricing, where customers pay for metered consumption such as API calls or storage, produces variable invoices that still need correct tax applied each cycle, and the variability means you cannot pre-compute tax in advance.

Your billing system must calculate the right rate at each billing event based on the customer's location at that moment.

Tiered pricing with feature gates is common for non-resident founders because it lets a single product serve hobbyists and enterprises.

From a tax perspective the tiers are just different prices for the same kind of digital supply, so the VAT treatment is identical across tiers, but the absolute tax amounts scale with the tier.

A founder should confirm that the higher enterprise tiers, which may be sold B2B, are handled with reverse-charge mechanics in the EU rather than charged consumer VAT, because business buyers with a valid VAT number self-account for the tax.

Whatever model you choose, the location-determination logic is the part that most often goes wrong.

Consumption taxes hinge on where the customer is, and digital services rules in the EU require at least two pieces of non-contradictory evidence of location, such as billing address and IP address.

Building this into your checkout from the start is far easier than retrofitting it after you have thousands of subscribers with incomplete location data.

Reverse charge and validating business customer VAT numbers

The original post covered B2C VAT through OSS, but a large share of SaaS revenue is B2B, and the rules there are different and friendlier.

When your Delaware LLC sells to a business in the EU that provides a valid VAT identification number, the reverse-charge mechanism generally applies, meaning you do not collect VAT and the buyer self-accounts for it in their own country.

This is a meaningful operational simplification because it removes you from the collection chain for those sales, but it depends entirely on validating the buyer's VAT number at checkout.

Validation is done against the EU VIES system, which confirms whether a given VAT number is active and belongs to the stated business.

If you accept an invalid or unverifiable number and apply reverse charge anyway, you can become liable for the uncollected VAT yourself, so the validation step is not optional.

Many billing platforms and merchant-of-record services perform VIES checks automatically, which is one practical reason a non-resident founder selling cross-border B2B might lean toward a platform that handles this rather than building the check independently.

Reverse charge also affects how you display prices to business buyers. A B2B checkout should show the net price, capture and validate the VAT number, and then suppress the VAT line when the number checks out.

Getting this flow right reduces friction for enterprise buyers who expect it and protects you from accidentally charging VAT you would then have to remit through OSS unnecessarily.

Digital services taxes beyond the EU

Founders often plan for EU VAT and US sales tax and then get surprised by the growing list of countries outside both that levy consumption tax on inbound digital services.

Countries including the United Kingdom, Canada, Australia, Norway, Switzerland, and a number in Latin America and Asia require non-resident digital sellers to register and collect their own value-added or goods-and-services tax once sales cross a threshold.

The UK left the EU VAT system, so a separate UK VAT registration is needed for B2C sales there rather than relying on OSS. Each regime has its own threshold, registration process, and filing cadence.

For a Delaware LLC owned by a non-resident, the practical question is how many of these regimes you realistically trigger.

If most of your revenue concentrates in the US, EU, and UK, you may only need a handful of registrations.

If your audience is globally diffuse, the administrative load of registering and filing in a dozen jurisdictions can exceed what a solo founder can manage, which is precisely the calculus that pushes many toward a merchant of record that absorbs all of these registrations under its own umbrella.

Thresholds matter because most of these countries do not require registration until you exceed a sales floor, so a new product with light international traffic may have no immediate obligation in many markets.

The right move is to monitor revenue by country as you grow and register in each jurisdiction as you approach its threshold, rather than registering everywhere preemptively or ignoring the issue until a tax authority makes contact.

How the merchant-of-record decision changes your unit economics

The original post framed merchant of record versus direct Stripe as a compliance choice, but it is equally a pricing and margin decision.

A merchant of record like Paddle or Lemon Squeezy charges roughly 5% to 9% of each transaction, which is several points above raw Stripe processing, and that spread comes directly out of your gross margin.

For a SaaS product with strong margins this is often worth it because the platform absorbs VAT, sales tax, chargebacks, and global registrations, effectively buying back the time and risk you would otherwise carry as a non-resident operator.

The way to evaluate this is to model your fully loaded cost of compliance under direct Stripe, including the tools, registrations, and accounting time needed to handle EU OSS, UK VAT, US multi-state sales tax, and the other digital-services regimes.

When you add those costs to Stripe's base rate and compare against a merchant of record's all-in percentage, the gap is frequently smaller than the headline fees suggest.

For many solo and small-team non-resident founders, the merchant of record is cheaper once your own time is priced honestly.

There is also a control trade-off baked into the pricing decision.

A merchant of record becomes the seller of record on the customer's statement and owns the customer payment relationship, which can limit your flexibility on custom invoicing, dunning, and enterprise contracts.

Direct Stripe keeps you as the named seller and gives full control, which matters more as you move upmarket.

The right answer often shifts over time, starting with a merchant of record for simplicity and migrating to direct processing once volume and team size justify the compliance build.

Pricing for refunds, chargebacks, and failed payments

Cross-border SaaS carries higher rates of failed payments and chargebacks than domestic-only businesses because cards from many countries fail more often and dispute resolution varies.

These realities should inform your pricing because every refund and chargeback reverses not just revenue but also the tax you collected and may have already remitted.

If you refund a European consumer their full inclusive price after you have remitted the VAT through OSS, you have to claim that VAT back in a subsequent filing, which adds reconciliation work and temporary cash drag.

Dunning, the process of retrying failed payments, is where small pricing and operational choices protect margin.

A non-resident founder running direct Stripe needs a dunning sequence that retries intelligently and updates customers, because involuntary churn from failed cards can quietly erase a meaningful slice of recurring revenue.

Merchant-of-record platforms typically build this in, which is part of what their fee buys, so the comparison between models should weigh recovered revenue from better dunning, not just the headline percentage.

Chargebacks also carry fixed fees and can threaten your processor relationship if they climb too high.

Pricing transparently, describing charges clearly on the customer's statement, and offering easy self-service cancellation all reduce disputes.

For a Delaware LLC whose banking access through Mercury, Relay, or Wise depends on staying in good standing, keeping dispute rates low is not only a margin issue but a continuity-of-operations issue.

Bookkeeping and bank-account hygiene for tax you collect

When your pricing collects consumption tax on behalf of foreign governments, the money flowing into your Delaware LLC's account is a mix of your revenue and other people's tax.

Treating it all as one pool is the most common bookkeeping mistake non-resident founders make.

The cleaner approach is to track collected VAT and sales tax as a liability from the moment it arrives, so your records always show how much of the balance is genuinely yours.

Banks like Mercury, Relay, and Lili make it easy to create separate sub-accounts or labels, and some founders sweep an estimate of collected tax into a dedicated balance each month.

This discipline pays off at two moments. The first is each remittance deadline, quarterly for EU OSS and on each jurisdiction's schedule elsewhere, when you need the cash on hand to pay what you collected.

The second is annual US filing, where the pro forma 1120 and Form 5472 must reflect the LLC's actual financial activity.

Overstating income by counting collected tax as revenue distorts the picture and can complicate the relationship with any CPA preparing the filing, where the $25,000 penalty for getting the 5472 wrong concentrates the mind.

Good hygiene also means keeping the LLC's money separate from your personal money, which is a core reason the entity exists.

Paying personal expenses from the business account or mixing collected tax into personal transfers undermines the liability protection the Delaware LLC provides and muddies the records you will rely on at filing time.

Clean books are cheaper to maintain than messy ones are to untangle.

A practical sequence for setting your first prices

Pulling the pieces together, a non-resident founder forming a Delaware LLC can follow a sensible order rather than deciding everything at once.

Start by forming the entity for the $110 state fee, obtain the EIN through the SS-4 process which takes roughly 8 to 10 business days for a non-resident without an existing US tax ID, and open a business account with Mercury, Wise, Relay, Lili, or Payoneer.

With the entity, EIN, and banking in place, you have the foundation that processors and merchant-of-record platforms require before you can charge anyone.

Next, decide your primary market and customer type, because that determines whether net or gross pricing fits and how heavy your tax compliance will be.

A B2B product selling to EU and US companies leans toward net pricing with VAT-number validation and reverse charge, which keeps you out of much collection.

A B2C product selling to consumers across many countries leans toward a merchant of record so you are not personally registering for VAT in a dozen places.

Only after this choice does the actual price number make sense, because the model dictates whether tax sits inside or on top of it.

Finally, build the operational backbone before scaling traffic.

Set up location determination at checkout, segregate collected tax in your bank from the first sale, and put a reminder system in place for the recurring deadlines: the $300 Delaware franchise tax due June 1, the Form 5472 and pro forma 1120 due April 15, and the quarterly OSS remittance if you sell B2C in the EU.

Note that a US-formed LLC has been exempt from the FinCEN beneficial ownership information report since the interim final rule of March 26 2025, so that is one filing you can take off the list.

Getting these mechanics right while you are small is far easier than fixing them once revenue and customer counts have grown.