> For the complete documentation index, see [llms.txt](https://olddocs.exivity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olddocs.exivity.io/getting-started/how-to-guides/how-to-automatically-trigger-a-monthly-billing-report.md).

# How to automatically trigger a monthly billing report

Exivity enables customers to generate summaries of the cloud spend on a schedule. You may choose to publish a report of your resource usage and costs quarterly, monthly or daily.\
\
This article guides you through the steps of publishing a monthly report:\
\
In order to trigger the publishing automatically, you must use the [Workflow engine](/data-pipelines/workflows.md).<br>

1\. Navigate to the **Data Pipelines** > **Workflow** menu and select *Workflows*.

2\. Click **Create Workflow**.&#x20;

3\. Provide a meaningful name and description.

4\. Click **Add Schedule**.&#x20;

&#x20;  4.1.   The **Type** selection should be monthly.&#x20;

&#x20;  4.2.  Furthermore, the interval field **Run Every** should be set to *1 Month*.

&#x20;  4.3.  Select the start date (**Effective from**), **Start time** and **Time zone**.

![Scheduling a monthly report](/files/Jan49ebBIenAqseYvLeo)

5\. Click the **Add Step** button and set the type to *Publish report*.

6\. Choose your report from the drop-down list.

7\. The **Timeout** setting allows you to choose the interval of waiting, before trying to execute this step again, in the event of a failure.

![Publishing the selected report monthly](/files/s23w7QGqWRkL6OHuMqPs)

8\. Finally, click **Create**.

{% hint style="info" %}
In combination with the [Notification engine](/administration/notifications.md), you can receive your monthly report on a notification channel (for example: *email*).
{% 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 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://olddocs.exivity.io/getting-started/how-to-guides/how-to-automatically-trigger-a-monthly-billing-report.md?ask=<question>&goal=<endgoal>
```

`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.
