VAT MOSS / OSS

EU VAT scheme for non-EU digital service providers. The Mini One Stop Shop (MOSS) was replaced by the One Stop Shop (OSS) and Import One Stop Shop (IOSS) in 2021.

Definition

VAT MOSS (Mini One Stop Shop) was the EU VAT system for digital services, but it was replaced on 1 July 2021 by the One Stop Shop (OSS) and Import One Stop Shop (IOSS) schemes; MOSS is no longer current terminology. Non-EU sellers (including Delaware LLCs) selling digital products to EU consumers register and remit EU VAT through the non-Union OSS scheme. A single registration in one EU country covers all EU sales.

Context

Affects Delaware LLCs selling SaaS, ebooks, downloads, or other digital products to EU consumers.

Example

A Delaware LLC SaaS company sells to EU consumers. The LLC registers for OSS in one EU country (typically Ireland) and remits VAT collected.

Common pitfalls

B2C sales to EU consumers trigger VAT; B2B sales typically reverse-charge.
MoR services (Paddle, Lemon Squeezy) handle EU VAT compliance.
Manual compliance is complex; consider MoR.

Why a Delaware LLC Owner Hears About VAT MOSS at All

If you formed a Delaware LLC to sell software, templates, courses, or other downloads, the phrase VAT MOSS tends to surface the first time a European customer asks for a VAT invoice. The acronym sounds like a US tax topic, but it is entirely European in origin. VAT is value added tax, a consumption tax charged on the final sale of goods and services to a consumer in the European Union. MOSS once stood for Mini One Stop Shop, the registration portal that let a single seller report VAT across many EU countries from one place rather than dealing with each national tax authority separately. As the underlying glossary entry makes clear, that MOSS label was retired on 1 July 2021 and replaced by the One Stop Shop, known as OSS, along with a companion scheme called the Import One Stop Shop, or IOSS. People still type MOSS into search bars and support tickets out of habit, which is precisely why the older term remains worth explaining even though it no longer names a live system. A founder who searches the old acronym should understand that it points to the modern OSS scheme today.

The reason this matters to a non-resident founder is that VAT does not follow your location as the seller. It follows your customer's location as the buyer. A Delaware LLC has no US sales tax obligation for most digital goods sold abroad, and it owes no EU corporate income tax simply by selling into Europe. Yet the moment a private individual in France or Germany buys your ebook or subscribes to your app, an EU VAT charge can attach to that single transaction. The buyer is the person who finally bears the cost, but the seller is frequently the party legally responsible for collecting that tax at checkout and remitting it to the right authority. That inversion of responsibility catches many first-time founders off guard, because nothing in the Delaware Certificate of Formation, the EIN application, or the bank onboarding flow ever mentions Europe or VAT. The obligation arrives quietly through your customers rather than through any document you signed when you set the company up, and it is easy to miss until a buyer asks for paperwork you were not expecting to provide.

Understanding the shape of this system early prevents a scramble later. You do not need to register before you have any EU customers at all, and you do not need to panic the first time a single European sale appears in your dashboard. What you do need to know is which sales actually create the obligation, who can carry that obligation on your behalf if you would rather not handle it directly, and how the whole thing interacts with the rest of your Delaware setup. This entry walks through those questions in concrete, practical terms aimed at a single-member, foreign-owned LLC selling digital products, so that the topic becomes a manageable checklist item rather than a vague source of worry that you keep deferring until it becomes urgent. The goal is to give you enough of the landscape to make a deliberate choice rather than a panicked one, and to know when professional advice is the sensible next step instead of guesswork pieced together from old forum posts.

From MOSS to OSS: What Actually Changed in 2021

The original MOSS scheme launched in 2015 and applied fairly narrowly to telecommunications, broadcasting, and electronically supplied services sold to EU consumers. It solved a real and painful problem. Before MOSS existed, a seller technically had to register for VAT in every single EU country where it had even one consumer, which was wildly impractical for a small digital business operating across the whole bloc. MOSS let that seller choose one EU member state, file a single periodic return there, and have the tax distributed onward to the other countries automatically behind the scenes. For a US company with no EU establishment, the relevant flavor was the non-Union MOSS, meaning the version of the scheme designed for sellers established outside the European Union. That non-Union distinction still matters today because it is the exact lane a Delaware LLC sits in, and recognizing which lane applies to you is the difference between following guidance meant for European businesses and guidance meant for outsiders like your company.

