Real scenario · Germany × SaaS

B2B SaaS founder from Germany forming a Delaware LLC

A Berlin-based B2B SaaS founder forms a Delaware LLC for US-enterprise contracting alongside the German GmbH.

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

B2B SaaS founder from Germany forming a Delaware LLC

The challenge

Berlin SaaS founder with US enterprise customers. German transfer-pricing rules under § 1 AStG apply.

Banking path

All major banks approve. Mercury typical primary.

Tax compliance path

Germany-US treaty applies. Engage German Steuerberater for intercompany pricing documentation.

Formation path with Delewarellc

Standard 8-10 day timeline. German GmbH retained for EU customers and team.

Outcome

German SaaS founder operates US-LLC for US revenue, GmbH for EU operations, intercompany services agreement.

Why German B2B SaaS founders look toward Delaware

A German B2B SaaS founder usually arrives at the idea of a Delaware LLC after a US customer asks an awkward question on a procurement call. The buyer wants to pay a US entity, sign a US-governed contract, and route invoices through a US accounts-payable system. From Berlin, Munich, or Hamburg, the founder realizes that a GmbH alone makes every US deal feel foreign to the people approving the budget. A Delaware LLC removes that friction by giving the American buyer a familiar counterparty that fits cleanly into their vendor onboarding.

The appeal is not about leaving Germany. It is about meeting the US market where it already operates. Delaware corporate law is the reference framework that US investors, banks, and enterprise legal teams expect, so a Delaware LLC is rarely questioned. For a SaaS company selling annual subscriptions to US enterprises, the entity becomes the contracting party, the merchant of record for US card payments, and the name on the W-9 that procurement requests before they release a payment.

German founders also value the predictability. The Certificate of Formation costs $110, the franchise tax is a flat $300 due each June 1, and the obligations are knowable in advance. After years of navigating German registration and notarization steps for the GmbH, the lighter administrative weight of a single-member LLC feels manageable to run from a European time zone without a US office or US staff.

The realistic banking approval picture from Germany

Germany sits in a favorable position for US fintech onboarding. It is a European Union member, a member of the Financial Action Task Force, and not on any sanctions or high-risk list, so the automated risk screening at US banking platforms treats a German resident as low concern. In practice this means a German founder forming a Delaware LLC can expect a smooth path with Mercury as the typical primary account, and Wise, Relay, Lili, or Payoneer available as secondary or backup options depending on how the founder wants to handle currency.

Approval still depends on completing the application carefully rather than on nationality. The platforms want the EIN confirmation, the Delaware Certificate of Formation, a clear description of the SaaS business, and a German passport plus proof of German address. Where applications stall, it is usually because the business description was vague, the founder listed a personal email instead of a domain email, or the stated activity did not match the website. A B2B SaaS founder who can point to a live product page and name a few US prospects gives the reviewer everything they need.

A practical sequence is to open Mercury first for US dollar operations and US customer payments, then add Wise to hold euros and convert at interbank rates when moving money back to the GmbH or a personal German account. Holding two rails from the start avoids the situation where one platform freezes a review and the founder has no way to receive a customer payment in the meantime.

How a B2B SaaS company earns and what that means for the entity

B2B SaaS revenue is recurring and contractual, which shapes how the Delaware LLC should be positioned. The typical pattern is annual or multi-year subscription agreements, sometimes with usage-based overage, billed in US dollars to American companies. The LLC signs the master subscription agreement, issues the invoice, and collects the payment, while the underlying software development and support may continue to happen inside the German GmbH with its engineering team.

Because the income is service and license revenue rather than physical goods, there is no inventory, no customs, and no shipping logistics to manage. That simplifies the operational side enormously. What matters instead is the contractual chain: who owns the software intellectual property, who employs the engineers, and which entity carries the customer relationship. For a German SaaS founder, the cleanest answer is usually that the GmbH owns the IP and licenses it, while the US LLC handles US customer contracting and US dollar collection.

