> 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/payment-groups.md).

# Payment Groups

## Overview&#x20;

The BSM Dashboard - Payment Groups interface serves as the centralized treasury control workspace for&#x20;monitoring, validating, and executing batch disbursement transactions across various corporate entities, currency&#x20;accounts, and banking institutions.

This module provides real-time visibility into scheduled payment batches (groups), funding balances in source wallet&#x20;accounts, commitment categories, and critical pre-processing alerts\
requiring administrative intervention. <br>

<figure><img src="https://2874191586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F55w5yhQ5DYMhZTTddKQn%2Fuploads%2FKEQGJjgYh2Zi13QBbbNx%2Fimage.png?alt=media&amp;token=ea749d14-7eec-457b-8aa3-1a08b931247c" alt=""><figcaption></figcaption></figure>

## Interface

**Global Navigation & Header Controls**

* Company Selector: Dropdown menu filtering all data and transaction groups by selected legal operating entity.
* Commitments Filter: Tag-based multi-select filter restricting visible payment groups to specific source document categories.
* Module Tabs: Navigation bar allowing operators to switch between Quick Launch, BSM Dashboard (active view), and BSM Sandbox (testing environment).

**Action Toolbar**

* Expand/Collapse All: Toggles expandable detail rows across all visible payment groups.
* Print Control: Generates a summary report / printable output of the filtered payment list.
* Process Payments Button: Primary action execution trigger for selected payment batches (active once valid, non-blocked rows are selected).


---

# 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/payment-groups.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.
