Federal Payroll Tax Deposits: Turn Pay Dates Into a Reliable Calendar
Updated: Oct 11

A payroll tax deposit calendar starts with your employer's deposit classification and the dates wages are paid. The employee pay frequency does not determine the federal deposit schedule. Once the correct rules are established, each pay event needs a due date, a submission cutoff, an accountable person and a way to confirm the money reached the intended tax account.
That last distinction matters when a provider withdraws payroll taxes from your bank account. The withdrawal tells you the provider received funds. It does not, by itself, prove which federal liability was deposited, when the deposit took effect or whether the payment was assigned to the correct period.
This guide addresses U.S. federal income tax withholding and Social Security and Medicare tax deposits for ordinary Form 941 employers. FUTA, state and local taxes, annual-return filers and special third-party arrangements need their own rules. Federal sources were checked on October 9, 2026. The reusable Deposit Run Sheet below connects the tax schedule to everyday payroll and treasury work without trying to replace a tax professional's interpretation of an unusual case.

Need a provider that makes tax-payment responsibilities visible? Use a free SelectSoftware Reviews advisor conversation to compare the work behind a tax-payment service. Bring your deposit calendar and ask who submits payments, confirms them and handles exceptions.
Table of contents
Establish the schedule before assigning dates
For a Form 941 employer, start with the returns that determine the lookback period. Under Publication 15, the ordinary 2026 lookback runs from July 1, 2024 through June 30, 2025. Add the taxes originally reported on Form 941, line 12, for those four quarters. A total of $50,000 or less means monthly deposits; more than $50,000 means semiweekly deposits. Form 944 history can change the lookback rule. New Form 941 employers generally begin as monthly depositors, subject to the $100,000 next-day rule.
Treat this as a documented annual decision, not a setting someone remembers from onboarding. Retain the four returns, a short calculation and the person who reviewed it. Put the resulting schedule, applicable calendar year and supporting file location beside the employer identity in the payroll setup record. An export showing only the current software setting is useful, but it does not explain why that setting is correct.
Use reported tax liability, not gross wages, bank withdrawals or deposits made. If a return was later corrected, separate the original amount used for the lookback from the adjustment. Publication 15 says adjustments on Form 941-X do not change prior-period liability for this lookback test. Preserve the adjustment separately so a reviewer does not inadvertently substitute the corrected accounting total.
Employers with a recent acquisition, a change in return type or an aggregate filing arrangement should have their tax adviser establish the applicable rule before using this worksheet. A payroll setup copied from another legal entity is not sufficient evidence. Even when the same staff and software serve two entities, the calendar record must identify the employer and the rule actually applicable to it.
Also distinguish a deposit requirement from the limited payment-with-return exception. The Form 941 instructions allow payment with a timely filed return when line 12 for the current or prior quarter is less than $2,500 and no $100,000 next-day obligation arose during the current quarter, provided the amount due is paid in full on time. If current-quarter liability is uncertain and the prior quarter does not qualify, use the required deposit rules. Do not infer eligibility merely because the employer has few employees.
Convert wage payment dates into deposit obligations
The IRS employment tax due-date guidance describes the ordinary schedules this way:
Monthly: taxes on wages paid during a calendar month are due by the 15th of the following month.
Semiweekly, Wednesday through Friday paydays: deposit by the following Wednesday.
Semiweekly, Saturday through Tuesday paydays: deposit by the following Friday.
Threshold override: accumulating $100,000 or more of tax liability on any day within a deposit period creates a next-business-day obligation.
These are starting rules, before holiday adjustments and special situations. Keep the wage payment date separate from the work-period end, payroll processing date and accounting accrual date. An off-cycle bonus, final paycheck or correction can create another pay event even if it is absent from the original annual calendar.
Begin with forecast rows so treasury can plan cash, then replace estimates with the approved payroll liability. Mark the amount as forecast or confirmed. Otherwise an early cash estimate can survive into the submission file after payroll changes. Keep a reference to the exact payroll report version used, especially when a register is rerun after approval.
For semiweekly employers, identify the Wednesday-through-Friday or Saturday-through-Tuesday deposit period on each row. Grouping by the company's biweekly pay period can conceal a separate deposit obligation. Where a semiweekly period includes pay dates in different quarters, Publication 15 requires separate deposits for the liabilities in those quarters. Preserve the quarter on every row before combining amounts.
The recurring payroll calendar should therefore carry a second layer of events: tax obligation created, submission prepared, submission approved and confirmation reviewed. These events may involve different people and systems. One owner should be able to explain how the approved payroll run becomes a specific deposit instruction.

