Say yes sooner. Explain every no.

No. Zoral can work alongside what you run today, including an existing mortgage origination system. It reads the file, runs checks and decisions, and writes the results back. Zoral’s decisions can also serve your other origination systems, so credit policy is kept in one place. Lenders often start where delays are worst and move more onto Zoral when it makes sense.

Yes. Products share customer data, checks, controls and audit history. Each product keeps its own rules, workflows, documents and reports. Conventional and Islamic versions run side by side, with Islamic terms on screens and documents. Your Shariah board remains the authority; Zoral provides the configurable structures and the evidence trail for its review.

Your credit and product teams make the change, and the platform keeps it controlled. Each change becomes a new version, simulated on past applications to show its effect on approvals and expected losses. A second person approves it, and it is released to all applications or a share of them. If results disappoint, the previous version can be restored, with the history kept.

Each decision is stored with the data used, the policy and model versions applied and the reasons for the outcome, so it can be reproduced as it was made. Your teams can use those reasons in customer notices and regulatory reviews. A customer who asks for a person to review an automated decision can be routed to one, with the full record. The obligations remain yours. Zoral keeps the evidence.

Speed only helps if customers can repay. Your policy sets pricing, limits and terms by risk. Zoral applies it, checks affordability as part of the decision, and watches for early warning signs once loans are funded. You compare actual losses with plan, see where and why they differ, and tune policy with approval.

Yes. Each works through a portal or an API for their role, sees only their own cases, and has tasks and response times tracked. Solicitors, valuers and insurers can be given the same controlled access, configured to their role. You decide what each partner can see and do.

Agents, configured to your policies and workflows, help at each step: completing and checking applications, reading documents, drafting the credit paper, chasing missing items and answering status questions. They work only through the permissions, workflows and approvals you set, and what they do is recorded. You choose the language models behind them, from enterprise model services to open-weight models hosted in your own environment. Your knowledge bases, conversation records and client data stay under your governance, within the environments and agreements you control. Agents do not make credit decisions. Credit decisions follow rules and models your bank approves. Exceptions go to named people, and accountability for each decision stays with your bank.

Alongside the agents, your teams can use:

a bank-statement analyser that checks statements are genuine and flags round-tripping, returned cheques and other unusual flows;

limit recommendations within your policy when affordability falls short, for the approver to accept or change;

machine-learning models compared with your current scorecards, on past and live applications, before you decide to use them;

campaign and product recommendations for existing customers, within your rules;

help for your testers to prepare and check test cases when products or rules change.

Each feature works within your policy and approvals, and every result is recorded.

Through documented interfaces, using what your bank already standardises on: APIs, messaging, events and file transfer, with robotic automation where a system has no interface. Typical connections include core banking, cards, hire purchase, bureaus, fraud and AML screening, document management, identity management, CRM, contact centre and your data lake. In Malaysia, they include the CCRIS central credit registry, CTOS, DuitNow and Jumio for identity checks. If a bureau, core or payment system is unavailable, applications are designed to wait at the step they reached and continue when it returns. Controls are designed to prevent duplicate bookings or payments. Operations teams see the cases affected. We have worked alongside modern cloud cores as well as traditional ones, integrating with them and maintaining their product configuration. Architecture documentation is available under a confidentiality agreement.

Yes. Your agents connect to Zoral fOS through a standard interface (MCP) and can read data, run decisions or start workflows only within the permissions you grant. Guardrails, budgets and human approval steps are set per agent, and every action is traced for review. Business analysts, product and risk managers can also configure Zoral with an AI assistant. Their changes still go through versioning and second-person approval.

Most product and decision logic is configured in a readable form your analysts can review. Where more is needed, business logic is written in readable JavaScript. Your engineers can also work through documented interfaces. Every change, configured or written, goes through the same versioning and approval.

Most banks move product by product or channel by channel, not all at once. Applications already in progress can usually be completed in the current system, and historical records can be migrated where you need them. We give you a realistic plan, including timing, once we have scoped the work together.

You choose who runs it. Zoral can run and support the platform for you, your own technology team can run it, or we share the work and hand over as your team grows. Your people run the banking operations. Your data, product definitions and audit history remain yours and can be exported in standard formats.

Zoral is an independent specialist, founded in 2004, with over 100 projects and 350+ years of combined experience. The platform is our own, and the people who built it lead delivery. 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 and offer references in confidence.

Atelier, Zoral’s consulting and implementation team, works with your teams and, where you choose, with your advisers and systems integrators. The same team can turn your credit policy into decision strategies and models, and take each product live in stages.

Credit risk and decisioning · Engineering and delivery