This earning model also affects how revenue is recognized across the two entities. If the LLC collects $200,000 in annual contracts but the real work is performed in Germany, the money cannot simply sit in the US account as profit. An intercompany services or license agreement has to move value to the GmbH in a defensible way, which is where German tax rules and treaty mechanics enter the picture in the next sections.

How the income is taxed across the German-US line

A single-member Delaware LLC owned by a German resident is, by default, a disregarded entity for US federal income tax. That means the US does not tax the LLC as a separate corporation. The question becomes whether the LLC has income that is effectively connected with a US trade or business and whether the founder has a US permanent establishment under the Germany-US income tax treaty. For a SaaS founder running everything from Berlin with no US office, no US employees, and no US dependent agent, the usual conclusion is no US permanent establishment, so the business profits are taxed in Germany.

The treaty is the anchor here. Under the Germany-US treaty, business profits are taxable in the US only to the extent they are attributable to a US permanent establishment. A server, a payment processor, or a registered agent in Delaware does not by itself create one. This is why so many German SaaS founders can operate a US LLC for US revenue while reporting and paying tax in Germany. The structure is not a way to avoid German tax. It is a way to contract in dollars while German taxation continues to apply.

Because the precise treatment depends on facts that the founder controls, this is the part to confirm with a German Steuerberater before the first large contract closes. The advisor will look at where decisions are made, where the people are, and how the intercompany agreement is written. Getting this characterization right early prevents a later dispute about whether profit was parked offshore.

German transfer pricing and the intercompany services agreement

The single sharpest issue for a German SaaS founder with a US LLC is transfer pricing. German rules require that transactions between related parties be priced as if they were between independent companies. When the US LLC collects revenue but the GmbH performs the development and support, the value that flows between them has to reflect what an unrelated party would pay. German tax authorities expect documentation that explains the pricing and demonstrates that the German entity is fairly compensated for the functions it performs and the risks it bears.

The practical instrument is a written intercompany services or license agreement between the LLC and the GmbH. It should describe what each entity does, who owns the software, how the fee is calculated, and on what schedule money moves. A common approach compensates the GmbH on a cost-plus basis for engineering and support, leaving the LLC with a routine return for its contracting and collection role. The exact method should be chosen with the Steuerberater so it matches the real functions rather than a tax-driven story.

Skipping this step is the most expensive mistake in this profile. If the LLC accumulates profit that the German team actually generated, a German audit can reallocate that income to the GmbH and assess back tax plus interest. Documentation written before the money moves is cheap. Reconstructing a defensible position after an audit notice is not. A German founder should treat the intercompany agreement as core infrastructure, not paperwork to handle later.

The Form 5472 duty every foreign-owned LLC carries

A German founder who owns a US LLC has a US filing obligation that has nothing to do with whether the LLC owes any US tax. A foreign-owned single-member LLC that is a disregarded entity must file Form 5472 attached to a pro forma Form 1120 each year. This form reports reportable transactions between the LLC and its foreign owner, which includes capital contributions the founder makes into the LLC, distributions back out, and amounts paid under the intercompany agreement. The form is informational, but the duty to file is strict.

The reason this matters so much is the penalty. Failure to file Form 5472, or filing it late or incomplete, carries a penalty of $25,000. This is not scaled to the size of the business, so a tiny early-stage SaaS LLC with two US customers faces the same exposure as a large one. Many German founders are surprised by this because the GmbH world does not have an equivalent standalone information return with a fixed penalty of that size attached to a disregarded entity.

The filing is due with the LLC's annual return on the standard US schedule, and it requires the LLC to have an EIN. Because the founder is reporting transactions with himself, the records have to be clean: every contribution into the US account and every transfer back to Germany should be traceable. A German SaaS founder who keeps a simple ledger of intercompany movements through the year makes the Form 5472 a short exercise rather than a scramble.

The formation timeline seen from the German time zone

