> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/retail-lending/account-opening.md).

# Account Opening

See how an applicant opens deposit accounts in Retail LOS and where each setting lives.

Retail LOS supports checking, savings and money market accounts, for individuals and businesses. An applicant can open one or several deposit accounts in one application, alone or together with a credit product.

> **A deposit application follows the same path as a loan, but it has no underwriting.** It moves through Intake and then the Account Opening stage.

### How an applicant opens an account

{% stepper %}
{% step %}

### Choose accounts

Deposit products appear under **Bank Accounts**. The applicant can select several. Each shows the rows from the product's **Features & Pricing** tab, for example *Minimum Opening Deposit: $25.00*. See [Starting an Application](broken://pages/802GfCWuEgm8kc5qwK7F).
{% endstep %}

{% step %}

### Answer once

Each selected product adds its own sections, and shared sections are merged so the applicant answers once. A savings step asks for the membership notice, the consent and the funding method. See [Applicant Journey](/retail-lending/user-journeys/applicant-journey.md).
{% endstep %}

{% step %}

### Verify identity

The identity check runs as it does for any application. See [Integrations](broken://pages/HDQLTIGTmB72aE21K90r).
{% endstep %}

{% step %}

### See the outcome

Deposit accounts show **Ready to open**.
{% endstep %}
{% endstepper %}

### What FI staff see

The application appears in [Applications List](broken://pages/zgMLkTd4A5I4oD2DlSqv) under the **Account Opening** stage. This stage replaces Underwriting, Closing and Funding for deposit products. See [Lifecycle and Queues](broken://pages/R7nNPhUkV7PFpoQXu97h).

### Where each setting lives

| To set                                                                                                                                  | Go to                                                                                                                                |
| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| The account type: checking, savings or money market                                                                                     | [Decide the Product Type](broken://pages/pUWg5cwsueJfptR9K75P)                                                                       |
| The terms the applicant sees, such as minimum opening deposit, monthly fee and APY                                                      | The **Features & Pricing** tab. See [Product setup tabs](broken://pages/Kw4nVkT343872n04UwP2).                                       |
| The savings and membership step: card title, minimum opening deposit (default $5), membership notice, consent label and funding methods | The **Savings Account** tab. See [Product setup tabs](broken://pages/Kw4nVkT343872n04UwP2).                                          |
| Where deposit questions appear in the journey                                                                                           | A **Product Application** step with the **Deposit / Bank Account** family. See [Flow Designer](broken://pages/ppvXFPRK3dMvYLASFBML). |
| Which tabs a deposit product has                                                                                                        | A deposit account has 13 tabs. See [Product Classification](broken://pages/iXWUGrvKWYOJg6yzNcaC).                                    |
| Events sent to PortX as an application moves                                                                                            | [Outbound events](broken://pages/HDQLTIGTmB72aE21K90r#outbound-events)                                                               |

The **Requires Core Banking** and **Requires CRM Sync** switches are on the product, for deposit types only, and are off by default. See [Decide the Product Type](broken://pages/pUWg5cwsueJfptR9K75P).

### Related

<table data-view="cards"><thead><tr><th>Learn more</th><th data-card-target data-type="content-ref">Page</th></tr></thead><tbody><tr><td>See the sample checking, savings and money market products.</td><td><a href="/retail-lending/sample-products.md">Sample Products</a></td></tr><tr><td>Follow the applicant, FI staff and Partner journeys.</td><td><a href="/retail-lending/user-journeys.md">User Journeys</a></td></tr></tbody></table>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://2966508920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff06WQMAu97E0STor0yyS%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/retail-lending/account-opening.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.