Sri Lanka's 18% Digital Services VAT: What Foreign SaaS and App Sellers Must Register For

A New VAT Bill Just Landed on Foreign SaaS Sellers Who Never Set Foot in Colombo​

If you sell software, an app, a streaming subscription, or any kind of online service, and you've never thought about Sri Lanka's tax code, you're not alone — and that's exactly the problem the country's Inland Revenue Department set out to fix. As of July 1, 2026, Sri Lanka charges 18% VAT on digital services sold by non-resident providers to customers inside the country, whether or not that provider has an office, an employee, or a bank account anywhere near the island.

It's part of a much bigger global pattern. Over the past decade, more than 100 countries have rolled out some version of a "digital services VAT" aimed at foreign platforms — the logic being that a customer in Colombo paying for a US-hosted SaaS tool is still consuming a service locally, so the local government wants its cut. Sri Lanka is simply the latest to close what regulators call the "non-resident loophole." If you run a subscription business, a marketplace, or any product with a global customer base, this is worth five minutes of your attention even if Sri Lanka is a tiny fraction of your revenue today.

What Counts as a "Digital Service" Under the New Rule​

The scope is intentionally broad. Sri Lanka's amended VAT law defines an in-scope digital service as anything delivered over the internet or an electronic network with minimal human intervention on the seller's side. In practice, the categories called out in official guidance include:

• Software-as-a-Service and cloud computing — the core target, and the reason indie SaaS founders should care
• Streaming media — music, video, and audio subscriptions
• Online gaming and in-app purchases
• E-learning platforms — automated courses, not live-instructor tutoring
• Search engines, digital advertising, and social media services
• E-commerce marketplaces and booking platforms
• Content-subscription and membership sites
• Fintech and cybersecurity services delivered remotely

If your product is a web app, a mobile app, an API, or a subscription that a customer in Sri Lanka can sign up for and pay from a browser without you ever speaking to them, it almost certainly qualifies.

Who Actually Has to Register​

The rule targets "non-resident persons" — a formal term for any provider with no fixed place of business in Sri Lanka who nonetheless supplies digital services to customers there. You don't need a Sri Lankan subsidiary, employees, or a local bank account to trigger the obligation; the test is based on where the customer consumes the service, not where you're incorporated.

Registration isn't automatic at your first Sri Lankan sale. It kicks in once you cross a threshold:

• LKR 36 million in taxable digital service supplies to Sri Lanka over a trailing 12-month period (roughly USD 110,000 at recent exchange rates), or
• LKR 9 million in a single calendar quarter (roughly USD 27,500)

Cross either line and you have three months from the date the obligation arises to submit an online VAT registration application to the Inland Revenue Department. Miss it, and the Department has signaled it will treat late or non-registration as an active enforcement priority, not a paperwork footnote.

For most small SaaS tools, hobby apps, or early-stage products, Sri Lankan revenue alone is unlikely to clear USD 100k+ a year — but if you sell through a broader South Asian go-to-market push, run a popular freemium app with regional pricing, or operate a marketplace with meaningful APAC traffic, it's worth checking your Sri Lanka-attributed revenue against these numbers now rather than after you've blown past them.

How the 18% Actually Gets Charged and Paid​

Once registered, you're required to charge 18% VAT on top of your price to Sri Lankan consumers, collect it at the point of sale, and remit it to the Inland Revenue Department on a quarterly basis — returns are due by the last day of the month following the end of each quarter. Payment can be made in Sri Lankan rupees or, notably, in approved foreign currencies, which removes one common friction point for overseas sellers who'd otherwise need a local bank relationship just to pay a tax bill.

Business-to-business transactions get different treatment: many jurisdictions with similar rules — and Sri Lanka's framework follows the pattern — shift the VAT obligation to the local business customer under a reverse-charge mechanism, meaning the registered Sri Lankan company self-assesses and remits the VAT rather than the foreign seller collecting it. If your customer base is mostly enterprise or B2B rather than individual consumers, confirm with a local advisor whether reverse charge applies to your specific transactions before you build VAT collection into your checkout flow for those accounts.