The 2021 reform broadened and renamed the system rather than abolishing it. The non-Union OSS now covers a wider range of services supplied to EU consumers, not only the narrow digital categories that the earlier MOSS was limited to. Alongside it, the Import One Stop Shop, IOSS, was introduced to handle low-value physical goods shipped into the EU from abroad, which is a separate lane that most pure software or content sellers can safely ignore for the moment. The glossary entry is precise on this point, and it is worth restating clearly. MOSS is no longer current terminology, and a non-EU seller such as a Delaware LLC registers and remits EU VAT through the non-Union OSS scheme rather than through anything still bearing the MOSS name. A single registration in one EU country covers all of that seller's EU sales, which is the core convenience the scheme exists to deliver and the reason it is worth understanding at all.

For a founder reading older blog posts and forum threads, this naming history matters because guidance written before the middle of 2021 may describe forms, thresholds, portals, and registration steps that have since been replaced. When you research your own situation, strongly prefer sources that reference OSS or IOSS and that carry a publication date after mid 2021. Treat any article that still calls the live scheme MOSS as potentially stale, and confirm the current rules against an official EU tax source or a qualified adviser before acting on any specific numbers you find. Tax procedure tends to be updated quietly without much fanfare, and an out-of-date walkthrough can send you toward a portal or a form that no longer functions the way it once did, costing you time you did not need to spend. Treating publication dates as a filter, rather than assuming all guidance is equally current, is one of the simplest ways to avoid following instructions that quietly stopped being accurate years ago.

Consumer Sales Versus Business Sales: The Key Distinction

The single most important practical fork in EU VAT for a digital seller is whether your buyer is a private consumer or a registered business. The glossary entry states the rule plainly. Business to consumer sales to EU consumers trigger VAT, while business to business sales typically use the reverse charge mechanism. Getting this distinction right changes whether you collect tax at checkout or not, and it changes who is finally responsible for accounting to the tax authority, so it deserves a careful look rather than a casual guess. Many founders treat all of their European sales as one undifferentiated bucket, and that habit is exactly what produces either over-collection that annoys legitimate business buyers or under-collection that quietly creates a liability for the seller down the line. Sorting buyers into the right category is the foundation everything else in this entry rests on, and it is worth building into your checkout from the very first European sale.

When you sell to a private individual, a consumer sale, the place of supply for most digital services is treated as the country where that consumer lives. Your Delaware LLC is then expected to charge the VAT rate of the consumer's country and to remit that amount, usually through the OSS registration described earlier in this entry. When you instead sell to a VAT-registered business, a business sale, the responsibility often shifts to the buyer under the reverse charge. The business buyer accounts for the VAT in its own country, and you, the seller, do not collect any VAT on that particular transaction. In practice this means asking for and validating the buyer's EU VAT identification number at checkout, because a valid, verifiable number is what evidences a genuine business buyer and supports your decision not to charge tax on that sale. Without that validation step you have no defensible basis for treating a sale as a business sale, so the number is not a formality but the actual evidence.

The edge case to watch closely is the buyer who claims to be a business but cannot supply a valid VAT number when asked. Without a verified number you generally have to treat the sale as a consumer sale and charge VAT accordingly. Many founders badly underestimate how much of their EU revenue is actually consumer revenue, because individual professionals, freelancers, students, and hobbyists frequently buy software and digital content on personal cards without holding any VAT registration at all. Mapping your real customer mix, rather than assuming that everyone who buys a productivity tool must be a registered company, tells you how large your VAT exposure genuinely is and whether handling it manually is even worth your time compared with the alternatives discussed later in this entry. That mix also tends to shift as a product matures, so it is worth revisiting periodically rather than deciding once and assuming the proportions stay fixed for the life of the business.

How OSS Applies to a Single-Member Foreign-Owned LLC

