ASApexlink Suite
Guides › Buyer's Guide

What Makes Core Banking Software Sharia-Compliant, and Do You Need a Specialist Core?

A Sharia label on a core banking brochure tells you very little. Here's what the system has to enforce, and how to decide between an Islamic module and a purpose-built core.

Apexlink Suite editorial team · November 2026 · 8 min read

The decision: an Islamic module or a purpose-built core

If you're launching an Islamic banking window, converting a conventional bank, or replacing an ageing system at a full-fledged Islamic bank, you'll hit the same question early. Can a conventional core handle Sharia-compliant products through an add-on module, or do you need Islamic core banking software designed around these contracts from the start?

The answer depends less on vendor marketing than on three things: how much of your balance sheet will be Islamic, how complex your profit-sharing deposits are, and how strictly your regulator and Sharia board expect every transaction to trace back to an approved contract. Below is what a Sharia-compliant core has to do, followed by a rule for deciding.

Advertisement

Why murabaha and ijara break conventional loan logic

A conventional loan engine is built on one idea: money lent, interest accrued over time. Islamic financing contracts don't work that way, and a core that just renames "interest" as "profit" will fail a Sharia audit.

Murabaha is a cost-plus sale. The bank buys an asset, takes ownership (actual or constructive), then sells it to the customer at a disclosed markup, payable in installments. The core has to record that ownership sequence. It has to fix the total sale price at signing, so the receivable can't be repriced like a floating-rate loan. And it can't compound late-payment charges. In many jurisdictions those charges go to charity, or are limited to actual-cost compensation, so the core must route them to a separate account rather than to income.

Ijara is a lease. The bank owns the asset, so rent accrues only once the asset is delivered. Major maintenance and takaful cover usually sit with the lessor, and rentals can be reset periodically against a benchmark. With ijara muntahia bittamleek (lease ending in ownership), the core must also manage the separate transfer-of-title undertaking. A conventional amortization schedule can't express any of this cleanly.

Retail home finance adds diminishing musharaka, where the customer buys out the bank's share unit by unit while paying rent on the rest. Treasury adds commodity murabaha (tawarruq) for liquidity, which needs integration with a commodity broker or a platform such as Bursa Suq Al-Sila' in Malaysia.

Mudarabah deposits and the profit distribution engine

The liability side is where weak Islamic modules usually show it. Under mudarabah, investment account holders provide capital and the bank manages it as mudarib. Depositors aren't paid a promised rate. They share in the actual returns of the assets their funds are invested in.

That requires a profit distribution engine that can:

  • Map assets to one or more profit pools (retail financing, corporate, sukuk) and prevent commingling without approval.
  • Calculate pool income after direct and approved indirect expenses.
  • Apply weightages by tenor, amount and product, then split profit between depositors and the bank at the agreed ratio.
  • Manage smoothing reserves such as the profit equalization reserve and the investment risk reserve, plus any hiba (gift) the bank pays from its own share.
  • Produce a pool-level calculation the Sharia board and auditors can recompute.

Hypothetical example: say a mid-sized Gulf bank runs four pools and 30 deposit products with monthly distribution. If the engine handles only one pool, or computes weightages in a spreadsheet outside the core, every month-end becomes a manual reconciliation. That's exactly where audit findings tend to appear.

Sharia board audit trails and AAOIFI standards

A Sharia-compliant core has to prove compliance, not just assert it. Expect your Sharia supervisory board and internal Sharia audit team to ask for:

  • A product register linking every product to the fatwa or resolution that approved it, with version history.
  • Evidence of contract sequencing: purchase before sale, delivery before rent, signed promise before the binding contract.
  • Segregated tracking of non-compliant income and charity disbursements.
  • Locked parameters, so a product manager can't change sharing ratios or pool mappings without recorded approval.

On accounting, AAOIFI standards are mandatory or used as a reference in several Gulf markets and influential in many others. Malaysia applies MFRS alongside Bank Negara Malaysia's Shariah governance and contract-specific policy documents. The UK and most of Europe report under IFRS with no Islamic-specific accounting rules. Your core and general ledger may need to produce both AAOIFI-style and IFRS views, so ask vendors to demonstrate dual reporting rather than promise it.

When a conventional core with an Islamic module is enough

For many institutions, a tier-one or tier-two conventional core with a mature Islamic module is the right call. Temenos, Oracle FLEXCUBE and Infosys Finacle all offer Islamic banking capability that is reported live at Islamic banks and windows across the Gulf and Asia. Ask each vendor for current references.

This route usually works when:

  • You're running an Islamic banking window where Islamic assets are a minority of the balance sheet. As a rough rule of thumb, well under a third.
  • The product range is mainstream: murabaha auto and personal finance, ijara home finance, qard current accounts, and a few mudarabah deposit products with simple pooling.
  • Your regulator lets you segregate the window through separate ledgers and reporting rather than separate systems.
  • Shared customer, channel, payments and AML infrastructure matter more to you than Islamic-specific depth.

The trade-off is that the Islamic module often lags the conventional roadmap, has fewer skilled implementers, and may run profit distribution as a batch process with limited configurability. Don't assume a module is deep just because it's licensed. Check the reference sites.

