> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/payments-and-invoicing/payments-and-payouts/scheduling-invoice-payments.md).
# Scheduling Invoice Payments
**Scheduling payments in Alternative Payments is a convenient way for your customer to make a payment on a specified date**
\*\*\*
{% hint style="info" %}
**Tip:** Payments won’t run unless there’s a valid payment method on file. Double-check that one has been added to the customer’s account.
{% endhint %}
**Steps:**
1. From your Alternative Payments Dashboard, go to [**Invoices**](https://app.alternativepayments.io/dashboard/invoices)
2. Click `...` next to the invoice you would like to schedule, and select **Charge**
3. Click **Charge on future date** and **select a date** to schedule when the payment should be processed
4. Click **Charge invoice**
That's it, the payment will be processed on the selected date! 🎉
{% hint style="info" %}
**Date constraints:** The scheduled date must be a future date.
{% endhint %}
{% hint style="info" %}
**Cancellation:** To cancel a scheduled payment before it processes, navigate to the invoice, click `...`, and select **Cancel scheduled payment**.
{% endhint %}
**Love our platform?** Rate us on [Channel Program](https://channelprogram.com/v/alternativepayments) and check out our [Referral Program page](https://www.alternativepayments.io/referral-partners/)!
---
# 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://help.alternativepayments.io/payments-and-invoicing/payments-and-payouts/scheduling-invoice-payments.md?ask=&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.
