> 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/review-payroll-runs/weekly-timesheets.md). # Review timecards by week and upload Exhibit G Work through one payroll week at a time on the Weekly Timesheets tab, and upload, download and import Exhibit G for SAG-AFTRA productions. The **Weekly Timesheets** tab shows one week of timecards at a time, with a summary of what's left to do. Owners, Super Admins and Managers find it on **Payroll > Review Payroll Runs**, and Department Heads on **Payroll > Review Timecards**, where they see only people in their department, plus themselves. {% hint style="info" %} Exhibit G appears only when SAG-AFTRA is ticked under **Unions enabled** in [payroll setup](/payroll/setup.md), and only Owners, Super Admins and Managers see it. **Find and Match Exhibit G** appears only if your company has Exhibit G scanning turned on. {% endhint %} ## Pick a week 1. Select the **Weekly Timesheets** tab. 2. Choose a week from the list at the top, or select the arrows beside it to move a week. The tab opens on the current week, or on the last week in the list if the list ends sooner. Weeks end on the **Week Ending Day** in payroll setup. ## See what's left for the week Select a card under the week picker to open or close it. The timecards card shows **N Timesheets Need Attention**, or **All timesheets Finished!** when nothing is left. Open it to see each person, by name and title, under: * **Pending Hours**: the week is on the **Hours Not Submitted** or **In Progress** tab. * **Pending Approval**: the timecard is on the **Submitted for Review** tab. * **Pending Payout**: the timecard is on the **Approved** tab, waiting for a payroll run. **PENDING PAYMASTER CALCULATION** next to a name means RollCredits paymasters are still working out pay for some of that timecard's days. On SAG-AFTRA productions, an Exhibit G card shows **Missing N Exhibit G Documents**, or **All Exhibit G Documents Uploaded!** once every day of the week has one. Open it to see the missing days, such as **Monday - 2026-11-02**. ## Work with the week's timecards Below the cards are the status tabs and table from **All Timesheets**, limited to the selected week, so **Send reminder to all** and **Preview Payroll Run (N approved)** include only its timecards. See [Review timecards and run payroll](/payroll/review-payroll-runs.md). ## Upload or download Exhibit G 1. Pick the week and select **Add, Edit, or View Exhibit G**. The **Exhibit G** panel opens in place of the timecards, with a row for each day. 2. On a day with no file, select **Upload Exhibit G** and choose the file. To get a file back, select **Download**. 3. Select the **X** at the top of the panel to go back to the timecards. Each day holds one file. To replace one, delete it first. ## Delete an Exhibit G 1. In the **Exhibit G** panel, select **Delete** on the day's row. 2. In **Delete Exhibit G**, select **Delete**. {% hint style="warning" %} **Delete** disappears once a timecard covering that day is in a payroll run. {% endhint %} ## Find and match Exhibit G files Find and Match reads the shooting date, performers and times from Exhibit G files and fills the times into timecards. 1. In the **Exhibit G** panel, select **Find and Match Exhibit G**. 2. Drag one or more PDF, PNG, JPG or HEIC files into the box, or select it to browse. 3. After the scan, each file shows a status: * **Ready to import**: its date is a day this week with no Exhibit G yet. * **Date outside selected week** or **No shooting date found**: choose the day the file covers in **Pick the day**. * **Day already has Exhibit G**, **Duplicate date in this batch** or **Failed to scan**: it won't be imported. 4. Select **Continue to performer review**. ## Review and import performer times **Review and import Exhibit G timesheets** shows one day at a time: the scanned file, then a row for each performer on it. 1. Check each performer's status: * **Matched**: will be imported. * **Needs review**: RollCredits picked the closest profile. Select **Confirm match** if it's the same person, or choose someone else in **Pick a Roll Credits Profile...**. Left as is, it's imported with that profile. * **No match**: won't be imported until you choose the person in **Pick a Roll Credits Profile...**. * **Skipped**: won't be imported. Select **Restore** to bring them back. 2. Fix any wrong times under **Work**, **Meals**, **Travel** and **Other**. Point at an edited cell's dot to see the scanned value. **Reset times** restores the scan. 3. Select the next day's button, such as **Next: Tuesday**, or **Previous day**. **Back to file review** returns to the file list. 4. On the last day, select the import button, such as **Import 3 days ยท 12 performer entries**. 5. If any performer already has times on their timecard for one of those days, **Replace existing data on N days?** lists them. Select **Yes, replace N days**, or **Cancel** to go back. * Select **Skip** on any row to leave that performer out. A profile you pick, **Confirm match** and **Skip** apply on every day in the batch with the same cast name. * A **Conflict** tag means two performers on one day are matched to the same person. Change or skip one. * When the button shows **Import to timesheets** and is greyed out, point at it to see why. RollCredits writes the times into each person's timecard for the week, creating it if needed, and attaches each file as that day's Exhibit G. {% hint style="info" %} Closing the review before importing clears the files, so you start again from **Find and Match Exhibit G**. {% 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/review-payroll-runs/weekly-timesheets.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.