Guides
Updating a Legal or Trade Name on EmaraTax
How to update a legal or trade name on EmaraTax: licence first, per-tile amendment, exact-match naming, evidence, and the 20-business-day rule.
change legal name EmaraTax
A legal or trade name change is reported on EmaraTax through the Tax Records Amendment service on each affected tax tile: amend the trade licence with the licensing authority first, then open each tile's Actions menu, choose amend, update the name fields to match the reissued licence exactly, attach the licence and supporting corporate documents, and submit for FTA approval within 20 business days. The TRN does not change — only the name on the record.
Basis: Federal Tax Authority
- Amendment service
- Tax Records Amendment service carries name changes per tax type
- Federal Tax Authority
- Reporting deadline
- Within 20 business days of the change
- Federal Tax Authority
- TRN stability
- The Tax Registration Number does not change on a rename
- FTA registration framework, 2026
- Evidence chain
- Resolution, amended MOA, reissued licence, name-change certificate
- FTA amendment practice, 2026
# What this service is, and where it lives in EmaraTax
When a business changes its legal name — or its trade name — every FTA tax registration must reflect it, because the name on the registration is the name on returns, certificates, refunds and correspondence. The Tax Records Amendment service carries the change per tax type, evidenced by the reissued trade licence and the corporate documents behind the rename.
A legal name change — the entity renamed with the licensing authority, not a trade-name tweak — must flow through to every tax registration, because the registration's legal name is the identity the FTA's systems, certificates and assessments carry. Invoices issued, returns filed and certificates held in the old name after the change create a paper trail that does not match the legal entity — and mismatched identity documents are the raw material of disputes about who owes what. The amendment is administrative; the consequences of skipping it are not.
Per affected tax tile: Actions menu, amend, name fields, reissued licence plus supporting documents attached, submit for FTA approval. The name entered must match the reissued licence character for character — including legal suffixes, spacing and capitalisation — because the FTA's record is verified against the licensing authority's.
Change the name through the registration amendment on the Taxable Person tile, per tax registration, attaching the amended trade licence showing the new legal name — plus the licensing authority's name-change approval where issued separately. The FTA's record follows the licence: the name on the tax registration must be the name on the current licence, character for character. File the amendment promptly after the licence reissues; the gap period's documents should already carry the new name.
Portal screens change without notice. This walkthrough describes the flow as published in the FTA's taxpayer user manuals and service pages, checked in September 2026. If a button has moved or a screen asks for something new, the manual for that service — linked below — is the authority, not this page. Treat every portal-version-sensitive claim here as "as of September 2026 — the portal changes; re-check".
Every reference number, TRN and amount on this page is a synthetic example, clearly marked. Never enter real taxpayer data into a demo, a screenshot tool or a third-party checker.
# The tax rules behind this form
A name change is an identity event for the tax file: mismatches between the licence, the FTA record, bank details and contracts create the kind of inconsistency that blocks refunds, confuses correspondence and fails counterparty checks. The discipline is exact-match naming everywhere, sequenced licence-first. The concept pages below cover the amendment framework.
The key concept is identity continuity. The entity is the same legal person — the TRN does not change, the filing history does not reset, liabilities do not vanish. Only the name updates. This distinguishes a name change from a restructure: no new registration, no deregistration, no transfer of history. The amendment preserves everything and relabels it.
The second concept is the document cascade. The tax registration is one of many records carrying the legal name — bank accounts, contracts, the excise goods register, customs records, the TRC profile. The tax amendment is necessary but not sufficient: plan the cascade across every record, because a tax registration in the new name with customs records in the old name breaks the identity chain the FTA verifies against. Amend tax, then walk the cascade.
# Before you start: documents and checks
The rename must be proven end to end: the corporate decision, the licensing authority's recognition, and the exact new form of the name.
Assemble the full chain: resolution, amended MOA, reissued licence. A licence alone, without the corporate authority behind it, can be queried — the chain proves the rename was properly made, not just requested.
The amended trade licence is the core evidence, plus any separate name-change approval from the licensing authority. Where the change involved a licence reissue with a new licence number, note the old-to-new mapping explicitly — the officer matches identity across the change, and the mapping statement makes the match trivial.
| Document or detail | What to have ready |
|---|---|
| Reissued trade licence | Showing the new legal and trade names — the core evidence. |
| Board/shareholder resolution | The corporate decision authorising the rename. |
| Amended MOA | Where the legal name changed: the updated memorandum. |
| Name change certificate | Any official name-change certificate from the licensing authority. |
| Updated signatory IDs | Where signatory documents show the old entity name. |
# The walkthrough, step by step
Corporate authority, licence reissue, then the FTA amendments.
Secure the renamed licence first, then amend each tax registration with the licence attached, then walk the document cascade — banks, contracts, customs, certificates. Licence, tax, cascade: the order matters because each step evidences the next.
-
Pass the corporate resolution
Board or shareholders resolve the rename; record it properly.
-
Amend the corporate documents
Update the MOA and obtain any official name-change certification.
-
Reissue the trade licence
With the licensing authority: the licence showing the new names.
-
List the affected tax tiles
Every registration carrying the old name — VAT, excise, corporate tax.
-
Amend each tile
Actions menu, amend, update the name fields to match the reissued licence exactly.
-
Attach the evidence chain
Reissued licence, resolution, amended MOA, name-change certificate.
-
Submit within 20 business days
All amendments reported within 20 business days of the change.
-
Confirm and cascade
On approval, cascade the new name to banks, contracts and the GIBAN records — the tax file is only one of the places the name lives.
# After you submit: statuses and what happens next
Each tile's amendment is approved independently; track each reference. Until approval, the old name stands on that tax's record — file and correspond under the approved name, not the aspirational one.
After approval, verify the name on the registration certificates and download fresh copies: counterparties, banks and government departments will ask for them, and a certificate showing the old name undoes the work.
Cascade beyond the FTA: the bank account and GIBAN details, supplier and customer contracts, the tenancy, insurance. A tax record updated while the bank mandate still shows the old name creates payment mismatches.
After approval, verify the new legal name on each amended tile and on the next certificate or correspondence issued — character for character, including legal suffixes and spacing. Then work the cascade deliberately: bank mandates, key contracts, customs registration, the TRC profile, invoicing templates. Each record in the old name is a future mismatch waiting for an audit to find it.
For the transition period's documents, keep the name-change evidence pack — the old licence, the new licence, the approval — with the records. Invoices or returns straddling the change date are explainable with the pack and suspicious without it. The pack is small; the disputes it prevents are not.
Exact-match naming
The FTA verifies against the licensing authority. Enter the new name character for character — suffixes, spacing, capitalisation, and the Arabic form where the portal captures it. Near-matches fail verification.
Trade name vs legal name
Update both where both changed, and be clear which is which on each tile. Banks and contracts usually key off the legal name; branding uses the trade name — the FTA record should carry both correctly.
When the name change came with a licence number change
Some licensing authorities reissue with a new licence number on rename — which turns a simple amendment into an identity-mapping exercise across every linked record, especially customs. State the old-to-new licence mapping explicitly in the amendment notes and attach both licences. Then verify the customs linkage specifically: the customs registration number tied to the TRN must resolve to the renamed entity, or declarations start failing validation against a name the customs system no longer recognises.
# Common errors and how to fix them
Name-change amendments fail on mismatch: the portal's name, the licence's name and the evidence chain disagree.
Name changes go wrong on partial propagation — the tax tile updated but customs still in the old name — and on timing, with documents issued in the old name after the change. The amendment is the easy part; the cascade is where identity breaks.
| What you see | Likely cause | Fix |
|---|---|---|
| Name paraphrased, not matched | Portal entry differs from the licence in suffix or spacing. | Copy the licence character for character — do not tidy it up. |
| Licence not yet reissued | FTA amendment filed on the old licence. | Reissue the licence first; the FTA approves what the licence proves. |
| Evidence chain incomplete | Licence without the resolution or amended MOA. | Attach the full chain: decision, amended constitution, reissued licence. |
| Only some tiles amended | VAT renamed; excise still shows the old name. | Amend every tile carrying the name; list them before starting. |
| Bank details left stale | GIBAN and mandates still in the old name. | Cascade to the bank immediately after FTA approval — payment mismatches follow stale bank names. |
# Troubleshooting when it still will not go through
If the portal rejects the new name at validation, the usual cause is a character the field does not accept — check how the portal renders special characters and legal suffixes, and match the licence within what the field allows, noting the variance in the supporting documents.
If one tile approves the new name and another queries it, answer the query with the same evidence chain that succeeded on the first tile. Inconsistent outcomes on identical evidence are usually a reviewer question, not a substantive problem.
If the amendment is queried on the supporting approval — the licensing authority renamed the entity but the separate name-change approval document is pending — supply what exists with a clear timeline: the amended licence showing the new name is the primary evidence, and the pending approval is supplementary. Do not stall the tax amendment waiting for the supplementary document where the licence itself already evidences the change; file on the licence, note the pending approval, and forward it when issued.
Arabic name form mismatched
Where the portal captures the Arabic name, ensure it matches the licence's Arabic form exactly. Arabic-vs-English mismatches are a known rejection source — treat both forms with equal care.
Contracts signed in the old name during transition
Date-awareness matters: contracts signed after the rename should use the new name. Keep the resolution and licence reissue dates as the transition evidence.
Invoicing during the transition
Invoices issued between the licence reissue and the tax amendment approval should carry the new legal name — the legal fact changed with the licence, not with the portal update. Keep the name-change pack with the invoicing records for the transition period. Invoices in the old name after the change date are technically misdescribed; where they already issued, the pack explains them, but do not keep issuing in the old name 'until the portal updates' — the portal follows the law, not the reverse.
The TRN does not change — saying so explicitly
Counterparties sometimes read a name change as a new entity and request a new TRN certificate or new tax documents. The TRN is unchanged; only the name on the registration updated. A short notice to key counterparties — 'same entity, same TRN, new legal name effective from the licence reissue date', with the amended licence attached — prevents the confusion from becoming a commercial friction. Proactive communication beats reactive explanation.
The old name on issued certificates
Certificates issued before the rename — the TRC, the tax registration certificate, clearance certificates — carry the old legal name, and replacing them all at once is rarely practical. The name-change pack (old licence, new licence, approval) travels with the old certificates as the bridge document: presented together, they prove the continuity the mismatched names obscure. For certificates the counterparty relies on actively, request reissue in the new name; for archival ones, the pack suffices. Prioritise by reliance, not by age.
# Stuck? We'll file it for you
Some filings are worth handing to someone who does them every day. As your appointed agent on EmaraTax, we take the filing off your hands: we review your documents against what the portal actually asks for, prepare the submission, and file it under your authority after you approve the final review screen. You keep full visibility — FTA correspondence still lands in your own account, and nothing is submitted without your sign-off.
This uses the appointment mechanism the FTA built into EmaraTax itself: you authorise us as your tax agent on your Taxable Person profile, and we act within the limits you set. If the filing is simple and you would rather do it yourself, the walkthrough above is the complete path. But where the stakes are high — a deregistration with a credit balance on it, a disclosure against the clock, a registration the FTA has already rejected once — a second pair of trained eyes on the form costs less than a rejected resubmission cycle.
Book an appointment and tell us which page brought you here; we will pick up from the exact step where you got stuck.
Sources and legal basis
Authorities, systems and registers3
- Federal Tax Authority
- EmaraTax
- Tax Registration Number (TRN)
Terms used5
- Tax Records Amendment
- Legal name
- Trade name
- Trade licence
- Memorandum of Association
- Tax Records Amendment — FTA service pageFederal Tax Authority
- EmaraTax FAQsFederal Tax Authority
- EmaraTax micrositeFederal Tax Authority
Rates, thresholds and deadlines change. Every figure above is linked to the authority that publishes it — if the two ever disagree, the authority is right and this page is out of date. Tell us and we will fix it.
Frequently asked questions
How do I change the legal name on my tax registration?
Through the registration amendment on the Taxable Person tile, per tax registration, attaching the amended trade licence showing the new legal name. The FTA's record follows the licence — the name must match character for character. Secure the renamed licence first, then file; the gap period's documents should already carry the new name.
Does the TRN change with the name?
No. The entity is the same legal person — the TRN, the filing history and the liabilities all continue unchanged. Only the name updates. This is what distinguishes a rename from a restructure: no new registration, no deregistration, no transfer of history. Tell counterparties explicitly: same entity, same TRN, new name.
What documents does the name-change amendment need?
The amended trade licence as core evidence, plus any separate name-change approval the licensing authority issues. Where the reissue changed the licence number, attach both licences and state the old-to-new mapping explicitly — the officer matches identity across the change, and the mapping makes it trivial.
How quickly must the tax registration be updated?
Promptly after the licence reissues — registration changes should be notified within 20 business days as a standing guide, as of September 2026, re-check. Documents issued after the change date should carry the new name regardless of the portal's update state; the legal fact changed with the licence.
Which records beyond tax need updating?
The full cascade: bank mandates, contracts, customs registration, TRC profile, excise goods register, invoicing templates, certificates. The tax amendment is necessary but not sufficient — each record in the old name is a future mismatch. Plan the cascade when the rename is decided, not when the first mismatch surfaces.
What about invoices issued during the transition?
They should carry the new legal name from the licence reissue date — the legal fact changed then, not when the portal updated. Keep the name-change pack (old licence, new licence, approval) with the transition period's records. Do not keep invoicing in the old name 'until the portal updates'; the portal follows the law.
The licence number changed too. Does that matter?
Yes — it turns the amendment into an identity-mapping exercise, especially for customs linkage. State the old-to-new mapping explicitly in the amendment, attach both licences, and verify the customs registration number still resolves to the renamed entity. Declarations against a name customs no longer recognises fail validation.
Do I need to notify counterparties?
Proactively, the key ones: same entity, same TRN, new legal name effective from the licence reissue date, with the amended licence attached. Counterparties sometimes read a rename as a new entity and request fresh tax documents — the short notice prevents the confusion becoming commercial friction. Update standing invoicing instructions at the same time.
Name change versus trade name — different?
A legal name change alters the entity's registered legal identity and must flow through every registration. A trade-name or brand change that leaves the legal name untouched needs no tax amendment — though invoicing should still show the legal name correctly. Confirm which changed with the licensing authority before filing anything.
Can my agent handle the rename cascade?
Yes, once appointed — and a rename is exactly the multi-record exercise worth project-managing centrally. Give the agent the renamed licence and the cascade checklist (tax tiles, banks, customs, contracts, TRC, invoicing); keep the counterparty communication yours. The amendment filings are routine — the cascade discipline is the value.