Why Zoral
What to ask before you choose a platform for lending and banking.
Many platforms for lending and banking sound alike. The real differences are how much of the work runs on one platform, who can change a credit rule, and whether you can see what each change did to the business. Below are the questions experienced buyers ask, with our answers. Each answer links to a page with more detail.
17 questions buyers ask, with our answers
The platform and your systems
1. Do we have to replace our core banking system?
Why it matters: replacing a core is one of the riskiest programmes a bank can run, and it delays everything else.
No. The Zoral Finance Operating System (fOS) works around the core you already run, whether it is a traditional core or a modern cloud core. New products can run alongside your core and post to your general ledger. For a new bank or brand, Zoral fOS can be the complete platform, including the product and account ledger.
2. How much of the work runs on one platform?
Why it matters: many lenders buy origination, decisions, documents and collections from different suppliers. They then pay to connect them, and often struggle to trace a result back to its cause.
On Zoral fOS, customer screens, origination, credit decisions, document checks, product rules, workflows, servicing, collections and results against plan share one record and one audit trail. You can start with one part and add the rest later.
3. How does it connect to our systems, including old ones with no interface?
Why it matters: most delays in lending projects come from connections, not from the new platform itself.
Through documented interfaces: APIs, events, batch and file transfer. Zoral Integration Gateway connects Zoral fOS to your core, cards, payments and data, and records every call. Ready connections cover identity, anti-money-laundering, bureau, alternative-data and fraud services. Where an older system or a partner offers only a web screen, Zoral Resilient RPA can complete the steps. If the screen changes, it flags the change instead of failing silently.
4. Where does it run, and who owns the data?
Why it matters: your regulator and your vendor risk team will ask both questions first.
Zoral fOS runs on AWS or Azure in the region you choose, including in your own cloud account, or in your own data centre. Our controls are independently audited under SOC 2, with details on the Zoral Trust Portal. Your data, product definitions and audit history remain yours, and can be exported in standard formats.
Credit, risk and your customers
5. Who can change a credit rule, and how is that controlled?
Why it matters: if every change needs an IT project, your credit strategy waits for the next release.
Your risk team changes rules, scorecards and strategies in Zoral Decision Engine. Each change is tested on past applications first and approved by a second person. It is saved as a new version and can be rolled back. Every decision is recorded with its data, rules and reasons.
6. Can we see what each change did to the business?
Why it matters: most lenders see losses months after the decision that caused them.
Yes. The Business Outcomes Layer compares actual results with your plan by product, channel and customer segment. It shows what each change did to conversion, cost and losses. Risk and finance work from the same figures.
7. Can we move off our current decision engine without disrupting the business?
Why it matters: a migration that changes decisions by accident can hurt both losses and customers.
We follow a method designed to protect your customers and your results. We rebuild your current rules, scorecards and strategies in Zoral Decision Engine. Old and new engines run side by side until the results match. You then move one product or channel at a time.
8. Will the models stand up to our model risk and validation teams?
Why it matters: a model your validation team cannot challenge will not reach production, however good it is.
They are built to be challenged. You can use your own models, ours or both. Each model is documented, tested on data it was not trained on, versioned, and monitored for drift and stability. A new model can run in shadow or as a challenger before it goes live. Scores come with reasons your teams can explain to a customer or a supervisor. Your own risk function validates and approves each model.
9. How do faster decisions stay safe and fair for customers?
Why it matters: speed that leads to losses or unfair outcomes costs more than it saves.
The speed comes from running more checks while the customer waits, not fewer. Affordability is part of each decision, and cases outside your policy go to a person. Customers who may be vulnerable can be routed to trained staff. You can compare outcomes across customer groups and show how customers in difficulty were treated. Your obligations remain yours, and Zoral gives you the controls and evidence to meet them.
10. Will it hold up at our volumes?
Why it matters: peak days, campaigns and online checkouts test a decision engine more than an average day does.
Zoral Decision Engine makes up to 5,000 credit decisions a second in production, around the clock. Results vary by product, geography, data quality and implementation scope.
AI and documents
11. How is AI kept under control?
Why it matters: your supervisor will ask who made each decision, and why.
AI agents prepare, check and draft, under human-in-the-loop supervision. For example, they read documents, prepare credit files and draft committee papers. They act only through the permissions and approvals you set, and every action is recorded. Agents do not make credit decisions. Those follow rules and models your bank approves, and accountability stays with your bank. You choose the language models, including open-weight models run in your own environment. They connect to Zoral fOS through a standard interface (MCP).
12. Can it read and check our documents?
Why it matters: retyping documents is slow, and a tampered document that is retyped is harder to spot.
Zoral Document Fabric reads 650+ financial document types, cross-checks them against each other and against the application, and flags signs of tampering. Your staff review the exceptions, not every page. Zoral Document Fabric runs in your own AWS or Azure account, or your private cloud, in your region and under your control.
Islamic banking
13. Can it run Islamic and conventional products together?
Why it matters: many banks offer both, and the Shariah board needs evidence for every product change.
Yes. Islamic products run on the structures your Shariah board approves, such as Tawarruq, Murabaha, Ijara, Wakala and Mudaraba. They run side by side with conventional products. Each product version keeps its approval history, as evidence for the board. Your Shariah board remains the authority, and Zoral does not certify products. Zoral built and launched the complete platform for a Shariah-compliant digital bank in South-East Asia.
Delivery and partnership
14. Who implements it, and do they understand credit?
Why it matters: a platform is only as good as the people who set it up for your credit policy.
Atelier, Zoral's consulting and implementation team, includes credit risk, collections and data science specialists as well as engineers. The people who built the platform are part of every programme. We work directly with your teams, or alongside your advisers and systems integrators.
15. Who runs it after go-live?
Why it matters: the operating model decides how much your own team learns and takes on.
You choose. Zoral can run and support the platform for you, or your own technology team can run it. We can also share the work and hand over as your team grows. Your people run the banking operations and make the credit decisions.
16. Who is Zoral?
Why it matters: you are choosing a partner for many years, not only a product.
Zoral is an independent specialist, founded in 2004 and privately held. We have delivered over 100 projects, and our team has 350+ years of combined experience. The platform is our own. We have worked with clients regulated by the FCA in the UK, the CFPB in the US and the central banks of Malaysia and Thailand. We have a long-standing relationship with KPMG. References are available in confidence.
17. How do we start?
Why it matters: large programmes that try to change everything at once are the ones most likely to stall.
We suggest starting with one product, one portfolio or one channel. You then add the next on the same platform, reusing what the first one built. We give a realistic plan after scoping, not before.
Our point of view, in brief
We have set out how we see three common problems in three short papers. Here are their main points, and the questions each one suggests your leadership team asks itself. Each paper can be downloaded in full.
The cost of change
Why bank strategies stall in a growing backlog of IT projects, and how to break the cycle
- The cost of change is a business problem, not an IT problem. It decides how many of the executive committee's priorities reach customers in time to matter.
- The usual remedies often make it worse. Large replacement programmes, platforms chosen by ticking boxes, and credit rules rebuilt separately for every channel all make the next change more expensive.
- The banks that move faster change one product at a time and build around their core system instead of replacing it. They keep credit and pricing rules in one place, and let business owners make changes themselves, with proper controls.
- They keep a record of every decision as they go. Over time, they spend less on maintenance and more on growth.
Download the paper (PDF) →Questions for the executive committee
- What did our last product launch really cost, across every budget it touched, and how much of that will we pay again for the next one?
- In how many places does our credit and pricing policy live, and how long does an approved change take to reach all of them?
- If a supervisor asked tomorrow, could we reproduce a decision we made a year ago, with its data and reasons?
- Where are our people already using AI, and could we show what it did?
- When we last chose a platform, did we test how quickly our own people could change it?
- How much of our technology budget goes on maintaining what we have, and how much on new products?
Converting more of the pipeline, profitably
A framework for improving conversion across a multi-product lending portfolio
- Most applications are lost before and after the credit decision, not at it. The larger losses now come at verification, approval, offer and funding.
- Conversion only counts if it is profitable. Every change is judged on three tests together: conversion, cost per funded loan, and credit quality with fair customer outcomes.
- The real advantage is how often you can make changes. When business owners can change the loan process themselves, with proper controls, it keeps pace with the market.
- Improvements build up across the portfolio. What lifts conversion in one product can be reused in the next.
Download the paper (PDF) →Questions for lending leadership
- Do we know our conversion at each stage of the pipeline, by product, channel and partner?
- Between application and payout, how much time is spent deciding, and how much waiting?
- When we improve conversion, do we check the effect on cost per funded loan and on credit quality at the same time?
- How long does an approved change to policy, pricing or journey take to reach customers, and how often do we make one?
- When one product improves, does the next one benefit, or do we start again?
- When we last chose an origination platform, did we test how quickly our own people could change it?
Closing the convenience gap in Islamic banking
Why many customers who would prefer Islamic finance still bank conventionally, and what the banks that grow do differently
- In our experience, many customers who would prefer Islamic finance still bank conventionally, because the Islamic option has meant more paperwork and more waiting.
- The cause lies in how Islamic products are run, not in what they are. Trade and ownership steps, profit calculations and evidence for Shariah governance are too often managed outside the bank's systems.
- The banks that grow let the platform run the contract structures their board approves, and show the board exactly what is running.
- They test each product over its full life before launch, and grow one product at a time.
Download the paper (PDF) →Questions for the executive committee and Shariah board
- Where does an Islamic customer meet more paperwork or waiting than a conventional one, and how many never apply because of it?
- Which steps in our Islamic products are carried by people and spreadsheets rather than by our systems?
- Could our Shariah board see today exactly what is live, with every version and who approved it?
- Do we see how a new product behaves over its full term, including early settlement and missed payments, before customers do?
- Does each new Islamic product make the next one easier to launch, or harder?
- If we could launch one more Islamic product this year, which would matter most, and what stands in its way?
Where to start, by role
| Your role | Start here |
|---|---|
| Chief executive | All solutions · Modernise around your core |
| Chief risk officer or head of credit | Zoral Decision Engine · Credit risk and decisioning · Portfolio optimisation |
| Chief information or technology officer | Zoral fOS · Zoral Integration Gateway · Zoral Trust Portal |
| Chief operating officer or head of operations | Underwriting automation · Intelligent document processing |
| Head of Islamic banking, or Shariah board | Islamic digital banking · Islamic banking implementation |
| Head of collections | Customer lifecycle and collections |
| Auto finance, hire purchase and leasing | Auto finance |
| US mortgage lender | US mortgage automation |
| New digital bank or fintech | Digital banking |
| Telco, marketplace or platform offering credit | BNPL and point-of-sale finance · Supply chain finance · Alternative finance |
| Procurement and vendor risk | Zoral at a glance · Zoral Trust Portal |
Chief executive
Start here
Chief risk officer or head of credit
Chief information or technology officer
Start here
Chief operating officer or head of operations
Head of Islamic banking, or Shariah board
Head of collections
Start here
Auto finance, hire purchase and leasing
Start here
US mortgage lender
Start here
New digital bank or fintech
Start here
Telco, marketplace or platform offering credit
Procurement and vendor risk
Start here
Bring the questions your committee will ask.
A senior Zoral team will answer them for your own products, and show you the platform working.
Contact Us
Prefer to pick a time? Schedule a meeting
Automate lending, banking and finance operations.
London
+44 20 3963 2002Miami
We are on Socials