One ZIP. Two jurisdiction results.
Does your evaluation preserve the delivery address and the jurisdiction code?
8.25% and 7.25% in ZIP 60084Inspect the execution →Sales Tax Engine + Sales Tax ComplianceYour tax software looks good in a demo.
Your tax software looks good in a demo.
Test the difficult transactions.
Start with inspectable public examples. See the result, the supporting evidence and the unresolved questions. Then evaluate the cases that matter to your business.
The public test pack
What would your system do?
These are bounded reference executions, not a vendor ranking or an all-state accuracy benchmark. Each case names the component exercised, configuration, exact inputs, outputs and limitations.
A missing product should be a question.
What happens when the integration cannot identify the product?
product_identity_required · 422Inspect the execution →The certificate must cover the date.
Does exemption evidence match this customer, state and transaction date?
$0.00 with effective evidence · expired request refusedInspect the execution →Follow the credit back to the sale.
Does a partial refund reconcile to the committed transaction?
$25.00 refund · $1.33 tax reversalInspect the execution →A retry should not become a second sale.
How does the integration distinguish a retry from a changed transaction?
One sale retained · conflicting retry refusedInspect the execution →Tax amount and payment responsibility are different.
Can a period include direct, facilitated and unresolved activity without mixing their liabilities?
$5.30 seller · $10.60 facilitator · $2.65 unresolvedInspect the execution →Beyond the tax quote
Can you explain the return?
Click a field in a generated Virginia ST-1 sample and trace it to its source rows. Inspect the exception that prevents a package from being generated.
Inspect the compliance package →Your next decision
Make switching measurable.
Use the discrepancy worksheet and neutral assistant instructions to compare equivalent inputs. Then evaluate five of your own difficult transactions.
Build your evaluation →Run the public examples again.
No account or key needed. This runs the address lookup and package writer afresh with the disclosed inputs. It does not run your own transactions or submit a return.
Evidence you can inspect. Limits you can see.
The business data is synthetic. The address example uses a small official-derived historical Illinois sample. The other executions use an isolated sandbox database, disclosed inputs and the same service implementations used by the application. No customer records, filings, payments or competitor credentials were used.
The pack distinguishes local component execution from hosted API execution. The optional replay script records your own sandbox results, including failures; it does not recreate the private reference database or certify a provider. Confirm supported coverage and effective dates before evaluating a real workflow.
Sales Tax Engine · Sales Tax Compliance · API coverage contract · Current pricing