Corporate Quarterly Tax Due Dates Checklist

A calendar-year C corporation’s federal estimated-income-tax installments generally fall on April 15, June 15, September 15, and December 15, adjusted for weekends and legal holidays. Fiscal-year corporations use the corresponding fourth, sixth, ninth, and twelfth months. These are not the company’s only quarterly dates: payroll returns, deposits, excise taxes, sales tax, and state estimates follow separate calendars.

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

Corporate income-tax estimates

A corporation generally makes installments when expected tax after credits is at least the current federal threshold.

Payroll returns

Form 941 is generally quarterly, but deposit frequency is determined separately and can be semiweekly or monthly.

S corporations

They usually pass federal income tax to shareholders but can owe specified entity-level taxes and state estimates.

State and local dates

Franchise, income, sales, unemployment, and local obligations use jurisdiction-specific calendars.

Weekend and disaster relief

Due dates can shift for holidays, weekends, or officially announced disaster relief.

Step-by-step workflow

1. List every tax account. Record agency, form, entity, tax year, frequency, and responsible person.
2. Map dates from official sources. Use Publication 509 and each state portal rather than a generic calendar.
3. Separate return and payment dates. A return date and deposit date can differ.
4. Calculate before scheduling. Update taxable-income and credit projections for each installment.
5. Pay through the correct account. Corporate estimates generally use electronic funds transfer and the corporation’s EIN.
6. Save proof and review notices. Retain confirmations by tax period and investigate misapplied payments promptly.

Worked example

A calendar-year C corporation expects federal tax above the threshold and runs biweekly payroll. Its income-tax estimate dates are April, June, September, and December, but its payroll deposits can be due more often and Form 941 follows its quarterly schedule. The controller maintains separate rows for each obligation rather than calling all of them “quarterly taxes.”

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

• Using individual 1040-ES dates for the corporation. Corporate estimates follow corporate rules.
• Treating S corporation estimates like C corporation estimates. Identify which taxpayer owes the tax.
• Confusing Form 941 with deposit timing. The return and deposits have different schedules.
• Paying under the wrong EIN. Verify entity and period.
• Copying last year’s calendar. Recheck weekends and law changes.
• Ignoring state accounts. Add every jurisdiction separately.

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.

Control checkpoint

Before filing or moving money, identify the legal entity, federal tax classification, effective date, owners, tax year, states, filing channel, and source records. Compare the proposed treatment with the prior return, elections, agency accounts, and reconciled books. Assign one preparer and one reviewer, record open assumptions, and replace those assumptions with evidence before submission. This checkpoint prevents a correct general rule from being applied to the wrong taxpayer, year, account, or form.

Finish with a status log that distinguishes prepared, reviewed, transmitted, accepted, furnished, paid, and corrected. Attach confirmation numbers and dates to the exact tax period and jurisdiction. If software or an agency rejects the filing, keep the rejection beside the corrected acceptance so the history remains visible. Reconcile the final filed amounts back to the ledger or source schedule after every correction. This last step catches situations where the form was fixed but the books, recipient copy, state filing, or next-year opening balance still contains the old information. Record who completed this reconciliation and the official guidance revision used, making the file understandable to the next preparer without relying on memory.

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.