Standard access and information requirements UiPath establishes with your institution before deploying the Loan Setup and Quality Control (QA/QC) capabilities, including system API access, event notifications, and PII storage.

Before deployment begins, UiPath works with your institution to establish the access and information needed to configure the solution. This page lists the standard requirements that apply to both Loan Setup and QA/QC implementations.

UiPath does not have direct access to your institution's systems of record or APIs. Any RPA automations requiring direct interaction with core systems rely on your Center of Excellence (CoE) team's expertise to extract data and write results back.

UiPath releases solution updates on a regular cadence, typically every few weeks, to improve agent quality, enhance performance, and resolve issues. Updates are deployed into your Development and UAT environments first. Production deployment follows your institution's established release schedule. UAT and Production environments can be deployed at the folder level in addition to the tenant level.

Running either capability requires customer PII to be stored in UiPath cloud products: Orchestrator Storage Buckets, Data Fabric (available in preview), and UiPath Agents. All PII is stored following UiPath platform security guidelines and applicable data residency rules.

Core banking systems contain data required to validate loan information. API access is the preferred integration method due to reliability and performance. A UI-based RPA approach is possible but introduces additional complexity and reduces stability.

The Loan Origination System (LOS) contains loan data the solution retrieves and validates throughout the workflow. API access is the preferred integration method due to reliability and performance. A UI-based RPA approach is possible but introduces additional complexity and reduces stability.

Both capabilities follow an iterative workflow where documents and data are updated repeatedly in the LOS. UiPath recommends subscribing to LOS events, as available in platforms such as Encompass, to trigger Maestro workflows automatically. If eventing is not available, a scheduled polling mechanism can be designed jointly to detect updates and initiate processing.

Most institutions store loan documents in repositories such as OnBase. Read access is required to retrieve documents, typically by Loan ID and date range, for IXP processing. Write access is needed to store outputs such as QC audit reports and process logs for servicing, compliance, and record-keeping.

Some workflows involve ordered reports such as flood certifications, credit reports, or appraisals. If these are not automatically ingested into your document repository, direct retrieval from the originating systems may be required.

Request a demo to connect with the UiPath team about the Loan Origination Solution.