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

# Transactions

## Overview

Transactions serves as the central operational workspace for managing cross-currency electronic&#x20;disbursements, supplier bank routing, and commit tracking within the Enterprise Resource Planning (ERP) platform.&#x20;It offers real-time visibility into active payment pipelines, funding source dynamics, FX conversions, and processing&#x20;statuses across defined organizational entities.

<figure><img src="https://2874191586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F55w5yhQ5DYMhZTTddKQn%2Fuploads%2FTaaoXoICXa6QL3FqGXga%2Fimage.png?alt=media&amp;token=7dcd0694-cd09-405e-9ad7-8be90b97ac36" alt=""><figcaption></figcaption></figure>

### Navigation & Top Control Bar

The primary control panel at the top of the application configures the operational context, filtering parameters, and system state:

| **UI Element**      | **Functional Description**                                                                                         |
| ------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Navigation Tabs     | Switches between *Quick Launch*, active *BSM Dashboard*, and *BSM Sandbox* testing environments.                   |
| Company Selector    | Sets the active multi-company context within the enterprise system to determine transaction ledger boundaries.     |
| Commitments Filter  | Multi-select filter tag box specifying transaction commitment categories included in the active grid display.      |
| System Utilities    | Top-right action bar containing system alerts, manual data refresh, and transaction export/download functionality. |
| Left Action Sidebar | Direct access to Main Navigation, Analytics, Calendar, Financials, Banking, Communications, and System Settings.   |

### Transactions Data Grid Structure

The core table presents individual batch payment runs. The grid splits financial data into two key operational columns: Funding Source (disbursement account debit) and Payment (vendor ledger credit).

| **Column Group**                                               | **Field Name** |
| -------------------------------------------------------------- | -------------- |
| Routing & Context                                              | Supplier Bank  |
|                                                                | Payment Date   |
|                                                                | Reference      |
| <p>Funding Source</p><p><br></p><p><em>(Source Debit)</em></p> | Amount         |
|                                                                | Fees           |
|                                                                | Total Amount   |
|                                                                | Currency       |
| <p>Payment</p><p><br></p><p><em>(Vendor Credit)</em></p>       | Amount         |
|                                                                | Currency       |
| Lifecycle State                                                | Status         |

### Reviewing & Filtering Queue Items

1. Verify that the correct Company Context  is selected in the top selection dropdown.
2. Ensure active commitments are filtered to include Accounts Payable and Purchase Orders.
3. Utilize column filter icons on *Supplier Bank*, *Payment Date*, *Currency*, or *Status* to isolate specific disbursement batches.

#### Managing Cross-Currency Discrepancies & Fees

* Cross-Currency Settlements: When source and payment currencies differ, ensure external treasury exchange rate locks are verified prior to final release.
* Banking Fee Auditing: Standard transaction fees are automatically calculated in the *Fees* column and added to *Total Amount*.

#### Exception Handling

If items remain in Processing status past expected banking clearing windows, click the Refresh Icon in the top utility bar. For persistent delays, review system alerts via the Warning Icon or notify the Treasury Operations Administrator.


---

# 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/transactions.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.
