How to Prepare a Sales Tax Return

Sales-tax returns are state and often locality-specific. Each account has its own entity, outlets, filing frequency, due date, prepayment rules, portal, taxability, sourcing, marketplace treatment, zero-return duty, and payment method. Start with complete invoices and transaction exports, not only the sales-tax liability balance. Reconcile processors and marketplaces to ledger revenue, separate direct and marketplace-facilitated sales, validate exemption certificates, map jurisdiction and product treatment, then compare calculated tax with amounts actually collected. Filing and payment are separate statuses.

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 defines the account

Confirm legal entity, state, localities, outlets, start date, frequency, and closure status.

Gross sales need a ledger tie

Explain differences among invoices, point-of-sale, processors, marketplaces, returns, and book revenue.

Taxability needs evidence

Product, service, customer, exemption, and bundled-charge rules vary.

Sourcing drives local tax

Ship-to, service location, origin, destination, and special rules can affect jurisdiction.

Marketplace sales need separation

Facilitator-collected tax should not be duplicated, but marketplace sales may still appear in gross or deduction fields.

Use tax is separate

Review taxable purchases where the seller did not collect the required tax.

Return and payment are distinct

Verify portal acceptance, bank settlement, and agency posting.

Zero returns can remain due

Continue filing until the agency closes or changes the account.

Step-by-step workflow

1. Confirm the filing calendar. List entity, account, jurisdiction, frequency, period, due date, portal, and approvers.
2. Close transaction data. Reconcile invoices, POS, processors, marketplaces, refunds, discounts, shipping, and ledger revenue.
3. Normalize locations and products. Resolve missing addresses, invalid jurisdictions, unknown SKUs, and service categories.
4. Separate marketplace activity. Identify facilitator, direct sales, tax collected, fees, returns, and jurisdiction treatment.
5. Validate exemptions. Match customer, certificate, jurisdiction, type, dates, and covered purchases.
6. Calculate taxable sales and tax. Apply current state and local sourcing, rates, caps, and special rules.
7. Add use tax and adjustments. Review purchases, prior credits, bad debts, prepayments, amendments, and notices.
8. Review the draft return. Tie gross, deductions, taxable sales, tax, use tax, payments, and ending liability.
9. File and pay separately. Authorize each action, save confirmations, and verify bank and portal status.
10. Reconcile and archive. Tie the filed return and payment to the ledger and retain source data, workpapers, and corrections.

Worked example

A service business sells directly in three states and through a marketplace in two. For one state return, it reconciles invoice gross sales to the ledger, separates marketplace-facilitated transactions, validates resale certificates, assigns local jurisdictions from customer locations, adds use tax on untaxed equipment, and applies an earlier prepayment. The reviewer approves the return and payment separately and later verifies both portal acceptance and bank settlement.

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 from the liability balance. Start with complete transaction data and reconcile to the ledger.
• Ignoring marketplace sales. Separate facilitator and direct activity under the state’s return layout.
• Using billing address blindly. Apply the jurisdiction’s sourcing rules.
• Accepting expired certificates. Validate customer, state, type, dates, and purchases.
• Using last year’s frequency. Follow current notices and portal assignment.
• Approving only cash. Review the return calculation and source tie-out.
• Treating submitted as accepted. Verify portal status and correct rejects.
• Stopping zero returns informally. File until official closure.

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

Jurisdiction dashboard

Track entity, account, localities, frequency, due date, source data, draft, approval, filing, payment, posting, and notices.

Data-quality report

List missing locations, unknown taxability, exemption gaps, marketplace mismatches, negative sales, and ledger variances.

Return workpaper

Preserve source totals, transformations, gross-to-taxable bridge, rates, tax, use tax, credits, payments, and reviewer.

Notice and amendment log

Record deadline, issue, affected periods, source correction, return, payment, response, acceptance, and control change.

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.