From Germany, the formation runs across a six-hour gap with Delaware in the Eastern US time zone, which actually works in the founder's favor for parts of the process. A German founder who submits documents in the morning is reaching US systems before the US workday starts, and replies often land back by the German evening. The core timeline is the standard 8 to 10 business days, driven mostly by the EIN step rather than the entity itself.

The first step is filing the Certificate of Formation with Delaware, which establishes the LLC and costs $110. This part is fast and can complete within a day or two. The longer wait is the EIN, the federal tax identification number obtained for free by filing Form SS-4. For a foreign founder without a US Social Security Number, the EIN typically takes about 8 to 10 business days because it cannot be issued through the instant online tool and must be processed by the IRS through fax or mail handling.

A German founder should plan around that EIN window because nearly everything downstream depends on it. Banking applications, Stripe or other payment processing, and the first customer invoice all need the EIN in hand. The sensible move is to start formation well before a US contract is due to be signed, so that by the time a German founder is shaking hands on a deal in Berlin, the EIN, the bank account, and the payment processor are already live and waiting.

Currency, the euro, and moving money home

A German SaaS founder operates across two currencies by design. US customers pay in dollars into the US LLC account, but the founder's costs, the GmbH payroll, and personal life are in euros. The exchange between the two is a recurring operational decision, not a one-time event, and the margin lost on conversion can quietly add up over a year of subscription collections. This is where holding more than one banking rail pays off.

The common pattern is to receive and hold US dollars in Mercury, then use Wise to convert to euros at rates close to the interbank mid-market rate when moving money to Germany. Keeping a dollar balance lets the founder time conversions rather than being forced to convert every incoming payment immediately. For a business with predictable annual contracts, this means the founder can convert in planned batches that align with when the GmbH actually needs euros for payroll or supplier costs.

Repatriation itself follows the intercompany agreement. Money moving from the US LLC to the German GmbH should be characterized as payment for services or license fees under the written agreement, which keeps the transfer documented and consistent with the transfer-pricing position. Distributions to the founder personally are a separate path and a reportable transaction on Form 5472. Treating both flows deliberately, rather than ad hoc transfers whenever the US account looks full, keeps the German tax picture defensible.

VAT, German invoicing, and the US sales tax question

German founders carry strong instincts about VAT from running a GmbH, and those instincts need adjusting for the US side. The United States has no VAT. Instead, US states operate sales tax, and most states treat pure software-as-a-service differently from physical goods. Some states tax SaaS, others do not, and the obligation generally only arises once the business crosses an economic nexus threshold of sales or transactions into a given state. A German SaaS founder selling to US enterprises should track where customers are located but does not face a single national US consumption tax to register for.

On the European side, supplies of services between the GmbH and EU business customers continue under German VAT rules, and the reverse-charge mechanism often applies for cross-border B2B services within the EU. The introduction of a US LLC does not erase any of this. The GmbH keeps its German VAT registration and its EU obligations, while the US LLC handles US customer billing where US sales tax, not VAT, is the relevant concept.

The practical guidance is to keep the two systems mentally and operationally separate. US customer invoices come from the US LLC and follow US sales tax logic per state. EU customer invoices come from the GmbH and follow VAT and reverse-charge logic. A founder who tries to apply German VAT habits to US invoices, or who assumes the US has a VAT to reclaim, will create confusion that a German Steuerberater and a US accountant can prevent with a short setup conversation.

Why BOI reporting no longer applies to this LLC

For a while, beneficial ownership information reporting under the US Corporate Transparency Act was a live concern for foreign founders of US entities, and many German founders heard alarming things about deadlines and personal disclosure to FinCEN. That concern has changed. Under the FinCEN Interim Final Rule issued on March 26 2025, US-formed entities, including a Delaware LLC, are exempt from the BOI reporting requirement. A German founder forming a Delaware LLC does not have a BOI filing to make.

This matters for planning because it removes a step that older guides and forum posts still describe. A German SaaS founder reading material written before that rule may believe they must report their ownership to FinCEN within a short window after formation. For a US-formed LLC that is no longer the case, so the founder should not act on outdated instructions or pay a provider to file something that is not required.

