> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md

# Pay Out batches overview

> Understand how a Pay Out batch moves from open to paid, and what each batch status means

A batch is a group of vendor payout transactions processed and funded together. Each batch carries a single status that reflects where it's at in its lifecycle, from collecting payouts to being fully paid out to vendors.

This page covers batch status and what each status means. For how individual payout transaction statuses relate to the batch they're in, see [Pay Out schemas](/guides/pay-out-schemas-overview#transactions).

## Batch statuses

These statuses appear in the Payabli Portal and the API. They describe a money out batch's status.

| Status    | Key | Description                                                                                                   | Events                                |
| --------- | --- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
| Open      | 0   | The batch is open and hasn't started processing yet.                                                          | None                                  |
| Closed    | 1   | The batch is closed and sent to be processed. Captured payouts can't be canceled at this point.               | Approved Payment Group, Waiting Funds |
| Funded    | 2   | Money has been received from the funding entity (typically the paypoint).                                     | Funded                                |
| Processed | 3   | All payout requests in the batch have a payment type defined for the vendor, and the payments have been sent. | Payment Group Processed               |
| Paid      | 4   | All payout transactions in the batch have been marked as Paid.                                                | Paid                                  |
| Canceled  | -1  | The batch has been canceled.                                                                                  | Cancelled                             |

If you are working with money out endpoints in the API, the **Key** is returned as `BatchStatus`. For example, a response body that includes batch data looks like this:

**`Example batch response`**

```json Example batch response
// Example truncated to show the most relevant fields
{
"Records": [
    {
      "IdBatch": 100,
      "BatchDate": "2023-05-05T00:00:00",
      "BatchNumber": "187-20230505-EXAMPLEBATCH",
      "BatchStatus": 1,
      "BatchStatusText": "Waiting Funds",
 ...
    }
  ]
}
```

The value of `BatchStatus` indicates the status. In the example, the `BatchStatus` is 1, which means it's closed. The `BatchStatusText` returns the most recent event for that status.

A batch starts **Open** and collects captured payouts until it closes automatically at your paypoint's daily cutoff. Once **Closed**, payouts can no longer be added or canceled.

> **Note**
>
> The cutoff time, and what canceling a payout looks like before and after it, both depend on whether you're on managed payables or on-demand payouts. See [Understanding payables](/guides/pay-out-payables-overview#running-your-payables) and [Understanding managed payables](/guides/pay-out-managed-payables-overview#canceling-payments) for the specifics of each program.

When the batch is **Funded**, money has been received from the funding entity — typically the paypoint. The payouts are then sent to vendors, and the batch status changes to **Processed**. A batch reaches **Paid** once every payout transaction in it has a status of *Paid*. For what each payout transaction status means, see [Payout transaction statuses](/guides/pay-out-status-reference#payout-transaction-statuses).

**Canceled** is a defined batch status, but no current UI or API action moves a batch into it directly. Canceling a payout in an open batch removes that payout from the batch instead of canceling the batch itself — the batch continues with its remaining payouts.

## Batch grouping

Payouts group into batches by payment method — the underlying rail, such as ACH, check, wire, or Real-Time Payments (RTP) — not by payment speed. Payment Speed is a label derived from the payout's method, not an independent grouping driver. For how long each method typically takes to reach a vendor, see the [payout timeline reference](/guides/pay-out-payables-overview#payout-timeline-reference).

## Related resources

See these related resources to help you get the most out of Payabli.

#### References

* **[Pay Out statuses](/guides/pay-out-status-reference)** - Learn about Pay Out statuses
* **[Pay Out schemas](/guides/pay-out-schemas-overview)** - Learn about money out statuses and events and how they work together

#### Related topics

* **[Manage Pay Out batches and funding (Portal)](/guides/pay-out-portal-batches-funding-manage)** - Manage batches and funding in the Payabli Portal