> 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/release-notes/2026/october.md).

# October

Read the release notes for Commercial Lending version 2.6.20.2, released in October 2026.

October adds entity checks, partner banks, schedules, bulk publishing, global configuration, and an audit trail log.

### Entity and identity checks

* Check an entity's Articles of Organization against its record. When an entity does not clearly outlast the loan, the check blocks moving the file into Closing until you resolve it.
* Review personal and business background reports against the entity record. Keep the entity value or apply the report's suggestions.
* Record the source of an entity field in a source note.
* Follow a UCC search on a progress view that updates by itself. If a search is already running, check its status, keep waiting, or replace it with a new search.
* Add a required checklist document to a deal, with its type, subtype, period, label, and the entities it applies to.

### Partner banks

* Sync partner (lead) banks nightly from your system of record. Partner Bank Sync is a feature that an admin enables in **Settings** → **Features**.
* Browse partner banks, choose the lead bank on an application, and show the lead bank's details and debt summary in the credit memo.

### Administration

* Schedule background jobs that run on a company's data, with a run-as account and a run history. My Schedules is a feature that an admin enables in **Settings** → **Features**.
* Publish the products of several companies and product types at once with Bulk Publish. Each product gets a new published version.
* Configure global products, including credit policy, document requirements, and memo configuration, and create Global Teams that are shared by every company.
* Review the Audit Trail: every insert, update, and delete on a business table, filtered by record, user, or table, with an event detail view.
* Create API keys for a specific user. The key acts as that user and follows that user's roles. Older company-level keys can be deactivated once replaced.
* Choose whether a section of a document template prints its heading, and whether an uploaded template's cover page is used. See [Document template](broken://pages/a3d1212da448a9d8a11ee2ea700447330496a985).

### Underwriting

* Choose which sources count for each year on the Layout tab of Underwriting Review, and review the resulting Aggregate P\&L.

### Intake

* Send applicants a global intake link for a product. They sign in with their email, answer the product's intake questions, and choose the company the application goes to. It is saved there as a draft.

***

{% 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/release-notes/2026/october.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.
