Implementation Guide
Plan and run a Retail LOS implementation in order, from foundation to go-live and beyond.
Use this guide to take Retail LOS from lending strategy to day-to-day governance. It follows the order an FI usually works in. Each phase names who owns it, what done looks like, and where to read and what to do.
The phases at a glance
2. Design the product portfolio
FI Administrator, with credit
Create a Product
3. Originate applications
FI Administrator
Build an Application Flow
4. Assess risk and make offers
FI Administrator, with credit
Publish the Decision Matrix
5. Fulfil and manage applications
In Branch Experience and FI Administrator
Work an Application
6. Govern and integrate Retail LOS
FI Administrator and System Admins
System Admins
7. Test, go live and improve
FI Administrator, with credit and compliance
Test Before Go-Live
1. Set the lending foundation
Establish shared context for your Retail LOS implementation. Confirm the Retail LOS model, available products and common terminology before configuration starts.
Done when your team shares one view of what Retail LOS is, which sample products exist and the terms it uses.
Overview: what Retail LOS is and who uses it.
Sample Products: the example products that show how a configuration fits together.
Foundation: Key Concepts: the layers and terms every configuration step uses.
Glossary: definitions, when a term needs clarifying.
2. Design the product portfolio
Turn lending policy and commercial requirements into configurable products. Select the right product model, complete the configuration and validate it before launch.
Done when each product has its type, category and core terms, and stays Inactive until it is ready.

Configure it yourself
Open Product Configuration and select New Product.
Enter the Product Name and Product Code, and select the Product Type and Category.
Set Status to Inactive so applicants cannot see the product while you build it.
Enter the terms that apply, then select Create.

See Create a Product for the other ways to create a product.
Product Configuration: what the module covers and how its parts connect.
Product Settings: the settings and tabs on a product.
Decide the Product Type and Ways to Create a Product.
Guides: Create a Product and Edit a Product's Details.
If you're stuck: Product Configuration troubleshooting.
3. Originate applications
Create a clear path from product selection to a submitted application. Design the applicant journey, then build, test and publish the supporting experience.
Done when an applicant can complete the flow for each Active product and submit.

Configure it yourself
Open Product Configuration and select Flow Designer.
Select Add step and set the Step Name, Description, Icon and Step Type. Select Save Changes.
Select Add Sub Step to add a page within the step, then add the sections the page needs.
Publish the flow. Applicants cannot load the application form without a published flow.
See Build an Application Flow for each step in detail.
User Journeys and the Applicant Journey: what the applicant goes through.
Building Applications: the flow, its steps and its screens.
Starting an Application: how an application begins.
Guides: Build an Application Flow and Set Up Documents and Eligibility.
4. Assess risk and make offers
Apply lending policy consistently at scale. Configure decision logic, pricing, offers and routing so each application receives the appropriate outcome.
Done when the decision matrix or scorecard is published, approval authority is set, and the workflow is published and tested.

Configure it yourself
Open the product and select its Credit Decision Matrix. Make your changes in the draft.
In the Matrix Flight Simulator, enter applicant values and select Run Simulation to check the outcome. It does not write data.
Select Save Draft, then open Diff and check every changed parameter.
Select Publish.
In Official Policy Release, record the business reason in the justification note. It must contain at least five characters.
See Publish the Decision Matrix.
Decisions, Pricing, Offers: the decision engines, pricing, offers and overrides.
Workflows: the steps an application follows and where each outcome leads.
Guides: Publish the Decision Matrix, Set Up a Scorecard, Set Up Approval Authority and Build and Publish a Workflow.
If you're stuck: Product Configuration FAQs.
5. Fulfil and manage applications
Take approved applications through fulfilment with the right controls. Manage documentation, queues, exceptions and lifecycle progress through completion.
Done when queues cover every status your teams work, lifecycle names fit your process, and staff can work and decide applications.

Configure it yourself
Open Configurations → Manage Queues and select Add queue.
Enter a name under New work queue.
Under Statuses that put a file in this queue, select the statuses.
Under Roles that may work this queue or People who may work this queue, select Add next to at least one role or person.
Under Products, add products to limit the queue, or leave it empty to cover every product.
Save the queue and drag it into position.

Documents: the registry, requirements and checklists. See Supported Documents for the types and formats.
Lifecycle and Queues: stages, statuses and work queues.
Application Record and Workflow Timeline.
Guides: Work an Application, Claim, Assign and Transfer an Application, Manage Work Queues and Change a Product's Lifecycle.
If you're stuck: Applications troubleshooting.
6. Govern and integrate Retail LOS
Maintain a controlled and connected lending solution. Configure external services, enforce appropriate access and review the audit trail.
Done when your vendors are connected, API keys and agents are set up, and roles and module access match your policy.

Configure it yourself
Open Settings → Integrations → Third Party Integrations.
Find the provider, for example CRS for credit pulls, and confirm it carries the tags you need.
If it is not connected, select Connect.
To set up failover, connect two integrations in the same family and set Routing priority to
1on the main integration and2on the backup.Open User Management, create the user with the role that matches the job, and add a second role with Assign Role if the person needs more access.
See Connect Third-Party Integrations and Assign Roles and Access.


Use Logs to review who changed what.
Integrations: which vendor handles which task.
Roles and Module Access: what each role can do and open.
Logs: the audit trail, emails, API calls and errors.
Guides: Connect Third-Party Integrations, Manage Users and Assign Roles and Access.
If you're stuck: Settings, User Management and Logs troubleshooting.
7. Test, go live and improve
Prove the configuration end to end, activate it, and keep it healthy as policy changes.
Done when each product has passed an end-to-end test, is set to Active, and changes are reviewed in Version History.

Open each product's page to check its tabs before you set Status to Active.
Test Before Go-Live and Common Mistakes.
The 14-Step Checklist: every step, where it happens and how to know it is done.
In Branch Experience, whose Set up Retail LOS tab walks the same path with guides.
If you're stuck: FAQs and Troubleshooting.
Maintained by Abhishek Paul
AI-assisted, human-approved

Last updated
Was this helpful?

