Real scenario · Poland × SaaS

B2B SaaS founder from Poland forming a Delaware LLC

A Warsaw-based B2B SaaS founder targeting US enterprise needs a US LLC for Delaware-governed contracts and Stripe subscription billing.

By Zawwad, Founder, DelewarellcPublished May 15, 2026 · Last updated July 5, 2026

B2B SaaS founder from Poland forming a Delaware LLC

The challenge

Warsaw SaaS founder with US enterprise pipeline. Polish IT industry has strong English fluency and EU banking infrastructure; all major US banks generally approve.

Banking path

Polish founders generally see smooth onboarding across the major providers, with Mercury a common primary choice. Approval is always the provider's decision and not guaranteed.

Tax compliance path

Poland-US tax treaty applies. Polish IP Box regime may apply for qualifying IT income. Form 5472 filing required.

Formation path with Delewarellc

Standard 8-10 day timeline. Polish entity (sp. z o.o.) often retained for EU customers and team employment; US LLC handles US customer billing.

Outcome

Polish SaaS founder operates US-LLC for US revenue with clean Mercury banking. Polish sp. z o.o. retained for EU operations and team. Intercompany agreement coordinates the two.

Why a Warsaw SaaS founder reaches for a Delaware LLC

A B2B SaaS company built in Warsaw usually grows up bilingual. The product ships in English, the documentation reads like a US startup wrote it, and the early customers are scattered across both the EU single market and North America. The moment a US prospect moves from a free trial to a signed annual contract, the founder runs into a question that has nothing to do with code. The American buyer wants to pay a US entity, sign under US-governed terms, and route the money through a recognizable US payment stack. A Polish sp. z o.o. invoice with a 26-digit IBAN and a VAT line tends to slow procurement teams down, and in enterprise sales a slow procurement cycle quietly kills deals that the product had already won on merit.

Forming a Delaware LLC is the structural answer to that friction. It gives the founder a US-resident-looking counterparty that can sign order forms, hold a US bank account, and run subscription billing through Stripe without the customer ever having to think about cross-border payment mechanics. The LLC is not a replacement for the Polish company and it is not a tax-avoidance trick. It is a contracting and collection vehicle that sits on top of the existing business so that the US side of the revenue can be earned, banked, and reported in the currency and legal language the US side expects.

The practical effect for a Polish founder is that the sales conversation stops being about where the seller is incorporated and goes back to being about the product. That is the entire point of the structure, and it is worth keeping in view through every administrative step that follows.

The realistic banking approval picture for Poland

Poland sits in a comfortable position for US neobank approval, and that is not an accident of geography. Polish founders typically present clean EU identity documents, a verifiable address inside the European Economic Area, and an IT business profile that US compliance teams have seen many times before. Mercury, Wise, Relay, Lili, and Payoneer all operate with Poland on their accepted-country lists, and the application experience for a Warsaw founder is closer to that of a US applicant than to the heavily scrutinized path founders from sanctioned-adjacent regions face.

In day-to-day reality the approval picture breaks into two layers. Mercury and Relay are full US business checking environments that pair well with Stripe payouts and US-dollar reserves, and they tend to be the accounts a SaaS founder actually operates from. Wise and Payoneer fill the role of currency rails when the founder needs to move money between US dollars and Polish zloty or euro without losing a margin to a traditional bank's spread. Lili is the lightweight option a solo founder might open early before revenue justifies a heavier setup.

What trips Polish applicants up is rarely nationality and almost always documentation hygiene. An EIN confirmation letter that does not match the LLC name on the Certificate of Formation, a residential address that disagrees with the passport, or a vague description of the business will stall an application that would otherwise clear quickly. The fix is to keep every document consistent across the formation, the EIN, and the bank application before the first form is ever submitted.

How a B2B SaaS business actually earns its money

SaaS revenue has a particular shape that matters for how the Delaware LLC is set up. The income is recurring rather than one-off, it arrives as monthly or annual subscriptions, and it is collected almost entirely through a payment processor rather than through wire transfers or invoices paid by hand. For a US-facing B2B product, Stripe is the usual engine, and Stripe wants to pay out to a US bank account tied to a US entity with a US tax identification number. The Delaware LLC plus an EIN plus a Mercury or Relay account is precisely the combination that lets Stripe treat the founder as a normal US merchant.

