When Radar polls data from your Point of Sale, the data within Radar should mirror the data in the POS. Comparing how the POS reports labor data to how Radar reports the same labor data is an important part of managing a Radar database. 

Recommended Reasons to Audit Labor:

  • New Location Added 
  • New POS Added
  • Data Discrepancy Troubleshooting
  • Ongoing Data Integrity

Step 1: Report from the POS

For auditing, you will need a current report run from the system proving labor data to Radar for the Location and week of business being audited. Typically, labor is provided by the POS. However, if your employees do not clock in and out through the POS, labor might be provided from another system through a Labor Flat File.

  • Important Note: This report must be run from the system providing the labor data and not from third-party software. 

The more detailed the POS report is, the more thorough the audit will be. If possible, the report from the POS should include:

    NamesIn Time PunchesRegular HoursCC Tips
    RatesOut Time PunchesRegular PayDeclared Tips
    JobsBreak PunchesOT/DT HoursTotal Gratuity
OT/DT PaySales Per Employee

Every POS has a different name for this general labor report. Common POS report names include:

  • Weekly Punch Report
  • Labor Detail
  • Punch Detail

Step 2: Report from Radar

For auditing Labor data, the 'Payroll Report' is used.  


The Payroll Report is found on the Labor page within the Reports Module

  • Note: You may not have access to the Payroll Report or Reports Module. If you do not have access, please contact your Superadmins for assistance.

Filtering the Payroll Report for a Labor Audit

  1. In Step 1, Select a Single Location
    • Auditing for labor should always be done for one Location at a time
    • If discrepancies are found, narrowing down the cause is simpler when limited to a single Location

  2. In Step 2, Select a Full Business Week
    • Auditing labor should always be done for one fiscal week at a time
    • OT hours are calculated per fiscal week.
      • Note: A full fiscal week is needed to audit OT.

  3. In Step 3, Change 'Metric' to 'Punch Audit Details'
    • This is the most detailed version of the Payroll Report

  4.  In Step 3, Change 'Zero Rate Employees' to 'Include'
    • It is important to check the labor being received for zero rate employees.


Step 3: Compare Reports

To audit labor, move through the report run from the POS and compare each metric to a comparable metric on the Payroll Report run from Radar. 

What to Audit

  • Names - Employee names should match

  • Employee List - ALL employees should match 
    • Important Note: Missing or unexpected employees may indicate an Employee Resolve issue

  • Punches - In, Out, and Break punches should match
    • Note: Punches marked with an asterisk (*) indicate that the punch has been edited in the provided POS or Labor Flat File data.

  • Jobs - Each set of In/Out punches will have an associated Job. The Jobs should match.

  • Regular Rate - Each set of In/Out punches will have an associated Regular Rate. The Regular Rates should match.

  • OT Rate - OT Rate is calculated in Radar based on FLSA standards and OT Rule configuration
    • Note: By default, Radar uses a blended OT calculation for employees working multiple jobs. This can be adjusted to 'Based on job where OT incurred'
    • Important Note: OT Rate for tipped employees may not match. Radar calculates the OT Rate for tipped employees based on the FLSA formula. Your POS may not calculate Tipped OT Rates correctly.

  • Hours - Hours are calculated in Radar based on punches, first day of the fiscal week, and the Daily/Weekly OT rules for the location 
    • Regular, OT, and DT Hours should match
    • Note: A large discrepancy in OT and/or DT hours may indicate that the first day of the fiscal week or OT rules need to be adjusted.

  • Pay - Pay is calculated in Radar as Hours multiplied by Rate. Regular, OT, and DT Pay should match.
    • Note: There may be a small discrepancy of a few cents based on differences between how Radar and the POS calculate partial minutes in the Hours calculation.

  •  CC Tips & Auto Gratuities - CC Tips and Auto Gratuities are combined by default on the Radar Payroll Report 
    • Note: In the Step 3 report filters, the report can be configured to show just CC tips or Auto Gratuities 

  • Declared Tips - Cash tips entered into the POS will be recorded in Radar as 'Declared Tips'. 
    • Note: Your POS may not provide declared tips data

  • Sales - Sales associated with a clocked-in employee
    • Note: Sales associated with individual employees is considered labor data. This data is often provided by the POS separately from sales data. Total Labor Sales may not match Total Sales. Radar's sales per employee should match the report run from the POS.
    • Note: Your POS may not provide sales by employee data. Flat Labor Files typically do not include sales by employee data.

What if something doesn't match?

If discrepancies are found during the Data Integrity Audit:

  1.  Confirm that the Report run from the POS is accurate and current
  2.  Repoll the Pay Periods data
  3.  Re-audit 
  4.  If the discrepancy is still present, submit a case to the Support Team
    • Reminder: When submitting a data discrepancy case to Support, include the report run from the POS for one date of business that illustrates the discrepancy. If the discrepancy involves OT hours/Rates/Pay, include a report run from the POS for a full fiscal week