What to check when an intercompany agreement and invoice do not match: a practical review using the UAE example

Short answer

If an intercompany invoice does not match the agreement, it is usually a mistake to choose between two extreme positions: “the contract decides the issue” or “the invoice decides the issue.” For transfer pricing purposes, the more reliable sequence in the UAE example is different: review the agreement first, then compare it with the invoice and with what the related parties actually did in practice [1].

Where documents and conduct do not align, the real question is not which file looks stronger on its face. The real question is which transaction actually took place, how that transaction can be evidenced, and whether the company can explain its pricing and conduct on an arm’s-length basis [1][2].

When this article applies, and when it does not

This article is built on FTA guidance and is therefore directly supported as a UAE example in the context of controlled transactions between related parties [1].

That limitation matters for two reasons.

First, this is not an article about VAT, e-invoicing, customs, licensing or third-party contracts. Those issues may also matter in practice, but the verified source base here is narrower: transfer pricing analysis and the evidential record around it [1].

Second, a mismatch between the agreement and the invoice does not by itself prove that a tax adjustment is automatically required. The supplied sources do not confirm that. The answer depends on the facts, the numbers and the company’s ability to explain the actual transaction [1][2].

Why the invoice alone is not enough

Many teams start with the invoice because it is closest to the accounting entry and to the reporting period. But one invoice rarely explains the full picture.

It may fail to show:

• what exactly was meant to be supplied;
• which period the charge covers;
• how the amount was calculated;
• which party actually performed the functions;
• whether the allocated risks and assets match the written arrangement.

That is why an invoice is best read as part of a three-layer review:

1. what the parties wrote in the agreement;
2. what they billed and paid in the documents;
3. what they actually did in operations.

If the first two layers diverge from the third, the third layer can become decisive [1].

Why the written agreement is not enough either

The reverse mistake is just as common: treating the written intercompany agreement as if it automatically answers the issue. For controlled transaction analysis, that is too weak.

The UAE FTA approach uses the contract as the initial reference point, but where the contractual terms and the actual conduct differ, the analysis must look at the real conduct of the parties and at the way functions, assets and risks were actually allocated [1].

In other words, a strong contract helps only if it is supported by practice and evidence.

If, for example, the contract says that one company provides management services to the group, but in reality decisions are made by another company, the invoicing entity has no people involved in those functions, and the charges are posted under a general label without a clear calculation, the problem is no longer the wording alone. The problem is the gap between paper and conduct.

What to check first

The list below is not a regulator’s mandatory form. It is a practical author method for finding where the mismatch actually sits.

1. The parties

Check whether the following align:

• the parties named in the agreement;
• the parties shown on the invoice;
• the parties that actually took part in the transaction;
• the parties between whom payment moved.

Sometimes the mismatch starts here: the agreement is signed with one group company, but another group company issues the invoice. In an intercompany context that is not automatically wrong, but it always requires an explanation and supporting records.

2. The subject matter

Compare whether the invoice describes the same thing that the agreement describes.

Useful questions include:

• does the invoice wording match the contractual scope;
• has a new service or supply appeared in the invoice that is not covered by the agreement;
• is the invoice description too generic for a transaction that may later need to be defended in detail.

For example, a label such as “management support” may be too broad if the real activity was a specific set of IT, procurement or HR functions.

3. The period and timing

One of the most common gaps is not the amount but the timing.

Compare:

• the period stated in the agreement;
• the period covered by the invoice;
• when the services or other actions were actually performed;
• whether the timing of the charge fits the factual transaction.

If the agreement contemplates a quarterly model but the group issues one year-end charge with no intermediate support, that is not automatically wrong. But it makes the calculations and the evidence more important.

4. The pricing and calculation

Next, review not only the amount but the logic of the amount.

Ask:

• what pricing formula the agreement uses;
• whether the invoice follows that formula;
• whether there is a calculation file, allocation key or other support;
• whether the methodology is applied consistently across periods.

If the agreement says cost plus but the invoice looks like a fixed annual amount with no visible calculation base, that is already a separate review point.

5. Functions, assets and risks

This is the central part of the analysis where documents and conduct diverge.

The company should understand:

• who actually performed the work;
• which people and business units were involved;
• which assets were used;
• who bore the operational and commercial risks;
• whether that picture matches the agreement.

If one company invoices for services but the work was actually done by people from another group company, this is where the main question about the actual transaction arises [1].

6. Commercial purpose and business logic

Sometimes the agreement and invoice match each other technically, but the business logic of the transaction is still weakly evidenced.

So it is useful to ask separately:

• why the group needed this transaction;
• what business result it was supposed to produce;
• why this particular company issued the invoice;
• whether emails, meeting notes, internal memoranda or other materials support the purpose.

This matters especially where the service is intangible and leaves fewer obvious operational traces.

A practical comparison table

The template below is a working tool, not an FTA-mandated form.

Scroll the table horizontally →

A hypothetical example

Imagine a group structure.

Company A in the UAE signs an intercompany agreement with Company B for management services. The contract says that Company B will provide quarterly finance and strategy support on a cost-plus basis. At year-end, however, Company A receives one invoice with a broad label, “shared services,” for a round amount and with no clear breakdown.

