--- title: "Payroll Audit and Troubleshooting" slug: "workforce-payroll-audit-troubleshooting" description: "Audit and troubleshoot common payroll issues in R365 Workforce Payroll — diagnose payment errors and resolve pay run problems." updated: 2026-07-27T15:51:42Z published: 2026-07-27T15:51:42Z canonical: "docs.restaurant365.com/workforce-payroll-audit-troubleshooting" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.restaurant365.com/llms.txt > Use this file to discover all available pages before exploring further. # Payroll Audit and Troubleshooting R365 Payroll audit and troubleshooting guides payroll administrators through verifying earnings, deduction, and tax calculations before approving a payroll batch, and tracing the cause of any discrepancies. Run a full audit prior to each payroll approval or any time calculations do not match expectations. --- ## Prerequisites Confirm the following before running a payroll audit: - The **Payroll** application is visible in the R365 app switcher. The Payroll app only appears when R365 Payroll is enabled for your tenant. If it is not visible, contact your R365 account manager. - POS integration is configured and the daily sales summary (DSS) is polling data into R365. The DSS is required for the POS Data Audit. - Employee records are fully onboarded to R365 Payroll. Employees who have not completed onboarding will not appear in payroll batches. - Access to the following reports: [Payroll Preview Report](/doc/docs/payroll-preview-report), [Employee Census Report](/doc/docs/workforce-reports-employee-census), [Benefits and Deductions Report](/doc/docs/workforce-reports-benefits-and-deductions), and [Payroll by Pay Period Report](/doc/docs/workforce-reports-payroll-by-pay-period-payroll-by-pay-date-reports) > [!NOTE] > **Required** permissions > > Running payroll audit reports requires the **Payroll > R365 Payroll > Reports > View Reports** permission. In R365 default roles, this permission is included in **Payroll Admin**, **Payroll Clerk**, and **Full Access**. > > Approving payroll batches requires the ability to approve Payments in the Payroll app. This is included in **Payroll Admin** and **Full Access**. Payroll Clerk can calculate and verify payroll but cannot approve payments. --- ## Payroll Audit Overview A full payroll audit confirms that all areas of R365 are configured correctly for payroll and helps trace the cause of discrepancies. ### About rounding While auditing and reviewing payroll reports, be aware that different systems round partial minutes and percentages differently. This can result in small discrepancies in earnings, deduction, and tax amounts. Discrepancies of less than 10 cents are typically caused by rounding differences and do not require correction. ### Recommended audit sequence > [!NOTE] > **Perform audits in order** > > For a thorough payroll audit, complete all four audits in sequence: (1) POS Data Audit, (2) Employee Record Audit, (3) Benefits and Deductions Review, (4) gross-to-net Calculation Audit. Starting with POS data ensures the source data is accurate before reviewing employee records and calculations. ### Audit and review descriptions | Audit/Review | Description | Data Reviewed | Discrepancy Troubleshooting | | --- | --- | --- | --- | | POS Data Audit | The POS Data Audit compares POS punch and pay rate information to the punch and pay rate information in R365. This audit is done first, as punch and pay rate information from the POS is one of the main sources of earnings information used for payroll. | - Employee Names - Punch Dates - Punch Times - Jobs - Pay Rates - Regular Hours - OT Hours - Total Hours - Regular Earnings - Overtime Earnings - Tips | - Inaccurate calculations by the POS - Incorrect POS settings - Incorrect R365 settings for a Location - Incorrect R365 Overtime Rule settings - Missing or duplicated Employee Records - Edits to Punches or Tips made in R365 after POS data is polled | | R365 Employee Record Audit | The R365 Employee Record Audit compares the list of employees expected for payroll to the list of employees onboarded for payroll in R365. | - Employee Names - Payroll Status - Primary Location - Jobs - Employment Status (Active, Leave, Terminated) | - Missing or duplicate Employee Records - Incorrect work Locations - Incorrect Jobs - Employees who have not been fully onboarded to payroll - Employees with the incorrect Employment Status | | Benefits and Deductions Review | The Benefits and Deductions Review reviews the list of configured deductions per employee. | - Employee Names - Deduction Names - Deduction Amounts - Contribution Amounts | - Incorrect Deduction configurations on Employee Records | | Gross to Net Calculation Audit | The Gross to Net Calculation Audit reviews the calculated earnings, deductions, and taxes within Workforce. During onboarding, this audit is often compared with the payroll register from an existing payroll system to confirm calculations in R365 before go-live. Perform this review for each payroll batch prior to approval. | - Employee Name - Primary Location - Regular Hours - Overtime Hours - Double Overtime Hours - Earning Amounts per Earning - Gross Pay - Deductions - Total Tax - Net Pay | - Missing or duplicate Employees - Incorrect Earnings - Incorrect Deductions - Incorrect Taxes - Incorrect ER Contributions | ### Areas and configurations for troubleshooting discrepancies The following R365 settings and configurations affect earnings, deduction, and tax calculations after POS data has been polled. Issues found in POS data must be corrected in the POS before the DSS polls again. | Discrepancy | Area/Setting | Impacts to Payroll | | --- | --- | --- | | Overtime Hours or Earnings | [Fiscal Calendar: Operational Calendar](/doc/docs/fiscal-calendar) | The operational calendar for a location determines the first day of the week. The first day of the week is used for overtime calculations. | | Missing Employee Tax Location | [System Preferences: Employee Master](/doc/docs/system-preferences-miscellaneous) | The Employee Master setting should be set to 'R365'. This ensures that employee information such as address, name, hire date, and so on that was updated in R365 is not overwritten nightly by POS data. | | Tax Location | [Payroll Location: Address](/doc/docs/workforce-locations-overview) | The address for each payroll location is used to determine required taxes. | | Overtime Hours or Earnings | [Location Record: Overtime Tracking](/doc/docs/legal-entities-location-record) | When overtime tracking is set to 'R365', overtime is calculated in R365 using R365 overtime rules. Overtime calculations provided by the POS are not used. | | Punch Date or Time Regular Hours Overtime Hours | [Location Record: Punch Edits](/doc/docs/legal-entities-location-record) | When punch edits are enabled in R365, changes to punches made in the POS after the DSS is polled will not be imported. Punch edits must be maintained in R365. | | Penalty Earnings Overtime Hours Overtime Earnings | [Labor Admin: Labor Rules](/doc/docs/admin-page-overview-security) - OT Rules - Break Penalties - Shift Differential - Spread of Hours - Tip Makeup | When labor rules are configured, additional earnings will be calculated and automatically added. These earnings will not appear in POS reports. | | Overtime Hours Overtime Locations Punch Date | [Operations Admin: Start of Day Time](/doc/docs/start-of-day-overview) | Overtime calculations use business days to determine the hours worked by an employee in a business day. By default, business days in R365 start at 12:00 am. Start of Day settings determine the start time for a location's business day. Align a location's Start of Day Time to the POS End of Day Time. | | Punch Date or Time Regular Hours Overtime Hours | [DSS Punch Edits](/doc/docs/r365-payroll-editing-dss-labor-punches) | When enabled, punches must be edited directly in R365. Edits made to punches in R365 are not reflected in reports from the POS. | | Regular Earnings Overtime Earnings Penalty Earnings | [DSS Pay Rate Edits](/doc/docs/punch-edits) | When enabled, pay rates can be edited per punch in R365. Changes to pay rates are not reflected in reports from the POS. | | Tips | [DSS Tip Import](/doc/docs/tip-management) | Tips can be redistributed via import in R365. Tips re-distributed in R365 are not reflected in reports from the POS. | | Tips | [Tip Automation](/doc/docs/tip-automation) | Tips can be redistributed via Tip Automation. Tips re-distributed in R365 are not reflected in reports from the POS. | | Earnings | [Adding and Editing Earnings](/doc/docs/workforce-r365-payroll-adding-and-editing-earnings-and-deductions) | Earnings can be added or edited directly in Workforce. Edits made to earnings will not appear on POS or DSS reports. | | Earnings Deductions Taxes | [One Time Payments](/doc/docs/workforce-one-time-payments) | One-time payments can be used to add earnings or deductions in Workforce. One-time payments will not appear on POS or DSS reports. | | PTO Earnings | [Labor Admin: PTO Accruals](/doc/docs/pto-accruals-overview) | PTO Accruals allows for managing employee PTO balances in Workforce. Balances can be viewed on the [Time Off tab](/doc/docs/workforce-employee-record-time-off-tab) of Employee records. Approved time off requests will add PTO earnings to the DSS. > If PTO Accruals is not enabled, the [legacy PTO Policy](/doc/docs/workforce-policies) is used to configure paid time off within Workforce and automatically add PTO earnings to pay cycle payroll batches. These earnings will not appear on POS or DSS reports. | | Taxes | Workforce: Unemployment Rate | A payroll location's unemployment rate is used when calculating taxes. | | Payroll Batch Date Range | [Workforce: Pay Cycle Setting](/doc/docs/workforce-settings-account-page) | A payroll location's pay cycle is used to determine the date range of each pay cycle payroll batch. | | Tax Location | [Employee Record: Employee Address](/doc/docs/employee-records-basic-info-tab) | The home address for each employee is used to determine the required taxes for that employee. | | Tax Location | [Employee Record: Primary Location](/doc/docs/employee-record-employment-tab) | The primary location for an employee is used to determine the required taxes for an employee's work location. | | Salary Earnings | [Employee Record: Salary Jobs & Pay Rates](/doc/docs/workforce-employee-record-employment-tab) | The jobs and pay rates of salaried employees are used to automatically populate salary earnings per pay cycle payroll batch. Salary earnings will not appear on POS or DSS reports. | | Deductions | [Employee Record: Deductions](/doc/docs/workforce-employee-records-deductions-and-benefits-details-sidesheet) | The employee-specific benefits and deductions configurations are used to calculate deductions per payroll batch. | | Missing Employee | [Employee Record: Payroll Status](/doc/docs/workforce-onboarding-an-employee-to-r365-payroll) | Only employees who have been fully onboarded to Payroll will be included in payroll batches. | | Missing Employee | [Employee Record: Employment Status](/doc/docs/workforce-employee-record-employment-tab) | Only active employees will be included in payroll batches. Employees with the status of 'Leave' or 'Terminated' will not be included. | | Missing Employee Duplicate Employee | Employee Record: Integrations | POS Employee records are linked to Employee records to connect the Employee record to employee-specific POS data. Incorrectly matched POS Records and incorrectly merged Employee records can result in missing employees. Employees with multiple POS Records will appear as duplicates and will need to be merged. | > [!NOTE] > **Using this table during troubleshooting** > > When a discrepancy is identified during any step-by-step audit below, use the Discrepancy column in the table above to locate the relevant area or setting in R365. Review that setting and correct it if needed, then re-run the affected report to confirm the discrepancy is resolved. --- ## POS Data Audit: Step-by-step The POS Data Audit compares POS punch and pay rate information to the corresponding data in R365. Complete this audit first, as POS data is the primary source for earnings calculations. ****POS Data Audit guide**** 1. **Select a data range to compare.** R365 recommends comparing all dates within a single full pay period. 1. **From the POS:** Run a punch report for the selected date range that shows all punches, pay rates, hours, and tips. 1. **From My Reports:** Run the [Workforce Preview Report](https://docs.restaurant365.com/doc/docs/workforce-payroll-preview-report) with the following report settings: - **Start Date and End Date** - Set to the selected date range for the pay period. - **Pay Frequency** - All Employees. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-07ID94V0.png?sv=2026-02-06&spr=https&st=2026-10-28T17%3A45%3A33Z&se=2026-10-28T18%3A45%3A33Z&sr=c&sp=r&sig=ecFFz%2BoS7I5y2usxYLWYH8WPPz2IgUWDRwVJe03Ys5A%3D) 1. **Compare the following key fields for each employee and punch:** Verify the following fields match between the POS report and the Workforce Preview Report - Employee Name - Punch Dates - Punch Times - Jobs - Pay Rates - Regular Hours - OT Hours - Total Hours - Regular Earnings - Overtime Earnings - Tips 1. **Troubleshoot discrepancies.** For each discrepancy found, identify the cause using the **Areas and configurations for troubleshooting discrepancies** table above. Common causes include: - Incorrect POS settings or inaccurate POS calculations - Incorrect R365 settings for a location (overtime tracking, punch edits) - Incorrect R365 overtime rule settings - Missing or duplicated employee records - Punch or tip edits made in R365 after POS data was polled Issues caused by POS data must be corrected in the POS before the next DSS poll. Issues caused by R365 settings can be corrected directly in R365. --- ## Employee Record Audit: Step-by-step The Employee Record Audit compares the list of employees expected for payroll against the employees onboarded to payroll in R365. Run this audit to confirm all employees are correctly set up before payroll is processed. ****Employee Record Audit guide**** 1. **Compile a full list of employees expected from Payroll.** Use the POS punch report from the POS Data Audit as the basis for this list. Add any salaried employees or employees who do not punch in through the POS from a separate source (such as an HR record or prior payroll register). 1. **From Reports:** Download the Worker census report with the following settings: - **Employee Status** - Active. - **As of Date** - First date of the pay period being audited. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-FGJWSTMW.png?sv=2026-02-06&spr=https&st=2026-10-28T17%3A45%3A33Z&se=2026-10-28T18%3A45%3A33Z&sr=c&sp=r&sig=ecFFz%2BoS7I5y2usxYLWYH8WPPz2IgUWDRwVJe03Ys5A%3D) 1. **Compare reports and confirm all expected employees are listed on the Employee Census:** Confirm all expected employees appear on the Employee Census Report. Verify the following fields for each employee: - Employee Names - Payroll Status - Primary Location - Jobs - Employment Status (Active, Leave, Terminated) 1. **Troubleshoot discrepancies.** For each discrepancy found, identify the cause and take the appropriate corrective action: - **Employee missing from report** — the employee may not be fully onboarded to payroll, may have an incorrect employment status, or may be assigned to the wrong location. Review the [Employee Record: Payroll Status](/doc/docs/workforce-onboarding-an-employee-to-r365-payroll) and complete onboarding if needed. - **Employee on report but not expected** — confirm the employee's employment status and primary location are correct. Terminated employees should not appear in active payroll batches. - **Duplicate employees** — duplicate records may be caused by multiple POS integrations. Review the Employee Record: Integrations setting to merge or correct the records. - **Incorrect jobs or locations** — update the [employee's employment record](/doc/docs/employee-record-employment-tab) with the correct job and primary location. --- ## Benefits and Deductions Review: Step-by-step The Benefits and Deductions Review confirms that all employee deductions and employer contributions are configured correctly for the pay period. ****Benefits and Deductions Review guide**** 1. From R365 Payroll, download the [Benefits and Deductions Report](/doc/docs/workforce-reports-benefits-and-deductions) with the following settings: - **Start Date** — first day of the pay period being audited - **End Date** — last day of the pay period being audited ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-Y0T6VTJP.png?sv=2026-02-06&spr=https&st=2026-10-28T17%3A45%3A33Z&se=2026-10-28T18%3A45%3A33Z&sr=c&sp=r&sig=ecFFz%2BoS7I5y2usxYLWYH8WPPz2IgUWDRwVJe03Ys5A%3D) 2. **Review key fields for each employee.** Confirm the following fields are accurate for each employee: - Employee name - Deduction type - Employee deduction amounts - Employer contribution amounts 3. **Troubleshoot discrepancies.** Incorrect deduction amounts are typically caused by incorrect deduction configurations on the employee record. Review the employee's [deduction settings](/doc/docs/workforce-employee-records-deductions-and-benefits-details-sidesheet) and correct the configuration as needed. Re-run the report to confirm the correction. --- ## Gross-to-Net Calculation Audit: Step-by-step The Gross-to-Net Calculation Audit reviews calculated earnings, deductions, and taxes in R365 Payroll. During onboarding, compare this audit against the payroll register from an existing payroll system to confirm R365 calculations before go-live. Perform this review for each payroll batch prior to approval. > [!WARNING] > **Approving a payroll batch is irreversible** > > Once a payroll batch is approved and submitted for processing, it cannot be recalled or reversed. Complete the Gross-to-Net Calculation Audit and resolve all discrepancies before approving a batch. ****Gross-to-Net Calculation Audit guide**** 1. **Select a** **pay period** **to audit.** Identify the [pay period](/doc/docs/workforce-settings-account-page) you want to audit. For go-live parallel audits, use the same pay period in both R365 and the existing payroll system. 2. **Run the Payroll by Pay Period Report.** From R365 Payroll, run the [Payroll by Pay Period Report](/doc/docs/workforce-reports-payroll-by-pay-period-payroll-by-pay-date-reports) for the selected pay period. 3. **Run a parallel register report (go-live audits only).** If completing a parallel audit prior to go-live, run a payroll register report for the same pay period in the existing payroll system. This provides the comparison baseline for reviewing R365 calculations. 4. **Review key fields for each employee.** Confirm the following fields match expected values for each employee: - Employee name - Primary location - Regular hours - Overtime hours - Double overtime hours - Earnings amounts per earning type - Gross pay - Deductions - Total tax - Net pay > [!NOTE] > The [Payroll Register Report]([PLACEHOLDER: Payroll Register Report article URL]) provides a per-employee register of earnings, deductions, taxes, and check or direct deposit amounts for a selected pay date range. Run it alongside the Payroll by Pay Period Report for a detailed employee-level view during the gross-to-net audit. 1. **Troubleshoot any discrepancies before approving the payroll batch.** For each discrepancy, use the **Areas and configurations for troubleshooting discrepancies** table in the overview section above to identify the setting causing the difference. Common causes include: Resolve all discrepancies before approving the payroll batch. Approving an incorrect payroll batch cannot be undone. - **Missing or duplicate employees** — review payroll status and integration settings on the employee record - **Incorrect earnings** — check that jobs, pay rates, and labor rules are configured correctly; review [adding and editing earnings](/doc/docs/workforce-r365-payroll-adding-and-editing-earnings-and-deductions) if manual adjustments are needed - **Incorrect deductions** — verify deduction configurations on the employee record - **Incorrect taxes** — confirm the employee address and primary location are correct, as both are used to determine required taxes - **Incorrect employer contributions** — review deduction and benefit configurations on the employee record --- ### FAQ #### I approved a payroll batch that has errors. What do I do? Approving a payroll batch is irreversible — once submitted, it cannot be recalled or corrected within R365. Contact [R365 support](/doc/docs/r365-support). Corrections at this stage are processed as an [off-cycle payroll run](/doc/docs/off-cycle-pay-runs-overview) — a separate payment run outside the regular pay schedule that addresses the specific error. Do not attempt to modify the approved batch in R365. #### How do I know if a small discrepancy is a rounding issue or a real error? Discrepancies of less than 10 cents are typically caused by rounding differences between R365 and your POS system — these do not require correction. If the same discrepancy appears consistently across multiple employees or in multiple pay periods, it is likely a configuration issue rather than normal rounding. In that case, contact [R365 support](/doc/docs/r365-support) to investigate. Discrepancies greater than 10 cents should always be traced using the [areas and configurations for troubleshooting discrepancies](/doc/docs/workforce-payroll-audit-troubleshooting#areas-and-configurations-for-troubleshooting-discrepancies) table in this article. #### What is the difference between Payroll Status and Employment Status? **Employment Status** indicates whether an employee is currently active, on leave, or terminated. Only employees with an Active status are included in payroll batches. **Payroll Status** is a separate field that tracks whether an employee has completed [R365 Payroll onboarding](/doc/docs/workforce-onboarding-an-employee-to-r365-payroll) — employees who haven't fully onboarded will not appear in payroll batches even if their Employment Status is Active. When an employee is missing from a batch, check both fields on their employee record. Restaurant365 POS (Point of Sale) A system used by businesses to process sales transactions and manage customer payments. Connected to R365 through a [POS integration](/doc/docs/pos-integration-overview). Daily sales summary (DSS) Record generated by daily data sent from the POS that may include sales, labor, menu items, and payment details. Process of importing data from the POS into R365. Daily sales summary (DSS) Record generated by daily data sent from the POS that may include sales, labor, menu items, and payment details. Access rights granted to users or user roles that dictate what actions they can perform within the system. The calculation that determines an employee's take-home pay by starting with gross earnings and subtracting applicable taxes and deductions. In R365, the Gross-to-Net Calculation Audit verifies this calculation is correct before each batch is approved. Adjustments made to employee clock-in and clock-out records in R365 or the POS. Punch edits correct missed, early, or duplicate punches before the DSS is approved and earnings are imported into the pay run.