LLC in Delaware, Income in Europe — Now What?

Draw your entity structure on paper. One box per entity, lines connecting them, jurisdictions labeled. Clean. Logical, even.

Now draw where your income actually flows. Which entity invoices which clients. Where the money lands first. How it moves between accounts.

I've done this exercise myself across four jurisdictions. The two maps never matched. The gap between them is where every structural problem I've had started.

The entity chart shows design. The income flow shows reality.

Most multi-entity structures get built one decision at a time. A US LLC for the first product. A Singapore entity when the Asian market opened up. A holding company because an advisor suggested it.

Each addition made sense in isolation. None of them were designed to work together.

Income doesn't follow the org chart. A German client pays the US entity because that's where Stripe lives. Revenue from a product built by contractors in Portugal flows through Singapore because that's where the IP was assigned on paper. The formal structure says one thing. The money says another. Both are real, but they tell different stories to different examiners.

Three mismatches I keep seeing

1. The invoice mismatch

Entity A is the operating company. Entity B holds IP. Invoices go out from Entity A for products built on Entity B's IP, but there's no licensing agreement, no transfer pricing documentation, no formal arrangement connecting the two.

Operationally, this works fine. Revenue arrives, products ship. Structurally, the income path doesn't match the entity purpose. Entity B's IP generates value that Entity A captures, and nobody documented the bridge between them. That missing bridge is a transfer pricing gap that triggers compliance obligations in both jurisdictions, regardless of entity size.

2. The bank account mismatch

Income from multiple entities funnels into one bank account because it was easier to set up that way. Or the founder's personal account becomes a transit point between entities in different jurisdictions.

Banks don't care about your org chart. When a bank sees income from five countries flowing into one account attached to one entity, the question isn't profitability. It's whether the account structure matches the entity structure. If it doesn't, the bank's interpretation of what's happening will differ from yours. The Mercury vs. Wise vs. Relay comparison covers how each platform handles multi-entity, multi-jurisdiction accounts.

3. The jurisdiction mismatch

Entity registered in Singapore. Founder living in Portugal. Clients in the US. Revenue processed through a US-based payment platform.

Each jurisdiction has its own view of where this income originates, where value is created, and who owes what. Singapore sees its entity. Portugal sees the founder doing all the work there, which is a permanent establishment question most CPAs don't even raise. Stripe sees a US transaction.

Three countries, three interpretations, one income stream.

Why this gap matters

The distance between your entity map and income map creates real exposure:

• Tax authorities see income flowing to entities that don't match where economic activity happens. Transfer pricing questions follow.
• Banks see account activity that doesn't match the entity's stated purpose or jurisdiction. Enhanced due diligence follows.
• Payment processors see transaction patterns that don't fit the account holder's profile. Risk reviews follow. More on this in why your Stripe dashboard is not a structure.

Nobody sees the full picture. Each examiner sees one slice, and each slice tells a different story. The risk isn't that any single relationship is wrong. It's that the stories contradict each other.

Mapping the gap

The first step isn't restructuring. It's seeing the gap clearly.

Which entities generate revenue? Which ones receive it? Where does value creation actually happen, not on the org chart, but in practice? Are the connections between entities documented, or do they exist only in your head? That documentation gap between what founders know and what authorities can see is usually widest at these inter-entity junctions.

Global Solo's META framework maps four dimensions: how Money moves through the structure, what Entity boundaries formally exist, where Tax positions intersect with operational reality, and whether the Accountability documentation supports the story connecting them.

The output is a clear picture of where your entity map and income map diverge, before someone else draws that picture for you. If you're evaluating entity decisions from scratch, the entity decision framework covers the key structural choices and what they mean downstream.

References

• IRS — Transfer Pricing
• OECD — Transfer Pricing Guidelines
• OECD — Permanent Establishment (Article 5, Model Tax Convention)
• Singapore ACRA — Business Registration
• Delaware Division of Corporations — LLC Formation
• Stripe — Global Payments
• Wise — Multi-Currency Accounts

---

Visual: Entity Map vs. Income Map Mismatch

Key Takeaways

• Entity structures built one decision at a time rarely match how income actually flows. Clients pay whichever entity has the Stripe account, not whichever entity the org chart says.
• Watch for three mismatches: invoicing from Entity A for Entity B's IP without licensing, funneling multiple entities into one bank account, and operating across jurisdictions with no documented connection between them.
• Tax authorities, banks, and payment processors each see a different slice of your structure. The risk isn't any single relationship. It's that the stories contradict each other.
• If the connections between your entities exist only in your head, they're invisible to every examiner who matters.

Check your risk profile →