> 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/help/faqs.md).

# FAQs

Get short answers to common questions about accounts, applications, stages, drafts and application links.

<details>

<summary>Is an account the same as a company?</summary>

Yes. The UI also calls a company an *account*; the two words mean the same thing. See [Platform organization](/commercial-lending/getting-started/concepts/how-the-platform-is-organized.md).

</details>

<details>

<summary>Is an application the same as a deal?</summary>

Yes. It is the same record. The Applications list calls it an *application* and the Deal Hub context calls it a *deal*. See [Applications and deals](/commercial-lending/getting-started/concepts/applications-and-deals.md).

</details>

<details>

<summary>Why doesn't the Dashboard show a Not Eligible tile?</summary>

The Dashboard has no **Not Eligible** tile. Find those deals on [Applications](broken://pages/HlkkNFhKVf67h4lJZGgG). The stage tiles are informational; selecting one doesn't filter anything. To filter by stage, use the chips on Applications.

</details>

<details>

<summary>Does matching a Schedule C business change any figures?</summary>

No. The confirmation reads: "This will identify {business} as {entity} for this year. It does not change any P\&L numbers; inclusion is handled separately." See [Schedule C business matching](broken://pages/UE0EkjiLmwJY2mdYWCeJ).

</details>

<details>

<summary>Where is my application draft saved?</summary>

Your draft is saved in the browser where you created it. Local drafts stay available only in that browser and device. Finish in one session, or share the application link to continue elsewhere. See [Create an application](broken://pages/jy8mBPWHRQj8daUlc1Il).

</details>

<details>

<summary>Why should I treat an application link as a secret?</summary>

The link carries credentials as plain query parameters, along with the user's email and ID. Don't post it in public channels, don't paste it into URL-shortener services that log inputs, and verify the recipient before sending. See [Share an application link](broken://pages/rcx1W9b9UuFC6sjfB4aJ).

</details>

<details>

<summary>What must a product be before applications can use it?</summary>

Both **Active** and **Published**. See [Products and product categories](/commercial-lending/getting-started/concepts/products-and-product-categories.md).

</details>

<details>

<summary>Which product line is my deal on?</summary>

A deal's product line follows its product's category. CRE and C\&I products are on Commercial LOS. See [Product lines](/commercial-lending/product-lines.md), and use the [Product guide](broken://pages/Np5ORd2exN02N4NoTvX8) to tell products apart from what you see on screen.

</details>

<details>

<summary>Why doesn't my deal have an LOI stage?</summary>

The stages depend on the product. An ICRE deal has no LOI, Credit Memo or Closing stage. Greenlight and Term Sheet take their place. See [Loan stages](/commercial-lending/getting-started/loan-stages.md) and [Product lines](/commercial-lending/product-lines.md).

</details>

## 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>Troubleshooting</strong></td><td></td><td><a href="/commercial-lending/help/troubleshooting.md">Troubleshooting</a></td></tr><tr><td><strong>Concepts</strong></td><td></td><td><a href="/commercial-lending/getting-started/concepts.md">Concepts</a></td></tr><tr><td><strong>Glossary</strong></td><td></td><td><a href="/commercial-lending/getting-started/glossary.md">Glossary</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/help/faqs.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.