Because the revenue is subscription-based, the founder is also managing deferred revenue and churn rather than discrete sales. An annual plan paid in January is cash today but service delivered across twelve months, and that timing shapes how the founder thinks about reserves and how the eventual US filing characterizes the activity. Enterprise contracts add another layer, since they often carry net-30 or net-60 payment terms, security questionnaires, and a redlined order form that the US LLC is the natural party to sign.

The key structural decision is which entity earns which dollar. US customer subscriptions flow into the US LLC and its Stripe account. EU customers, with their VAT obligations and preference for a local invoicing entity, generally continue to be served by the Polish company. Drawing that line clearly at the start prevents the messy situation where the same customer base is split across two entities for no defensible reason.

How the income is taxed across two jurisdictions

A single-member Delaware LLC owned by a non-US person is, by default, a disregarded entity for US federal income tax. That phrase does the heavy lifting here. It means the LLC itself does not pay US income tax on its profits, and the profits are instead attributed to the owner. Whether the US gets to tax those profits depends on whether the LLC is engaged in a US trade or business and whether it has income effectively connected to that business. A Polish founder selling software remotely, with no US office, no US employees, and no US dependent agent, frequently lands outside the net of US income taxation on the business profit, though that is a determination a CPA must confirm against the specific facts.

On the Polish side, the income does not disappear. A Polish tax resident is taxed on worldwide income, so the profit that the US LLC earns generally remains reportable and taxable in Poland under Polish rules. The Poland-US treaty is the instrument that prevents the same dollar from being taxed twice, allocating taxing rights and providing relief mechanisms. For qualifying IT income, Poland's IP Box regime can reduce the effective rate on income derived from qualifying intellectual property, which is a meaningful consideration for a software company but one that requires Polish tax advice to apply correctly.

The practical takeaway is that a Delaware LLC for a Polish SaaS founder is usually a US compliance and banking structure rather than a US tax structure. The real income tax conversation happens in Warsaw, and skipping that conversation is the most expensive mistake on this list.

The Form 5472 duty that catches founders off guard

Even when the Delaware LLC owes no US income tax, it almost certainly owes the US an information return. A single-member LLC owned by a foreign person and treated as a disregarded entity is a reporting corporation for the purpose of Form 5472, and it must file that form together with a pro forma Form 1120 each year. The form reports reportable transactions between the LLC and its foreign owner, which for a Polish SaaS founder includes capital contributions into the LLC and distributions out of it, as well as any other transactions between the founder and the company.

The reason this matters so much is the penalty. Failure to file Form 5472 on time, or filing it incomplete, carries a penalty of $25,000. That penalty applies regardless of whether the LLC made a profit, and regardless of whether any US tax was due, which is exactly why it surprises people. A founder who correctly concludes that the LLC owes no income tax can still walk into a $25,000 problem by assuming that no tax means no filing.

The filing is not difficult once it is understood as an annual obligation rather than an afterthought. The form is filed with the IRS by the corporate due date, the pro forma 1120 carries the identifying information while the 5472 carries the transaction detail, and the whole package is something most cross-border accountants handle routinely. The discipline is simply to treat it as a fixed yearly event that happens whether or not the business had a good year.

The formation timeline from the Central European time zone

Warsaw runs on Central European Time, which is six hours ahead of US Eastern Time for most of the year. That gap is small enough that it rarely causes real friction, and in some ways it helps. A founder who files paperwork or sends documents at the end of the Polish workday is hitting the Delaware and IRS systems in the middle of the US morning, so requests tend to land during US business hours rather than queuing overnight. The Delaware Division of Corporations and the relevant filing systems operate on US East Coast time, and a Warsaw founder can comfortably plan around that.

The mechanical timeline itself is straightforward. The Certificate of Formation is filed with Delaware at a state fee of $110, and the entity exists once that filing is accepted. The EIN is the part that requires patience. A foreign founder without a US Social Security number obtains the EIN by submitting Form SS-4, and the realistic turnaround runs about 8 to 10 business days. From the Central European vantage point that is a week and a half of waiting, after which the EIN confirmation letter becomes the key that unlocks bank and Stripe applications.

Stacking those steps, a Polish founder who starts the process should expect the formation itself to be quick and the EIN to set the real pace. Banking applications and Stripe onboarding can only begin once the EIN is in hand, so the entire setup from a standing start to a live, billing-capable US entity tends to span a few weeks rather than a few days. Planning for that window prevents the disappointment of expecting to invoice a US customer the same week the LLC is born.

Currency, repatriation, and getting money home to Poland

