> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/charted-configuration/on-premise-check-printing/managing-check-formats-and-bank-mapping.md).

# Managing Check Formats & Bank Mapping

### Abstract <a href="#x0xojzjnahfi" id="x0xojzjnahfi"></a>

In *Advanced Check Printing*, each check format must be mapped directly to a general ledger GL account and a bank account in a one-to-one relationship. This mapping ensures that the correct check layout and bank information are applied consistently during check printing. For example, an organization with separate *U.S.* and *Canadian* bank accounts may require distinct check templates to meet formatting standards in each country.

This article explains how to access and configure check formats linked to GL and bank accounts.

### **Managing Check Formats and Bank Mapping** <a href="#yvxtnba7nmqv" id="yvxtnba7nmqv"></a>

Check formats define how printed checks are structured and are directly linked to specific GL and bank accounts. These configurations support formatting requirements across different banking institutions, helping ensure compliance with layout standards such as regional date formats or custom templates.

Follow these steps to access and review check format configurations:<br>

1. To navigate to **Check Formats**, hover over the **Setup** menu, go to **Check Printing**, and select the **Check Formats** option, which will take you to the **CPB Check Format List** page:\ <br>

   <div align="left"><img src="/files/JLrLxY5EZPZZPJ2pmg1J" alt="" width="458"></div>

   ![](/files/KlooorFH69rDItGZzI5p)

   \
   \
   This page contains half of the check printing configuration, specifically where the bank-related information is managed.\ <br>
2. To view a specific check, click the **View** button next to the entry, which will take you to the **CPB Check Format** page:\ <br>

   <div align="left"><img src="/files/24LWtR8Q9uDfj0JPLLx8" alt=""></div>

   <div align="left"><img src="/files/0kR8Av3pbw7Es0gzktZw" alt=""></div>

   <br>
3. At the top of this page, you’ll find the **Check Name**. The number in the name (e.g., 1338) represents the last four digits of the related bank account:\ <br>

   <div align="left"><img src="/files/71ziM3r5IXYnWX1c5Hop" alt=""></div>

   <br>
4. Each check format is tied to a specific GL account. This forms a one-to-one relationship between a check format, a GL account, and a bank account — meaning they cannot be shared or mixed:\ <br>

   <div align="left"><img src="/files/1zPa3PU7UXl2H1vM8WDn" alt=""></div>

   <br>
5. In this view, you must also select a **CHECK TEMPLATE** for the check format. This ensures that each bank can use a layout that meets its requirements:\ <br>

   <div align="left"><img src="/files/lTc2AouJrSXQrMePJuKx" alt=""></div>

   \
   \
   For example, if a customer has both **U.S.** and **Canadian** banks, they may need different check templates. This is because **Canadian** banks require a different date format than **U.S.** banks, making a separate template necessary.\ <br>

This concludes the overview of managing check formats and bank mapping.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.charted.com/ap-automation/charted-configuration/on-premise-check-printing/managing-check-formats-and-bank-mapping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
