UAE and Hong Kong company roles: how to map each side’s function without country stereotypes

Short answer

If we answer directly, there is no reliable rule that says one function must automatically sit in the UAE and another must automatically sit in Hong Kong. Within the supported methodology here, the safer route is to start from facts: who actually performs the functions, which assets are used, which risks are taken, and what evidence supports that picture [1].

That makes the first practical step quite simple. Do not begin with labels or country assumptions. Build a working map for each side: which decisions it takes, what work it performs, which resources it uses, and where the written contract diverges from actual conduct. That is the logic of the functional analysis described in the FTA guidance [1].

Where this article applies

This article relies on the UAE Federal Tax Authority Transfer Pricing Guide [1]. The limits matter from the start.

The source supports a method: analyse functions, assets and risks, compare contractual terms with actual conduct, and prepare a functional organisation chart. It does not establish which functions must sit in the UAE or in Hong Kong, it does not prove bank expectations, and it does not answer licensing questions for a specific jurisdiction.

So the article below is not a rule for how a UAE–Hong Kong structure should be arranged. It is a working procedure for an owner or team that wants to describe the structure without guesswork and with stronger evidence.

Why the error usually starts with labels rather than facts

In a cross-border group, it is easy to fall into shorthand.

A UAE entity is called a holding company, so people assume it must carry the strategic role.

A Hong Kong entity issues invoices, so people assume it must be the trading side.

One team handles negotiations, so people automatically assign commercial risk to that side.

The problem is that these formulas often collapse when you test them against documents and real behaviour. The FTA guidance starts from a different logic: understand what the parties actually do, which assets they use, and which risks they take, and only then describe their functional profile [1].

That is why the better question is not “what is each country for?” but “what does each side in this specific UAE–Hong Kong link actually do, and how is that shown by the evidence?”

What the FTA method supports directly

For this topic, three core points matter.

1. The review should focus on functions, assets and risks

This is the foundation of the functional analysis. It helps move away from broad labels such as “operating company” or “management centre” and into concrete questions:

• who conducts negotiations;
• who makes commercial decisions;
• who uses the people and systems;
• who controls the intangibles;
• who carries the relevant risk in a transaction.

This is not a theoretical exercise. It is how the role of each side in the value chain becomes visible [1].

2. The contract is a starting point, not the whole answer

Even a well-written contract does not by itself prove the full factual picture. If the agreement says one thing but emails, KPIs, reports and operating behaviour show another, the safer approach is not to ignore the gap but to document it [1].

For an owner, the implication is practical: a contract file alone is not enough. You also need evidence of actual performance.

3. A functional organisation chart is useful

The source expressly supports a practical tool: preparing a functional organisation chart for the parties involved [1]. This is especially helpful in a UAE–Hong Kong structure, where job titles may look similar across the group but the underlying authority may be very different.

The same guidance also points to questionnaires and interviews with personnel. That matters because a formal title such as director, sales manager or finance lead does not yet tell you what that person actually does in the transaction chain [1].

What not to do in a UAE–Hong Kong link

Before building the working map, it helps to remove three common mistakes.

Mistake 1. Assigning roles by country reputation

If Hong Kong entities are often used in trading models, that does not prove that the Hong Kong side in your structure must perform the trading function.

If a UAE entity sits in the group, that does not prove it is the side making the key decisions or controlling the relevant assets.

The source does not support those conclusions. It supports only the method: review the actual functions, assets and risks [1].

Mistake 2. Treating document flow as the same thing as function

One side may issue invoices while another side actually negotiates the deal, approves non-standard terms, manages execution and controls the client relationship.

Documents matter, but documents alone do not answer the functional question.

Mistake 3. Looking for one decisive file

In a cross-border structure, there is rarely one document that answers everything. In most cases, the picture has to be built from several layers:

• contracts;
• organisational charts;
• job descriptions;
• correspondence;
• reports;
• KPIs;
• internal approvals and operating instructions.

That is why a useful review is better designed as an evidence map rather than a search for one perfect file.

A working map: which functions to test for each side

The table below is an author’s first-pass template. It is not an FTA-mandated form and not a universal checklist for every group.

Scroll the table horizontally →

The value of this table is simple: it moves the discussion away from “this is the main company” and toward observable actions.

How to build an evidence pack for the UAE–Hong Kong link

The sequence below follows the supported methodology and the author’s working recommendation in the source.

1. Pull the documents for both sides

Start by gathering for each entity:

• contracts relevant to the transaction chain;
• functional organisation charts or internal role maps;
• current job descriptions;
• documents showing actual performance, such as emails, reports, KPIs and internal approvals.

At this stage, the goal is not yet to conclude. It is to assemble the layers of the picture.

2. Build the functional organisation chart

Separate out who, on each side:

• takes decisions;
• performs the operations;
• controls the assets;
• manages the people;
• approves exceptions and non-standard terms.

This is useful because it maps function at team and individual level, not only at entity-label level [1].

If you first need to sharpen your thinking around functions within one entity, the related article on what functions a holding company actually performs in the UAE may also help.

3. Run short interviews with key roles

This is a useful step to include explicitly.

Useful questions include:

