> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/support/transactions/billing-schedule.md).

# Billing schedule

Customize what time of day and in what timezone your recurring subscription orders will be processed

Within the Smartrr app, navigate to **Transaction Settings** under CONFIGURATION in the left-hand menu:

<figure><img src="https://3658670565-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FndNAuxS4koYyI8AQTpS9%2Fuploads%2FtPEQZLMxWrmcGuf0bKWi%2Fbilling.png?alt=media&amp;token=847a104d-b583-4567-97b4-070e900238ca" alt="The billing schedule determines what time and which days the app should attempt to bill your customers. You can set the billing time, the time zone, and select the day/s of the week that the app should attempt to bill your customers."><figcaption></figcaption></figure>

Under the **Billing Schedule** heading, you’re able to set the time of day and time zone for which your store will charge customers for their subscriptions and generate orders. By default, Smartrr charges customers at 9:30AM in the time zone of your store.&#x20;

{% hint style="info" %}
**Note:** your Billing Time will be when your transaction run starts, but depending on the number of customers in queue some might be charged slightly after this time.&#x20;
{% 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://help.smartrr.com/docs/support/transactions/billing-schedule.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.