Key Takeaways
4 insights · 8 min readA branch is an extension of the parent company: the same legal person.
So branches share the parent’s TRN, TIN and Peppol ID, and one ASP onboarding covers all of them.
Only a separate legal entity (a subsidiary, or a separately incorporated company) onboards on its own.
Your phase is measured on the whole legal person’s revenue, all branches included.
A branch is part of the same legal person as its parent company, so it uses the parent's TRN, its TIN and its Peppol ID. One ASP onboarding in EmaraTax covers the company and all its branches, whether they're in other emirates or under additional trade licences. Only a separate legal entity, such as a subsidiary, onboards separately with its own TIN.
In this guide
The principleWho's whoOn the invoiceOne ASPStuck profilePhase and allowanceWorked exampleChecklistNext stepThree questions keep coming up about branches: does a branch licence need its own ASP even with the same TRN; what name goes on the e-invoice for a sole establishment with several licences under one TIN; and why a main profile would get stuck when branches are already registered. They all have the same starting point: a branch is not a separate legal person. This guide explains what that means for TRNs, Peppol IDs, onboarding, invoice numbering and your phase. For the TIN itself, see our TIN guide; for set-up, our UAE e-invoicing service.
Does a branch need its own registration?
No. A branch is an extension of its parent company. It isn’t a separate legal person, so it doesn’t get its own TRN, TIN or Peppol ID. The MoF and FTA clarification on e-invoicing makes the same point from the other side: each legal entity onboards with its own TIN, and a pure branch uses its head office’s TIN.
Branches are part of the parent company, one legal person, so one registration does it. Onboard the company once with its ASP, and every branch issues e-invoices under the same TRN and Peppol ID. Only a separate legal entity, like a subsidiary, onboards on its own.
Branch or separate entity: how do you tell?
| Structure | Separate legal person? | E-invoicing |
|---|---|---|
| Branch in another emirate | No | Parent’s TRN, TIN, Peppol ID |
| Additional trade licence, same company | No | Parent’s TRN, TIN, Peppol ID |
| Sole establishment with several licences | No | One TIN for all |
| UAE branch of a foreign company | Part of the foreign legal person | One UAE registration, one onboarding |
| Subsidiary LLC | Yes | Own TRN, TIN, onboarding |
| Separately incorporated free zone company | Yes | Own TRN, TIN, onboarding |
| VAT group member | Yes, each member | Own TIN; not the group’s |
VAT groups are the common confusion: the group shares a VAT TRN, but each member onboards with its own TIN. See e-invoicing for VAT groups.
What goes on a branch’s e-invoice?
| Field | Value |
|---|---|
| Seller name | The legal entity’s legal name |
| Seller TRN / TIN / Peppol ID | The parent’s, for every branch |
| Invoice number | Unique across the legal entity; branch prefixes help |
| Address and branch name | As your system and ASP support; agree the approach |
Invoice numbers must not repeat across branches. A prefix per branch, such as DXB-, SHJ-, AUH-, keeps each series unique and traceable, and makes it easy to see which branch issued an invoice when a customer queries it.
Credit notes follow the same logic: a branch corrects its own invoices with credit notes in the entity’s credit note series, referencing the original invoice, whichever branch issued it.
Can branches use different systems or providers?
This is where branch structures most often go wrong in practice: each branch manager picks software, and nobody notices until onboarding.
A legal entity can be onboarded with only one ASP at a time, so all branches issue through the same provider. Branches can technically run different accounting systems, but each must connect to that one ASP, which multiplies integration work. Most businesses consolidate onto one system before go-live.
Why might a main profile get stuck while “branches” are registered?
A business reported exactly this: its branches were registered with an ASP, but the main profile couldn’t complete onboarding, and the FTA helpline couldn’t resolve it. The usual explanation is that the “branches” were actually separate legal entities with their own TRNs, or that a registration already exists for the same TIN. Check EmaraTax’s Linkage Status for each TIN, confirm which entities are legally separate, and raise a ticket with both the ASP and the FTA. See EmaraTax onboarding.
⚠️ One TIN, one ASP link
If the same TIN is already linked, a second onboarding for it will fail. Offboard or correct the existing link first.
Which revenue and which allowance apply?
| Question | Answer |
|---|---|
| AED 50 million threshold | Measured on the legal person’s revenue, all branches together |
| 100 free e-invoice services | Per end user: the legal entity, not each branch |
| Deadline | One deadline for the entity, covering every branch |
This cuts both ways. Three small branches that each look well below AED 50 million can add up to a legal person above it, which moves the whole company, every branch, into the earlier phase. Add the branches up before you decide your deadline. See which revenue decides your phase.
What does it look like in practice? (worked example)
An illustrative retail company with three branches, one in each of Dubai, Sharjah and Abu Dhabi, each with its own licence:
| Item | Set-up |
|---|---|
| Legal entities | 1 |
| TRN, TIN and Peppol ID | 1 of each |
| ASP onboarding | 1, in EmaraTax |
| Invoice series | DXB-0001, SHJ-0001, AUH-0001 |
| Revenue for phase test | AED 38 million across all three: Phase 2 |
| Set-up cost with Fastlane | AED 299 + VAT, once |
Had the Sharjah outlet been a separate LLC, it would onboard separately with its own TIN and revenue test. Illustrative.
Branches or several licences?
Tell us how your licences are structured on WhatsApp. We’ll confirm which entities onboard and how, free.
What should you check before go-live?
Five checks, in this order, settle almost every branch question before it becomes an onboarding problem:
- Map your legal entities — Not your licences: legal persons.
- One TIN per legal entity — Branches use the parent’s.
- One onboarding per legal entity — With one ASP.
- Unique invoice series — With branch prefixes.
- Test from every branch — Before your mandatory date.
How can Fastlane help?
We map your structure, onboard each legal entity once, set up branch numbering and test from every branch, from AED 299 + VAT through our UAE e-invoicing service; see also our Zoho and Xero pages.