Keep three dates visible. A processing reminder cannot substitute for the statutory due date or the chosen payment method's cutoff.
Account for holidays and payment-method cutoffs
A holiday check belongs on the actual obligation, not only on the employee pay calendar. Publication 509 explains that a deposit due on a weekend or legal holiday generally moves to the next business day. Semiweekly depositors receive at least three business days after their deposit period closes, so a holiday inside that interval can move the deadline even when the nominal due date is not a holiday. The relevant federal deposit holidays are District of Columbia legal holidays, not every statewide holiday.
For a fictional semiweekly employer paying wages on Friday, October 9, 2026, the ordinary following-Wednesday deadline would be October 14. Monday, October 12 is a listed federal deposit holiday. The three-business-day rule makes Thursday, October 15 the deposit deadline. Record the holiday reason on the row; do not simply overwrite Wednesday with Thursday and leave the reviewer guessing.
Use the current IRS tax calendar to validate dates, then add the submission cutoff for the actual payment route. Those are two separate checks. A tax deadline on Thursday does not mean a provider will accept a funding instruction late Thursday afternoon. Ask for the provider's cutoff, time zone, amount limits and confirmation process in writing, including how an emergency payment is coordinated.
Current Notice 931 states that EFTPS accepts same-day payments of $1 million or less submitted before 3 p.m. Eastern time on a business day. Payments above $1 million must be submitted by 8 p.m. Eastern time the day before the deposit is due. Other payment methods and third parties may have different conditions. Do not carry an old blanket “EFTPS always requires the prior day” assumption into a new calendar, and do not treat same-day availability as your normal operating target.
Set an internal preparation deadline that leaves time for approval and recovery from a rejected instruction. That buffer is your operating choice, not an IRS extension. Label it accordingly. If your payroll provider requires funds earlier, use the earlier contractual deadline for the handoff while retaining the federal due date for oversight.
Before relying on a backup route, confirm access and bank availability. A same-day wire through the Federal Tax Collection Service requires advance arrangements with the financial institution; availability, deadlines and fees must be checked. The useful contingency record names an authorized operator and verified contact route, not just the phrase “wire if needed.”
Watch the accumulated liability when payroll changes
The $100,000 next-day rule is a daily accumulation test within the applicable deposit period. Publication 15 requires testing the threshold before reducing liability for nonrefundable credits. A monthly employer that reaches the threshold becomes a semiweekly depositor the next day and remains so for at least the rest of that year and the following year. The calendar must change as well as the immediate payment deadline.
A fictional monthly employer has $60,000 of accumulated November liability before a November 19, 2026 bonus run adds $45,000. The resulting $105,000 requires a deposit by the next business day, Friday, November 20. Leaving the combined amount on the normal December 15 reminder would miss the accelerated obligation. The new semiweekly status also needs to reach the provider and the filing reviewer.
Make the payroll change process include a tax-calendar impact question. A pay-date move can shift the deposit period; an extra run can change its total; a larger bonus can trigger next-day funding. The person approving employee compensation should not be assumed to have approved the resulting payment instruction or bank authorization.
Use a threshold watch on every confirmed run, not only when someone labels a payment “large.” Give payroll responsibility for the liability data and the tax owner responsibility for interpreting the rule. Treasury should see the revised amount and deadline early enough to act. If two runs are processed on the same day, combine the relevant liability for the test rather than evaluating isolated reports.
Track deposit periods precisely. A semiweekly liability on Tuesday and another on Wednesday belong to different accumulation periods. Once the threshold is reached, the IRS rules also specify how accumulation restarts for later liabilities. Escalate a complex sequence to the tax owner instead of summing the whole week or subtracting whatever cash was already sent.
The off-cycle approval record should identify who recalculates the deposit deadline and who updates an existing instruction. If an instruction has already been submitted, retain its status and reference before changing or replacing it. This protects against both underpayment and duplicate payment without making a payroll processor invent a tax correction rule.

