What Is Dhareeba? Qatar’s Tax Portal, Explained

Definition at a glance

Question	Working answer
What is it?	Dhareeba is Qatar’s electronic tax administration portal used for taxpayer services administered by the General Tax Authority. Depending on the taxpayer and obligation, it supports registration, returns, requests, payments, correspondence and status tracking. Businesses should reconcile portal acknowledgements with ERP and accounting records, control user access and follow current GTA guidance for applicable filings and deadlines.
Who should own it internally?	Assign the operational or compliance owner responsible for the underlying process and evidence.
What should the system hold?	Authoritative master data, dated source requirements, workflow status, approvals, exceptions and retrievable evidence.
What is the main mistake?	Treating a general definition as a substitute for the current rule, standard, contract or operating context.

Use the definition as an orientation point. Verify current primary sources before making a regulated, financial, safety or certification decision.

Operational control map

Use this map when translating the guide into system configuration or procedure. Replace every placeholder and add jurisdiction-specific rows before approval.

Control area	Minimum requirement	Owner	Evidence
Scope and applicability	Confirm entity, jurisdiction, activity and effective date.	[ASSIGN]	[EVIDENCE LINK]
Authoritative requirement	Link the current source from FTA, EmaraTax.	[ASSIGN]	[EVIDENCE LINK]
Master data	Define fields, identifiers and ownership.	[ASSIGN]	[EVIDENCE LINK]
Workflow control	Record submission, approval, rejection and correction states.	[ASSIGN]	[EVIDENCE LINK]
Evidence	Retain source documents, acknowledgements and versions.	[ASSIGN]	[EVIDENCE LINK]
Exception handling	Assign escalation, target and acceptance authority.	[ASSIGN]	[EVIDENCE LINK]
Periodic review	Set an owner and regulatory review date.	[ASSIGN]	[EVIDENCE LINK]

Treat this as a maintained record. Store source publication, internal approval and next review dates, and preserve prior versions whenever a rule or workflow changes.

A licence activity and a ledger account answer different questions

A UAE trade licence states which business activities an establishment is authorised to conduct. A chart of accounts classifies the economic substance of assets, liabilities, equity, income and expenditure. They intersect, but they are not interchangeable.

The common implementation mistake is to reproduce every licence activity as a revenue account. A company licensed for several trading, repair and installation activities may end up with dozens of nearly identical sales accounts. Staff choose inconsistently, reporting becomes fragile, and every licence amendment appears to require a ledger redesign.

The opposite mistake is one sales account for everything. The trial balance remains tidy, but management cannot demonstrate which activity generated revenue, whether costs belong to trading or service work, or why the business description in tax and licensing records differs from operational evidence.

The answer is a two-layer model:

1. Chart of accounts: stable classification by economic nature.
2. Activity mapping: controlled dimensions that identify the licensed and operational context.

This is accounting-system design, not a legal conclusion about whether a particular transaction is permitted. Confirm licensing scope with the relevant UAE licensing authority and tax treatment with a qualified adviser.

Start from authoritative activity records

In Dubai, the official Invest in Dubai business-activity search allows users to search by activity name or number and groups activities into classifications including trading, services, manufacturing, construction, transport, education and health. Other emirates and free zones have their own licensing authorities, identifiers and rules.

Build an activity master from the actual licence and current authority record—not from the sales team's description of the business. Capture:

• legal entity and licensed establishment;
• licensing authority and jurisdiction;
• licence number, issue date and expiry date;
• official activity code and exact description;
• activity status and effective dates;
• branch or premises to which it applies;
• external approval or restriction, where applicable;
• internal business-line owner;
• products, services and channels mapped to the activity;
• evidence and date of the last mapping review.

Keep the original authority wording. An internal short name may help users, but it should not replace the official description.

Design the chart of accounts for economic substance

A maintainable chart should answer: what is this transaction? Examples include retail revenue, wholesale revenue, service revenue, cost of merchandise sold, installation labour, warranty provision, inventory, trade receivables and output VAT.

Use accounts where accounting treatment genuinely differs. Separate revenue may be appropriate when streams have different recognition patterns, gross-margin behaviour or financial-statement disclosure. Sale of stock and a long-duration service are economically different. Two licensed categories of similar goods sold through the same process may not require separate general-ledger accounts.

A practical structure might include:

Account family	Example purpose	Activity detail belongs in
Product revenue	sale of owned goods	activity, product category, channel, branch
Service revenue	installation, repair or support	activity, service type, contract, branch
Cost of goods sold	inventory cost released on sale	product category, warehouse, activity attribution
Direct service cost	technician time or subcontract work	service order, project, activity
Operating expense	rent, marketing, administration	cost centre, branch, allocation driver
Inventory	goods held for sale or consumption	item, warehouse, ownership status
Receivables	customer amounts due	customer, invoice, legal entity, activity
Tax accounts	VAT and corporate-tax balances	tax code, return period, tax registration