• who makes the commercial decision;
• who can approve deviations from standard terms;
• who really carries the issue when the client disputes, supply fails or margin changes;
• where the people and tools are that the transaction cannot function without.

The important point is to record concrete examples of decisions and actions, not only general opinions.

4. Compare contract and conduct

The aim here is not to force perfect alignment. It is to identify and record the gaps honestly.

For example:

• the contract names one side as the performer, but another side actually manages the client;
• one entity is described as controlling an asset, but the access, development and decisions sit elsewhere;
• the commercial risk is allocated on paper to one side, but disputes and downside decisions are handled by another.

These are exactly the points that matter when describing the functional profile of a party [1].

5. Separate key functions from routine functions

The next step is to look at the value chain.

Useful questions include:

• which actions really create value;
• which functions are supportive or routine;
• where the real management core of the transaction sits;
• which side only executes a repeatable process and which side influences the overall commercial result.

This is not a question of status. It is a question of describing contribution to the value chain [1].

6. Record the conclusion in one map

The final document should show for each side:

• which functions are supported by evidence;
• which assets are used or controlled;
• which risks are actually borne;
• where contract and practice align;
• where they diverge;
• which documents support each conclusion.

Once that exists, the adviser discussion becomes far more useful.

A hypothetical example

Imagine a group with two main parties.

The UAE company is named in part of the intercompany documentation as the relationship-management centre for customers. The Hong Kong company is involved in invoicing and in day-to-day coordination with part of the supplier base. At presentation level, it is easy for the owner to say: “the UAE is the strategic centre and Hong Kong is the operating trade side.”

But the working review may show a more mixed picture.

Interviews may show that major deal terms are in fact negotiated by the Hong Kong team.

Emails may show that non-standard discounts and commercial exceptions also move there.

At the same time, the approval of strategic budgets, new market entry and control over certain intangibles may remain with the UAE side.

What does that change in practice?

It does not mean you should instantly rewrite the structure with one broad sentence. It means you should describe more precisely that:

• commercial decision-making is not distributed in the same way the contract wording suggests;
• part of the routine execution and part of the substantive negotiation sit with one side;
• control over specific assets and strategic decisions sits with another;
• the functional map needs a more careful description than “one company manages and the other simply executes.”

That example is useful not because it gives a legal outcome, but because it shows how often the real structure is more blended than the corporate label suggests.

Questions to ask about each side

To avoid getting lost in the file set, it helps to use a short question list.

On decisions

• Who approves pricing?
• Who changes deal terms?
• Who decides in a disputed situation?

On execution

• Who manages the client or supplier day to day?
• Who controls timing and delivery?
• Who fixes the problem when the transaction does not go to plan?

On assets

• Where do the systems, IP or key processes actually sit?
• Who controls them?
• Who can limit or expand their use?

On risks

• Who actually bears the downside when something goes wrong?
• Who decides whether the risk is accepted?
• Who absorbs the consequences of deviations?

On evidence

• Which document or record supports the point?
• Does that evidence match the contract?
• If not, how significant is the gap?

What an owner can do now

It is usually more productive not to map the whole international structure at once.

Start with one recurring transaction chain between the UAE side and the Hong Kong side. For that chain, gather:

1. the contracts;
2. the functional organisation chart for both sides;
3. short interviews with the key people;
4. one example each of a real decision, real execution, real asset use and real risk-taking;
5. a table showing the gaps between contract and conduct.

If you are also reviewing how to describe a product or operating activity before a regulatory discussion, the related article on what product actions to describe before a UAE licensing check may also help.

Common mistakes in the final write-up

Mistake 1. Jumping too early to a country conclusion

Statements such as “this function must be in the UAE” or “this role is typical for Hong Kong” sound confident, but they are not supported by the evidence base for this article.

Mistake 2. Mixing legal description with actual work

An entity may be labelled one way in the group chart, but its actual function is defined by conduct, not by label alone.

Mistake 3. Ignoring blended models

Sometimes a function is genuinely split. In that case, it is usually more accurate to describe shared or divided execution than to force one side into a full-function role without enough evidence.

Conclusion

In a UAE–Hong Kong structure, the question “what function does each side need?” is usually better reframed as: who actually makes the decisions, who performs the work, which assets are used, which risks are borne, and what evidence supports that picture.

The FTA methodology is useful precisely because it pushes the analysis in that direction: review functions, assets and risks, compare contracts with actual conduct, use a functional organisation chart, and build the evidence through documents, questionnaires and interviews [1].

The practical next step is simple: choose one transaction chain between the UAE side and the Hong Kong side and complete a table of functions, assets, risks and supporting records. Only after that should you discuss with advisers how the roles should be described and which contract-versus-conduct gaps really matter.

Sources

[1] UAE Federal Tax Authority, Transfer Pricing Guide CTGTP1, sections 5.1.1 and 5.1.1.4: https://tax.gov.ae/Datafolder/Files/Pdf/2023/Transfer%20Pricing%20Guide%20-%20EN%20-%2023%2010%202023.pdf

Disclaimer: This material is for general information only and describes an author’s working method for preparing facts in a UAE–Hong Kong structure. It does not replace individual tax, banking or regulatory review and does not establish which functions must sit in a specific jurisdiction.