Sales Tax Filing and Remittance Guide

Sales Tax Filing and Remittance: The Bookkeeper's Complete Guide to Compliance, Penalties, and Due Dates

Sales tax filing and remittance are two legally distinct obligations, and bookkeepers who treat them as a single action are walking into avoidable penalties, separate due dates, and double-fine exposure across all 45 states plus Washington, D.C. that levy a statewide sales tax. The average combined state and local sales tax rate in the U.S. is 6.6%, and the most common economic nexus threshold is $100,000 in sales or 200 transactions per year — but exceptions in California, Texas, New York, and Florida change the math for multi-state sellers. Filing frequency is assigned by states based on tax liability (often $1,500 per month as the monthly trigger), not chosen by the business, and zero-return filings are mandatory in most states. The bottom line: a bookkeeper must manage filing and payment as a two-step workflow, with separate reminders, early remittance buffers, and a firm grasp of state-specific thresholds to keep clients compliant and penalty-free.

Why Sales Tax Filing Is a Silent Liability for Bookkeepers

Most businesses don't fail because they forget to charge sales tax. They fail because their bookkeeper files the return on time but pays a day late — or registers in one state while quietly creating nexus in seven others. Sales tax compliance is a state-by-state patchwork of thresholds, due dates, and penalty schemes, and the burden of getting it right falls squarely on the bookkeeper's workflow.

Consider the scale of the problem. According to the Tax Foundation, the average combined state and local sales tax rate in the United States is 6.6% as of 2023. That rate is collected on billions of dollars in retail transactions annually, and states have become aggressively sophisticated at auditing remote sellers and their records. For bookkeepers serving e-commerce clients, the risk is no longer hypothetical — it is a matter of when, not if, a nexus review or audit notice arrives.

This guide covers the full lifecycle of sales tax compliance: determining nexus, understanding assigned filing frequency, separating the filing act from the remittance act, handling zero returns, amending errors, and building a defensible internal workflow. If you manage books for clients in even two states, every section below applies to your practice.

Economic Nexus: The Post-Wayfair Thresholds That Trigger Filing Obligations

On June 21, 2018, the U.S. Supreme Court decided South Dakota v. Wayfair and effectively ended the physical presence requirement for sales tax collection. Overnight, a business selling $80,000 a year into a state from across the country could be obligated to register, file, and remit sales tax there — even with no office, warehouse, or employee in the state.

The most common economic nexus threshold across states is $100,000 in gross sales or 200 separate transactions in the current or prior calendar year. "Gross sales" here generally means gross revenue from sales of tangible personal property, digital goods, or taxable services delivered into the state — not just taxable sales. Bookkeepers often miss this detail and under-report nexus because they look only at taxable transactions.

State-Specific Nexus Threshold Exceptions You Cannot Ignore

While $100,000/200 transactions is the baseline, several major states deviate. California and Texas set the bar at $500,000 in sales with no transaction count. New York also uses $500,000 with a 100-transaction alternative. Florida, which has no transaction count, triggers nexus at $200,000. These are not rounding errors; they change whether a client with $250,000 in Florida sales but $450,000 in California sales owes registration in the latter.

Five states — Alaska, Delaware, Montana, New Hampshire, and Oregon — have no statewide sales tax, though Alaska and Montana allow local jurisdictions to impose their own. Do not let a client assume that selling into Oregon means zero compliance work; it typically means zero state-level work, but local rules in Alaska can still bite.

Marketplace Facilitator Laws Shift Liability to the Platform

In roughly 40 states, marketplace facilitator laws place the burden of collecting and remitting sales tax on platforms like Amazon, eBay, Etsy, and Walmart Marketplace. If your client sells through a marketplace, the platform generally collects the tax, and the client's filing obligation is limited to their direct (non-marketplace) sales.

This is a crucial bookkeeping distinction. When reconciling a client's sales tax, you must separate marketplace-collected sales from direct sales. A bookkeeper who treats total platform revenue as client-reported sales will overstate liability and file inflated returns. Conversely, a client selling through a marketplace and their own Shopify site must include only the direct sales in their economic nexus calculation — and must still register if those direct sales cross the threshold.

Filing Frequency: Assigned by the State, Not Chosen by the Client

One of the most persistent myths in sales tax compliance is that a business can simply "elect quarterly filing." States assign filing frequency based on the amount of tax collected, and new registrants are frequently placed on monthly status regardless of how small their sales are. The rule of thumb in many states — including Florida, Georgia, and Illinois — is that a monthly return is required when tax liability exceeds $1,500 per month; below that, quarterly or annual filing may be permitted.

This assigned frequency directly affects cash flow. A client who expects to file quarterly may instead be required to file monthly for the first year, which means twelve separate reconciliations instead of four. Bookkeepers who fail to check the state's assigned frequency calendar will miss returns entirely.