Once US subscriptions are flowing into the US LLC, the founder faces a currency question that the Polish company never had to solve in the same way. Stripe pays out in US dollars to the US bank account, and the founder lives in a zloty and euro economy. Moving those dollars to Poland efficiently is where Wise and Payoneer earn their place in the stack, since both convert and transfer at rates far closer to the mid-market rate than a traditional bank, and the cost of a careless transfer setup compounds quietly over a year of recurring revenue.

Repatriation from a disregarded single-member LLC is mechanically simple, which is one of the quiet advantages of the structure. Because the LLC is disregarded for US tax, moving money from the LLC to its owner is not a dividend and is not a taxable distribution event at the US level. The founder can move funds from the US LLC account to a personal or Polish business account as a transfer of their own money, with the US side treating it as a reportable transaction on Form 5472 rather than as a taxable payout.

The discipline that keeps this clean is separation. The founder should move money deliberately on a schedule rather than treating the US business account as a personal wallet, and every transfer between the founder and the LLC should be recorded so the year-end Form 5472 can report contributions and distributions accurately. Sloppy commingling does not usually create a tax problem, but it creates a reporting and bookkeeping problem that is tedious to untangle later.

Coordinating the Polish sp. z o.o. with the US LLC

Most Warsaw SaaS founders who form a US LLC do not abandon their Polish company. The sp. z o.o. usually remains the entity that employs the team, holds the EU customer relationships, manages VAT, and serves as the founder's primary tax home. The US LLC is layered on for the US revenue and US contracting. The result is a two-entity structure, and a two-entity structure only works if the relationship between the two is documented rather than improvised.

The instrument that does this is an intercompany agreement. It defines what each entity does, which one owns or licenses the intellectual property, and how money moves between them. A common pattern has the Polish company develop and own the software while licensing it to the US LLC, or has the US LLC pay the Polish company for development and support services. Either arrangement needs to reflect arm's-length pricing so that neither tax authority can argue the profit was parked in the wrong jurisdiction. This is transfer pricing in miniature, and even a small SaaS business benefits from getting the principle right early.

Without that agreement, the two entities look like one pool of money split across two bank accounts for convenience, which is exactly the shape that draws questions from tax authorities. With it, the structure tells a coherent story. The US LLC earns US revenue under US contracts, pays or licenses the Polish company on defined terms, and the Polish company remains the operational and tax center of gravity. Getting a Polish tax advisor and a US-aware accountant to agree on this split is time and money well spent before the revenue scales.

Stripe and the US payment stack for subscriptions

Stripe is usually the deciding reason a Polish SaaS founder wants a US entity at all. Stripe is available in Poland, but a US Stripe account tied to a US LLC and EIN unlocks the US-facing experience that enterprise buyers expect, including US-dollar settlement and the kind of merchant profile that procurement teams treat as routine. Setting it up means giving Stripe the LLC's EIN, the US bank account, and the standard business details, after which subscriptions and invoices run through the same automated machinery a US-based SaaS company uses.

The practical sequence is that Stripe sits downstream of the EIN and the bank account, not upstream of them. A founder cannot meaningfully onboard the US Stripe account until the EIN confirmation letter exists and the Mercury or Relay account is open to receive payouts. This is why the EIN wait shapes the whole launch. Everything that touches money, Stripe included, is waiting on that one document.

Beyond Stripe itself, the subscription stack often includes tools for invoicing, dunning, and revenue recognition. None of those change the legal structure, but they all assume a US entity and a US bank account underneath them. Choosing the payment and billing tools after the LLC, EIN, and bank are in place keeps the founder from rebuilding the stack twice, and it keeps the customer-facing payment experience consistent from the first signed contract onward.

The $300 franchise tax and the annual maintenance rhythm

A Delaware LLC is cheap to maintain but not free, and the maintenance is predictable enough that a founder can put it on a calendar and forget about it until the reminder fires. The central recurring obligation is the Delaware franchise tax, which for an LLC is a flat $300 due each year on June 1. It does not scale with revenue, it does not require a complicated calculation, and it is not the same as the corporate franchise tax that uses share-based formulas. For an LLC it is simply $300, on time, every year.

Alongside the franchise tax sits the registered agent. Delaware requires every LLC to maintain a registered agent with a Delaware address to receive legal and state correspondence, and that is an annual cost the founder budgets for separately. Together the franchise tax and the registered agent are the floor of keeping the entity in good standing, and letting either lapse moves the LLC toward administrative trouble that is far more expensive to cure than to prevent.