When a specialist core is the safer choice

Specialist or Islamic-heritage platforms, such as Path Solutions' iMAL and ICS BANKS Islamic from ICSFS, were built around Sharia contracts. Several regional vendors in Malaysia and Indonesia also offer Islamic-first systems. These tend to fit better when:

  • You're a full-fledged Islamic bank, or will be after a conversion or spin-off.
  • You run many profit pools, restricted investment accounts, or complex participation products such as musharaka in project finance.
  • Your Sharia board expects contract-level workflow controls built into the system, not added through customization.
  • You can't afford a long, consultant-heavy build to make a conventional engine behave Islamically.

The specialist risks are different: smaller vendors, thinner partner ecosystems, and sometimes weaker cloud, API and digital channel capability. For a full Islamic bank with complex deposits, we'd lean toward a specialist core unless the conventional vendor can show a live reference of similar size and complexity.

How the choice plays out in five markets

Regulatory structure shapes the answer as much as product mix does. These are general patterns. Confirm current rules with local counsel and your regulator.

MarketTypical structureWhat it means for the core
Gulf (Saudi Arabia, UAE, Bahrain, Qatar, Kuwait, Oman)Large full-fledged Islamic banks plus windows at conventional banks; central Sharia authorities in several statesHigh Islamic share and multi-pool deposits favor specialist or very mature modules; AAOIFI-based reporting is common
MalaysiaIslamic subsidiaries of conventional groups under the Islamic Financial Services Act 2013, with detailed BNM contract policy documentsGroup-wide cores with strong Islamic modules are common; the system must follow BNM contract-specific requirements
IndonesiaSharia banks plus Islamic business units, with long-running regulatory pressure to spin units off; DSN-MUI fatwas applyPlan for a possible spin-off, since a module that can't be separated cleanly becomes a migration project later
PakistanIslamic banks and windows growing alongside a national policy push to move the financial system away from ribaConversion programs need cores that can migrate conventional books to Islamic products at scale
UKA few small Islamic banks under standard PRA/FCA rules and IFRSLow volumes and IFRS-only reporting make a modular or cloud core with Islamic configuration realistic

Cost drivers, red flags and a demo script

Typical 2026 market ranges vary widely by contract and region, so confirm with vendors. An Islamic module on a tier-one core often adds a noticeable premium, commonly in the low double-digit percentages, to license or subscription fees. Total implementation at a mid-sized bank commonly runs from a few million to $30 million or more, depending on scope. Specialist cores can cost less to license in emerging markets, but savings can disappear if you need heavy integration work. The biggest cost drivers are the number of profit pools, data migration from a conventional book, dual AAOIFI and IFRS reporting, and how scarce Islamic-skilled implementers are in your region.

Red flags: profit distribution run in spreadsheets outside the core; "murabaha" built as a fixed-rate loan with a renamed field; late-payment charges booked to income; no fatwa-to-product linkage; no live reference with a comparable Islamic share.

Run this demo script with your Sharia team in the room:

  1. Book a murabaha with asset purchase, sale and an early settlement with rebate (ibra).
  2. Run an ijara through delivery, a rental reset and a total-loss event.
  3. Close a month across three pools with a reserve adjustment, then show the depositor-level result.
  4. Pull the audit trail for a sharing-ratio change.

Here's a working rule. If Islamic assets will exceed about a third of your balance sheet, or you run more than two profit pools, put a specialist core on the shortlist and make module vendors prove equal depth at a live reference. Treat those thresholds as a starting point, not a standard.

Common questions

Can we run an Islamic banking window on our existing conventional core?

Often, yes, provided the vendor has a mature Islamic module and your regulator accepts ledger-level segregation. Check that the module handles contract sequencing and profit pools natively rather than through customization. If your regulator requires the window to be fully separable, test that before you commit.

What is a profit distribution engine and why does it matter?

It's the part of the core that calculates returns for mudarabah and other investment account holders from actual pool income, weightages and sharing ratios. Depositors' returns aren't contractually fixed, so errors are both a Sharia issue and a customer-fairness issue. Weak engines push calculations into spreadsheets, which creates audit risk.

Do we have to follow AAOIFI standards?

It depends on where you operate. Some regulators mandate AAOIFI standards, others use them as a reference, and markets such as Malaysia and the UK rely on their own frameworks or IFRS. Confirm your obligations with your regulator, external auditor and Sharia advisers.

Who signs off that our core banking setup is Sharia-compliant?

Your institution's Sharia supervisory board or committee approves products and reviews how the system implements them. In some markets a central Sharia authority at the regulator also issues binding rulings. A vendor can provide certifications, but they don't replace your own board's approval.

How long does an Islamic core banking implementation take?

As a rough guide, a window launch on an existing core with an Islamic module can take about a year or somewhat more, while a full core replacement at an Islamic bank often runs two to three years. Scope, migration volume and product complexity drive the difference. Get timelines from reference clients of similar size, not just from the vendor's proposal.

Written by the Apexlink Suite editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.