Ask a prospective provider to show the exception path. Bring the bonus, holiday and failed-payment cases to a free SelectSoftware Reviews advisor conversation and ask which services show the exception path. Confirm each finalist's promised work in the service agreement.
Use the Deposit Run Sheet from forecast to confirmation
Copy the following nine fields into a note, task system or spreadsheet. Use one record for each deposit obligation and connect every contributing payroll run. Keep sensitive bank credentials outside the sheet. The sheet is a coordination tool; it does not calculate payroll taxes or decide a special tax treatment.
1. Employer and tax account. Employer name: ____; EIN reference: ____; return type: ____; calendar year and quarter: ____. Identify the account without copying login secrets. If the provider files in an aggregate arrangement, record the arrangement and the tax owner's approved method for confirming your employer's share.
2. Schedule authority. Monthly or semiweekly: ____; lookback support location: ____; reviewer and review date: ____; threshold-triggered change, if any: ____. A newly discovered inconsistency stays open until someone resolves the authority, rather than accepting whichever setting produces the later deadline.
3. Contributing pay events. Wage payment dates and run IDs: ____; confirmed liability by date: ____; source report version: ____. Mark any forecast amount clearly. Include extra runs and retain a replacement reference when an earlier payroll report becomes obsolete.
4. Deposit-period and threshold review. Period start and end: ____; accumulated liability: ____; $100,000 test result and reviewer: ____. Identify any quarter boundary or accelerated deadline. If multiple payrolls contribute, attach a short list that lets the reviewer reproduce the total.
5. Federal due date. Ordinary rule: ____; due date: ____; holiday or other adjustment and source: ____. Keep the explanation even when software calculates the date. A disagreement between the provider calendar and the tax review needs a named resolver before the applicable cutoff.
6. Payment route and working deadline. EFTPS, other approved electronic route or provider: ____; submission cutoff and time zone: ____; internal preparation deadline: ____; backup contact: ____. Verify that the chosen route accepts the amount, tax type and requested date. Do not substitute a bank debit date for a payment effective date.
7. Funds and authorization. Funding account reference: ____; available funds confirmed by: ____; preparer: ____; payment approver: ____. Follow the organization's access and segregation rules. A payroll approver can authorize the run without having bank-payment authority, so retain both decisions where the roles differ.
8. Submission details. Amount: ____; tax form and period selected: ____; requested effective date: ____; submission time: ____; confirmation or trace reference: ____. Record the instruction status exactly as shown. “Scheduled” and “completed” describe different stages and should not share one unchecked completion box.
9. Independent confirmation and exceptions. Payment-history evidence: ____; bank settlement checked by: ____; differences or rejection: ____; case owner and next action time: ____. Record what evidence is still expected and when it will be checked. Remove “awaiting confirmation” only after the required evidence arrives or a documented exception is escalated.
Use these selectable checks at the appropriate stage:
☐ Ready to submit: identity, liability, deadline, payment route, funds and authorization agree.
☐ Submitted: a traceable instruction exists for the intended amount, form, period and date.
☐ Confirmed: payment-history evidence and bank settlement have been reviewed; unresolved differences have owners.
☐ Exception active: rejection, missing evidence or uncertainty has an action time and an authorized resolver.
These statuses prevent an open issue from disappearing behind a single “done” label. They do not authorize withholding required payments while paperwork is improved. If a deadline is approaching, escalate the unresolved item and available payment options immediately to the tax and treasury owners.