A single-member LLC owned by a non-US person is, by default, a disregarded entity for US federal tax purposes. That US classification has no bearing whatsoever on EU VAT. From the EU's perspective, your Delaware LLC is simply a taxable person established outside the European Union that may be making taxable supplies to EU consumers. The disregarded status that drives your annual Form 5472 and pro forma 1120 filing in the United States does not exempt the LLC from the European obligation, and the European obligation in turn does not change anything about how you file in the US. They are parallel systems that rarely interact, and conflating them is one of the more common conceptual mistakes a new founder makes when first trying to map out the full set of duties attached to the company. Treating each system on its own terms, rather than expecting one to cancel or modify the other, keeps the picture clear from the start and saves a great deal of confusion later.

Under the non-Union OSS, your LLC can choose one EU member state of identification and register there. As the glossary example notes, founders often select Ireland, partly for the language and partly for administrative familiarity, though it is not the only available option. That single registration then covers your consumer digital sales across all EU member states at once. You file periodic OSS returns, report the VAT you collected broken down by country, and pay a single consolidated amount, which the member state of identification then redistributes to the other countries on your behalf. You do not need to obtain a separate VAT registration in each individual country where a customer happens to live, which is the entire convenience the One Stop Shop was designed to deliver to sellers like you. That consolidation is what makes direct compliance even plausible for a small operation, since registering in a couple dozen countries individually would be far beyond what a solo founder could realistically maintain alongside running the actual business.

Because the LLC has no physical presence, staff, or office in Europe, there is generally no permanent establishment and no EU income tax that arises merely from selling digital products into the region. The OSS obligation is about VAT collection on consumer sales, not about taxing your profit. Keeping those two ideas firmly separate helps you avoid a false fear that registering for OSS somehow drags your LLC into the European corporate tax net. It does not do that. Registering makes you a collector of a consumption tax that your EU buyers finally bear, and nothing more than that. Your profit continues to be addressed through your US filings and, depending on your personal situation and country of residence, through your own personal tax position, which is a separate matter standing outside the scope of VAT entirely. Drawing that line clearly matters because the fear of accidentally creating an income tax footprint in Europe is one of the most common reasons founders avoid registering when they probably should, when in reality VAT registration and income taxation are different questions answered by different rules.

A Worked Example: A SaaS Founder's First EU Year

Consider a non-resident founder who forms a Delaware LLC, pays the $110 Certificate of Formation fee, obtains a free EIN by filing Form SS-4 with a roughly 8 to 10 business day turnaround, and opens a Mercury account to receive card payments from a worldwide audience. The product is a $19 per month analytics tool sold through a simple hosted checkout. In the first quarter of selling, the founder makes 40 sales in total, of which 12 are to EU consumers buying on personal cards and 6 are to EU companies that supplied valid, verifiable VAT numbers at checkout. The remaining 22 sales are to customers outside the EU, who fall entirely outside this particular tax regime and need no VAT treatment at all under these rules. Already the founder can see that European VAT touches only a portion of total sales, which helps put the size of the task in proportion before deciding how much effort to spend on it.

The 6 company sales fall under the reverse charge, so the LLC charges no VAT on them and instead keeps a record of each validated VAT number as evidence supporting that treatment. The 12 consumer sales are consumer sales and carry VAT at each buyer's national rate. If those consumers sit in countries with standard rates in the rough range of 20% to 23%, the founder either added the VAT on top of the $19 advertised price at checkout or, more commonly when a flat headline price is shown to everyone, effectively absorbed the VAT out of the $19. Either way, the VAT portion of those payments is not revenue belonging to the business. It is money held on behalf of European tax authorities and later remitted through the OSS return, and treating it as spendable cash would create a shortfall when the payment falls due. Setting that portion aside as it arrives, rather than discovering the gap at filing time, is the habit that keeps the example from turning into a cash crunch.

By the end of the year the founder files an OSS return for each relevant period, reporting the per country VAT collected and paying it to the chosen member state of identification, denominated in euro. Separately, and on a completely different timeline, the founder still handles the US obligations attached to the same company. There is the $300 flat Delaware franchise tax due 1 June, and the annual Form 5472 filed together with a pro forma 1120, the latter carrying a $25,000 penalty if it is missed. None of those US items change because of OSS, and OSS does not change because of them. The example illustrates the central theme of this entry, which is that two independent compliance tracks run side by side from the very same set of underlying sales, and each must be tended on its own schedule. A founder who internalizes that picture early stops expecting one filing to satisfy the other and instead plans for both, which is exactly the mindset the rest of this entry is trying to build.