Avoid embedding emirate, branch, channel, department and activity into a long account code. Those characteristics change more often than economic classification and create an unmanageable combination of accounts.

Use ERP dimensions as the bridge

The exact labels vary by platform, but the information model should distinguish:

• legal entity: the person entering the transaction;
• licensed establishment or branch: the location and licence responsible;
• licensed activity: official authorised activity;
• business line: management view, which may group several activities;
• product or service: what was supplied;
• channel: store, wholesale, marketplace, web or field service;
• cost centre: who controls expenditure;
• project or contract: a specific delivery obligation;
• tax code and tax registration: VAT treatment and reporting identity.

These dimensions must not be free text. Use controlled values, effective dates, owners and validation rules.

The licensed activity can default from item or service, branch and transaction type. A repair service sold at Branch A might default to the repair activity on that branch's licence. A product sold online can map to the relevant trading activity and fulfilment establishment. Users should change a default only with an allowed reason and audit trail.

Build a mapping matrix before configuration

For every material revenue flow, document the full path:

Source	Mapping question
Contract or order type	What has the customer agreed to buy?
Item or service master	Which product/service family is supplied?
Fulfilment branch	Which licensed establishment performs the activity?
Official activity	Which current licence activity supports the supply?
Revenue account	What is the economic nature of income?
Cost account	How are directly attributable costs classified?
VAT code	What tax treatment applies to the transaction?
Corporate-tax attributes	Which evidence or adjustment category may apply?
Management dimensions	How will margin and performance be analysed?

The matrix should identify exceptions. A bundled sale may contain goods, installation and maintenance. One order can therefore produce several accounting lines and activity mappings. Do not force the entire contract into the activity of its largest line.

Licence scope should control transaction setup

Mapping is weak if the ERP merely reports unlicensed activity after month-end. Use it as a preventive control.

When a product or service is created, require an approved activity mapping for every selling establishment. When a branch is selected, restrict the order to activities valid for that licence and date. When an activity expires or is removed, prevent new commitments while preserving historical transactions.

The control needs nuance. Blocking fulfilment immediately at licence expiry might disrupt obligations already under authorised renewal processes. Define warning, approval and block rules with legal and operations teams. The system should expose the condition; authorised management decides the response.

Monitor:

• revenue posted to an unmapped activity;
• transactions after activity or licence expiry;
• manual overrides by user and reason;
• items mapped differently across similar branches;
• newly created products without licensing review;
• revenue activity inconsistent with contract or invoice description;
• activity values changed after posting.

Keep VAT mapping separate from licence mapping

A licensed activity does not determine VAT treatment by itself. VAT treatment depends on the particular supply, parties, place, evidence and applicable law. Two transactions under the same trading activity can have different tax codes. Two activities can share the same VAT treatment.

Build tax determination from relevant facts, such as legal entity, customer location and registration, ship-from and ship-to, item or service tax category, transaction date and documentary evidence. The activity code may be an input or review attribute, but it should not be the sole tax engine.

Keep separate accounts or reconciliation logic for output VAT, input VAT, recoverable and non-recoverable amounts, adjustments and payments. Never create one output-VAT account per licence activity unless a clear reporting requirement justifies it. Tax return reconciliation should trace from return box to tax code, document and source transaction.

Corporate tax needs traceable accounting records

The UAE Federal Tax Authority's Corporate Tax FAQs state that taxable income begins with accounting net profit or loss, followed by adjustments under the Corporate Tax Law. The FTA's General Corporate Tax Guide says records should enable taxable income to be readily ascertained and gives examples including transaction, asset, liability and stock records, ledgers, invoices, till rolls, orders and delivery notes.

That does not mean the chart of accounts should attempt to encode every tax adjustment. Use a controlled tax-adjustment layer with source, legal basis, period, calculation, approver and supporting documents. Examples may include non-deductible expenditure, depreciation-related adjustments or other applicable reconciling items.

The activity mapping helps explain how income was generated and connects the licence, operation and records. It does not replace the corporate-tax computation.

For UAE branches of a domestic company, the FTA's corporate-tax registration page notes that they are extensions of the parent or head office rather than separate legal entities for registration and filing. ERP branch dimensions can still be vital for licensing, VAT, management and operational control. Do not confuse an internal branch segment with a separate juridical person.

Free-zone and mainland structures need entity-first design

A group may operate through mainland companies, free-zone entities and branches. Similar brand names and shared warehouses can hide the legal boundary.

Every order, purchase, stock movement, expense and receipt must first identify the correct legal entity. Only then should the system apply branch, activity and tax mappings. Inventory ownership should remain visible even if goods share a physical location. Intercompany sales, services, cost allocations and settlements require their own documents and evidence.

