Revenue Test Notification
Required from the registered entity each year; a failed test does not mean silence.
Based on NBR Manual v1.1 · August 2026
From the Revenue Test Notification to return and settlement
A practical workflow separating a failed Revenue Test, central or local filing, the Bahrain return deadline and the GloBE Information Return receipt checkpoint.
This workflow is indicative; it does not file a return or verify a particular exchange agreement. Confirm status, fields and format through the NBR portal and current guidance when filing.
Annual filing cycle
Start with the notification, build the return, then settle the balance
The Revenue Test is a separate annual gateway; when met, the return comprises three connected parts before payment or credit treatment.
Choose the information route
Qualifying central filing with receipt monitoring, or local filing in the prescribed format.
Complete the return parts
Central Filing Notification, Information Schedule and Tax Computation Schedule.
Payment, credit or refund
Reconcile final tax to advance payments, credits and adjustments.
Deadline helper
Fifteen months for the return, then a separate receipt checkpoint
The following three months do not extend the Bahrain return deadline; they are a window for monitoring NBR receipt of the GloBE Information Return under central filing.
15 months after fiscal year-end.
3 months after the return deadline; not an extension.
If the last day falls on an official holiday, apply Regulations Article 85. This helper shows the base Gregorian calculation and does not verify the official-holiday calendar.
Return anatomy
Three parts that cannot be reduced to the tax figure
Central filing changes the Information Schedule route but does not remove the other Bahrain return or settlement components.
Central Filing Notification
Identifies the GloBE Information Return filer, location and route by which information reaches Bahrain.
Information Schedule
Filed locally or supported through central exchange when its conditions and receipt monitoring are met.
Tax Computation Schedule
Reports the Bahrain computation, separate categories and reconciliation to payments, credits and adjustments.
Central filing
- An effective qualifying competent-authority agreement with Bahrain.
- Identify the GloBE Information Return filer and jurisdiction.
- Monitor NBR receipt within three months after the Bahrain deadline.
Local filing
- Full GloBE Information Return or Bahrain Information Schedule.
- A data file using the prescribed schema referenced by the NBR Manual.
- Manual entry following a technical problem requires NBR permission.
Reconciliation before submission
Five checks against duplicate tax or missing data
Based on Return Filing Manual 1.1, pages 7 and 18–29. The examples below use BHD amounts from the Manual.
Include subgroups, then allocate payment responsibility
Include every subgroup in the Information Schedule, even where it appointed another filing entity. Keep each subgroup computation separate and enter amounts represented by another filer in the exclusions-from-tax-due field; do not delete their rows.
Zero tax is different from another filer's liability
Where an eligible Safe Harbour or Exclusion reduces tax to zero, record the election in the Information Schedule and carry zero tax into the computation. The exclusions-from-tax-due field is for another filing entity's liability, not the value of tax relief.
Distinguish the two exchange rates
Revenue conversion to EUR for the scope test uses the average December rate in the calendar year preceding the relevant fiscal year. Conversion of return tax to BHD uses the fiscal-year average. Document the source and keep the two bases distinct.
Deduct payments and credits actually applied
Reconcile tax for the entities you represent to advance payments made, then to credits actually applied to this return. Available credits are not automatically applied. A negative result becomes excess credit handled under the prescribed process, not an immediate cash refund.
Do not count Additional Current Tax twice
Additional Current Tax relating to prior years belongs in the current-year subgroup liability in the Information and Tax Computation Schedules. The prior-year corrections table tracks it without charging it again; this item alone does not require amending the prior-year return under the Manual.
Manual example: two different filing entities
The first filer reports 10,000 for its subgroup and 11,000 for the JV, then excludes the 11,000 represented by the second filer. After payments of 9,000 and applied credits of 300, 700 remains payable.
The second filer also reports both subgroups and excludes the 10,000 represented by the first. From JV tax of 11,000, it deducts payments of 10,000 and applied credits of 200, leaving 800.
Manual example: zero tax and payments of 9,000
Following a qualifying De Minimis Exclusion election, tax is zero and the exclusions-from-tax-due field is also zero. Deducting payments of 9,000 creates excess credit of 9,000; tax relief does not go in the field for another filer's liability.
Readiness pack
Data to assemble before opening the return
The Manual turns filing into a data and reconciliation project; separate categories, payments and credits can change the computation and settlement.
Group and Bahrain constituent-entity data
Joint ventures and JV subsidiaries in a separate computation
Stateless, investment and minority-owned entity categories
Include all computation subgroups and separate tax amounts represented by another filing entity
Information file matching the prescribed schema and version
Reconciliation of advance payments and excess tax credits
Election register and prior-year adjustments
Evidence of filing, receipt, representative authority and approvals
Boundary of the OECD's role
The international GloBE Information Return and data schema help explain the technical requirement referenced by the NBR Manual, but they do not themselves change Bahrain law or replace current NBR instructions.
Workflow sources
The new Manual within Bahrain's legislative framework
The Manual is operationally significant, but it does not amend the Law or Regulations or create a new tax.