> 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/setup/production-documents.md). # Upload payroll documents Upload, preview, download and delete your production's payroll documents, including the certificate of insurance and escrow agreements. Use the **Documents** tab to upload and manage payroll documentation for your production, such as stunt paperwork, talent lists, shoot schedules, your certificate of insurance (COI) and escrow agreements. Open **Payroll > Setup** in the sidebar and select the **Documents** tab. Owners, Super Admins and Managers can use it. {% hint style="info" %} If RollCredits payroll is turned on for your production, **Payroll > Setup** has a **Documents** tab. It stays greyed out until the payroll settings are saved on the **Setup Payroll** tab. See [Set up payroll](/payroll/setup.md). {% endhint %} ## Upload a document 1. On the **Documents** tab, select **Upload Document**. The **Upload New Document** panel opens. 2. Choose a **Document Type**: **Stunts Documentation**, **Cast Member Files**, **Talent Lists**, **Shoot Schedules**, **Liability COI**, **Escrow Agreement**, **Minors Documents** or **Other Documents**. It starts on **Stunts Documentation**. 3. Enter a **Document Name**. 4. If you want, type a **Description**. 5. Under **File**, drag the file into the box, or select the box and choose the file. You can add one PDF, PNG, JPG or HEIC file of up to 50 MB. 6. Select **Upload Document**. **Upload Document** stays greyed out until every required field is filled in. To close the panel without uploading, select **Cancel**. ## Upload your certificate of insurance 1. Select **Upload Document**. 2. In **Document Type**, choose **Liability COI**. A **COI Requirements** note appears. 3. Check your certificate against the note. It lists the certificate holder's name and address, the minimum coverage and limits the payroll agreement requires, and the wording each policy needs, such as naming RollCredits as an additional insured. 4. Enter a **Document Name**, add the **File** and select **Upload Document**. RollCredits then verifies the certificate. Select the COI's card to see its status under **Verification**: * **Pending Verification** or **Under Review**: RollCredits hasn't finished checking it. * **Verified**: the certificate is accepted. The date and time it was verified show below the status. * **Rejected**: the reason, if RollCredits gave one, shows below the status. Upload a corrected certificate as a new **Liability COI**. Owners, Super Admins and Managers see a **Certificate of Insurance (COI) - Required** banner at the top of **Payroll > Setup**, above the tabs, in two cases: * With no COI uploaded, it says "A Certificate of Insurance must be uploaded for this production. Please upload your COI in the Documents tab". * When the most recently uploaded COI was rejected, it says "COI was rejected. Please upload a corrected COI". The banner goes away once your newest COI is waiting for verification or verified. ## Upload an escrow agreement An employee set up as an **Escrow Employee** on their employee panel needs an escrow agreement uploaded and assigned to them. See [Add and edit payroll employees](/payroll/setup/employees.md). Once they've finished their other onboarding steps, their onboarding status shows **Escrow Agreement Needs Document** until the agreement is attached. They can still fill out timecards, but their timecards can't be approved for payroll until then. See [Track employee onboarding](/payroll/setup/employee-onboarding.md). 1. Select **Upload Document**. 2. In **Document Type**, choose **Escrow Agreement**. 3. In **Escrow Employee**, choose the employee. The list shows only escrow employees who don't have an agreement attached yet. 4. Enter a **Document Name**, add a **Description** if you want, and add the **File**. 5. Select **Upload Document**. When it works, you see "Escrow agreement document uploaded and linked successfully", and the document shows the employee's name. {% hint style="warning" %} Each escrow employee gets one agreement, and an uploaded escrow agreement can't be deleted. Check the employee and the file before you upload. To fix a mistake, select the agreement's card, point at the greyed-out **Delete** button in its panel, and contact the email address it shows. {% endhint %} ## Find a document Above the documents are filters for **All** and for each document type, with the number of documents of that type in parentheses. Select a filter to show only that type. Each card shows the document type, name and description, the employee it's assigned to (for escrow agreements), the upload date and time, who uploaded it, and a **Download** button. ## Preview, download or delete a document 1. Select a document's card. When you point at a PDF or image, you can also select **Preview**. A panel opens with the document's name, description and type, **Assigned to** (when it's assigned to an employee), **Upload date**, **Uploaded by**, and the **Verification** status for a Liability COI. A preview of the file shows below. 2. To save the file, select **Download**. If the file can't be previewed, the panel shows **Preview Unavailable**. Select **Download to View** to download it and open it on your device. 3. To delete the document, select **Delete**, then select **Confirm** in the **Delete Document** window. To close the panel, select the card again. {% hint style="danger" %} Deleting a document can't be undone. {% 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/payroll/setup/production-documents.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.