Pricing: VAT Inclusive Versus VAT Exclusive

One decision that quietly shapes your margins is whether your advertised price includes VAT or sits on top of it. EU consumer protection norms generally expect prices shown to consumers to be tax inclusive, meaning the number displayed on your pricing page is the total the buyer pays, with no surprise additions at the final step. If your page advertises a single flat figure to a global audience, an EU consumer paying that figure is effectively having VAT carved out of it after the fact, which lowers your net take on those specific sales compared with an identical sale to a buyer outside the EU. Over a large volume of European consumer transactions, that carved-out portion adds up to a meaningful difference in what you actually keep, and a founder who never models it may be surprised at how much thinner European margins are than they assumed when setting one global headline price.

The alternative is to display prices excluding VAT and add the correct national rate at checkout once the buyer's country is known from their billing details. This is common in business to business contexts and on platforms that geolocate the buyer automatically. It protects your margin because the VAT is added on top rather than absorbed from within, but it produces a higher final number for EU consumers than for US buyers paying the same headline price, which some founders find awkward for a product marketed at a single global price point. Neither approach is inherently right or wrong, and both are used widely in practice. The point is to choose deliberately and to model the impact across the specific countries where you actually sell, since standard VAT rates vary noticeably from one EU member state to another and the spread between the lowest and highest rates is wide enough to matter to a thin-margin product.

A practical middle path for very small sellers is to advertise one global price, accept that EU consumer sales yield slightly less after VAT, and revisit pricing only once EU revenue becomes a material share of the total. Founders sometimes assume they can simply keep the VAT collected to offset this margin pressure, but that assumption is mistaken and dangerous. Collected VAT is not earnings under any circumstance, and treating it as available cash creates a real shortfall at filing time when the authority expects the full amount handed over. Set the held VAT aside, ideally in a separate ledger line or a sub account within your banking stack, so that the money is actually present and accounted for when the OSS payment comes due rather than having quietly been spent on operating costs in the meantime. The discipline of separating held tax from real revenue is worth establishing while volumes are small, because retrofitting it after the money has already been commingled is far harder.

The Merchant of Record Shortcut

The glossary entry flags a path that a great many small founders take, and it is worth unpacking in detail. Merchant of record services such as Paddle and Lemon Squeezy handle EU VAT compliance on your behalf as part of their core offering. A merchant of record, abbreviated MoR, becomes the legal seller of record to the end customer, stepping into that position so that your Delaware LLC sells to the MoR rather than directly to the consumer. The MoR charges the correct VAT to the buyer, files the relevant returns, and remits the tax across the various jurisdictions, which means your LLC never registers for OSS at all. Instead of receiving the gross payment and then owing VAT out of it, you receive a cleaner payout from the MoR with the European tax already handled upstream before the money ever reaches you. For a founder who would rather not become a part-time tax administrator, this single structural choice removes most of the topic from the daily running of the business.

This arrangement trades convenience for cost and a degree of control. A merchant of record typically charges a higher percentage of each sale than a bare payment processor would, because that elevated fee is buying global tax compliance, fraud screening, and chargeback handling all bundled together rather than just card processing. For a founder selling digital products to a worldwide consumer base across dozens of countries, that premium can be well worth paying, because manual multi country VAT compliance is genuinely involved and time consuming to run correctly. The glossary entry is candid on exactly this point, noting that manual compliance is complex and suggesting that a founder consider a MoR for that very reason. The related merchant-of-record entry in the glossary covers the underlying model in greater depth than space allows here, and reading it alongside this section gives a fuller picture of what you are actually buying when you hand the seller-of-record role to a third party.

There are tradeoffs that go beyond the headline fee. With a merchant of record you generally have less direct control over checkout branding, the customer data you receive, and the timing of your payouts, and you become dependent on the provider's country coverage, supported payment methods, and account policies. Some founders run a hybrid setup, using a MoR for self serve digital sales to consumers while invoicing larger business clients directly under the reverse charge, which keeps the high volume consumer flow simple while preserving direct relationships with major accounts. The right answer depends heavily on your sales volume, your customer mix between consumers and businesses, and how much administrative work you are genuinely willing to own. There is no single configuration that fits every business, and switching approaches later is possible if your needs change, though migrating customers and billing relationships does carry its own friction that is worth weighing before you commit to either path.

