Quarterly Payroll: Returns Versus Deposits

Most employers file Form 941 each quarter to report federal income tax withholding and Social Security and Medicare wages and taxes. The employer reconciles quarterly liabilities with deposits and any balance or overpayment on the return. Deposits generally follow monthly or semiweekly schedules based on the federal lookback period, with a next-day rule for certain $100,000 liabilities. State withholding and unemployment reports have their own frequencies, accounts, wage bases, and dates. FUTA is generally reported annually on Form 940, although deposits can be required during the year when the accumulated liability crosses the applicable threshold.

This guide is part of Steady’s Business Taxes & the IRS library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

Quarterly return is not quarterly payment

The filing period and deposit cadence are separate controls.

Payroll dates create liability

Deposit rules generally look to when wages are paid and the employer’s deposit status.

Form 941 covers specified federal taxes

It generally reports federal withholding plus Social Security and Medicare wages and taxes, adjustments, deposits, and balance.

States have independent calendars

Withholding, unemployment, paid leave, local tax, and wage-detail reports can follow different schedules.

FUTA has its own workpaper

Form 940 and federal unemployment deposits do not belong in the Form 941 reconciliation.

Year-end forms build on quarterly data

Forms W-2 and W-3 should reconcile to the four quarterly returns and annual payroll records.

Provider use does not remove oversight

The employer should verify returns, deposits, states, notices, and agency posting.

Step-by-step workflow

1. Map every payroll account. List federal forms, state withholding, unemployment, local tax, paid leave, portals, and account numbers.
2. Confirm deposit schedules. Document federal monthly or semiweekly status and each state’s required frequency.
3. Close the quarter. Post payroll runs, manual checks, voids, benefits, third-party sick pay, tips, and corrections.
4. Tie employee-level wages. Reconcile gross, federal, Social Security, Medicare, state, unemployment, and local wages.
5. Tie tax liabilities. Compare payroll reports with liability dates, tax calculations, adjustments, and the ledger.
6. Tie payments. Match EFTPS and state confirmations with bank settlement and agency account history.
7. Prepare returns. Complete Form 941 and every required state or local wage and contribution report.
8. Review filing status. Confirm submitted, accepted, rejected, paid, settled, and corrected statuses separately.
9. Update year-to-date controls. Carry clean wage, tax, and deposit totals into the next quarter and W-2 workpaper.
10. Resolve notices. Assign each agency notice, response deadline, cause, correction, payment, and outcome.

Worked example

A monthly depositor pays employees twice a month. It deposits federal employment taxes by the monthly deadline during the quarter, then files Form 941 after quarter-end. The bookkeeper ties taxable wages and taxes to the payroll registers and matches three monthly deposits to EFTPS and the bank. The state unemployment return, state withholding return, and FUTA workpaper remain separate even though they use some of the same payroll data.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Waiting for quarter-end to deposit. Follow the employer’s actual deposit schedule.
• Calling every payroll payment Form 941 tax. Separate federal withholding, FICA, FUTA, states, localities, benefits, and garnishments.
• Using gross pay for every wage base. Each tax can use a different taxable-wage definition and limit.
• Ignoring rejected state reports. A federal acceptance does not close the quarter.
• Posting payments without periods. Record form, jurisdiction, period, liability date, and confirmation.
• Skipping quarter-to-date tie-outs. Errors become harder to correct at W-2 time.
• Combining Forms 940 and 941. Maintain distinct calculations, deposit rules, and returns.
• Trusting provider status alone. Verify agency and bank evidence.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Assign one owner and one reviewer to the calendar. The owner prepares the source schedule and resolves open items; the reviewer tests identities, totals, rule references, filing status, and evidence. Record the date of the official guidance used because form pages and software menus can change during the filing season. If a rule is uncertain, document the question and escalate it before the deadline rather than placing an unsupported assumption in the final file. This short control list protects both accuracy and continuity when another bookkeeper, payroll specialist, or tax preparer takes over the work. Save the checklist with the return so next year’s team can see which controls were completed and which exceptions required follow-up.

Practical implementation notes

Account calendar

Track jurisdiction, form, deposit frequency, return frequency, account, portal, owner, and reviewer.

Quarterly close

Tie employee wages, taxes, liabilities, deposits, returns, acceptance, ledger, and bank.

W-2 bridge

Carry quarter totals into an annual reconciliation and explain valid wage-base differences.

Exception log

Record manual checks, voids, fringe benefits, third-party items, corrections, and notices.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.