Quickbooky

Accounting News

Payroll

Tennessee New Hire Report in QuickBooks: What Fields Matter and What to Check

QuickBooks auto-populates Tennessee's New Hire Report, but several fields need review before submission — and some may require manual correction.

COMMUNITY ISSUESQUICKBOOKY

QuickBooks generates a state-specific New Hire Report for Tennessee employers, and while the software auto-populates most fields from existing employee records, users have flagged confusion over which data points are mandatory, which are optional, and which ones may need a manual once-over before the report is filed.

Under Tennessee law, employers must submit new hire information to the State of Tennessee New Hire Reporting Program within 20 days of an employee being hired, rehired, or returning to work. The mandatory fields are straightforward: employer name and address, the employer’s Federal Employer Identification Number, the employee’s name and home address, the employee’s Social Security number, and the employee’s first day of work. QuickBooks pulls these details from the records you have already set up, but the burden is on the employer to confirm accuracy before filing.

Where QuickBooks Needs a Hand

The friction users run into tends to involve the fields Tennessee treats as optional but still encourages employers to provide. These include the employee’s date of birth, gender, state of hire, and whether medical insurance is available to the employee. QuickBooks imports date of birth, gender, and state of hire from employee setup if you have entered them there. Because these are optional under Tennessee guidelines, you can delete the imported values if you prefer not to share them with the state.

The medical benefits field is a manual entry. QuickBooks does not auto-populate it, so you need to enter “Y” if medical benefits are available to the employee or “N” if they are not.

The Date Fields That Trip People Up

Two date-related fields deserve particular attention. The first is the employee date of hire. QuickBooks imports this from your employee setup, but Tennessee defines “date of hire” as the first day the employee performs services for wages. If the imported date does not match that definition — for instance, if the setup date reflects an offer or acceptance rather than the actual first day worked — you can and should correct it on the report.

The second is the “Date Started to Work or Recalled” field. Federal law made this a mandatory field starting January 1, 2012. It is defined as the date an employee first performs paid work. Because most employers treat the hire date as the first day of work, QuickBooks automatically transfers the value from the Date of Hire field into the First Day of Work field. In most cases that transfer is correct, but if the two dates genuinely differ — say, an employee was hired weeks before actually starting — you need to verify the right date appears in the mandatory field.

Getting Help Inside the Form

For users who cannot locate what they need or run into issues with the form window itself, QuickBooks provides a Help button directly on the form. Clicking it opens guidance on using the form generally as well as troubleshooting specific problems. The form also includes a hyperlink for those who want to learn more about the New Hire Reporting Form and its requirements.

The Takeaway for Tennessee Employers

The report itself is functional and pulls the right data from employee records in most situations. The problems arise at the margins — optional fields that may or may not be populated depending on your setup, a medical benefits entry that always requires a manual “Y” or “N,” and date fields where the imported value may not match the state’s or federal government’s specific definition. Reviewing each field against Tennessee’s requirements before submitting is the simplest way to avoid a rejected filing or a compliance gap.

For broader QuickBooks payroll help and field-level troubleshooting across state reports, additional resources are available that walk through common setup and reporting issues.

← Back to Community Issues