> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/resources/reports-and-exports.md).

# Reports & Exports

Boza makes it easy to get your data out for audits, finance reviews, or sharing with people who don't use the platform. Most list pages offer a one-click CSV export, and the Payments view also supports importing data in.

***

## Exporting Data

List exports download the rows that match the current search and filters, so you can prepare a focused file instead of exporting the entire workspace.

| What you can export       | Where                                                                                        | How                                                                            |
| ------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| **Applications**          | [Applications](/docs/inventory/applications.md)                                              | Click the export button (upload icon, tooltip **Export data**) above the table |
| **Users**                 | [Users](/docs/user-management/users.md)                                                      | Click the export button (upload icon, tooltip **Export data**) above the table |
| **Payments**              | [Analysis → Payments](/docs/platform/analysis/payments.md)                                   | Click **Export** to download `payments.csv`                                    |
| **Access Review results** | Open a non-cancelled campaign from [Access Reviews](/docs/user-management/access-reviews.md) | Click **Export** in the campaign view                                          |

{% hint style="info" %}
Application and user exports honor the filters visible on those pages. Campaign exports are campaign-specific and include the review status recorded for each application and reviewer.
{% endhint %}

***

## Access Review Evidence

An Access Review export includes the application, reviewer, reviewer role, result, confirmation date, and comment for each review record.

* **Pending** items can appear while a campaign is still running.
* At the deadline, remaining pending items become **Incomplete**.
* **Not covered** identifies applications for which no reviewer or eligible fallback was available.
* Cancelled campaigns cannot be exported.

Resolve **Incomplete** and **Not covered** rows before treating the file as complete audit evidence. See [Configure and Manage Access Review Campaigns](/docs/user-management/access-reviews/configure-campaigns.md).

***

## Import Data

| What you can import | Where                                                                           | Notes                                                                                      |
| ------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Payments**        | [Analysis → Payments](/docs/platform/analysis/payments.md)                      | Use **Import payments → Download CSV template**, fill it in, then **Upload payments CSV**  |
| **Invoices**        | [Upload Invoices](/docs/inventory/subscriptions-and-vendors/upload-invoices.md) | Upload supported PDF or image invoices for extraction and review; this is not a CSV import |

***

## Before Sharing an Export

* Confirm the selected filters, year, and time window.
* Check that synchronization and invoice processing are complete.
* Treat names, email addresses, cost data, and review comments as confidential.
* Store audit exports according to your organization's retention and access policies.

See [Metrics & Data Freshness](/docs/resources/metrics-and-data-freshness.md) when two reports do not reconcile.

## Need Help?

If you need a report that isn't available as a built-in export, contact us at **<support@getboza.io>** — we may be able to help or add it to the roadmap.


---

# 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://boza.gitbook.io/docs/resources/reports-and-exports.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.