> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/biscit-spend-management/add-supplier-banks.md).

# Add Supplier Banks

## Overview

The Add Supplier Banks sub-module within the BSM Dashboard allows administrators and accounts payable specialists to review, validate, and select newly imported or configured supplier bank profiles for enterprise disbursement processing. It enforces system integrity by highlighting invalid data fields (such as invalid routing methods, malformed routing codes, missing bank details, or incomplete address records) prior to finalizing account integration.

**Module Context & Functionality:** This interface functions as a staging area for batch onboarding supplier banking details. Profiles are batch-selected via checkboxes and committed to the active system using the Add Selected action button.

<figure><img src="https://2874191586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F55w5yhQ5DYMhZTTddKQn%2Fuploads%2Ft34zt9XZCjdrpzx3gTNB%2Fimage.png?alt=media&amp;token=1c65918c-c894-4a3e-93c4-6d54109feefb" alt=""><figcaption></figcaption></figure>

## Control Header & Navigation Panel

| **UI Element**             | **Functional Purpose**                                                                                                                              |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Active Module Tab          | Primary operational workspace tab within the BSM suite environment.                                                                                 |
| Company Context            | Determines the corporate entity context to which selected supplier bank profiles will be bound.                                                     |
| Commitments Filter Tag Box | Filters staging records to align with active AP and PO commitment workflows.                                                                        |
| Primary Action Button      | Commits selected, validated supplier bank records into the active enterprise database. Enabled only when valid records are selected via checkboxes. |
| Pagination Controls        | Grid navigation bar supporting page switching and showing total staged records (25 total entries across 2 pages).                                   |

### Staging Grid Column Structure

The staging grid organizes bank profile parameters into structured columns equipped with individual filter indicators:

| **Column Header**  | **Field Type**           |
| ------------------ | ------------------------ |
| Selection Checkbox | Multi-Select Control     |
| Supplier Bank      | Text / Identifier        |
| Currency           | ISO Currency Code + Flag |
| Routing Method     | Dropdown Select          |
| Routing Code 1     | Numeric Code             |
| Routing Code 2     | Numeric Code             |
| Account Number     | Alphanumeric Code        |
| Bank Name          | Text                     |
| Bank Address       | Text                     |
| Account Name       | Text                     |
| Address            | Text                     |
| Email              | Email Address            |

## Data Validation Diagnostics & Exception Types

The staging grid automatically screens imported records and visually highlights missing, incomplete, or malformed data elements using red badges and red background shading:

**Identified Validation Exception Classes:**

* **Invalid Routing Method:** Occurs when the assigned method does not match supported payment protocols.
* **Routing Code Errors:** Shaded red fields in *Routing Code 1* or *Routing Code 2* indicate malformed digits or character length mismatches.
* **Bank Detail Exceptions:** Flagged bank name entries prevent automated routing.
* **Incomplete Supplier Address:** Flagged red badges next to supplier street addresses highlight invalid/dummy formats .


---

# 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.biscit.com/biscit-spend-management/add-supplier-banks.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.
