> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/billing/bill-runs.md).
# Bill runs
The bill run is responsible for generating invoices on an account's billing day. It runs every day at 8:15 am in the entity's timezone and performs the following functions.
* Processes all accounts who's billing day is the current day
* Merges any pending invoices for accounts that use consolidated billing
* Aggregates usage records for subscriptions with usage-based charges
* Calculates sales tax or VAT
* Generates an invoice for each account
Once the job has completed, a summary record is produced that shows how many invoices were generated, how much money was invoiced etc.
If you have multiple entities, each entity will be processed in a separate bill run.
Bill run table
By clicking on a row in the table, you will get a new table with all the invoices that were generated.
Bill run details
---
# 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://docs.bunny.com/guide/tour/billing/bill-runs.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.