Completing Alaska Form TQ01C Continuation Sheet in QuickBooks Payroll

QuickBooks Desktop payroll users responsible for Alaska state unemployment filings periodically encounter the TQ01C Continuation Sheet — the employee wage listing that accompanies the Alaska Quarterly Contribution Report. The form is generated automatically when you run state payroll forms, and while QuickBooks populates most fields from existing company and employee records, several lines require hands-on review. Users who assume the prefill is always correct can end up filing inaccurate wage reports, which may trigger state inquiries or corrections later.

What QuickBooks Fills Automatically

When the TQ01C Continuation Sheet is generated, QuickBooks draws on the payroll setup, employee profiles, and wage data already in the company file. Company information, employee names, and most wage figures carry over without manual entry. In a properly maintained file — one where employee records and payroll items are current — the form may be complete enough that no additional input is needed beyond a final review.

The friction tends to arise on three specific lines where QuickBooks either leaves fields blank or prefills values that may not match the employee’s actual situation during the quarter.

Line 12 — Reportable Wages Paid This Quarter

This line captures all reportable wages for each employee during the quarter. Alaska statute defines wages broadly as all remuneration for service, but there are specific exclusions. Payments that fall outside the statutory definition of wages should not be reported here.

This is where many users run into trouble. If a company issues payments that are excluded under Alaska rules — certain types of compensation that do not count as taxable for state unemployment purposes — those amounts should not appear on Line 12. The risk is twofold: including excluded payments inflates reported wages and may overstate tax liability, while omitting reportable wages understates them. Either error can require an amended filing.

The Alaska Employment Security Tax Handbook, available through the state’s Department of Labor and Workforce Development website, provides the authoritative reference for what counts as wages, which payments are excluded, and which types of employment fall outside reporting requirements. Users handling unusual compensation scenarios — severance, certain reimbursements, or specialized pay categories — should verify treatment against that handbook rather than assuming all payments flow through identically.

Line 13 — Full Occupational Title or Code

QuickBooks prefills a six-digit occupational code for each employee based on payroll records. The critical step is verifying that the code reflects the work the employee actually performed during the quarter — not the job they were trained for or a job title on paper.

A common pitfall: an employee trained in one role who was working in a different capacity. Someone trained as a computer programmer but functioning as a manager during the reporting quarter should carry the manager code, not the programmer code. QuickBooks has no way to detect this kind of role shift on its own; the software relies on the occupational code stored in the employee profile. If that profile was set up based on the employee’s original hire position and never updated, the prefill will be wrong.

Users should pull the current occupational code list from the Alaska Department of Labor and Workforce Development website and cross-check each prefilled code against the employee’s actual duties. The reporting codes page on Intuit’s payroll tax support site links to the state’s current code definitions.

Line 14 — Full Geographic Code

This two-digit code identifies the employee’s primary work site during the quarter. As with occupational codes, QuickBooks prefills the value from stored records, but the prefill is only as accurate as the underlying employee setup.

The geographic code should represent where the employee primarily worked — not the company’s headquarters or a mailing address. Employees who relocated, worked from a different job site, or split time between locations during the quarter may need a code that differs from what QuickBooks pulls in. The same reporting codes reference page links to the state’s current geographic code definitions.

Common Setup Pitfalls

Most TQ01C errors trace back to stale employee records. Occupational codes assigned at hire and never revisited, geographic codes tied to old work sites, and wage items set up without checking Alaska’s exclusion rules are the typical culprits. Running the form without a line-by-line review — especially when employee roles or locations changed mid-year — is where filings go wrong.

The total page count at the bottom of the return is calculated automatically and reflects the full number of pages in the filing. Users printing or submitting electronically should verify that the page count matches what was actually generated, since missing pages in a multi-employee filing can go unnoticed.

For broader payroll form troubleshooting, including situations where QuickBooks generates state forms with missing or mismatched data, our QuickBooks payroll help resources cover common filing errors and setup corrections.