How VAT Fits Into Your Banking and Payment Stack

VAT does not exist in isolation from how you actually get paid, and your choices about each interact more than founders expect. A non-resident Delaware LLC commonly uses a fintech account such as Mercury, Wise, Relay, Lili, or Payoneer to receive customer funds, since traditional US branch banking is rarely practical for a founder living abroad. If you sell directly and handle OSS yourself, the gross payment that lands in that account includes the VAT you owe to European authorities. Your banking choice then matters for cash management, because you need a clean and reliable way to separate the portion of each deposit that is genuinely yours from the portion you are merely holding on behalf of the tax authorities until the next remittance. Without that separation, your visible balance overstates how much money you can actually spend, which is a quiet trap for founders who watch their account total rather than a true revenue figure.

Several of these providers support sub accounts or multiple balances, which makes it practical to sweep collected VAT into a dedicated holding bucket as payments arrive rather than letting it blend into your spendable balance. Wise and Payoneer additionally let you hold and convert between currencies, which is directly relevant here because OSS payments are typically made in euro while your headline pricing might be denominated in dollars. Currency timing can swing the euro value of what you owe between the moment you collect and the moment you remit, so converting and parking the VAT close to when you collect it reduces the risk of a shortfall caused purely by an unfavorable exchange rate movement during the intervening weeks. Treating the euro VAT liability as a euro liability, rather than as a dollar one that you will convert at whatever rate happens to apply later, keeps that exchange risk contained and your remittance predictable.

If you instead route sales through a merchant of record, the banking picture simplifies considerably. The MoR handles VAT before paying you, so the funds that reach Mercury or Wise are much closer to true net revenue that you can actually deploy in the business. This is one underappreciated reason small founders favor a MoR even setting aside the compliance burden, because it keeps the bank ledger clean and removes the need to reconcile held VAT against advertised prices every period. Whichever route you choose, the durable habit that keeps VAT accounting honest is reconciling your processor or MoR reports against your bank deposits each period, so that the money you think you collected, the money you actually received, and the money you owe all line up against one another rather than drifting apart unnoticed over months. That reconciliation is unglamorous, but it is the single practice most likely to catch a problem while it is still small enough to fix easily.

Registration Thresholds and the Idea of Early Liability

A frequent and comfortable misunderstanding is that there must be a generous revenue threshold below which a non-EU seller can simply ignore EU VAT entirely. The domestic distance selling thresholds that EU based sellers sometimes rely on do not work the same way for a business established outside the European Union. For a non-Union seller of digital services to EU consumers, the obligation can attach from early sales rather than only after crossing some large turnover figure that conveniently gives a long grace period. Because the precise rules and any applicable figures change over time, you should confirm the current position against an official EU source or a qualified adviser before concluding that you are exempt, rather than relying on a half-remembered threshold from an old article that may have described a different scheme or a different category of seller entirely.

This is a large part of why many founders either register for OSS once meaningful EU consumer revenue begins or route those consumer sales through a merchant of record from the very first day. Waiting until some large threshold is supposedly crossed, on the assumption that small sellers are quietly ignored, can leave a backlog of uncollected VAT that is awkward and time consuming to remedy after the fact. It is generally far easier to design the collection step directly into your checkout from the start than to reconstruct, months or even years later, who owed what across many different countries from incomplete records. The earlier the collection mechanism exists in your sales flow, the less painful the whole topic becomes, because the system simply runs quietly in the background as sales happen rather than demanding a stressful cleanup project once the numbers have grown.

None of this should be read as a directive that you must register immediately or that any specific number is guaranteed to apply to your particular circumstances. The practical takeaway is more modest and more useful than that. EU VAT for non-Union digital sellers tends to apply earlier than US founders intuitively expect, so it is worth deciding your approach, whether direct OSS registration or reliance on a MoR, around the time you first start actively marketing to European consumers rather than treating it as a problem to be solved at some undefined later date. Making the decision early is mostly about avoiding a cleanup project, and the decision itself can be revisited as your volume and customer mix evolve. The cost of deciding early is small, while the cost of discovering an accumulated obligation after the fact can be considerable in both time and money.

Evidence, Invoicing, and Record Keeping

