# Reporting

## General reporting framework

General reporting with Ylem requires the following 4 steps:

* Retrieve data or receive it automatically from streaming or queueing software
* Convert to CSV or XML format
* Send a file via Email or any other convenient way
* Schedule this pipeline to run with the necessary frequency

<figure><img src="/files/NhlS5nyGDYDQFzZRe6wn" alt=""><figcaption><p>Typical reporting pipeline</p></figcaption></figure>

<figure><img src="/files/TSIqMjTfRpeP9YBFluxU" alt=""><figcaption><p>Typical reporing schedule. Every Monday at 7am</p></figcaption></figure>

Other more specific reporting examples can be found on the use case pages:

* [General financial reporting](/use-cases/industry-specific-use-cases/finance-and-payments.md#generate-commercial-reports-and-send-them-to-bi-software-or-directly-to-stakeholders)
* [Commercial reporting](/use-cases/industry-specific-use-cases/e-commerce.md#generate-commercial-report-and-send-it-to-bi-software-or-directly-to-stakeholders)
* [Customer engagement report](/use-cases/industry-specific-use-cases/customer-success.md#customer-engagement-summary-report)
* [KPI reports](/use-cases/functional-use-cases/kpi-monitoring.md#monitor-average-value-per-customer)


---

# Agent Instructions: 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:

```
GET https://docs.ylem.co/use-cases/functional-use-cases/reporting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.