Quickbooky

Accounting News

Payroll

Minnesota Quarterly Wage Detail Report in QuickBooks

How QuickBooks populates the Minnesota UI and Paid Leave Quarterly Wage Detail Report, what each field means, and how to review before filing.

COMMUNITY ISSUESQUICKBOOKY

QuickBooks Desktop includes a built-in state payroll form for Minnesota employers that combines unemployment insurance reporting with the state’s newer Paid Leave program. The report is designed to prefill wage and tax data from your existing payroll records, leaving you to review the results and file through the state’s online portal.

What the Report Covers

The Minnesota UI/Paid Leave QTD report functions as a Quarterly Wage Detail and Paid Leave filing document. QuickBooks pulls company information, employee wage data, and tax calculations from the records you have already entered throughout the quarter. In most cases, if your payroll setup is complete and current, the report requires little to no manual entry.

Minnesota requires all Wage Detail Reports to be submitted electronically. Employers reporting 50 or more employees in any calendar quarter must also remit payments electronically. The filing deadline falls at the end of the month following the close of the reporting quarter.

Fields QuickBooks Fills Automatically

Several core identifiers flow directly from your company setup. The report pulls your Minnesota Employment Tax Account Number, your Minnesota Paid Leave Account Number, your company name and address, your federal Employer Identification Number, and the quarter-end date. If any of these fields appear blank or incorrect, the underlying cause is typically missing or inaccurate information in your QuickBooks company or payroll settings rather than a problem with the report itself.

Worker Count for Each Month

One field that warrants close attention is the count of covered workers for each month of the quarter. The report asks for the number of full-time and part-time employees who worked or received pay during the payroll period that includes the 12th of each month.

Workers on paid sick leave, paid holiday, or paid vacation should be included. Employees on unpaid leave should be excluded. Even workers who have exceeded the annual taxable wage base for the year still count as covered workers for headcount purposes. If no employees were reportable during a given month, QuickBooks enters a zero in that field.

Wage Calculations

The report breaks wages into several categories. Total gross wages paid or due for covered employment during the quarter flow from the sum of individual employee detail on the report’s second page.

QuickBooks then applies the current year’s taxable wage base — the annual earnings threshold above which wages become nontaxable for unemployment purposes. Wages paid to an employee up to that threshold are taxable. Anything earned beyond it in a calendar year is classified as nontaxable.

The report calculates taxable wages by subtracting excess wages from total wages. It then computes the unemployment insurance contribution by multiplying taxable wages by your assigned UI contribution rate, which includes any additional state assessments. A separate line calculates the Workforce Enhancement Fee by applying the current WEF rate to the same taxable wage base.

What to Review Before Filing

Because QuickBooks populates the report from existing data, the accuracy of your filing depends on the accuracy of what you entered during the quarter. Before submitting, verify that your state account numbers are correct, that the quarter-end date matches the period you intend to file, and that the employee headcount for each month reflects the actual payroll period containing the 12th.

Review the wage totals against your payroll summaries to confirm nothing is missing or duplicated. If you discover discrepancies on the report — whether in wage totals, tax calculations, or employee detail — the issue generally traces back to a data-entry problem earlier in the quarter rather than the report generator itself. Correcting the underlying transactions and regenerating the report typically resolves the mismatch.

For broader help troubleshooting payroll form generation or data flow issues in Desktop, the underlying payroll records are usually the first place to look.

← Back to Community Issues