Record the payment reference beside its tax form, period and amount before closing the row.
Check the provider's work without duplicating its payment
Ordinary payroll service providers and reporting agents do not automatically transfer the employer's federal tax responsibility. IRS guidance on outsourcing payroll duties recommends employer oversight and access to verify payments. Other legal arrangements, including certain CPEO situations, can have different liability rules. Establish the arrangement before assuming either that all liability transferred or that every third party works identically.
Ask the provider for a sample confirmation record before implementation. It should let your reviewer identify the employer or allocation, tax type, period, amount, effective date and payment reference. If the available report merely shows “taxes collected,” ask what later evidence demonstrates deposit completion and when it becomes available.
Name the person inside your business who reviews this evidence. The provider can prepare and submit the deposit while finance compares payment history with the obligation record. That oversight is different from sending a second payment independently. Before a replacement payment, confirm the status of the original instruction and agree who will cancel, repair or reissue it.
Keep the employer's address of record and agency correspondence under employer control. A notice should reach a responsible person promptly even when the vendor is expected to investigate it. Preserve the notice, its response deadline, the relevant deposit references and the provider's written response together. Give the notice its own owner and response date in the case record.
When changing providers, agree who owns each deposit that straddles the handoff. Include wages already paid, outstanding deposit instructions, refunds or credits and access to earlier payment records. A new vendor can calculate future payroll correctly while an old obligation remains unassigned. Confirm the boundary by employer, pay date and tax period, not just by the date the new subscription starts.
Service selection should include this retained employer work. Compare how notices, bank failures, late payroll changes and high-liability runs are handled, then price the internal oversight that remains. A promise to “handle taxes” needs a description of the actual submission and exception tasks before it is useful in a purchase decision.
Resolve missing or rejected payments as incidents
When expected evidence is absent, first establish what failed: liability calculation, instruction creation, approval, provider funding, electronic submission, bank settlement or allocation to the tax period. These are different problems with different owners. Preserve the last known status and timestamps before anyone overwrites a record.
For a rejected payment, have the authorized treasury or payment operator verify the bank reason through established contacts. Have the tax owner determine the required corrective payment and timing. Tell the provider which party is acting, so its automatic retry does not collide with a replacement. Keep both the failed reference and the later successful reference in the same case.
For a payment that settled but appears in the wrong tax period, gather the original instruction and agency record. Do not assume another debit is the answer. The tax owner or provider should establish the appropriate correction route and track it to confirmation. A general ledger journal can reclassify an internal balance without changing how the IRS applied a payment.
Failure-to-deposit penalties can apply to timing, amount or method failures. The IRS penalty guidance describes graduated rates based on lateness and separate notice-related conditions; relief depends on the facts and applicable criteria. A later successful payment does not by itself resolve a penalty or notice. Keep any notice review and response as a separate task with its own deadline.
An incident is operationally closed when the required payment outcome is confirmed, the liability record is reconciled and remaining notice work is assigned. Capture the specific prevention change, such as an earlier approval reminder, a corrected provider cutoff or a tested backup operator. Do not turn every incident into a complete calendar redesign when one broken handoff explains it.
Carry the evidence into quarter-end and the next year
The deposit calendar should feed the quarterly tax tie-out, rather than become another disconnected report. Connect each payment to the liability it covers and label unresolved amounts before the filing reviewer begins. Keep tax-liability dates and deposit dates in separate fields so a settled bank item is not accidentally used as the date wages were paid.
The Schedule B instructions require liabilities on the dates wages were paid, not deposits on their payment dates. A semiweekly employer's filing support therefore needs the daily liability record as well as payment evidence. If those two histories disagree, investigate the difference instead of changing liability dates to make the schedule resemble the bank statement.
Build next year's classification review into the calendar before year-end. Collect the applicable originally filed returns, have the tax owner confirm the lookback, and obtain written acknowledgement when the provider setting changes. Recheck current annual guidance and payment cutoffs; a recurring task copied from last year can preserve an obsolete assumption as efficiently as it preserves a correct one.
For the next actual deposit, complete the Run Sheet with your payroll report and payment route. Have a second person reproduce the amount and due date, then follow the record through submission and confirmation.

Make deposit evidence part of your provider comparison. If your current service cannot clearly show who submits, verifies and repairs tax payments, take your completed Run Sheet to a free SelectSoftware Reviews advisor conversation. Ask potential services to specify the retained employer work.
Continue with related tools:

About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.




