Digital services tax (DST)

Country-specific taxes on revenue from digital services (advertising, marketplaces, social media).

Definition

Digital services tax (DST) is a country-level revenue tax on certain digital services. Implemented or proposed in UK, France, Italy, Spain, India, and others. Typically applies to large multinationals (revenue thresholds), but smaller LLCs may have indirect exposure.

Context

Relevant for Delaware LLCs serving customers in DST jurisdictions.

Example

A Delaware LLC operates an ad-tech platform serving UK customers. Above the UK DST revenue threshold, the LLC may face UK DST obligations.

Common pitfalls

Revenue thresholds typically apply, exempting small businesses.
OECD Pillar 1/2 may replace some DSTs.
Engage international tax adviser for cross-border digital services.

What a digital services tax actually targets

A digital services tax sits in an unusual place in the tax world because it does not behave like the taxes a non-resident founder usually plans around. Income tax looks at profit, sales tax and value added tax look at the value of a transaction, and a digital services tax looks at gross revenue earned from a narrow band of online activities inside a specific country. The activities that tend to fall in scope are online advertising sold against user data, the operation of a digital marketplace that connects independent buyers and sellers, and the running of a social or user-generated platform where the audience itself is the product being monetized. The common thread is that value is treated as created by users located in that country, even when the company has no office, no staff, and no warehouse there. That design is what makes the tax feel foreign to founders who have only ever thought about taxation in terms of where a business is physically based or legally registered, and it is why a Delaware wrapper does nothing to change the analysis. The activity and the audience drive the question, not the place of incorporation.

For a non-resident who owns a Delaware LLC, the practical lesson is that physical presence is not the trigger. A founder can live in Lagos, route a company through Delaware, and never set foot in Paris, yet still touch the French regime if the platform earns advertising revenue tied to French users. The tax is built precisely to reach businesses that operate at a distance over the internet, which is the whole reason it exists as a separate instrument alongside ordinary corporate tax. That does not mean every small LLC owes it, and most do not. As the underlying glossary entry notes, these regimes generally apply to large multinationals through revenue thresholds, and smaller LLCs more often face indirect exposure than a direct bill from a foreign authority. Understanding the target helps a founder judge quickly whether the topic is a live concern that needs a specialist or simply background knowledge to file away for a later stage of growth. That early triage, deciding whether a question even applies, is the single most useful thing a small operator can do with the concept before spending money on advice they may not yet need.

Why a revenue tax behaves so differently from income tax

Most founders build a mental model around income tax, where only profit is taxed and a loss-making year produces no liability at all. A digital services tax breaks that model because it is levied on in-scope gross revenue regardless of whether the business is profitable. A platform can run at a loss while still generating taxable revenue under a country digital services tax, which is one reason the regimes were politically controversial when they first appeared. The design choice was deliberate rather than accidental. Governments argued that highly digital businesses booked profit in low-tax locations while earning revenue from local users, so taxing the revenue stream directly was a way to capture value that traditional profit-based rules were thought to miss. The result is an instrument that scales with activity rather than with margin, which is a fundamentally different shape from the income tax a founder already understands. A business that would owe nothing under a profit test can still register on a revenue test, and a founder who has only ever planned around profit can be caught off guard by that distinction if it ever becomes relevant to them at scale.

This distinction matters when a founder maps out cash flow and pricing. An income tax obligation can be smoothed by deductions, depreciation, and timing, but a revenue-based charge is harder to manage because it scales with top-line activity rather than with what is left after costs. Even at a modest rate such as 2% or 3%, a revenue tax can represent a meaningful share of thin platform margins, and that is before any other tax in the chain is considered. The point is not to alarm a small operator who sits far below any threshold and will never file such a return. The point is conceptual and worth holding onto for the long run. A founder should not assume that because the LLC reports little or no profit, no foreign digital tax could ever attach, because the two taxes answer genuinely different questions. One asks how much was left over after expenses, the other asks how much came in from a particular country regardless of expenses. A careful founder keeps them in separate mental buckets rather than collapsing them into a single vague idea of being taxed somewhere abroad, which is how planning errors creep in.

How the tax intersects with a single-member foreign-owned LLC

