> 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

# Documentation changes for November 6, 2026

As part of an ongoing effort to better align the documentation with the API, we've documented billing transfers in outbound transfer responses. This change affects the documentation only; the API was already returning this data.

## Documented billing transfers without a batch in outbound transfer responses

Payabli collects vendor enrichment and bank account verification charges through a daily ACH debit from the paypoint, separate from payout batch funding. These debits are returned as transfers with `type` set to `billing` and `processor` set to `billing`. Each paypoint gets one transfer per fee type per day, identified by a `transferIdentifier` of `BILL_{paypointId}_{yyyyMMdd}_VendorEnrichment` or `BILL_{paypointId}_{yyyyMMdd}_BankAccountVerification`.

These transfers aren't tied to a batch, so `batchId` and `batchRecords` are `0` and `batchNumber` is an empty string. `grossAmount`, `billingFeesAmount`, and `netTransferAmount` each hold the charge total as a negative value. Billing transfers for payout fees still belong to the payout's batch. This change affects the following endpoints:

* [Get list of outbound transfers for a paypoint](/developers/api-reference/query/get-list-of-transfers-out-for-entrypoint)
* [Get list of outbound transfers for an organization](/developers/api-reference/query/get-list-of-transfers-out-for-organization)

See [Vendor enrichment](/guides/pay-out-vendor-enrichment-overview#billing) to learn more about how Payabli bills vendor enrichment.