> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/charted-faqs/payment-automation/when-will-my-vendor-receive-an-ach-payment.md).

# When will my vendor receive an ACH payment?

Usually 4 to 5 business days after you release it, typically one business day after the debit posts to our account. Release by 5:00 PM Eastern time for the payment to process that day. After the cutoff, it processes the next business day. The cutoff is Eastern time wherever you are: 2:00 PM Pacific or 3:00 PM Mountain.

| Released before 5:00 PM ET on | Typically received |
| ----------------------------- | ------------------ |
| Monday                        | Friday morning     |
| Tuesday                       | Monday             |
| Wednesday                     | Tuesday            |
| Thursday                      | Wednesday          |
| Friday                        | Thursday           |

These times are approximate. Bank holidays delay processing: a payment released after the cutoff on a Friday before a Monday holiday is not processed until after the holiday. The receiving bank can also add delay.

{% hint style="info" %}
See [Tracking and reconciling payments](https://docs.charted.com/ap-automation/charted-features/payment-automation/tracking-and-reconciling-payments.md).
{% endhint %}


---

# 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.charted.com/ap-automation/charted-faqs/payment-automation/when-will-my-vendor-receive-an-ach-payment.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.