A single-member LLC owned by a non-resident is, by default, a disregarded entity for United States federal tax purposes. The Internal Revenue Service looks through it to the owner, and the entity does not file its own income tax return in the way a corporation does. That status shapes how a founder should think about a foreign digital tax, but not in the way many people expect when they first hear it. The disregarded nature is a United States classification and has no bearing on whether a foreign country decides its digital services tax reaches the platform. A country writing such a rule cares about where users are located and how much in-scope revenue is earned there, not about how Washington characterizes the entity for its own purposes. A label that matters enormously for a Form 5472 filing can be completely irrelevant to a tax authority in Madrid or Rome, because that authority is asking an entirely different question about user-driven value within its own borders rather than about the entity's status under another country's code. The founder who internalizes this stops looking for an answer in United States classification and starts looking at the only things a foreign regime actually weighs, which are the country of the users and the size of the in-scope revenue.

So a foreign digital tax, if it ever applied, would generally attach at the level of the business activity occurring in that country rather than being filtered through the LLC's United States classification. For most non-resident owners of a small single-member LLC the realistic exposure is indirect rather than direct, and that difference is worth internalizing. A platform might serve as one node in a larger advertising chain, and a counterparty that is itself subject to the tax may pass on cost or impose contractual terms that allocate the burden downward to smaller participants. Direct registration in a foreign digital tax regime is uncommon for a business that falls well below the high revenue thresholds these regimes use, and most small founders will never face it during the ordinary life of their company. A founder building a genuinely large advertising or marketplace operation should treat the topic as live and seek a cross-border tax adviser, which the glossary entry recommends, rather than relying on general reading or assuming the Delaware wrapper resolves the question on its own. The wrapper is a starting point, not a shield.

Worked example: an ad-tech platform crossing a threshold

Consider a founder in Karachi who forms a Delaware LLC, pays the $110 Certificate of Formation fee, obtains a free EIN by filing Form SS-4, and opens a Mercury account to collect payments. The LLC builds an advertising platform that places ads against content consumed by users in the United Kingdom. In year one the platform earns a small amount of United Kingdom advertising revenue, well below the level that any country digital services tax regime tends to use as a floor for liability. In that situation the founder's realistic obligations sit in the United States, including the Form 5472 with a pro forma 1120 filing that a foreign-owned single-member LLC must lodge, where failure to file carries a $25,000 penalty. The foreign digital tax in this first year remains background context rather than a filing duty, and treating it as anything more would waste effort that belongs on the United States paperwork the founder genuinely does owe. The discipline here is to size the risk honestly and put attention where a real obligation already exists rather than where an imagined one might one day appear.

Now move the example forward several years. The platform scales, signs direct advertiser relationships, and its United Kingdom-attributable advertising revenue grows substantially while group revenue climbs into the range where large-multinational thresholds come into play. At that point the indirect exposure described in the glossary entry can harden into a question that needs professional review rather than self-assessment from general reading. The exact figures, the way revenue is attributed to users in a country, and whether the activity counts as in-scope advertising all turn on the specific national rules in force in that year, which is exactly why no single number can be quoted as a universal trigger that applies everywhere. The worked example is meant to show the shape of the journey, from clearly out of scope to potentially in scope, not to assert that any particular revenue figure produces a bill. The lesson a founder should carry away is that the same business can move across the line as it grows, so the question deserves periodic revisiting rather than a one-time answer that is filed away and never reconsidered. Growth itself is the event that changes the analysis.

Worked example: a marketplace versus a simple online store

The category of business matters as much as the revenue figure, and sometimes more. Imagine two Delaware LLCs owned by the same non-resident founder. The first runs a marketplace that connects independent sellers with buyers and takes a commission on each sale, with users in Italy and Spain forming a large slice of the audience. The second simply sells the founder's own products directly to customers in those same countries through a basic online store. A marketplace that intermediates between third parties is the classic in-scope activity for many digital services tax regimes, while a first-party retailer selling its own goods usually is not the intended target, because the value is the product rather than the platform's matching of users. Two businesses serving the same buyers in the same countries can therefore land on opposite sides of the line purely because of how they create value and whose transactions they sit between. That is a counterintuitive result for a founder who assumes geography of customers is the only thing that counts toward exposure, when in fact the relationship between the platform and the people transacting on it matters at least as much. A commission earned for connecting two strangers reads very differently to these rules than a margin earned for selling a thing the founder already owned.

