> 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/transactions/transactions/reports.md).
# Download transaction reports
Download a production's transactions as a wrap PDF, a zip of files, a spreadsheet, a general ledger or a cost report from the Transactions page.
Use the **Reports** button on the Transactions page, from **Transactions** in the sidebar, to download all of a production's transactions as one file. Owners, Super Admins and Managers see it on a computer or tablet, not on a phone.
To download only some transactions, use the table's **Export** button ([Find and edit transactions in the table](/transactions/transactions/find-and-edit.md)) or the **Export Documents** bulk action ([Act on many transactions at once](/transactions/transactions/bulk-actions.md)).
{% hint style="info" %}
Some choices depend on your company's or production's features: **P-Card Grid** if your production uses RollCredits cards, **Greenslate Spreadsheet** if your company exports to Greenslate, and **Include only approved transactions?** if the production has approvers.
{% endhint %}
## Download a report
1. On the Transactions page, select **Reports**.
2. In the **Download report** window, choose a **Report Type**.
3. Set the options shown for that type.
4. Select the download button, such as **Download PDF** or **Download Zip**.
| Report Type | What you get |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wrap PDF** | A cover page listing transactions by category with page numbers, then each transaction's documents and approval log. Estimate-only transactions are left out. |
| **Zip File** | Estimates, invoices, receipts, proofs of payment, extra documents and approval logs in folders, as separate files or one PDF per transaction, plus a spreadsheet. |
| **Transactions Report** | An Excel file with every transaction's details, one row per line item. |
| **General Ledger Report** | A ledger grouped by chart of accounts (or category), with subtotals per account and a report total. |
| **Cost Bible** | A cost report as of today, grouped by account, with actuals, commitments and budget. |
| **P-Card Grid** | An Excel grid of every P-Card charge on the production, by cardholder and code. |
| **PC Envelope** | One envelope's files, or summary sheets for all envelopes. |
| **Greenslate Spreadsheet** | Your transactions in a spreadsheet Greenslate can read. |
Until you [wrap the project](/transactions/transactions/wrap-project.md), the Wrap PDF's cover page carries a **SAMPLE PREVIEW** watermark.
## Choose what's included
* **Include RollCredits line items?** (Wrap PDF, Transactions Report, General Ledger Report): includes transactions whose vendor is RollCredits. It starts ticked when there are any, and is greyed out when there are none. The Wrap PDF lists them but adds only their payroll documents.
* **Include proofs of payment?** (Wrap PDF, Zip File): untick it to leave out receipts attached to invoices.
* **Include only approved transactions?**: includes only fully approved transactions. Kinds of transactions that have no approvers are all included.
* **Combine line items into single transaction row?** (Transactions Report): one row per transaction instead of one per line item.
* **Scope** (Transactions Report): **Production** for this production, or **Company** for every production in your company.
* **Group files by** (Zip File): a folder per **Vendor**, or per **User** who added the transaction. All of a transaction's files and its approval log go in one folder, chosen by its primary document. The primary document is the first of these the transaction has: its invoice, journal entry, receipt or estimate.
* **Save each transaction's documents as** (Zip File): **Separate Files** saves each document and approval log as its own file. **Combined PDF** saves one PDF per transaction, named after the document that chose its folder. That document comes first, then the transaction's other documents, such as its proof of payment, then its approval log. Extra documents aren't combined: each is saved as its own file beside the PDF, its name starting with the PDF's name. If a document that goes in the PDF can't be read, the whole export fails, so use **Separate Files** instead.
* **Format** (General Ledger Report, Cost Bible): **PDF** or **Excel**.
## Filter by date
Most report types show **Payment date** and **Created date**, each with **From** and **Through**. Both days you enter are included.
* **Payment date** is the date in the **Issued At** column. If you set it, transactions without that date are left out.
* **Created date** is the day the transaction was added to RollCredits.
Set **From** before **Through**: the dates are checked when you change **Through**. If **Through** is before **From**, you see **Through date must be after From date** and the download button is greyed out until you change **Through** again.
The Wrap PDF, Zip File and General Ledger Report use both dates. The Transactions Report and Greenslate Spreadsheet use only **Created date**. The P-Card Grid always covers every card charge, whatever the dates and approval option say.
## Download a Cost Bible
1. In **Report Type**, choose **Cost Bible**, then a **Format**.
2. In **Categories to omit**, choose any categories to leave out.
3. Tick **Include transaction-level line item details?** to list each transaction line item.
4. Select **Download PDF** or **Download Excel**.
The Cost Bible uses the production's first budget. Without one, you see **This production has no budget, so a Cost Bible can't be generated.** and can't download. For other cost reports, see [Run cost reports and close periods](/budget-and-cost-report/cost-reports.md).
## Download an envelope
1. In **Report Type**, choose **PC Envelope**.
2. Choose the **Envelope**.
3. Select **Download Envelope**.
The zip holds a spreadsheet of the envelope's transactions, a spreadsheet for Hot Budget and the documents. It also holds a PDF of the envelope.
For every envelope at once, tick **Export summary sheets for all envelopes?** instead. You get a zip with one PDF per envelope, each with a cover page and its documents. You can also export envelopes from [Manage envelopes](/project/envelopes.md).
## While your file is being made
The window closes, you see **Your file download will begin shortly. Please wait...**, and the file downloads when it's ready.
A Zip File or a single PC Envelope also shows **Generating export: Export...** until it's ready. Keep that browser tab open, since the file downloads there. Up to three run at once, and more start as each one finishes.
If it fails, you see **There was an error generating your file. Please try again later** or **Error starting file export. Please try again later**.
{% hint style="warning" %}
A Zip File also shows **Error starting file export. Please try again later** when no transactions match your options and dates.
{% 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 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/transactions/transactions/reports.md?ask=&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.
