> 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/automations/setting-up-auto-pay/invoice-creation-date-auto-pay-rules.md).
# Invoice Creation Date Auto-Pay Rules
**Here’s how you can set up auto-pay rules for your customers based on the invoice creation date.**
***
You now have more flexibility in [setting up auto-pay rules](/automations/setting-up-auto-pay/setting-up-auto-pay.md) based on when the invoice was created. This configuration is particularly useful for customers who have invoices with net terms to make arrangements to pay their invoices.
You can set this auto-pay rule within the Customers or Auto-pay sections of your Alternative Payments dashboard.
***
### **Customers**
In the [Customers > All customers](https://app.alternativepayments.io/dashboard/customers) section, click the customer profile you wish to edit. Scroll down to the Automation section and select “+Add new rule.”
From the conditions dropdown, select “Days past creation” and then select the number of days. Click on “Confirm” to save the rule.
***
### **Creating Auto-pay Rules**
Within the [Automations > Auto-pay](https://app.alternativepayments.io/dashboard/autopay-rules) section, select “[Create new](https://app.alternativepayments.io/dashboard/autopay-rules/new)”
We always recommend making auto-pay rules customer-specific. Go to the "Customer specific" section, and Select the applicable customer(s).
From the conditions dropdown, select “Day past creation” and then select the number of days. Click “Review” to see the affected invoices.
Review the details of the new rule, including the affected customers and invoices. You can exclude specific invoices from autopay if needed. Click "Create rule" to save the rule for the customer.
{% hint style="info" %}
**NOTE:** Auto-Pay rules are evaluated nightly. Once a rule is created or updated, it takes effect on the next nightly processing cycle.
{% endhint %}
You’re all set 🎉!
{% hint style="info" %}
**Tip**: Auto-Pay rules follow **AND/OR** logic. Within a single rule, **all** conditions must be met for auto-pay to trigger (**AND logic**). If you have multiple rules, the system checks each one separately and will trigger auto-pay if at least one rule meets **all** of its conditions (**OR logic**). This means auto-pay won’t trigger if only some conditions of a rule are met, but as long as one rule is fully met, auto-pay will be triggered.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.alternativepayments.io/automations/setting-up-auto-pay/invoice-creation-date-auto-pay-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.