This contrast is useful because founders often assume that any online sales into a country create the same exposure, and that assumption is simply wrong. The marketplace model, the advertising-against-user-data model, and the user-platform model are the recurring in-scope shapes, and a straightforward direct-to-consumer store generally sits outside them even when it ships to the same buyers in the same cities. A founder choosing a business model can therefore factor this into design decisions early, before the structure and revenue mix are locked in and harder to change. None of this removes the separate question of value added tax, customs, or local consumption taxes, which follow their own rules and can apply to a plain online store regardless of any digital services tax. Keeping the two questions distinct prevents a founder from either overreacting to a digital tax that does not apply or quietly ignoring a real consumption-tax duty that does. The discipline is to ask which activity is in scope for a digital tax and then to ask separately which consumption taxes apply, treating them as two different filters rather than one blurred worry about being taxed abroad.

Revenue thresholds and why small LLCs usually sit below them

The single feature that protects most non-resident founders is the threshold structure built into these regimes. Country digital services tax regimes were generally written with very large companies in mind, and they typically use two-part tests: a high worldwide group revenue figure and a separate in-country revenue figure that must both be cleared before the tax attaches. These floors are deliberately set so that the regimes capture major platforms rather than independent operators running lean businesses from a laptop. The glossary entry makes this point directly, noting that revenue thresholds typically apply and exempt small businesses, and that smaller LLCs are more likely to face indirect exposure than a direct assessment from a tax office. For a founder who has just paid the $110 formation fee and is collecting modest revenue through Wise or Relay, both legs of such a test will almost always remain far out of reach for years, if not for the entire life of the business. The structure is not an accident or a loophole. It is the explicit policy intent of regimes aimed squarely at the largest digital firms.

For a founder running a lean operation through a Delaware LLC, this means the day-to-day reality is usually one of awareness rather than active compliance. The platform may be growing steadily, the founder may be earning revenue in a country with a digital services tax, and still the LLC sits comfortably under both legs of the threshold test with room to spare. The right posture is to know the regime exists, understand which activities are in scope, and revisit the question only if the business scales toward the magnitude where large-multinational rules begin to bite. Because thresholds and rules change from year to year and country to country, a founder should not memorize a single number as if it were permanent and reliable. The durable takeaway is structural rather than numeric: small operators are generally outside the net by design, and the moment to seek advice is when growth genuinely changes that picture, not before it does. Until then the topic is sensibly logged as a future review item alongside the routine maintenance the entity already requires, such as the annual franchise tax, rather than as an urgent open task demanding immediate attention.

How OECD Pillar One and Pillar Two reshape the landscape

Digital services taxes emerged partly as unilateral national responses to a perceived gap in the international tax system, and that gap is the subject of a multilateral effort led by the Organisation for Economic Co-operation and Development. The two strands of that effort are often called Pillar One and Pillar Two. Pillar One concerns the reallocation of certain taxing rights toward the countries where customers and users are located, and Pillar Two concerns a global minimum level of taxation for very large groups. Part of the political bargain around these pillars was an expectation that some countries would withdraw their standalone digital services taxes if a multilateral solution took hold, which the glossary entry flags directly when it notes that the pillars may replace some of these taxes over time. The upshot for a founder is that the very existence of a given country's digital services tax can be temporary, tied to the progress of negotiations that sit far above the level of any individual operator and move on their own diplomatic timeline rather than on a business cycle. A rule that looks settled today may be one diplomatic agreement away from being unwound, which is a reason to hold any conclusion loosely rather than to carve it in stone.

For a non-resident founder this is mostly context rather than an immediate action item, because both pillars are aimed at very large enterprises far above the scale of a typical single-member LLC. The reason it still matters is that the rules in this area are in motion rather than settled into a final form. A digital services tax that exists in one year might be repealed, suspended, or replaced as international agreements advance, and a new mechanism might appear in its place under a different name and a different design. A founder who plans to operate at significant scale benefits from knowing that the framework is unsettled, so that assumptions made today are revisited rather than treated as fixed truths that never expire. The practical instruction is simply to keep the topic under periodic review and to lean on a specialist when the numbers grow large, because a moving target cannot be managed responsibly with a one-time reading done years earlier. For the small operator, the broader takeaway is reassuring rather than worrying: the heavy machinery of the pillars is built for businesses many times their size, and it will not reach down to a modest platform any time soon.

