> 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/commitment-details-1.md).

# Commitment Details

## Overview

The Commitment Details page provides treasury specialists and AP administrators with a&#x20;comprehensive, centralized view of outstanding corporate liabilities. It serves as the primary staging grid for&#x20;selecting, filtering, and grouping outstanding financial commitments such as Purchase Orders (PO) and&#x20;Accounts Payable (AP) Invoices, prior to generating consolidated payment batches.

<figure><img src="https://2874191586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F55w5yhQ5DYMhZTTddKQn%2Fuploads%2FykC8eTTQztTJ7Acf3xsn%2Fimage.png?alt=media&amp;token=d88357cf-fe44-4ab4-8d74-13af908646c7" alt=""><figcaption></figcaption></figure>

## Interface

#### Top Filter & Selection Bar&#xD;

**Company Selector:** Dropdown menu filtering commitments by legal entity context.

**Commitments Tag Filter:** Multi-select field allowing users to filter shown records by commitment types.

**Create Payment Groups&#x20;Button:** Primary action button located in the top right. Triggers the payment batching&#x20;workflow for selected or filtered commitment records.

Interactive Staging Grid Features

**Grouping**: Header drop area enabling dynamic, multi-level row&#x20;grouping by dragging column headers.

**Column Filtering & Sorting**: Each column header includes inline filter and sort controls for precise&#x20;query refinement.

## **Data Grid Reference**

| **Column Header** | **Field Description**  | **Operational Notes**                              |
| ----------------- | ---------------------- | -------------------------------------------------- |
| Supplier          | Vendor name            | Identifies beneficiary supplier.                   |
| Reference         | Source document ID     | Hyperlink opens source document in Epicor.         |
| Balance Due       | Current unpaid balance | Amount eligible for disbursement.                  |
| Total Amount      | Original gross value   | Full document total prior to partial payments.     |
| Currency          | Transaction currency   | Payment currency requirement.                      |
| Due Date          | Payment deadline       | Schedule date for discount & cash flow management. |
| Type              | Commitment type        | Originating transaction category.                  |
| Status            | Lifecycle state        | Indicates document is ready for batching.          |

## Special Alerts & Exception Handling

**Caution Flag (⚠️):** Invoice Reference displays a yellow caution icon.

**Common Causes:**

* Supplier account compliance or tax verification hold.
* 3-way matching price/quantity variance on PO/Receipt.
* Duplicate invoice number detection warning.
* Unverified vendor bank account details.


---

# 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/commitment-details-1.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.
