> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/cards/cards/export-card-statements.md).

# Export card statements

Download a Hot Budget PO log or a P-Card statement for a date range from the Total Spend card on the Cards page.

Use **Export** on the **Total Spend For** card, at the top of **Cards** in the sidebar, to download the production's card spend as a PO log for Hot Budget or as a P-Card statement. Owners, Super Admins and Managers can use it.

{% hint style="info" %}
**Cards** appears only if your production uses RollCredits cards. The **Total Spend For** card isn't shown when the card provider's own app opens inside Cards. See [Manage cards](/cards/cards.md).
{% endhint %}

## Download a PO log for Hot Budget

1. On the **Total Spend For** card, select **Export**.
2. In the **Choose export format** window, leave **Export Type** set to **PO Log (Hot Budget)**.
3. Select **Download PO Log (Hot Budget)**.

The PO log is an Excel sheet of every card transaction on the production, ready to use in Hot Budget. It has no date range.

## Download a P-Card statement

1. On the **Total Spend For** card, select **Export**.
2. Set **Export Type** to **P-Card Statement**.
3. Choose a **Scope**. **Production** covers this production. **Company** covers every production in your company and comes as Excel only.
4. Enter a **Start Date** and an **End Date**. Both days are included.
5. For **Production** scope, keep **Include Excel?**, **Include Pdf?** or both ticked.
6. Select **Download P-Card Statement**.

The statement lists settled and pending card transactions in the period, plus payments toward your balance. The Excel file shows each row's production, date, amount, user, merchant, category, card's last 4 digits, status and transaction ID. The PDF shows the production at the top, the statement total and every row with its category and a running balance. If your company is on the Stripe card program, the PDF also lists ACH/wire details for paying your balance.

**Category** shows how the charge is coded in RollCredits, as the category code and description, such as "2100 - Wardrobe Purchases". If your production uses a chart of accounts, it shows the account on the side expenses post to: the debit account, or the credit account if **Expense** is set to **Credits are +** under [Configure Account Types](/trial-balance/trial-balance.md#configure-account-types). A charge split across categories lists each one, separated by a semicolon. **Category** is blank for payments and for charges that aren't coded yet.

**Production** scope downloads your files in one .zip file. **Company** scope downloads one Excel file covering every production.

Date rules:

* Neither date can be after today.
* For **Production** scope, neither can be before the day the production was set up in RollCredits.
* The **End Date** can't be before the **Start Date**.

{% hint style="info" %}
**Download P-Card Statement** stays greyed out until the dates follow these rules and, for **Production** scope, a file is ticked. The window doesn't say which rule isn't met.
{% endhint %}

## While the file is made

When you select a download button, the window closes and a message stays on screen until the file is ready: "Your card statement is being generated. Please wait..." (or "Your company card statement is being generated. Please wait...") for a statement, or "Your file download will begin shortly. Please wait..." for the PO log.

The file then downloads in your browser, and a statement's message changes to "Downloaded pcard statement!" or "Downloaded company card statement!". If the export fails, you see an error message instead.


---

# 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://knowledge.rollcredits.io/cards/cards/export-card-statements.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.