Indirect exposure through advertising and platform partners

Even when a Delaware LLC sits below every threshold, it can still feel the gravity of these taxes through its commercial partners rather than through any direct filing. The advertising ecosystem is layered, and a small platform often sells inventory through an exchange, a network, or a larger intermediary that is itself in scope of a country digital services tax. When that larger partner faces a revenue tax in a jurisdiction, it may respond by adding a surcharge, adjusting rate cards, or inserting contract clauses that allocate the cost down the chain to smaller participants. The founder does not file anything with a foreign authority, yet the economics of the deal shift in ways that show up directly in revenue share and net payouts. This is precisely the indirect exposure the glossary entry describes, and it is the form most relevant to independent operators who will never come close to a direct threshold themselves. The cost is real even though the obligation is not the founder's own, which is why it can be easy to overlook until it appears on a statement.

The practical response is to read platform terms and advertiser agreements with this possibility in mind rather than skimming past the fee schedules and assuming they are boilerplate. Some large advertising platforms have publicly added fees in countries that introduced digital services taxes, passing the burden down to advertisers and publishers who use their systems to reach audiences. A non-resident founder cannot control whether a partner does this, but can anticipate it when modeling margins and can ask, during contract review, how digital tax surcharges are handled and who actually absorbs them. Treating the topic as a line item in commercial negotiation is far more useful than treating it as a compliance filing, because for a small LLC the cost almost always arrives through a counterparty rather than through a direct assessment from a foreign tax authority. A founder who builds this question into how they evaluate partners and price their own services will rarely be surprised by a surcharge that quietly erodes a thin margin, and that foresight is worth more than any amount of worry about a direct bill that will not arrive.

Where this sits relative to your United States filing duties

It helps to anchor a foreign digital tax against the United States obligations a non-resident LLC owner actually does have, because confusing the two leads to costly mistakes in both directions. A foreign-owned single-member LLC treated as disregarded must generally file Form 5472 together with a pro forma Form 1120 to report reportable transactions with its foreign owner, and the penalty for failing to file is $25,000. That is a real, concrete, recurring United States duty that applies to most non-resident owners regardless of where their customers happen to live or what those customers buy. A country digital services tax is a separate matter that depends on foreign rules and high thresholds, and for the large majority of small LLCs it produces no filing at all in any given year. Putting the two side by side makes their relative weight obvious to a founder deciding where to spend limited time and money, and it makes clear which one is the near-certain obligation and which one is the distant contingency that may never materialize. The United States filing arrives on a known schedule every year, while the foreign digital tax waits behind a wall of thresholds the small operator is unlikely to cross.

Keeping these in clear order prevents two failure modes that both cost real money. The first is a founder who fixates on an exotic foreign tax they will almost certainly never owe while overlooking the routine Form 5472 obligation that carries a steep penalty if it is missed even once. The second is a founder who, having handled the United States paperwork, assumes nothing else in the world could ever apply and stops thinking about international questions entirely, even as the business grows toward a different category. The balanced view is that the United States filings are the predictable core a non-resident must get right every single year, while a foreign digital tax is a conditional, growth-dependent topic to monitor in the background. A founder who has formed the LLC, obtained an EIN, and set up United States compliance has built the foundation, and the digital tax question layers on top only as the business scales into the relevant jurisdictions at meaningful size. First the floor, then the upper stories, in that order, because skipping the floor to worry about the roof helps no one.

How formation, banking, and EIN steps connect to the topic

