Deposit and investment accounts
Set up current, savings, term, and investment-style accounts with product-specific rules for fees, maturity, statements, and customer lifecycle events.
Specialized Banking
Islamic Banking
Configure Islamic deposit, financing, profit-distribution, and servicing rules with clear ledger boundaries and evidence for Sharia, finance, and operations review.
01Product and policy review
02Ledger and workflow setup
03Profit and separation controls
04Pilot with reconciliation evidence
Islamic financing structures
Explore the contract behind the product.
Four documented contract lifecycles, configured around institution-approved terms and Sharia review.
Murabaha
Asset-backed cost-plus financing.
Follow the asset purchase, agreed markup, sale, and installment schedule as a coherent financing lifecycle.
Explore your financing scope →Interest-free banking in Ethiopia.
Plan for the institution’s licensed operating model, including a dedicated interest-free bank or Islamic window. Product terms, Sharia review, ledger separation, and supervisory reporting must be mapped to the approved scope.
Explore the Ethiopian regulatory context →Institution Problem
Islamic banking becomes risky when product terms, profit treatment, and approvals are handled outside the core ledger.
In many banks, Islamic windows are supported by spreadsheets, side journals, or manual maker-checker notes layered on top of a conventional core. That can work for a pilot, but it becomes difficult to defend when volumes, branches, and product variations grow.
Teams need product parameters, account treatment, approval steps, and reporting evidence in one place, while still respecting the institution’s own Sharia governance and the separation required between Islamic and conventional activity.
Current Operating Constraints
The Usual Blockers Are Side-Ledger Work, Unclear Product Boundaries, and Slow Sharia-Review Cycles
01
Terms kept in spreadsheets
Murabaha, Mudarabah, Wakala, Ijara, and other institution-approved structures often rely on manual schedules, separate profit worksheets, or local branch instructions.
02
Weak separation by product line
Islamic and conventional balances, fees, approvals, statements, and reporting extracts need separation without forcing the bank to run two unrelated technology stacks.
03
Changes take too many handoffs
A new product variant can require Sharia review, finance mapping, operations instructions, digital-channel changes, and test evidence before it is safe to launch.
SelamNow Rollout Model
Start with the Approved Product Scope, Prove the Accounting, Then Expand
A SelamNow rollout begins by documenting the institution-approved product structures, chart-of-accounts treatment, expected profit allocation, statement wording, approval flow, and reporting outputs. The first phase should be small enough to reconcile every balance and product event. After finance, operations, and Sharia reviewers are comfortable with the evidence, the same setup can be extended to more products, entities, branches, or channels.
Product and policy review
Capture approved structures, customer disclosures, pricing/profit rules, fees, early-settlement handling, late-payment treatment, and required review points.
Ledger and workflow setup
Map accounts, posting rules, maker-checker steps, exception queues, servicing actions, and statement outputs before pilot transactions begin.
Profit and separation controls
Configure product boundaries, pool logic where applicable, distribution steps, reporting filters, and reconciliation checks for Islamic activity.
Pilot with reconciliation evidence
Run test cycles and limited live use, compare balances and journals, review exceptions, then expand only after sign-off from the required teams.
Modules Activated
Activate the Islamic Banking Capabilities That Match the Institution’s Approved Offering
Financing product setup
Configure institution-approved financing products with schedules, collateral references, disbursement controls, repayment handling, and servicing workflows.
Profit allocation and distribution
Support configured profit rules, participation treatment, maturity events, distribution runs, and finance review without relying on disconnected worksheets.
Islamic window separation
Keep Islamic products, workflows, ledger mappings, and reporting outputs distinct while sharing the same customer, branch, and channel foundation where appropriate.
Approvals and customer evidence
Use maker-checker steps, servicing history, audit trail, and statements that reflect the product rules approved by the institution.
Operating Outcomes
The Outcome Is Fewer Side Processes and Clearer Evidence
Product rules are visible
Operations, finance, and review teams can see the configured product treatment instead of reconstructing decisions from scattered files.
Separation is easier to prove
Product, workflow, ledger, and report boundaries make it easier to show how Islamic activity is handled inside a dual-banking environment.
Rollout is less disruptive
Teams can launch the approved scope first, reconcile it, and then reuse the tested setup for additional branches, entities, or product variants.
Review evidence is retained
Approvals, product events, journals, profit runs, exceptions, and servicing actions remain traceable from the same operating record.
Implementation Scope
Implementation Depends on Careful Mapping, Not a Generic Product Switch
Product and ledger mapping
Map structures, balances, schedules, fees, chart-of-accounts entries, reporting fields, and exception paths into the target setup.
Approval configuration
Set up maker-checker flows, product limits, servicing permissions, maturity actions, and exception review before pilot use.
Channel and interface alignment
Align onboarding, customer statements, payment interfaces, reporting feeds, and digital channels with the exact product scope being launched.
Rehearsal and stabilization
Run setup rehearsals, validate balances and product behaviour, support pilot users, and stabilize operations before broader rollout.
Plan product approval, reconciliation, and servicing rehearsals with your institution’s Sharia, finance, and operations teams before rollout.
Next step
Review the Platform and Plan the Rollout Scope
Start with the modules you need and add more as the institution grows.