> 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/payroll/crew-tax-documents.md).

# Download your tax documents

Download your W-2 or 1099, your paystubs for the year and your FLSA overtime report.

Use the Payroll Tax Documents page, at **Payroll > Payroll Tax Documents** in the sidebar, to download your own tax forms, paystubs and overtime report. Everyone on the production can open it, managers included, and each person sees only their own documents.

{% hint style="info" %}
**Payroll Tax Documents** appears only if RollCredits payroll is turned on for your production. Each paystub also includes a page with your timecard.
{% endhint %}

The page covers one tax year, set by RollCredits and shown in each tab's title. You can't choose another year.

## Download your W-2 or 1099

1. Select the **W2/1099** tab. **Income Tax Documents for \[year]** lists **W2**, **1099-MISC** and **1099-NEC**.

   <figure><img src="https://2309910149-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIZxLlI2W3d1mFnHRFWWa%2Fuploads%2Fgit-blob-f722acc8497251c7c73386c86f75b2b65ce50a53%2Fpayroll-tax-documents-w2-1099-tab.png?alt=media" alt="The W2/1099 tab of Payroll Tax Documents listing W2 with Download File, and 1099-MISC and 1099-NEC with No document."><figcaption></figcaption></figure>
2. Select **Download File** next to the form you need.

A row shows **No document** when RollCredits doesn't have that form for you for the year.

## Download your paystubs

1. Select the **Paystubs** tab. **Paystubs for \[year]** lists your weeks that end in that year, newest first, with **Week Starting**, **Week Ending** and **Payout Status**.
2. Select **Download** on a week to save its paystubs as a ZIP file. If the week was paid in more than one payroll run, the ZIP holds a paystub for each run.
3. Or select **Download All Paystubs** to save one ZIP file with a paystub for every week whose **Payout Status** is **Paid**.

**Download** stays greyed out until that week's paycheck is processed, and **Download All Paystubs** until at least one week is **Paid**. **Payout Status** is blank for a week with no hours submitted. For what each status means, see [Fill out your timesheet](/payroll/crew-timesheet.md).

On a phone, swipe the table sideways to see the other columns. **Download** stays at the right edge.

{% hint style="info" %}
The tab shows only the production you're on. To see another production's paystubs, switch to it first. See [Switch projects and companies](/getting-started/switch-projects.md).
{% endhint %}

## Download your FLSA overtime report

As part of the 2025 tax changes, some of your overtime pay can be deducted on your taxes, up to a limit. The FLSA overtime report sums up your eligible overtime hours and gives details about the deduction.

1. Select the **Other Documents** tab. **Additional Tax Documents for \[year]** shows the **FLSA Overtime Report** button and a message.
2. When the message says "Your FLSA report is ready to download.", select **FLSA Overtime Report**. The report saves as a PDF.

The button stays greyed out while the message says:

* "No FLSA overtime data available for this tax year.": there's no report for you.
* "Your FLSA report is being processed. Please check back later.": the report isn't ready yet.


---

# 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/payroll/crew-tax-documents.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.