The early mechanical steps of building a Delaware LLC do not create digital services tax exposure, but they do create the structure through which any such exposure would later be measured if it ever arises. Filing the Certificate of Formation for $110 brings the entity into existence as a legal person. Obtaining a free EIN through Form SS-4, which typically takes around 8 to 10 business days for a non-resident without a Social Security number, gives the business an identifier needed to open accounts and file United States returns. Opening an account with a provider such as Mercury, Wise, Relay, Lili, or Payoneer gives the platform a way to collect revenue from customers around the world and to keep that money organized. None of these steps registers the LLC for a foreign digital tax, and none of them should be expected to, because they are United States formation and banking actions rather than foreign tax registrations. A founder who completes them has built a company, not triggered a foreign liability, and it is worth being clear about that so the steps are not approached with misplaced anxiety.

What these steps do is determine how revenue flows and where it is recorded, which becomes relevant only if the business later approaches the scale where a foreign regime could apply to it. Clean banking records and clear bookkeeping make it far easier for a future adviser to attribute revenue to particular countries, which is exactly the analysis a digital services tax question demands once it becomes live rather than hypothetical. A founder also pays the $300 flat Delaware franchise tax due each June 1 to keep the entity in good standing, a fixed cost unrelated to digital taxes but part of the same maintenance rhythm that keeps the structure intact year after year. The connective tissue across all of this is record quality and consistency. Good early hygiene around formation, banking, and bookkeeping pays off if and when a more complex international tax conversation finally arrives, because a founder who can show clearly where revenue came from and which users it was tied to is in a far stronger position than one trying to reconstruct it after the fact from incomplete statements.

Beneficial ownership and why it is a separate question

Founders often bundle every compliance acronym together into one anxious heap, so it is worth deliberately separating beneficial ownership reporting from digital services taxes because they answer entirely different questions. Beneficial ownership information reporting was a transparency measure about who finally owns and controls a company, administered by the Financial Crimes Enforcement Network. Following the FinCEN Interim Final Rule of March 26 2025, United States-formed entities such as a Delaware LLC are exempt from the beneficial ownership information filing, so a domestic LLC owned by a non-resident does not lodge that report under the current framework. That is an ownership-transparency matter about identity and control, not a tax on revenue, and folding it into a discussion of digital taxes only muddies both topics for a founder trying to keep an accurate running list of what they actually owe and to whom. The two belong on different shelves entirely, even though both wear the broad label of compliance and both involve a government agency on the other end. One asks the company to name its humans, the other asks the company to share a slice of its revenue, and no amount of effort on the first does anything to settle the second.

A digital services tax, by contrast, is about taxing revenue from specific online activities in specific countries, and it has nothing to do with disclosing the identity of owners to anyone. A founder could be fully exempt from beneficial ownership reporting and still, at sufficient scale, fall within a foreign digital tax, or could face neither of them, because the two move completely independently of one another. Treating them as one bundle invites errors, because the rules, the administering authorities, and the triggers are unrelated and live in different legal worlds. The clean mental map is to file United States income-related paperwork like Form 5472 where required, recognize that the beneficial ownership filing is not required for a United States LLC after the March 2025 rule, and treat any foreign digital tax as a distinct, growth-dependent question handled with a cross-border specialist when it becomes live. Three separate boxes, each with its own rule and its own authority, is a far more reliable way to think than one large undifferentiated box labelled compliance that hides which obligations are real and which are not.

Related terms a founder should understand alongside this

Digital services tax does not live in isolation, and a founder grasps it better by placing it next to neighboring concepts that often get confused with it in conversation. Transfer pricing, the related term the glossary entry links to, governs how transactions between connected entities in different countries are priced, and it becomes relevant when a single founder operates more than one entity across borders and moves value between them. Permanent establishment is the threshold concept that asks whether a business has enough presence in a country to be taxed there on profit, and a digital services tax was partly designed to reach businesses that fall short of a permanent establishment yet still earn from local users without a taxable foothold. Withholding tax describes amounts a payer deducts at source on certain cross-border payments, which can interact with how foreign revenue reaches the LLC and reduce what actually lands in the account once the payer has taken its cut. Each of these is a distinct lever in the cross-border tax machine, and knowing which lever a given question pulls is half the battle.

