When Is Sales Tax Due? A Multistate Guide

There is no national sales-tax due date. Each state sets the reporting period, return deadline, payment deadline, filing method, and zero-return rule. A business can have different frequencies in different states, and a state can change frequency as liability changes. Streamlined Sales Tax guidance explains that each participating state notifies a seller when filing begins and that registered sellers generally remain responsible until registration is properly ended. Current North Carolina guidance illustrates frequency-based variation: quarterly returns are due on the last day of the month after the quarter, monthly returns on the twentieth, and high-liability accounts use monthly filing with prepayment. Texas generally uses the twentieth after the reporting period. These are examples, not universal dates.

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

Registration creates the calendar

Use the account notice and portal profile for each legal entity, state, locality, outlet, and tax type.

Filing frequency can change

States may assign monthly, quarterly, annual, seasonal, or prepayment status based on expected or actual liability.

Return and payment can be separate

Some jurisdictions require an earlier prepayment, electronic-funds cutoff, or separate return even after payment.

Zero returns may continue

A registered account commonly requires a return for every assigned period until the state approves closure or inactive treatment.

Collection does not set the due date

Tax held from customers is not the business’s cash; the reporting period and account frequency control remittance.

Marketplaces require reconciliation

Separate marketplace-facilitator sales from direct sales while still reporting gross, exempt, or marketplace amounts as the state requires.

Use tax can increase the balance

Untaxed taxable purchases may enter the same return or a related filing.

Local filing can differ

Home-rule jurisdictions, local accounts, outlets, or special taxes can create additional returns and deadlines.

Weekend rules vary in detail

Confirm whether the next business day applies and whether electronic payment must be initiated before the due date.

Closing the business does not close the account

File through the final period and follow the jurisdiction’s cancellation process.

Step-by-step workflow

1. Inventory every registration. List legal entity, EIN, state, locality, tax type, account ID, portal, filing frequency, start date, and responsible person.
2. Capture the official due rule. Record period end, return date, payment date, prepayment, weekend rule, time zone, electronic cutoff, and zero-return duty.
3. Set two reminders. Schedule a data-close date and an approval or filing date early enough to resolve portal and payment problems.
4. Close sales by jurisdiction. Reconcile invoices, point-of-sale data, processors, marketplaces, refunds, discounts, shipping, exemptions, and the ledger.
5. Classify the tax base. Separate taxable, exempt, resale, marketplace, out-of-state, local, and use-tax transactions with support.
6. Recalculate liability. Compare tax collected with tax due and explain rate, sourcing, rounding, exemption, and timing differences.
7. Apply prior payments. Tie prepayments, credits, carryforwards, amended periods, notices, and agency adjustments to the correct account and period.
8. File and pay. Use the required portal and payment method, review authorization, and retain human-readable copies and confirmations.
9. Verify posting. Confirm the return and payment were accepted under the correct account and period and resolve any debit or portal rejection.
10. Update the calendar. Record frequency changes, new locations, nexus decisions, marketplace changes, acquisitions, closures, and notices.

Worked example

A business is registered in North Carolina and Texas. Its North Carolina account is quarterly and its Texas account is monthly. The business does not choose one companywide due date. It closes transaction data monthly, files Texas under the current twentieth-day rule, and files North Carolina for the quarter by the last day of the following month. When North Carolina changes the account to monthly because liability increases, the business updates the calendar from the official notice. It continues zero returns until each state confirms a valid closure.

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 the twentieth everywhere. Some states or frequencies use the last day of the month, another date, a prepayment, or a local rule.
• Letting software assign frequency. Confirm the official account notice and portal status.
• Skipping a zero period. Registration can continue the filing duty even when sales stop.
• Reporting bank deposits as sales. Reconcile processors, timing, refunds, loans, transfers, gift cards, and marketplace settlements.
• Using tax collected as tax due. Undercollection does not necessarily reduce liability, and overcollection can have special treatment.
• Ignoring marketplace reports. Prevent both omission and double counting.
• Paying without filing. A debit does not replace a required return.
• Closing an account informally. Complete final returns and the official cancellation process.

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

Use one row per entity, jurisdiction, account, and tax type with return, payment, prepayment, cutoff, owner, reviewer, and evidence.

Liability rollforward

Tie beginning payable, tax collected, use tax, payments, credits, return liability, adjustments, and ending payable.

Registration review

Quarterly, compare sales locations and channels with active accounts, thresholds, marketplace facts, and closure status.

Portal continuity

Maintain employer-owned access, multiple authorized users, current contact information, secure recovery, and saved confirmations.

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.