> 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/commercial-lending/getting-started/concepts/applications-and-deals.md).

# Applications and deals

Learn what an application is, why the UI says deal, and what happens when it reaches Closed.

An application is the record that represents a loan request through every pre-servicing stage. It enters the system at **Intake**, moves through underwriting via **Application**, **Pre-Screening**, and the memo stages, and ends at **Closed**, **Not Eligible** or **Withdrawn**.

Once an application reaches **Closed**, it spawns a loan account in Servicing.

Across the UI, the same record is called an *application* on the Applications list and a *deal* in the Deal Hub context. These docs use *application* consistently for pre-servicing.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Loan stages</strong></td><td></td><td><a href="/commercial-lending/getting-started/loan-stages.md">Loan stages</a></td></tr><tr><td><strong>Applications</strong></td><td></td><td><a href="broken://pages/HlkkNFhKVf67h4lJZGgG">Broken link</a></td></tr><tr><td><strong>Loan accounts</strong></td><td></td><td><a href="broken://pages/9TlAoueET4bz7Ghm30HL">Broken link</a></td></tr><tr><td><strong>Portfolio stages and the deal workflow</strong></td><td></td><td><a href="/commercial-lending/getting-started/concepts/portfolio-stages-and-the-deal-workflow.md">Portfolio stages and the deal workflow</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://2424445642-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoNOfYlgbuwiWKkdQsRIp%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/commercial-lending/getting-started/concepts/applications-and-deals.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.
