Why doesn't an uncommitted Avalara transaction show up on my sales tax return?

Committed is a status, not a synonym for "created"

Creating a transaction in AvaTax and having it count toward your tax liability are two separate steps. Avalara's own developer documentation describes commit status as "a simple flag that determines if a transaction should appear on your compliance reports for remittance to the Department of Revenue at the end of your filing period." A transaction created without that flag set defaults to uncommitted — it exists in AvaTax, it can be retrieved and calculated against, but Avalara's reportable-transactions documentation is explicit that uncommitted transactions "are considered provisional — they are subject to review and will generally not appear in reports or liability calculations."

Why this is easy to miss

Nothing about an uncommitted transaction looks broken from inside AvaTax. It has a status of Saved or Posted, it calculated tax correctly, and it's fully visible if you look it up directly by document code. The gap only shows up when someone reconciles what accounting believes was sold in a period against what AvaTax actually reports — and by design, that reconciliation usually happens close to the filing deadline, which is the worst time to discover a batch of real transactions was silently excluded.

How transactions end up stuck uncommitted

Three patterns account for most cases. First, an integration calls CreateTransaction without ever setting commit to true, and nothing downstream calls CommitTransaction either — the integration was built to calculate tax, not to finalize it, and nobody added the second step. Second, a batch commit job that's supposed to run on a schedule fails silently for a subset of transactions — a validation error on one record can leave others in the same batch uncommitted without an obvious alert. Third, someone manually reviewing transactions in the AvaTax UI intends to commit a batch after checking it, and the review step gets deferred past the point it should have, leaving transactions in limbo through the filing deadline.

How to find and fix it before a filing deadline

Query for transactions in the period with a status other than committed, rather than trusting that everything created was committed. If you find real, finalized sales sitting uncommitted, the fix is to commit them explicitly — either through the CommitTransaction API or manually — before the filing period's reconciliation runs. Avalara's documentation also notes a hard constraint worth planning around: committed document codes lock on the first day of the following calendar month, so a transaction that should have been committed for last month's filing needs to be caught and corrected before that window closes, not after.