Sales tax reconciliation software should help a reviewer explain a period’s numbers. A calculation total alone cannot show whether every source transaction arrived, whether collected tax agrees with the records, or whether a return adjustment has support. Evaluate software by asking it to reconcile one entity and one closed period you understand.
Define the records and the expected answers
Prepare source exports, transaction identifiers, the relevant accounting totals, credit or refund records, exemption support, and the period’s workpapers. Remove unnecessary personal information before sharing a sample. Record which entities, locations, channels, time zones, and transaction dates the sample includes. Document the treatment your reviewer expects for each known exception.
Build an input control sheet with row counts, gross amounts, tax collected, credits, and rejected or excluded rows. Reconcile each source separately before comparing combined totals. A connector label or successful upload does not establish that the whole period was imported.
Reconcile three different amounts
**Source tax collected** is what the transaction records report. **Calculated tax** is the engine’s result under the facts and rules used for the calculation. **Return amounts** reflect the approved period composition and any supported adjustments. Keep these visible separately so the reviewer can understand differences.
Here is an arithmetic example, not a tax rule or customer result: a source export reports $10,000 of tax collected, while imported records contain $9,700. The first question is why $300 is missing from the import. Do not hide that gap by adding a manual adjustment to the return. Identify the omitted rows, date filter, failed import, or other cause and preserve the explanation.
After source completeness is established, investigate calculation differences using the actual transaction date, location, product treatment, and exemption evidence. A difference is a review item; it is not automatically an amount to collect, refund, or remit.
Test the exceptions that matter at close
Include a duplicate import, a credit tied to an earlier sale, a transaction outside the period, an exempt sale without its expected document, and an unresolved location. Where marketplace activity is relevant, show how the software records the applicable facts and prevents an assumed treatment from becoming an unexplained adjustment.
Ask the vendor to demonstrate what happens to each case. Can the reviewer trace an exception to its source? Can unresolved items be assigned and kept visible? What prevents a reimport from silently changing an already-reviewed result? Record which controls were demonstrated and which still require confirmation.
Inspect the close package
A useful acceptance package should let your team move from a summarized amount back to the underlying records. Request source totals, import exceptions, reconciliation differences, adjustment explanations, reviewer decisions, and the proposed return workpaper. Open an actual export during the evaluation and check that identifiers survive outside the application.
Recordkeeping obligations depend on the jurisdiction. California’s guidance identifies original transaction documents, accounting records, and workpapers used to prepare returns as relevant records. Use that as one jurisdiction-specific reason to test traceability; do not assume a dashboard screenshot alone satisfies your record requirements. CDTFA Publication 116: Types of Records.
Agree on acceptance before choosing a vendor
Write down what must reconcile, which exceptions require a decision, who can approve the period, and which output will be used for filing. Keep preparation, approval, submission, and payment as separate actions. A prepared workpaper does not prove that a jurisdiction accepted a return or received payment.
Use Prophit.ai’s sales tax filing software overview to scope period-close and filing-support needs. If your team is replacing an existing process, the switching sales tax software guide helps frame the transition. Request the same one-period demonstration from each vendor, then compare costs for that scope with the software cost calculator.
*Originally published 2026-07-14. Substantially rewritten and editorially reviewed September 8, 2026. The evaluation checklist is our recommendation; jurisdiction examples link to the responsible tax authority.*