EU VAT compliance is as much about records as it is about rates, and underestimating the record keeping side is a common trap for founders who focus only on the numbers. To apply the correct national VAT, you generally need to establish where each consumer is located, and to apply the reverse charge to a business sale, you generally need to hold a validated VAT number for that buyer. The customary approach for consumer location is to collect at least two non contradictory pieces of evidence, such as the billing address and the country indicated by the buyer's IP address, and to retain that evidence stored alongside the transaction record. This pairing of evidence is the backbone of being able to defend your treatment of any given sale if it is ever questioned later by an authority, and it is far easier to capture at the moment of sale than to reconstruct afterward from fragments.

Invoices also carry specific expectations that differ from a plain US receipt. A compliant EU style invoice generally shows the VAT rate applied, the VAT amount in money terms, the identities of the parties involved, and, for reverse charge sales, a clear note indicating that the reverse charge applies together with the buyer's VAT number. For a small Delaware LLC, the checkout platform or billing tool usually generates these documents automatically once it has been configured correctly, which is one more reason founders tend to lean on dedicated tooling rather than handcrafting invoices in a spreadsheet that is easy to get subtly wrong. The obligation to retain these records, often for a period of several years, sits with the seller even when the software is the thing that physically produces the documents on your behalf, so choosing tools that let you export and archive your records cleanly is part of meeting that obligation rather than an afterthought.

Good record keeping also smooths your US side considerably, which is an underrated benefit of doing it well. The very same sales data that feeds an OSS return also feeds your general bookkeeping and, in the end, the financial figures behind your annual Form 5472 and pro forma 1120. Keeping one clean and authoritative source of transaction truth, exported regularly from your processor or your merchant of record, means you are not maintaining two disconnected sets of books that have to be reconciled by hand under deadline pressure. The EU and the US filings ask different questions of the same underlying sales, and a single tidy ledger is capable of answering both sets of questions without forcing you to rebuild the data twice from scratch each time a deadline approaches. Investing a little in clean data early pays off repeatedly, because every future filing draws on the same well-kept record rather than a hurried reconstruction.

Common Misunderstandings Founders Carry In

The first myth worth dismantling is the belief that a US company has nothing to do with European tax. As shown throughout this entry, VAT attaches to the customer's location rather than the seller's, so a Delaware LLC selling to EU consumers can be squarely within scope despite having no European presence of any kind. The second myth is that because the single-member LLC is a disregarded entity in the United States, it must somehow be invisible everywhere else as well. The EU does not recognize US disregarded status for VAT purposes, and it treats the LLC as a taxable person making supplies into Europe. These two myths together account for a large share of the confusion that founders arrive with when they first encounter the topic, and clearing them up early removes a surprising amount of the anxiety that surrounds VAT for newcomers who assumed their US structure shielded them from it.

A third common misunderstanding is conflating VAT with income tax, as though registering for one exposes you to the other. Registering for OSS does not make your LLC liable for European corporate income tax, and it does not create a permanent establishment in Europe by itself. VAT is a pass through consumption tax collected from buyers and handed onward, distinct from any tax on your profit. A fourth misunderstanding is assuming that physical goods and digital goods follow the same lane through the system. They do not. Pure digital services run through the OSS scheme, while low value physical imports run through the separate IOSS scheme, which has its own distinct rules that most software and content sellers never need to touch at all. Mixing these up leads founders to research the wrong scheme entirely and then apply rules that were never meant for their kind of product.

A fifth, and genuinely costly, misunderstanding is treating collected VAT as profit that you have earned. Money charged to a buyer as VAT belongs to the relevant tax authority and is effectively held in trust, not earned by you in any meaningful sense. Founders who spend it as though it were revenue face an unwelcome gap when the return eventually comes due and the full amount is expected to be handed over. Recognizing these five patterns early, namely that VAT follows the buyer, that disregarded status is a US only concept, that VAT is not income tax, that digital and physical goods differ, and that collected VAT is never yours to keep, removes most of the fog that surrounds this topic for someone approaching it for the first time. Each of these is simple once stated plainly, yet each is a mistake that founders routinely make precisely because the system is unfamiliar and counterintuitive at first encounter.

How VAT Connects to Your Formation and Compliance Calendar