At that point the company has three review lines.

The first is the documents. Does the invoice wording match the agreement, and is there a calculation behind the amount?

The second is the facts. Who actually provided the services: Company B, a regional team from another group company, or partly Company A itself?

The third is the evidence. Can the group assemble emails, meeting notes, reports, calculation files, cost allocations and other support showing what work was actually done?

If it turns out that a significant part of the work was performed not by Company B but by another group entity, or that the operating model changed during the year, that is what needs to be described as the actual transaction rather than relying only on the broad contract language [1].

How to document the actual transaction

Once the mismatch is identified, it helps to describe the conclusion in a short and structured way. Do not stop at saying there is an inconsistency. Set out the chain of facts.

A useful format is often four parts:

1. what the agreement says;
2. what the invoice says;
3. what actually happened;
4. what evidence supports that conclusion.

For example:

• the agreement contemplated quarterly management services on a cost-plus basis;
• the group issued one annual invoice without a breakdown;
• the work was actually performed by a mixed team from two group entities;
• that is supported by correspondence, internal reports, approval routes and calculation files.

This is useful not only for advisers. It helps the company see what really needs attention: the agreement wording, the charge mechanics, the operating model, the invoice itself or the evidence set.

Should the invoice be corrected immediately?

Not always.

The earlier question is more important: is the issue only documentary, or is the underlying transaction model itself different from what was written?

There are at least three broad possibilities:

• the actual transaction is sound, but the invoice description is too generic;
• the invoice reflects reality, but the agreement is outdated;
• both the agreement and the invoice fail to reflect what really happened.

Only after that analysis does it make sense to discuss whether any correction is needed and, if so, of what kind. The UAE sources do not confirm a universal rule that every mismatch automatically requires an immediate tax adjustment or that the answer is simply to reissue one invoice [1][2].

At the same time, the logic of monitoring controlled transactions during the period and considering adjustments before filing is consistent with the FTA approach where a company identifies the issue in time [1].

Which documents should be retained

Even a strong analysis helps little if the evidence is not kept.

For the UAE example, it is important to remember that the source guidance says companies should retain records and documents for seven years, and that the FTA may request documentation [2].

In practical terms, it helps to keep one file containing:

• the agreement and appendices;
• all pricing calculations;
• invoices;
• intercompany reconciliations;
• emails and meeting notes on the substance of the transaction;
• performance or delivery records;
• payment confirmations;
• an internal memo on the conclusion about the actual transaction.

If the issue may later be reviewed, it is also sensible to preserve dates, authorship and the location of original or official copies.

A practical sequence once the mismatch is found

Step 1. Stop arguing from isolated wording and build one file

Do not debate the issue only around one invoice. First collect the agreement, invoice, calculations, payment support and the evidence of actual performance in one place.

Step 2. Review the eight fields in the table

Go through the parties, subject matter, period, price, functions, assets, risks, commercial purpose and accounting treatment.

Step 3. Record the exact point of divergence

Do not stop at “there is a mismatch.” Write down where it sits:

• different party;
• different period;
• different service description;
• missing calculation;
• mismatch in actual functions;
• missing operational support.

Step 4. Prepare a short memo on the actual transaction

In one or two pages, describe what really happened and what supports that conclusion.

Step 5. Only then discuss any correction

Once the factual picture is clear, the company can discuss with advisers whether anything should be changed in the agreement, the invoice, the pricing, the accounting or the documentation before the return is filed.

If you are also reviewing the wider role of group companies, the article on what functions a holding company actually performs in the UAE may help with the same evidence-first mindset.

What this article deliberately does not claim

To avoid overstatement, the limits should be explicit.

This article does not claim:

• that every mismatch between agreement and invoice necessarily leads to a tax adjustment;
• that correcting the invoice alone is enough;
• that the same rule automatically applies outside the UAE;
• that the issue can be resolved without analysing the numbers and facts;
• that having a written agreement automatically protects the company.

Its purpose is narrower and more practical: to help you rebuild the factual picture quickly and organise the evidence so that the next discussion with a tax adviser, finance lead or owner is useful.

Conclusion

Where an intercompany agreement and invoice do not match, the key question is not which document looks better in isolation. The key question is which transaction actually took place and whether the company can prove it.

Using the UAE FTA approach as an example, the working sequence is: start with the agreement, compare it with the invoice, then test the actual functions, assets, risks, period, pricing logic and commercial purpose, and finally document the conclusion on the actual transaction while retaining the supporting evidence [1][2].

A practical next step is simple: take one disputed intercompany transaction and complete the comparison table from this article. Only after that should you decide with your adviser whether the agreement, invoice, calculation or documentation needs to change.

Sources

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

[2] UAE Federal Tax Authority, Corporate Tax – General Guide (CTGGCT1), publication dated 10 September 2023: https://www.tax.gov.ae/DataFolder/Files/Guides/CT/CT%20General%20Guide%20-%20EN%20-%2010%2009%202023.pdf

Disclaimer: This material is for general information only and is not individual legal or tax advice. Any conclusion on a specific intercompany adjustment, evidential package or the applicability of rules in your jurisdiction requires a separate review of the transaction facts, calculations and current requirements with a qualified adviser.