Do not use a licence activity to bridge legal entities. “Electronics trading” on two licences does not make the companies one accounting unit. Conversely, do not duplicate accounts merely because several legal entities use the same economic classifications. A group chart can standardise account meaning while each entity maintains its own ledger and statutory evidence.

Map direct and shared costs carefully

Revenue mapping alone gives an incomplete margin view. Direct purchase cost can follow the item and stock transaction. Technician labour can follow a service order. Marketplace commission can follow the channel. These are traceable costs.

Shared rent, administration, marketing and technology require an allocation policy if management wants activity profitability. Choose a driver that reflects consumption—floor area, headcount, transactions, revenue, orders or system usage—and document its limits. An allocation is a management model, not automatically a tax conclusion.

Post shared costs to their natural account and responsible cost centre first. Run transparent allocation entries or reporting calculations with source pool, driver, period and approval. Avoid asking accounts-payable users to guess an activity for every shared invoice; that creates precision without evidence.

Review contribution margin at several levels:

1. revenue less directly attributable product or service cost;
2. contribution after channel and fulfilment cost;
3. segment result after controlled shared-cost allocation;
4. legal-entity profit reconciled to the general ledger.

The final level must reconcile. Management dimensions cannot become a parallel set of ungoverned books.

Master-data governance is the real control

An elegant model fails if anyone can create an activity, item or account.

Assign owners:

• company secretarial or compliance owns licence evidence;
• finance owns the chart of accounts and posting rules;
• tax owns tax codes and reporting logic;
• commercial teams own product and service descriptions;
• operations owns fulfilment establishment and process;
• ERP governance owns workflow, access and change history.

A change request should state why a mapping changes, effective date, affected open transactions, reporting impact, tax review and evidence. Test it before activation. Never overwrite a historical mapping; close the old version and begin the new one.

Quarterly governance should reconcile active licence activities to active ERP mappings, revenue streams, product masters and branches. Also look for products sold with no recent activity, which may indicate discontinued lines or accidental reuse.

A practical implementation sequence

1. Inventory licences and entities

Collect current official records for every company, branch and jurisdiction. Resolve duplicate names and expired activities.

2. Profile transactions

Sample orders, invoices, credit notes, purchases, inventory issues, contracts and returns. Identify economic substance and actual operational activity.

3. Rationalise the chart

Find accounts created only to represent a branch, activity or channel. Decide which detail should move into a dimension without losing financial-statement or tax requirements.

4. Build and approve the matrix

Map items, services, branches, activities, accounts and tax categories. Resolve bundles and exceptions with finance, tax, legal and operations.

5. Configure preventive rules

Create defaults, allowed combinations, expiry warnings, overrides and approval workflow.

6. Migrate with effective dates

Preserve original source values. Map history explicitly and identify periods where comparison is limited.

7. Reconcile end to end

Test from licence and contract to order, invoice, inventory, journal, VAT report, management report and corporate-tax records.

What the monthly control pack should show

Use a compact exception-led pack:

• revenue by legal entity, branch and licensed activity reconciled to the ledger;
• transactions with missing, expired or overridden mapping;
• new products and services awaiting compliance approval;
• negative margin or unusual account/activity combinations;
• VAT return totals reconciled to source tax codes;
• activity-level revenue changes requiring commercial explanation;
• shared-cost allocations and unreconciled balances;
• mapping changes made during the period;
• licence renewals and amendments approaching effective dates.

The purpose is not to claim that accounting proves licensing compliance. It is to show that the organisation can trace what it sells, under which establishment and activity, how it accounted for the transaction, and who reviewed exceptions.

FAQ

Should every trade licence activity have its own revenue account? Usually not. Use a separate account when the economic treatment or required disclosure differs. Use a controlled activity dimension for licensing and operational analysis.

Is a DED activity code the same as a tax code? No. A licensing activity describes authorised business scope. A tax code determines treatment of a specific transaction under tax rules.

Can one item map to several activities? Yes, when the correct activity depends on establishment, transaction type or bundled service. The determination rule must be explicit and auditable.

Should historical transactions change when a licence activity is renamed? No. Preserve the value and definition effective when the transaction occurred, with a governed mapping to the new classification where comparison is needed.

Does activity-level profitability equal taxable income? No. It is a management view. Taxable income begins from accounting profit and follows applicable corporate-tax adjustments and rules.

Where a system helps

A well-designed SMB ERP can keep the chart stable while enforcing valid combinations of entity, branch, item, activity, account and tax code. It can preserve effective dates, block invalid sales, trace overrides and reconcile operational activity to financial and tax evidence without proliferating ledger accounts.

Explore RetailOS for SMB ERP.

Related reading: Multi-State GST Registration (KB-462) and Retail and Wholesale in Oman (KB-463).

Sources

• Invest in Dubai, Search Business Activities
• UAE Federal Tax Authority, Corporate Tax FAQs
• UAE Federal Tax Authority, General Corporate Tax Guide
• UAE Federal Tax Authority, Corporate Tax Registration