Why a Compliance Calendar Matters
Islamic finance compliance is not a one-time exercise. It runs on annual and quarterly cycles tied to regulator filing windows, standards body publication schedules, and internal audit rhythms. Institutions that manage these cycles reactively spend disproportionate effort reconstructing evidence under deadline pressure.
The two principal standards bodies operating on annual cycles are AAOIFI and IFSB. Each publishes new or revised standards on a schedule that creates downstream compliance work for institutions: obligation register updates, Shariah board reviews, internal policy changes, and evidence production for regulators. Getting lead time on standard changes reduces the cost of adaptation.
This article maps the key calendar events for 2026 across the GCC, Malaysia, Indonesia, and Pakistan. Specific deadlines change annually and vary by institution fiscal year. Institutions should verify current requirements directly with their licensing regulator.
Note: Filing windows listed below reflect general patterns based on publicly available regulatory frameworks. Specific deadlines vary by institution type, fiscal year, and regulator guidance. Always verify current requirements with your licensing regulator directly.
Standards Body and Regulatory Activity by Quarter
The following calendar maps recurring compliance activities by quarter based on established patterns from AAOIFI, IFSB, and major jurisdiction regulators.
Q1 (Jan - Mar)
- •Annual Shariah compliance report production for prior year (GCC jurisdictions)
- •Prior year financial statement filing windows open (SAMA: 90 days from year end)
- •Review new AAOIFI/IFSB standards published in prior year for implementation impact
- •Update obligation registers with any new or revised requirements
- •Shariah Supervisory Board annual report preparation
Q2 (Apr - Jun)
- •IFSB Annual Summit (typically May) - standards adoption announcements
- •BNM Financial Stability and Payment Systems Report publication (advance notice of Shariah Standard revisions)
- •UAE CBUAE annual financial statement filing deadline (within 4 months of year end)
- •Indonesia OJK Islamic banking quarterly compliance submission
- •Pakistan SBP quarterly Islamic banking reporting period
Q3 (Jul - Sep)
- •AAOIFI exposure drafts for proposed standard revisions (45-90 day comment periods)
- •Mid-year internal Shariah audit checkpoint for most GCC institutions
- •Malaysia BNM Shariah Standard implementation deadlines (for standards published 12-24 months prior)
- •QCB quarterly reporting submission (Qatar licensed banks)
Q4 (Oct - Dec)
- •AAOIFI Annual Conference (typically November in Bahrain) - new standard approvals
- •Year-end compliance posture review across all active frameworks
- •Prepare Shariah audit plan and scope for the following year
- •CBB Bahrain annual Islamic banking compliance filing (within 3 months of fiscal year end)
- •Assess implementation readiness for any forthcoming standard changes announced at AAOIFI Conference
Key Jurisdiction Reporting Windows
Annual and interim reporting windows differ across jurisdictions. The table below summarises the key windows for the primary markets covered by this calendar.
Bahrain (CBB)
Most prescriptive AAOIFI jurisdiction. CBB Rulebook Volume 2 mandates AAOIFI standards directly.
Saudi Arabia (SAMA)
Islamic banking disclosures required under the Banking Control Law for all AAOIFI-aligned institutions.
UAE (CBUAE)
ADGM and DIFC free zones maintain separate reporting requirements from mainland UAE.
Qatar (QCB / QFCRA)
QFC-licensed entities report to QFCRA separately. Different deadlines may apply.
Malaysia (BNM)
BNM Shariah Standards carry force of law under IFSA 2013. New standard implementation dates specified per standard.
Managing Multiple Jurisdictions
Institutions operating across the GCC and Southeast Asia face a compound compliance calendar. Each regulator has distinct deadlines, distinct standard adoption timelines, and distinct documentation requirements. The practical risk is missed deadlines or inconsistent evidence when managing these obligations in parallel.
A structured obligation register that maps each requirement to its source standard, responsible owner, deadline, and evidence location provides consolidated visibility. This is more reliable than calendar reminders distributed across individual team members because the register creates an auditable record rather than a set of personal commitments.
For institutions using manual spreadsheet-based tracking, the primary risk is version control: registers become outdated when new standards are published, and there is no mechanism to flag obligations that may be affected by a standard change. Automated tracking against regulatory calendars reduces this risk by linking obligations to source standards and propagating updates when standards change.
Frequently Asked Questions
When does AAOIFI typically publish new standards?
AAOIFI publishes standard updates and new pronouncements through its annual conference, which is typically held in November in Bahrain. Final approved standards are published in the months following. Exposure drafts for proposed new standards are released for a public comment period of 45 to 90 days before finalisation. Institutions should monitor AAOIFI's official website and member communications for exposure drafts, as these indicate upcoming changes that will require compliance action once finalised. AAOIFI also convenes working groups throughout the year on specific topics such as digital assets and crypto-assets, where interim pronouncements may be released outside the main annual cycle.
What are the key reporting deadlines for Islamic banks in the GCC?
Reporting deadlines vary by jurisdiction. In Bahrain, licensed Islamic financial institutions submit annual Shariah compliance reports to the CBB within three months of fiscal year end, with interim submissions required quarterly. In Saudi Arabia, SAMA requires annual financial statements filed within 90 days of year end, with specific Islamic banking disclosures under the Banking Control Law. In the UAE, CBUAE-licensed Islamic banks follow reporting cycles aligned with the federal banking law, with annual reports required within four months of year end. Qatar-licensed banks report to QCB on a quarterly basis. Institutions should verify current deadlines directly with their licensing regulator, as specific windows are subject to change.
When is the IFSB Summit and why does it matter for compliance planning?
The IFSB Annual Summit is typically held in May, hosted by a member central bank or monetary authority. The Summit is where IFSB member regulators formally discuss and adopt new or revised prudential standards. Standards approved at or following the Summit become the basis for regulatory implementation guidance issued by member central banks in the subsequent months. Compliance teams should track Summit announcements because they provide lead time to assess how forthcoming IFSB standard changes will affect capital adequacy calculations, liquidity reporting, and governance requirements under their specific jurisdiction.
How does Malaysia manage Islamic finance compliance deadlines differently from the GCC?
Bank Negara Malaysia issues Shariah Standards under the Islamic Financial Services Act 2013 that carry the force of law, unlike the GCC where AAOIFI and IFSB adoption varies in legal enforceability by jurisdiction. BNM publishes an advance notice of upcoming Shariah Standard revisions in its Financial Stability and Payment Systems Report each year. BNM-licensed Islamic financial institutions are required to comply with new Shariah Standards by the implementation date specified in each standard, which is typically 12 to 24 months after publication. Malaysia's Securities Commission separately regulates Islamic capital markets, with its own annual reporting calendar.
What compliance preparation should institutions do in Q1 of each year?
Q1 is the primary window for annual compliance review activities. Institutions should: complete their prior year Shariah audit and produce the Shariah Supervisory Board annual report, review any new AAOIFI or IFSB standards published in the prior year for implementation impact, update their obligation registers to reflect new or revised requirements, and assess whether internal workflows and controls are calibrated to upcoming deadlines. Q1 is also the period when regulators in most GCC jurisdictions process annual financial statement filings, so compliance teams are typically operating at peak load.
How should an institution track compliance deadlines across multiple jurisdictions?
Institutions operating in multiple jurisdictions face a compound calendar: each regulator has distinct deadlines, distinct standard adoption timelines, and distinct evidence requirements. The practical risk is missed deadlines or inconsistent documentation when managing obligations in parallel. A structured obligation register that maps each requirement to its source standard, responsible owner, and deadline provides visibility across jurisdictions in one place. This is more reliable than calendar reminders or email threads because the register creates a searchable record that can be audited rather than a set of individual reminders that depend on individual team members to act on. Automated tracking against regulatory calendars reduces the probability of gaps when staff changes occur.