Layered on top of those state items is the federal Form 5472 filing discussed earlier. Put together, the annual rhythm for a Polish founder is a small set of fixed events. The franchise tax on June 1, the registered agent renewal, and the Form 5472 package filed by its federal due date. None of these is large, but missing any of them is disproportionately costly, so the right mental model is a short annual checklist rather than a set of surprises.

BOI reporting and where it stands for US-formed LLCs

Beneficial ownership information reporting was, for a stretch, one of the most anxiety-inducing topics for foreign founders of US entities. The Corporate Transparency Act introduced a regime requiring companies to report their beneficial owners to FinCEN, and the prospect of a Polish founder having to file personal ownership details into a US federal database raised real questions about privacy and compliance burden. For a while the rules were in flux, with court challenges and shifting deadlines making it hard to know what actually applied.

The position changed with the FinCEN Interim Final Rule of March 26 2025. Under that rule, entities formed in the United States are exempt from the beneficial ownership information reporting requirement. A Delaware LLC is a US-formed entity, so a Polish founder forming one falls within that exemption and does not have a BOI filing obligation for the US LLC under the current framework. This removed a meaningful piece of friction and uncertainty from the structure.

It is still worth understanding the boundary of the exemption. It applies to US-formed entities, which is exactly the situation here, but it does not rewrite every other obligation the founder has. The franchise tax, the Form 5472 filing, and the founder's Polish tax duties all remain. The BOI exemption simply means one specific federal reporting line that once loomed large is, for a US-formed Delaware LLC, not a line the founder has to fill in.

Common mistakes for the Polish SaaS profile

The first recurring mistake is treating the US LLC as a tax shelter rather than a contracting and banking layer. A Polish tax resident remains taxable in Poland on worldwide income, and a founder who assumes the US LLC makes the profit invisible to the Polish authorities is building a problem that grows with every year of revenue. The structure is legitimate when it is transparent on both sides and abused when it is sold as a way to make income disappear, and the difference is entirely in how the founder treats the Polish reporting.

The second mistake is neglecting Form 5472. Because the LLC often owes no US income tax, founders convince themselves there is nothing to file, and then a $25,000 penalty appears for a missed information return. The third mistake is documentation drift, where the name on the Certificate of Formation, the EIN letter, the bank application, and the Stripe account do not perfectly match, which stalls onboarding and can freeze a Stripe payout at the worst possible moment.

The fourth mistake is running the two entities as one undocumented pool of money. Without an intercompany agreement and clean records of contributions and distributions, the founder ends up with a structure that is hard to defend and tedious to report. The fifth, smaller mistake is forgetting the June 1 franchise tax and the registered agent renewal, which are trivial to pay on time and surprisingly costly to fix after the entity has slipped out of good standing. Every one of these is avoidable with a short checklist and the right advisors.

A practical step-by-step for the Warsaw founder

Start by getting the names and addresses right before any filing happens. Decide the exact LLC name, confirm the founder's residential address as it appears on the passport, and write a clear one-line description of the business that will read consistently across every form. Then file the Certificate of Formation with Delaware at the $110 state fee, which brings the entity into existence. With a $297 one-time formation package the filing, registered agent, and the supporting paperwork are handled together, which removes most of the room for the documentation drift that derails later steps.

Next, file Form SS-4 to obtain the EIN, and plan for the roughly 8 to 10 business day turnaround. While that is pending there is little point rushing the banking, since the EIN confirmation letter is required for everything downstream. Once the EIN arrives, open the primary US bank account with Mercury or Relay, add Wise or Payoneer for currency movement, and only then onboard the US Stripe account so subscription billing can begin. Each step depends on the one before it, so the order is not optional.

Finally, set up the ongoing rhythm before it becomes urgent. Engage a Polish tax advisor and a US-aware accountant to define the intercompany relationship between the sp. z o.o. and the US LLC, calendar the $300 Delaware franchise tax for June 1 and the registered agent renewal, and treat the annual Form 5472 plus pro forma 1120 as a fixed event rather than a surprise. With the BOI exemption for US-formed entities in place under the March 26 2025 rule, the maintenance load is genuinely light, and a founder who front-loads the setup spends the rest of the year selling software rather than fighting paperwork.

Related guides for this scenario

Related pages for this scenario

Your scenario, your formation

$297 + Delaware state fee, one-time. WhatsApp the founder in your preferred language.

Form your LLC WhatsApp

WhatsApp Form your LLC