The Journal
Murabaha Origination on Manual: What Saudi Retail Banks Cannot Recover
Saudi retail banks lose Murabaha conversions when approval takes two to five days. That drop-off never shows up as a declined application.
Most Saudi retail banks still approve Murabaha financing applications through a chain of manual steps: document collection, bureau pull, credit review, committee approval. The window from application to decision often spans two to five business days. Customers who were ready to commit on day one are often gone by day four.
Murabaha financing covers the majority of retail lending at Saudi banks, from car purchases and home furnishing to personal goods and consumer electronics, structured under SAMA's Islamic banking framework. The product is not niche. In a mid-size retail bank, the origination desk may process hundreds of applications per week. Every day added to the approval cycle is another day the customer is in play for a competitor.
What Murabaha Origination Looks Like Without Automation
The standard manual origination process at a Saudi retail bank follows a recognizable sequence:
- Application intake. A branch officer or digital form collects the national ID, salary certificate, bank statement, and vendor invoice. Documents get uploaded to an internal portal, emailed to back office, or handled across the branch desk.
- Bureau pull. A back-office analyst requests a SIMAH report manually, matches it against the customer file, and flags any issues for review.
- Credit assessment. A credit officer evaluates the debt-to-income ratio, existing obligations, and lending policy criteria. Non-standard cases escalate to a credit committee that meets on a fixed schedule.
- Pricing and offer generation. An officer calculates the profit rate, generates the payment schedule, and prepares the Murabaha contract for customer signature.
- Disbursement. Once signed, the bank settles the purchase price with the vendor and confirms disbursement with the customer.
Each step in this sequence carries a queue. Documents sit waiting for someone to review them. Bureau reports are batched. Credit committees meet weekly. A file that could be fully assessed in under an hour waits days for each organizational handoff to complete.
The delay is not caused by credit policy or regulatory requirement. It is caused by the absence of tooling to connect the steps.
What Gets Lost Before the Offer Is Sent
The cost of manual origination does not appear as a line in the bank's P&L. It appears as customers who never received an offer.
When a customer applies for Murabaha to finance a vehicle or appliance, they are in an active purchase moment. They have visited the showroom, selected the product, and are comparing financing options across two or three institutions simultaneously. The bank that responds first captures the transaction. The bank that responds on day three receives a polite message that the customer has already proceeded elsewhere.
Banks track approval rates and default rates carefully. Very few track day-one-to-day-three attrition: the share of applicants who dropped off not because they were declined, but because approval arrived after the purchase window closed.
In a volume-driven retail lending book, this attrition compounds across thousands of applications per month.
Before vs. After: Murabaha Origination at a Saudi Retail Bank
| Step | Manual Process | AI-Augmented Process |
|---|---|---|
| Document collection | Officer-led, per branch, completeness varies | Automated checklist; instant completeness check |
| Bureau pull | Manual request, 4–24 hours depending on batch cycle | API-connected, result in seconds |
| Credit assessment | Credit officer review; committee escalation for edge cases | Rules-based auto-decisioning for standard cases; officer reviews flagged files only |
| Offer generation | Manual calculation and template-filled contract | System-generated offer with pricing logic applied |
| Decision time (standard cases) | 2–5 business days | Under 2 hours |
| Staff time per application | 2–4 hours across teams | Under 30 minutes |
The table reflects process change, not policy change. The bank's credit criteria, SAMA compliance requirements, and risk appetite remain exactly as defined. What automation replaces is the queue: the idle time between steps where a file waits for a human to pick it up.
What This Costs at Scale
Saudi household lending has grown steadily under Vision 2030's Financial Sector Development Program, with SAMA reporting consumer financing volumes in the hundreds of billions of SAR. Murabaha-structured retail products represent a large and growing share of that total.
A bank processing 3,000 Murabaha applications per month with an 8 percent delay-driven attrition rate loses roughly 240 potential approvals per month before they were ever declined. At an average Murabaha value of SAR 35,000, that is SAR 8.4 million per month leaving the pipeline for reasons entirely unrelated to credit quality.
Over a year, the compounding figure reaches SAR 100 million in unrealized origination for a mid-sized retail lender. That is before accounting for the CLV loss from customers who moved to a competitor and may not return for subsequent financing needs.
Why Most Saudi Banks Are Still Running This Process
The persistence of manual origination is not evidence that banks are unaware of the delay. It reflects three structural realities.
Core system constraints. Legacy banking platforms at Saudi institutions were not built for real-time decisioning. Connecting them via APIs to SIMAH and SAMA reporting infrastructure requires investment that competes with other technology priorities in the capital budget.
Organizational separation. Credit, operations, and technology sit in separate divisions with distinct budgets and performance metrics. Automating a process that spans all three requires cross-divisional governance structures that did not exist before the automation project.
Risk posture. Compliance teams interpret regulatory expectations conservatively, defaulting to human review. Automating credit decisions requires a documented, auditable rules engine that can satisfy both internal reviewers and SAMA examiners. Building that engine takes time even when the intent is clear.
None of these are permanent blockers. Several Saudi retail banks have already brought Murabaha origination timelines from days to hours. The institutions treating this as a 2026 operational priority are capturing conversions that slower competitors are not.
What Changes When Origination Is Automated
Automating Murabaha origination does not change the credit decision. It changes when and how the decision is made.
For applications that meet standard criteria (salary within policy, bureau score above threshold, existing obligations within limits), the system assesses, prices, and generates an offer without a credit officer touching the file. The officer's attention shifts to edge cases that genuinely require judgment.
For the customer, the experience changes completely. An application submitted Tuesday morning can produce an offer by Tuesday afternoon. The customer is still in the purchase moment. Conversion rates on same-day decisions are structurally higher than on decisions delivered 72 hours later.
The bank's risk profile does not change. Its capture rate on applications it was already going to approve does.
The Compounding Effect on Customer Lifetime Value
A customer whose Murabaha application was approved in two hours starts their relationship with the bank differently from one who waited four days. The friction of the wait is not forgotten: it shapes whether the customer returns for the next financing need, recommends the branch to family members, or considers the bank's savings or investment products.
In Saudi Arabia, where repeat household lending across a family network represents meaningful branch volume, the CLV effect of a fast first experience accumulates over years. Banks that automate origination are not only capturing today's conversions. They are beginning a customer relationship with a demonstration of competence rather than a delay.
The Decision Saudi Retail Banks Are Facing
The gap between manual and automated Murabaha origination is widening, not narrowing. Banks that have invested in API-connected origination platforms are operating on a different timeline from those still running on email and committee schedules.
Every month of inaction is another month of attrition that will not be measured, because the customer left before the bank had a chance to decline them. If your Murabaha origination process still depends on manual bureau pulls, batch committee approvals, or email-routed document reviews, the number of conversions your institution is losing is almost certainly larger than it appears.
→ Book a free automation audit to understand what your origination pipeline is actually costing you. No commitment, no sales call: just a clear read on where the delay is and what addressing it would be worth.