Filing Frequency Cheat Sheet: State Thresholds That Trigger Monthly Filing

What does this mean practically? New registrants in Florida, Georgia, and Illinois should assume monthly filing until the state assigns otherwise. Your first return after registration is the moment to read the state's determination letter carefully — it will state the assigned frequency, the filing due dates, and the access code for the state portal.

Frequency Is a Privilege, Not a Choice

You cannot ask for a less frequent schedule simply because your client prefers it. The state sets the frequency based on expected or actual liability, and changing it requires either hitting a lower liability threshold over a lookback period or filing a formal request. In most states, a business with consistently low liability can request quarterly status after three or four consecutive months of steady filings — but until the state approves the change, the original schedule controls.

If your client's sales drop dramatically, do not assume the system will automatically reschedule them. File a request with the state, keep the monthly returns current while the request is pending, and document everything. This is one of the highest-value proactive services a bookkeeper can provide, because late monthly returns accumulate penalties at a brutal rate.

The Filing vs. Remitting Split: The Trap Most Guides Miss

Here is the single most valuable concept in this article: filing a sales tax return and remitting the payment are separate legal acts with separate due dates and separate penalties in many states. Most compliance guides treat them as one activity — "file and pay by the 20th" — but the states themselves do not.

In New York and California, for example, the return submission and the payment are processed independently. A bookkeeper who e-files the return on the 19th but schedules the ACH payment for the 21st has filed late — or paid late — depending on the state's rules, and each violation carries its own fine structure. Failure-to-file penalties are commonly 5% of the tax due per month, capped at 25%, while failure-to-pay penalties typically run 1% per month on the unpaid balance. File on time and pay late, and you owe the payment penalty. Pay on time and file late, and you owe the filing penalty. Both, in the worst case, stack.

The Reconciliation Lag Problem with Third-Party Tools

If you use TaxJar, Avalara, or a similar remittance engine, you must understand that funds transferred through these services do not always post to the state's account on the actual due date. The tool generates the return and initiates the payment, but ACH processing, internal buffers, and state-side reconciliation can create a 1- to 3-day lag. This lag is invisible in the tool's dashboard but visible in the state's system as a late payment flag.

The operational fix is simple: build a buffer. Remit through third-party services one to two business days before the state's due date, or set the payment initiation date earlier than the filing date. If a client insists on paying on the exact due date, use the state's own portal for payment rather than a third-party engine. This is the kind of detail that separates a competent bookkeeper from one who gets clients audited.

Zero Returns: Why Filing $0 Still Matters

If a client collected zero sales tax during a period — no sales, all exempt sales, or no nexus activity in a state where they remain registered — the return must still be filed. Most states require a zero return, and failing to file one triggers the same penalties as failing to file a return with a large liability.

Zero-return failures often generate flat fees of $50 to $100 per period, and they accumulate. A client who stops selling in a state but never cancels their registration is a ticking liability: three years of quarterly zero returns at $75 per missed filing equals $900 in avoidable penalties, plus potential interest. Bookkeepers should reconcile the business's state registrations at every annual review and close accounts the moment a client stops selling into a state.

Canceling a registration is not the same as letting it go dormant. States require a final return — often marked "final" — and many require the client to affirm that all tax obligations have been satisfied. A bookkeeper who simply stops filing because "there's nothing to report" is creating a snowball of penalties that will become an audit issue later.

Common Due Dates and E-Filing Mandates

Due dates vary by state and by filing frequency, but the 20th of the following month is the most common date for monthly returns. Florida, Illinois, Texas, and many others use the 20th. California uses the 15th, and Arizona uses the 15th or 20th depending on filing frequency. Quarterly returns typically fall on the last day of the month following the quarter — April 30, July 31, October 31, and January 31 — but not uniformly.

Electronic filing is no longer optional for most businesses. States require e-filing and electronic remittance once tax owed exceeds roughly $500 to $1,000 per period, though the exact threshold varies. In practice, nearly every bookkeeper will file through the state's online portal or through a third-party engine, because paper filing is slower, more error-prone, and often not even permitted for businesses with consistent liability.

Amended Returns and the Three-Year Refund Window

Mistakes happen — a client over-collects sales tax, a bookkeeper misclassifies a taxable product as exempt, or a return is simply keyed in backwards. The correction process is an amended return, and the statute of limitations for claiming a refund is typically three years from the date the return was due or filed, whichever is later.

If a client under-collected sales tax, the business is still liable for the tax, and an amended return is required to report it. This is a painful position because the tax was never collected from the customer, but the state does not care. The business owes the tax, plus interest and potentially penalties. Bookkeepers should advise clients to treat under-collection as a cash flow emergency, not a deferral opportunity.

