Quickbooky

Accounting News

Payroll & Compliance

Tennessee New Hire Report in QuickBooks: What Auto-Fills and What Needs Review

QuickBooks generates Tennessee New Hire Reports with pre-populated employee data, but several fields require manual verification before submission to the state.

COMMUNITY ISSUESQUICKBOOKY

QuickBooks Desktop generates state-specific New Hire Reports to help employers meet their compliance obligations, and Tennessee employers have flagged questions about which fields the software populates automatically versus which ones require a manual check before submission.

The Reporting Requirement

Tennessee employers must submit a New Hire Report to the state’s New Hire Reporting Program within 20 calendar days of hiring, rehiring, or recalling an employee to work. For employers who file electronically or magnetically, the state requires two monthly transmissions spaced no more than 16 days apart.

The report draws on employee data already stored in QuickBooks, but the software’s ability to populate every field depends entirely on what information was entered during employee setup. Employers who leave optional fields blank in their payroll records will see corresponding gaps on the generated report.

Mandatory Fields QuickBooks Should Populate

Tennessee requires seven core data points on every new hire submission: the employer’s name, address, and federal Employer Identification Number, plus the employee’s name, home address, Social Security number, and first day of work.

QuickBooks pulls most of this directly from the employee record. The one field that warrants close attention is the Date Started to Work or Recalled. QuickBooks attempts to auto-fill this by copying the value from the Date of Hire field, and in most cases that transfer is correct. However, Tennessee defines the first day of work as the date the employee first performs services for wages — which may not always align with the hire date in your records. If the imported date does not reflect the actual first day worked, you can correct it directly on the report form before submitting.

Optional Fields and Manual Entries

Tennessee also encourages — but does not require — employers to include additional details. QuickBooks will populate these fields if the underlying data exists in the employee setup, but each one can be edited or removed entirely if you prefer not to share it with the state.

Employee Date of Birth — Imported automatically when present in the employee record. Optional for Tennessee reporting; you may delete it from the form.

Employee Gender — Imported automatically when present in the employee record. Optional for Tennessee reporting; you may delete it from the form.

Employee State of Hire — Imported automatically when present in the employee record. Optional for Tennessee reporting.

Medical Benefits Availability — Not auto-populated from employee data. You must enter “Y” if medical insurance is available to the employee or “N” if it is not. This is an optional field for Tennessee.

What to Check Before Submitting

The core issue users encounter is that QuickBooks treats the report as a pre-filled draft, not a final document. Fields that look complete may still contain inaccurate or incomplete data if the source employee record was not fully maintained. The Date of Hire field, for instance, imports as-is from setup — and if that date was entered incorrectly during onboarding, it carries through to the report unless you catch and correct it.

The practical takeaway: after generating the Tennessee New Hire Report, review every field against the employee’s actual record and the state’s definitions before transmitting. The mandatory fields must all be present and accurate, and the first-day-of-work date should reflect the literal first day the employee performed paid services — not necessarily the date on the offer letter or the date they were entered into payroll.

If the generated report is missing data or the form window itself is behaving unexpectedly, the built-in Help button on the form window provides additional troubleshooting guidance specific to the report interface.

← Back to Community Issues