How to File S Corporation Taxes Online

The corporation must first close and reconcile its books. Form 1120-S reports income, deductions, assets, liabilities, tax attributes, shareholder information, and separately stated items. Schedule K totals must tie to every Schedule K-1. Payroll for shareholder-employees should reconcile to Forms 941, W-2, W-3, deposits, benefits, and the ledger. Electronic filing uses current approved software or an authorized provider and requires a valid signature authorization. States may use different portals, forms, extensions, elections, and payment systems. A federal e-file acceptance does not complete the state or shareholder filing.

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

Software does not close the books

Reconcile cash, revenue, expenses, payroll, debt, fixed assets, equity, and shareholder activity before import.

The correct tax year matters

Use current schema, forms, and instructions for the corporation’s year, including short-year facts.

Shareholder identity must tie

Verify legal names, addresses, TINs, ownership dates, percentages, and changes.

K-1 totals must reconcile

Schedule K and all shareholder allocations, statements, basis inputs, and state equivalents need a controlled tie-out.

Payroll is part of the return review

Officer compensation, benefits, employment taxes, and distributions must be separately reconciled.

Extensions do not pay tax

Address entity-level federal taxes, state payments, payroll, and shareholder estimates by their own dates.

Transmission is not acceptance

Monitor rejects, correct the source, retransmit, and save final acknowledgment.

Delivery is separate

Securely furnish K-1s and supplemental statements and track corrected packages.

State returns require their own status

Record prepared, filed, accepted, paid, and delivered by state.

Archive data, not only PDFs

Keep the final return file, source trial balance, workpapers, authorization, acceptance, payments, and K-1 delivery.

Step-by-step workflow

1. Confirm S status and year. Review Form 2553 acceptance, legal name, EIN, tax period, ownership, and any termination or late-election issue.
2. Close the general ledger. Reconcile all balance-sheet accounts, income, expenses, payroll, taxes, assets, debt, equity, and shareholder transactions.
3. Build tax workpapers. Prepare book-to-tax adjustments, depreciation, basis inputs, distributions, compensation, benefits, state differences, and special taxes.
4. Prepare Form 1120-S. Complete required schedules and statements using the current form and e-file rules.
5. Validate shareholders. Tie ownership days, percentages, K-1 allocations, addresses, TINs, and supplemental information.
6. Complete federal review. Run diagnostics, compare to prior year, inspect elections, verify signatures, and approve the final tax result.
7. Authorize and transmit. Use the proper electronic signature authorization and approved filing channel.
8. Monitor acceptance. Resolve each reject and save the final IRS acknowledgment.
9. Complete state returns. File, pay, monitor, and retain every state and local result.
10. Deliver and archive. Provide K-1s securely and preserve the complete final filing package.

Worked example

A calendar-year S corporation imports its trial balance into tax software, but the diagnostic shows officer wages in the ledger do not agree with the W-2. The preparer does not force the return to transmit. The company reconciles a taxable health-insurance adjustment, updates payroll and the books, reruns the tax return, ties Schedule K to two K-1s, obtains authorization, and e-files. The team saves the accepted federal acknowledgment, files two state returns, records payments, and documents secure K-1 delivery.

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

• Filing before payroll ties. Resolve Forms 941, W-2, benefits, and officer compensation first.
• Treating distributions as wages. Keep payroll and equity treatment separate.
• Importing an unreconciled trial balance. Tax software cannot identify every missing or misclassified transaction.
• Assuming a federal acceptance covers states. Track each jurisdiction independently.
• Giving shareholders draft K-1s. Label estimates clearly and deliver final packages only after controlled approval.
• Ignoring rejects. A sent return can remain unfiled.
• Saving only a PDF. Retain source data, workpapers, authorization, acceptance, payments, and delivery 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

E-file status board

Track draft, review, authorization, transmission, reject, acceptance, state filing, payment, K-1 delivery, and archive.

Diagnostic log

Record each software warning, reviewer decision, correction, and unresolved disclosure.

Shareholder control

Use a dated ownership schedule and delivery log with restricted access to TINs.

Final package index

List the signed return, workpapers, trial balance, elections, depreciation, basis, payroll tie-out, states, payments, and acknowledgments.

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.