Singuard Home Blog Contact eTrader eTrader for Businesses eTrader for Traders Broker Broker CRM Live Demo Prop Firm Prop Firm CRM Live Demo
Licenses & Regulation

Running an Offshore and an EU Entity Together.

Two companies, one brand, one trading platform. The structure is common and legal in the right shape, and it fails for reasons that have nothing to do with how the licences were obtained.

Alex Onta, Executive Director, SINGUARD By August 28, 2026 7 min read

A firm holds an EU investment firm licence in one member state and an offshore dealer registration in the Caribbean or the Indian Ocean. One website, one platform, one support desk. Onboarding sorts each applicant into one of the two companies depending on residence. This is the shape most growing retail brokers end up in, and it is a legitimate shape. It also fails audits more often than any other structure, and rarely because of the paperwork behind either licence.

The failure is almost always at the boundary: who marketed to whom, from where, using which company's name, and whether a paper trail exists that says so.

What the second entity actually buys

An EU licence buys permissions inside the EU and the ability to notify other member states under the passport regime. It comes with capital scaled to the permissions held, a local presence, appointed function holders, ongoing reporting and a compensation scheme. An offshore registration buys the ability to contract with clients in territories where the local rule set is thin or where the client's own regulator does not claim jurisdiction over a foreign counterparty.

What an offshore entity does not buy is EU clients. That is the single most common misreading. The rules that matter there are not incorporation rules, they are solicitation rules: an EU resident may in narrow circumstances approach a third country firm entirely on their own initiative, but the moment the firm advertises, runs affiliates, pays for search placement or emails a prospect in that market, the exemption is gone. We wrote about that boundary in detail in reverse solicitation and in marketing offshore entities to EU clients.

So the honest framing of the dual structure: the offshore entity serves markets the EU entity cannot economically serve, at leverage and product terms the EU entity is not permitted to offer, to clients who are not in the EU. Anything wider than that is a bet against an enforcement action.

The boundary has to exist in systems, not in a memo

Regulators and, increasingly, banks ask for evidence rather than intent. The questions are practical. Which entity's name is on the client agreement the trader accepted, and is the accepted version retrievable? Which entity's bank account received the deposit? Which entity issued the statement? Which advertising account paid for the campaign that produced the lead, and which countries did it exclude?

If your CRM stores one client record with a single set of terms and the entity is decided later by an operations person, you do not have a boundary. You have a habit. The record has to carry the entity from the first touch, and the trading accounts, ledgers, statements and communications under it have to inherit that value. Systems built for one operating company usually cannot do this without a rebuild, which is why the structure question should be settled before the software is chosen and not after.

Nothing here is legal or tax advice. Group structures touch securities law, company law, tax residence and data protection at the same time, and the answers differ by member state. Take advice from counsel qualified in each jurisdiction before you incorporate anything.

How banks and payment providers read the structure

Financial counterparties do not see two independent companies. They see a group, and they price the group by its weakest member. A bank onboarding the EU entity will ask about ultimate beneficial owners, and the offshore entity appears in the same ownership chart. Compliance then applies its jurisdiction risk rating to that second company, checks whether its home territory appears on any monitoring list, and asks what proportion of group revenue comes from it.

Card acquirers apply the same logic through a different mechanism. High risk merchant categories already carry underwriting scrutiny, and the acquirer's underwriter wants to know which legal entity is the merchant of record, whether the descriptor matches that entity, and whether refunds and chargebacks land against the same balance sheet. A mismatch between the entity on the website terms and the entity on the card statement is a well known trigger for review. The general pattern is covered in which licences banks actually accept and in correspondent banking de-risking.

The result many founders find surprising: adding an EU licence to an offshore book does not automatically fix banking. It gives you a credible entity to bank, but only if the offshore side of the group is small, clearly separated, and demonstrably not selling into regulated markets.

Intragroup contracts and the substance question

The two companies will exchange services. One holds the platform licence, one employs the support staff, one owns the brand. Each of those needs a written agreement with a price that an unrelated party would plausibly pay, because tax authorities test intragroup pricing and because regulators test outsourcing arrangements against their own rules on delegation and oversight.

The substance question follows from the same place. An entity that exists only as a certificate, with a nominee director, no local decision making and no staff, is treated as an extension of wherever the decisions are actually taken. That has consequences for tax residence, for whether a regulator considers the offshore firm to be operating in its territory, and for whether the offshore licence is renewed at all. See offshore substance requirements for what regulators have started to ask for.

Where the structure usually breaks

Four points, in the order we see them go wrong. Affiliates, because a partner runs traffic into a country the offshore entity is not allowed to touch and the firm finds out from a complaint. Support, because an agent answers a question about the offshore entity from a desk inside the EU. Statements, because the branded PDF carries the wrong company number. Payouts, because the money leaves an account belonging to the entity the client never contracted with.

All four are operational, and all four are fixable in software before they become a filing. Firms serving the region from an EU base often anchor the licensed side in Cyprus or Malta and keep the group's commercial team elsewhere, which is workable as long as the marketing rules are honoured by market rather than by convenience. Our note on Cyprus as a base covers the operating side of that choice.

The structure is not a trick. It is a way of serving two very different rule sets without pretending one of them applies to both. Firms that treat it that way keep it. Firms that treat the offshore entity as a way around the EU rules lose the EU licence, which was the valuable one.

"The offshore company is the easy part. The hard part is proving, two years later, that the client who signed with it was never sold to from Frankfurt."

— Alex Onta, Executive Director, SINGUARD

Key Takeaways

Frequently Asked Questions

Can an offshore entity accept EU clients if they sign up themselves?

Only in the narrow circumstances the reverse solicitation rules allow, where the client approaches the firm entirely on their own initiative and the firm has not advertised, promoted or otherwise solicited in that market. Any marketing activity aimed at the market removes the exemption, and the burden of proving otherwise sits with the firm. Take local legal advice before relying on it.

Does holding an EU licence make banking easier for the offshore entity?

Not directly. Banks assess the ownership chain, so the offshore company appears in the file for the EU company as well. A regulated entity gives you a credible applicant, but the group's jurisdiction mix, revenue split and client geography still drive the risk rating and the decision.

Which entity should own the trading platform and the CRM?

Usually one group company licenses the technology and provides it to the other under a written intragroup agreement priced on arm's length terms. What matters operationally is that the software can hold the entity on the client record and carry it through terms, ledgers, statements and payouts.


About the Author

Alex Onta, Executive Director, SINGUARD
Alex Onta Executive Director, SINGUARD

Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.

Your Own Trading Firm, Live in 24 Hours.

SINGUARD builds the technology behind brokers and prop firms: trading platform, CRM, client portal and payment rails, one bundle, one predictable price. Book a call and see it working, or keep reading the guides.

More in Licenses & Regulation