Value added tax and goods and services tax are the broad consumption taxes that apply to many cross-border digital sales and are far more likely to touch a small platform than a digital services tax ever is. A founder selling digital products to consumers in the European Union, the United Kingdom, or other jurisdictions may face consumption-tax registration well before any digital services tax threshold comes near, so the two should never be treated as interchangeable or lumped together. Seeing these terms as a family clarifies what each one actually does and where it bites. A digital services tax is a narrow revenue tax on certain platform activities aimed at large players, consumption taxes are broad and reach small sellers directly, and the profit-based concepts of permanent establishment and transfer pricing govern a different layer of the system entirely. A founder who can place a new tax question into the correct one of these buckets has already done most of the work of figuring out whether it applies and how seriously to take it, and that sorting skill is worth more than memorizing any single rule that may change next year.

Edge cases that complicate the simple picture

Several edge cases push beyond the clean description and deserve real attention from a founder operating near the margins of these rules rather than comfortably below them. One is the founder who runs several Delaware LLCs or a mix of entities across countries, where revenue might be aggregated at a group level for threshold purposes depending on the national rule in question. Aggregation can lift a set of individually small businesses toward a threshold that none of them would reach alone, which is exactly the kind of nuance that calls for professional review rather than confident self-assessment from general reading. Another edge case is the platform whose activity blends categories, such as a marketplace that also sells advertising against its own audience, where part of the revenue could be in scope and part outside it, and the split itself becomes a question that needs careful analysis under the specific rule in force in that year. These are the situations where a tidy summary stops being enough and the detail starts to matter a great deal. A founder who has layered several entities or stacked several revenue types on one platform should assume the simple picture no longer holds and that the specifics of each national rule will drive the answer.

A further wrinkle is attribution, which is harder than it sounds. Deciding how much revenue belongs to users in a particular country can be genuinely difficult for a platform with a global, mobile audience, and different national rules use different proxies such as user location, device data, or billing address to make that call. A founder cannot resolve these questions with a simple rule of thumb, and guessing in either direction carries cost, whether through overpayment or through an unexpected assessment later. The honest position is that edge cases like multi-entity aggregation, mixed-activity platforms, and contested revenue attribution are precisely where general information stops being adequate and a specialist becomes worth the fee they charge. This is general information and not legal or tax advice, and a founder who recognizes one of these patterns in their own structure should treat that recognition as the cue to bring in a cross-border tax adviser before the situation grows rather than after a problem has already surfaced. The skill to develop is pattern recognition: knowing enough to spot when a question has outgrown a glossary and needs a human expert.

Common misunderstandings to avoid

The most common misunderstanding is the belief that forming a Delaware LLC somehow shields a business from all foreign taxes everywhere. It does not, and acting as if it does can be expensive when a real obligation eventually surfaces. The Delaware entity is a United States legal form, and a foreign country's decision to tax in-scope digital revenue does not defer to that form in any way whatsoever. A second misunderstanding is assuming that because the LLC pays no United States income tax as a disregarded entity with no effectively connected income, no tax anywhere on earth could possibly apply. The two questions are entirely unrelated, and a foreign digital tax follows its own logic about users and revenue rather than the LLC's United States status. A founder who treats a quiet United States position as proof of global immunity has confused one jurisdiction's silence for every jurisdiction's blessing, and that is a dangerous leap that can leave a growing business unprepared for questions it should have seen coming. The disregarded status answers a United States question and nothing more, so reading it as worldwide protection is exactly the kind of error that grows costly as a platform scales into new markets.

A third misunderstanding is conflating a digital services tax with consumption taxes such as value added tax, which are different instruments with different triggers and different scopes. A small seller is far more likely to encounter value added tax registration than a digital services tax obligation, so collapsing the two leads a founder to worry about the wrong one. A fourth is treating the rules as static when they are actively shifting under the OECD pillar negotiations, so a position that is true in one year may change in the next without much warning. The grounded conclusion mirrors the glossary entry closely: revenue thresholds generally exempt small businesses, the OECD pillars may replace some of these taxes over time, and a founder with cross-border digital activity at scale should engage an international tax adviser rather than self-diagnose from a summary. For most non-resident owners of a small single-member Delaware LLC, the practical reality is awareness rather than a filing, with the United States obligations such as Form 5472 remaining the predictable core to get right first. Knowing what the tax is, who it targets, and when it might apply is exactly the right amount to know at a small scale.

Related terms

Transfer pricing

Related glossary terms & guides

Form your LLC WhatsApp

WhatsApp Form your LLC