Quickbooky

Accounting News

Payroll

Filing Indiana W-2s Electronically in QuickBooks: What to Know

Indiana employers using QuickBooks payroll must verify county and wage data on the WH-3 worksheet before electronically filing state W-2s each year.

COMMUNITY ISSUESQUICKBOOKY

Indiana is one of the states that requires employers to submit employee wage data alongside their annual WH-3 withholding return — and for QuickBooks payroll subscribers, that means working through a dedicated state worksheet before the electronic filing goes through. The process is mostly automated, but the county-tax portion has tripped up enough users to make it worth a clear walkthrough.

What the Worksheet Actually Does

When you initiate an electronic Indiana W-2 filing from QuickBooks, the software opens a review worksheet pre-populated with wage and withholding data pulled from your payroll records. The purpose is twofold: confirm that the dollar amounts for state income tax and county tax are correct for each employee, and verify that each worker is assigned to the right Indiana county for withholding purposes.

The state requires this employee-level breakdown to accompany the WH-3, which is Indiana’s Annual Withholding Tax form. Without verified county assignments, the filing can be rejected or the tax allocation can be wrong.

County Selection Is the Critical Step

The step that causes the most confusion is county assignment. QuickBooks asks you to select a default county — generally the county where the majority of your employees live and pay county tax. Every employee on the worksheet then defaults to that county.

That default will be wrong for any employee who lives or works in a different county. For each of those workers, you need to click the county name displayed on their row and select the correct one from the dropdown list. If you skip this step, county tax dollars can be reported against the wrong jurisdiction.

To help with this, QuickBooks added a field called “County subject to withholding” in the Indiana Counties Tax section of employee setup. There is also a Local Tax Summary report — available as an Excel export — that breaks down county, county wages, and county tax withheld for each employee. Running that report before you start the worksheet can save time and catch misassignments early.

Third-Party Sick Pay Has a Catch

If any employee received third-party sick pay during the year, there is a checkbox on the worksheet that opens a separate sick-pay detail section. There, you enter the wage amounts associated with that pay, along with any state income tax or county tax that was withheld.

Those tax amounts are added directly to lines 1 and 2 of the WH-3, so accuracy matters. The sick-pay wages themselves get folded into the employee’s total wages on the filing.

There is, however, a notable limitation. QuickBooks does not support electronically filing a record for an employee whose only compensation for the entire year was third-party sick pay — meaning no wages paid directly by the employer. To be included in the electronic filing, an employee must have received at least some earned income and withholdings from the employer itself.

Employees With Zero Withholding

Another detail that has puzzled users: only employees who have either a state income tax amount, a county tax amount, or both will appear on the worksheet and in the employee count. The WH-3 reports tax amounts withheld, not gross wages — so if an employee had no Indiana or county tax withheld for the year, their wages will not display and they will not be included in the filing.

This is by design and follows state specifications, but it can look like data is missing if you are expecting to see every employee listed regardless of withholding.

Practical Takeaway

The worksheet is essentially a verification checkpoint. Most of the numbers will already be filled in from your payroll data, and the built-in Help button on the form window can guide you through field-specific questions. The manual work centers on county assignments and any third-party sick pay entries — getting those right before you submit is what keeps the filing clean.

← Back to Community Issues