It helps to see EU VAT as one lane within a wider compliance calendar rather than as an isolated standalone chore that lives off on its own. Your Delaware formation begins with the $110 Certificate of Formation and a free EIN obtained by filing Form SS-4, which usually takes roughly 8 to 10 business days to come back. Once the company is formed, the recurring US duties include the $300 flat franchise tax due 1 June each year and the annual Form 5472 filed alongside a pro forma 1120, the latter carrying a $25,000 penalty for non filing. These dates are fixed and entirely US specific, and importantly they do not move or change in any way because you happen to have European customers buying your product. Seeing them written out together makes it obvious that the US side has its own rhythm that VAT neither adds to nor subtracts from, which is exactly the clarity a founder needs to plan the year.

EU VAT, where it applies to your sales, layers a separate periodic rhythm on top of that US calendar. OSS returns follow their own reporting cadence and their own payment deadlines, and the payments are denominated in euro rather than dollars. The two calendars rarely align neatly with one another, which is precisely why founders benefit from maintaining a single shared calendar that lists both the US franchise tax and federal filing dates and any EU VAT return dates side by side in one view. Missing a US deadline and missing an EU deadline are different failures with different consequences attached, but both are equally avoidable through the same basic discipline of writing every relevant date down in one place and reviewing it regularly so that nothing quietly slips past unnoticed until it has become a penalty rather than a reminder. The calendar itself is a small effort that prevents the most avoidable category of problem entirely.

There is one genuinely reassuring simplification on the US ownership side that is worth knowing about. Beneficial ownership information reporting under FinCEN, commonly called the BOI requirement, was exempted for US formed entities such as Delaware LLCs by the FinCEN Interim Final Rule of 26 March 2025. That development removes one compliance box that many non-resident founders previously worried about and budgeted time for. It has no connection to EU VAT in any direction, but it does mean that your overall compliance map is a little less crowded than guidance written before that 2025 rule would lead you to believe. As always, confirm your current obligations against authoritative sources, since rules in both jurisdictions continue to evolve and an exemption granted at one point is not an unconditional permanent guarantee that it will remain unchanged forever. Treating compliance as a thing you check rather than memorize keeps you from acting on a snapshot that has since moved on.

Related Concepts and Where to Go Next

The most directly connected term is merchant of record, which the glossary explicitly links from this entry. Because a MoR can absorb the entire OSS obligation on your behalf, properly understanding that model often resolves the VAT question for a small founder without any direct registration ever being required. Reading the merchant-of-record entry alongside this one gives you the two realistic paths in full, namely registering for OSS yourself and running the compliance directly, or letting a merchant of record carry that compliance for a fee while you focus on building the product. For many small digital businesses the choice between those two paths is the single most consequential VAT decision they will make, and it is worth making it consciously rather than defaulting into one path simply because it was the first option a payment provider happened to offer at signup.

Adjacent ideas that are worth exploring once the basics are clear include the place of supply rules that determine which country's VAT actually applies to a given sale, the reverse charge mechanism that governs business to business transactions, and the distinction between digital services handled under OSS and physical imports handled under IOSS. On the US side, the disregarded entity concept, the Form 5472 filing obligation, and the Delaware franchise tax all help explain why your American and European duties remain stubbornly separate from one another. Each of these threads finally connects back to the same underlying sales data that your business already generates every time a customer checks out, so learning one tends to reinforce the others rather than adding wholly unrelated work to your plate. The topic is more interconnected than it first appears, and a little study in one area tends to make the neighboring areas easier to grasp.

When you are ready to actually act on all of this, the sensible sequence is to first map your real customer mix between EU consumers and EU businesses, then decide between direct OSS registration and using a merchant of record, and finally configure your checkout to collect location evidence and to validate VAT numbers accordingly. This entry is general information rather than legal or tax advice, and EU rules genuinely do change over time, so verify the specifics with an official EU tax resource or a qualified professional before you register or remit anything based on what you read here. The aim throughout has been to make the overall landscape legible enough that, whichever route you finally choose, you are choosing it on purpose and with open eyes rather than stumbling into it after a surprise question from a customer who expected paperwork you had not prepared. That clarity, more than any single rule, is what turns VAT from a source of dread into a routine part of running a digital business across borders.

Related terms

Merchant of record (MoR)

Related glossary terms & guides

Form your LLC WhatsApp

WhatsApp Form your LLC