Non-compliance carries real teeth: failure to register or late registration can draw an administrative penalty (reported around LKR 25,000), late filing penalties run up to roughly LKR 50,000 per return, and the Department has indicated that persistent non-compliance can escalate to service restrictions. None of these numbers are large in absolute terms for a company doing six figures of Sri Lankan revenue, but they're a real signal that enforcement, not just registration, is coming.

A Practical Checklist Before You Do Anything Else​

You don't need to hire a Sri Lankan tax advisor to take the first useful steps. Before you touch your checkout flow or pricing page, work through this:

1. Pull 12 months of billing data filtered by customer country. If your payment processor (Stripe, Paddle, Chargebee, or similar) supports a billing-address or IP-based country field, this is a five-minute export. If it doesn't, that's a gap worth fixing regardless of Sri Lanka.
2. Compare your trailing-12-month and largest-single-quarter Sri Lanka revenue against the LKR 36 million / LKR 9 million thresholds. Convert at a recent exchange rate and build in a buffer — currency moves alone can push you across a line you didn't cross in local-currency terms.
3. Separate B2C from B2B customers. If most of your Sri Lankan revenue comes from registered local businesses rather than individual consumers, the reverse-charge mechanism may shift the collection obligation to them — but confirm this with current guidance rather than assuming, since implementation details are still being finalized by the Inland Revenue Department.
4. Decide on merchant-of-record vs. self-managed compliance. If Sri Lanka is one of several dozen jurisdictions where you have meaningful exposure, a merchant-of-record platform that already handles VAT/GST registration and remittance across multiple countries is usually cheaper than building in-house tax compliance for each one individually.
5. If you're near or over threshold, register within the three-month window rather than waiting for a warning notice — the administrative penalties are modest, but Inland Revenue Departments worldwide have gotten more aggressive about cross-referencing app-store and payment-processor data to identify unregistered foreign sellers.

How Sri Lanka's Rule Compares to Other Digital VAT Regimes​

If this is your first encounter with a "digital services VAT," it helps to see it in context. The mechanics are broadly similar across jurisdictions, but the thresholds and rates vary enough that a one-size-fits-all compliance approach doesn't work:

The pattern to notice: newer entrants like Sri Lanka tend to set a meaningful revenue threshold before registration kicks in, while more established regimes (EU, UK, Kenya) increasingly require registration from the first sale. That trajectory — thresholds shrinking or disappearing over time — is worth keeping in mind even if you comfortably clear Sri Lanka's bar today; the next country you expand into may not offer the same grace period.

Why This Matters Even If Sri Lanka Is a Rounding Error for You​

The specific numbers here are Sri Lanka's, but the shape of the rule is not unique to Sri Lanka. Indonesia, the EU, the UK, South Africa, Kenya, and dozens of other jurisdictions have adopted near-identical "non-resident digital services VAT" frameworks over the past several years, each with its own threshold, rate, and filing cadence. If you sell a digital product internationally, you are very likely already subject to at least one of these regimes somewhere, whether you've registered for it or not.

The practical risk isn't usually a single country's tax bill — it's the compounding administrative burden of tracking a dozen different thresholds, rates, and filing deadlines across a spreadsheet, plus the audit exposure of discovering three years later that you crossed a threshold in country after country without noticing. Payment processors like Stripe and Paddle increasingly offer "merchant of record" services that absorb this complexity by collecting and remitting VAT/GST on your behalf across many jurisdictions — worth evaluating once your international revenue starts meaningfully diversifying beyond your home market.

Keeping the Books Straight Across a Growing List of Tax Jurisdictions​

Whether or not Sri Lanka specifically applies to you today, this kind of rule is a good prompt to check how well your bookkeeping actually tracks revenue by customer country. If your accounting system can't answer "how much did we bill customers in Sri Lanka last quarter" in under a minute, you won't know you've crossed a threshold until it's already a compliance problem.

Beancount.io offers plain-text accounting that makes this kind of question trivial to answer — every transaction is a queryable, version-controlled line of text, so tagging revenue by customer jurisdiction and running a quarterly report takes minutes, not a fire drill. There's no black box between your data and your answer, which matters more every year as more countries roll out their own version of this rule. Get started for free and see how straightforward tracking multi-jurisdiction revenue can be when your books are plain text from day one.