Why the structure decides the configuration
Murabaha financing looks simple on a slide and gets complicated the moment someone has to build it. A customer wants an asset. The bank buys it and owns it before selling it on at a disclosed price. Every one of those verbs creates a record and a point where a configuration shortcut can void the contract.
The pressure to build it properly is rising. Sub-Saharan Africa now has 104 Islamic banks and windows operating, according to the ICD-LSEG Islamic Finance Development Report 2025, and markup-based instruments already account for about 56 percent of financing at Islamic banks in the region on IMF estimates. So the question is whether your product behaves like a sale in the ledger, or like a loan wearing a different label.
How murabaha financing works
A cost-plus sale has two legs, and they happen in order. The institution acquires an identified asset from a supplier at a known acquisition cost and takes ownership before selling that same asset to the customer at a price that states the cost and the markup separately. The customer pays that price.
Compare that with a conventional facility, where the bank credits an account and the customer does whatever the sanction letter permits. Abu Dhabi Islamic Bank puts the distinction bluntly in its own customer guidance: "The bank's profit is earned through the sale of an asset that it has owned, rather than from charging interest on money lent." The obligation is a sale price, fixed at contracting.
That single difference drives most of the build. Because the selling price is fixed when the contract is signed, there is no accrual engine recalculating a rate. Because ownership must sit with the institution first, there is an inventory position on the balance sheet, however briefly, which the Accounting and Auditing Organization for Islamic Financial Institutions (AAOIFI) addresses in FAS 28 on deferred payment sales. And because the cost must be disclosed, the acquisition figure stops being an internal number and becomes a contractual representation. A suitable core banking system should preserve those records and controls across the transaction lifecycle.
Murabaha financing example

The figures below are illustrative. They are chosen to make the arithmetic visible.
A manufacturing customer in Nairobi identifies a packaging machine. The supplier quotes KES 1,200,000. The institution buys the machine at that price and sells it to the customer for KES 1,380,000 after taking ownership. The contract discloses the KES 1,200,000 acquisition cost and the KES 180,000 markup on its face. The customer pays a KES 180,000 deposit at execution and settles the remaining KES 1,200,000 in twelve monthly installments of KES 100,000.
That is the whole murabaha financing example, and the deposit is where configuration goes wrong first. If the deposit is treated as a payment against the selling price, the schedule balances at exactly twelve installments. If it is treated as a reduction of acquisition cost, the disclosed cost figure in the contract is now wrong, and so is every downstream statement.
The 15% is not a rate
The KES 180,000 markup is 15 percent of the KES 1,200,000 acquisition cost. It is not an annual rate, and nothing in the contract converts it into one. A twelve-month tenor happens to make the two numbers look comparable, which is precisely why the comparison misleads: stretch the same markup over twenty-four months and the cost to the customer does not change, while the implied annualized figure halves.
Your disclosure templates have to hold that line. Where a central bank requires an effective-rate equivalent for consumer comparison, publish it as a separate regulatory disclosure and keep it out of the contractual price fields. Mixing the two inside one document is how a murabaha financing example turns into evidence that the product is a loan.