Most content about cross-border company formation stops at the moment of incorporation, as though registering the entity were the achievement.
In our experience it is the least difficult step. Incorporation in the UK is fast, largely electronic, and well documented. What founders actually struggle with is the operating layer underneath a company that exists in one country while its owner, its customers and its bank are in others.
Here is what that layer consists of, based on the formations we have supported.
An address that works, not just an address that exists
Every jurisdiction requires a registered office. Founders correctly treat this as a box to tick and then discover it is a live operational dependency.
Official correspondence arrives there. Tax notices arrive there. Deadlines arrive there. If that address is a formality that nobody monitors, the first sign of a problem is usually an escalation, not the original notice.
What actually matters is not having an address but having a process attached to it: mail is received, identified, digitised, and routed to someone who understands what it means and when it must be answered.
A compliance calendar that starts before you want it to
The single most underestimated thing about forming a company abroad is that the obligations begin immediately, and they are indifferent to whether the business has started trading.
For a UK company that means annual accounts, a confirmation statement, keeping the company's information accurate as it changes, and the relevant tax registrations. None of these are difficult individually. All of them have dates attached, and the dates do not move.
A company that is registered correctly but never filed is a problem waiting to happen. That is not a hypothetical: it is the most common serious issue we see, and it is almost always caused by a founder who assumed the obligations would begin when revenue did.
Infrastructure that helps here does something simple and unglamorous: it knows the dates, it tells you before they arrive, and it tells you again.
Identity verification that accepts your actual documents
Verification designed for domestic customers tends to assume a domestic document set. Non-resident founders routinely hit checks that cannot process their passport, or that expect a proof of address in a format their country does not issue.
The failure mode is not usually rejection. It is a stalled application with no clear reason and no obvious way forward, which is worse, because there is nothing to correct.
Useful verification infrastructure is explicit about what it needs, accepts the document formats that non-residents actually have, and — when a check cannot be completed automatically — routes to a person who can look at the case rather than returning a generic failure.
Documents in a form other institutions will accept
A founder does not want a certificate of incorporation because it is nice to have. They want it because a bank, a payment provider, a marketplace or a supplier has asked for it, usually with specific requirements about format, recency and certification.
This is where document delivery stops being a file download and becomes an operational problem. The questions that matter are practical: is this the version the bank will accept? Is it recent enough? Does it need certification? Can the founder retrieve it again in eight months when someone else asks?
Banking and payments: be honest about what you control
Founders frequently expect that whoever forms the company will also solve banking. It is worth being precise about this, because vagueness here does real harm.
A formation provider can prepare the documentation a financial institution will ask for, and can explain what the process typically involves. It cannot guarantee that a regulated institution will accept a given customer. Those decisions belong to the institution, are subject to its own obligations, and are not something a formation service can commit to on its behalf.
The right posture is to be clear about the boundary: here is what we do, here is what the licensed institution does, and here is what neither of us controls. Anything less sets up a founder to be surprised at the worst moment.
Communication infrastructure that is actually operated
A company needs a business email domain, and it needs someone to notice what arrives at it.
This sounds trivial until you look at how much of the compliance failure we see traces back to a mailbox nobody read. The notice went to the right address, and the address was not monitored.
At any scale, managed mailboxes stop being a convenience and become part of the compliance system.
What ties it together
Each of these is individually straightforward. The difficulty is that they are usually assembled from separate providers who do not share state.
The formation agent does not know what the accountant knows. The mail-forwarding service does not know what the compliance calendar says. The verification provider does not know which documents were already collected six months ago, so it asks for them again.
The founder becomes the integration layer. They are the only party with the whole picture, which means every gap between providers becomes their problem, and they are the least equipped person to be holding it.
Infrastructure worth building for this market is not another point solution. It is the connective tissue: one record of the company, one set of verified documents, one calendar, and one place where the state of things is visible.
Where this sits at Dorsko
This is a description of the problem our live platforms — anasirket and Dorsko Formations — were built around, and it is the reason our product work moved from delivering formations to building the infrastructure underneath them.
The company formation part is solved. The operating layer is the interesting problem.