If the client over-collected, the refund path is cleaner but not automatic. The business must file an amended return, and many states require proof that the over-collected tax was remitted to the state in the first place or returned to customers. The three-year window is unforgiving — a bookkeeper who discovers an over-collection on a return from four years ago has likely lost the right to recover it.

Penalties: Failure to File vs. Failure to Pay (A Two-Column Reality)

Penalty structures differ by state, but a common framework exists. Failure to file carries a 5% per month penalty on the tax due, capped at 25%. Failure to pay carries a 1% per month penalty, capped at 25%. Both can run simultaneously for the same period, and interest compounds separately.

The table below compares the two penalty tracks for a hypothetical $10,000 tax liability that is three months late. This is the exact scenario bookkeepers face when a client misses a filing entirely and the state sends a notice.

The asymmetry is stark. A bookkeeper who files on time but pays late faces a far smaller penalty than one who files late — which is why the two-step workflow matters. Always prioritize the filing itself, then the payment, and never let a filing become delinquent while waiting for the client to fund the tax account.

Bookkeeper Liability, Power of Attorney, and Unauthorized Practice Risks

A question every bookkeeper should be able to answer: who is legally liable if I file late or make an error? The answer is typically the client, because the return is filed under the client's name and tax ID. However, the bookkeeper can face professional liability, malpractice exposure, and in some states, penalties for unauthorized practice if they act without proper authority.

Some states require anyone who handles sales tax filings professionally to register as a tax preparer or to hold a valid power of attorney on file. Filing a return under your own practitioner credentials when you are not authorized is a compliance violation that can result in fines, suspension, or legal action. Before filing on behalf of a new client, confirm the state's requirements for third-party filers and have the client execute the appropriate authorization documents.

Even with a power of attorney, the smartest bookkeepers add a hold-harmless clause to their engagement letter, clearly stating that while the firm prepares and files returns, the client remains ultimately responsible for the accuracy of the underlying data. This does not eliminate risk, but it sets expectations and protects the practice if a client conceals sales.

In-House Filing vs. Third-Party Tax Engines: A Decision Framework

Should you file directly through state portals or use TaxJar, Avalara, or similar automation? There is no universally correct answer, but a practical decision framework exists based on three variables: number of states, return frequency, and average liability.

• One or two states, simple products: File directly through the state portals. It costs nothing beyond your time, and it gives you direct visibility into due dates, payment posting, and audit trail. This is the right approach for most service businesses and simple e-commerce sellers.
• Three to five states, growing sales: A tax engine becomes cost-effective, especially if the client sells through multiple channels. The automation eliminates the manual slog of logging into five different portals, but you must still verify that payments post on time.
• Six or more states: Use a third-party engine as the source of truth, but run a monthly reconciliation report comparing the engine's remittances against each state's portal. The engine is a tool, not a defense against state errors.

Third-party engines typically charge $19 to $100 per month per state, which is a fraction of the cost of a penalty. However, the engine is only as good as the product taxability rules you configure. A bookkeeper who does not review exemption certificates and product codes is automating their own errors at scale.

The Two-Step Internal Workflow Every Bookkeeper Should Adopt

To avoid the filing-versus-remitting trap, install a two-step workflow in your practice management system. Step one: the return is prepared and filed by the due date, with the filing confirmation saved to the client's permanent file. Step two: payment is scheduled separately, ideally one to two days before the due date, with a verified payment confirmation.

Do not rely on your calendar alone. Build a monthly compliance checklist that includes:

1. Review each state's assigned filing frequency for every active client.
2. Reconcile taxable sales against the accounting system before touching the return.
3. Separate marketplace sales from direct sales when the client sells on platforms.
4. File the return first — even if the client has not yet funded the payment.
5. Schedule the payment for one to two days before the due date to absorb processing lags.
6. Save confirmation numbers for both the filing and the payment.
7. Flag any state notice immediately and respond within the deadline stated in the notice.

This workflow appears obvious, but it is rarely documented. The bookkeepers who operate this way are the ones who never see penalties, never field panicked calls from clients, and never appear in an audit trail as the source of a missed deadline.

Sales Tax and the Reconciliation Gap: Matching Returns to the Ledger

Sales tax compliance does not end at the state's portal. The return you file must reconcile to the general ledger, or your client's financial statements will carry a mismatch that surfaces during any review. A common error is recording sales tax collected as revenue, which inflates top-line results and creates a false profit picture.

In your client's accounting system, sales tax collected should be recorded as a liability — typically a "Sales Tax Payable" account — and cleared when the payment is made. The balance in that account at month-end should match the amount reported on the next return. If it does not, investigate before filing. This reconciliation habit catches errors that would otherwise become amended returns, penalty triggers, or audit findings.

The same discipline applies to sales tax included in deposits from marketplaces. Amazon and Shopify payments arrive net of tax collected, which means