What remains in force are the obligations covered elsewhere here: the franchise tax of $300 due June 1, the annual Form 5472 with its $25,000 penalty for non-filing, and the German-side reporting through the Steuerberater. BOI simply is not on that list for a Delaware LLC. Knowing which obligations are real and which have been removed keeps a German founder from spending effort on the wrong things.

Common mistakes for the German SaaS profile

The first recurring mistake is letting the US LLC accumulate profit that the German engineering team actually generated. Without a written intercompany agreement and transfer-pricing documentation, this looks to a German auditor like income shifted out of Germany, and it can be reallocated with back tax and interest. The fix is structural and cheap if done early: define the functions, price them at arm's length, and move money under a documented agreement from the first large contract.

The second mistake is treating the EIN as instant. German founders used to fast online registration sometimes promise a US customer they can invoice next week, then discover the EIN for a foreign-owned LLC takes about 8 to 10 business days and that banking and Stripe cannot start without it. Building the timeline backward from the contract signing date, with the EIN window included, prevents an embarrassing gap where the company exists but cannot collect money.

The third mistake is ignoring the Form 5472 obligation because the LLC owes no US tax. The $25,000 penalty applies to the failure to file the information return, independent of any tax due. A fourth, smaller error is acting on outdated BOI advice and filing or paying for something no longer required after the March 26 2025 rule. None of these are hard to avoid. They simply require knowing the German-US specifics rather than assuming US rules mirror the GmbH world.

A practical step-by-step for a German SaaS founder

Start by confirming the structure with a German Steuerberater before filing anything. Decide whether the GmbH keeps the software IP and licenses it, or whether the LLC takes a contracting and collection role, and agree on how the intercompany fee will be calculated. This conversation defines the transfer-pricing position and shapes every money flow that follows, so it belongs at the front of the process rather than after the accounts are open.

Next, form the Delaware LLC by filing the Certificate of Formation for $110, then file Form SS-4 to obtain the EIN for free, allowing about 8 to 10 business days for issuance. Once the EIN arrives, open Mercury as the primary US dollar account and add Wise for euro conversion and repatriation, keeping Relay, Lili, or Payoneer in mind as alternatives. With banking live, connect a payment processor and you can begin issuing US dollar invoices to US customers under US-governed contracts.

Finally, run the annual rhythm. Pay the flat $300 franchise tax by June 1 each year, file Form 5472 with the pro forma Form 1120 on schedule to avoid the $25,000 penalty, and keep a clean ledger of every contribution into and distribution out of the LLC plus all intercompany transfers. The whole setup is available at $297 one-time pricing, and once the structure and documentation are in place, a German founder can run US contracting from Berlin alongside the GmbH with predictable, knowable obligations on both sides.

Keeping the two-entity structure healthy over time

A German SaaS founder rarely sets up the US LLC and then forgets about it. The structure stays healthy only if the two entities keep matching reality. As the company grows, the functions can shift: maybe the LLC starts hiring a US-based customer success contractor, or the GmbH spins up a separate support team. Each meaningful change in who does what should prompt a quick review of the intercompany agreement so the pricing still reflects the real division of work between Germany and the US.

Record-keeping is the other half of staying healthy. Because the founder is on both sides of the intercompany transactions, the discipline of logging every transfer with a clear reason pays off at three moments: the annual Form 5472, the German transfer-pricing documentation, and any future due diligence if the founder raises capital or sells. A clean, consistent paper trail turns each of those from a stressful reconstruction into a routine export from records already kept.

The reward for this discipline is optionality. A German founder who maintains a clean US LLC alongside a well-documented GmbH has a structure that US investors recognize, US customers trust, and German tax authorities can follow. That combination is what lets a Berlin SaaS company sell into the US market in dollars while staying fully grounded in Germany, which is the whole point of forming the Delaware LLC in the first place.

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