Automation that keeps working when screens change

The problem with retyping

Every lender has systems it cannot connect to. A warehouse bank’s portal. An investor’s portal. An old core system with a green screen. The data still has to move, so people copy it from one screen to another. It is slow, it causes errors, and it pulls skilled staff away from the work only they can do.

Traditional robotic process automation helps, until a screen changes. Then the robot stops, someone has to fix it, and the work piles up again. And it usually runs on a separate platform, with its own records and its own team.

What Zoral Resilient RPA changes

Zoral Resilient RPA, part of the Zoral Finance Operating System (fOS), reads and enters data on screen, as a person would. It runs under Zoral Core Orchestrator, as a step in your lending workflow. There is no separate bot platform to manage.

When a screen changes, a vision language model reads it. Your bank approves the model and sets its guardrails. The model works on a test account, or on a screen with the data removed. The data the robot brings back is checked by the workflow’s rules before it is used.

What this means for your operations team:

• less retyping between systems, and fewer errors;
• automation that keeps running when a portal changes its layout;
• work that sits in the same queues, with the same approvals, as the rest of the loan file;
• staff freed for the cases that need judgement.

Control and evidence

Every step the robot takes is recorded in the same audit trail as the rest of the workflow. Screen snapshots are blurred or masked before they enter the audit trail. Each robot is versioned, tested and approved like any other change. Before go-live, your bank confirms that each external site’s terms of use and local rules allow automated access.

Keep your own where you need to

Already use an RPA platform such as UiPath? Zoral fOS works with it. Use Zoral Resilient RPA where screens change often, or where automation must sit inside your lending workflows. One point to weigh: work done inside Zoral fOS shares one audit trail and one record of each loan file.

Where it fits

Zoral fOS has one centre. Zoral Data Fabric remembers every application, decision and change. Zoral Decision Engine makes every decision. The Business Outcomes Layer measures every result against plan. Around that centre, the other components do the work. Every Zoral solution reaches out from it into a product or a channel, and draws on the same data, rules and measurement. So each new product costs less to launch, and starts smarter, than the last.

Zoral Resilient RPA sits around the centre. It works most closely with Zoral Core Orchestrator, Zoral Document Fabric and Zoral Integration Gateway.