One ZIP. Two jurisdiction results.
Does your evaluation preserve the delivery address and the jurisdiction code?
8.25% and 7.25% in ZIP 60084
The actual Illinois address-index resolver returned location codes 04900278 and 04950006 for two rows from the July 2026 official-derived sample.
What this execution establishes
Historical destination-rate lookup over a nine-row subset. Live geocoding, full-file coverage and a complete tax determination were not tested.
Executed using the published version’s source hashes. The Virginia lifecycle cases use a disclosed 5.3% snapshot and fixture address handling; they do not claim a live geocoder or current production-rate test.
Reproduce and review
Primary source: Illinois Department of Revenue: address-specific rate files. Source review: 2026-10-21. Transaction date: 2026-07-26.
Make it your test
Bring two delivery addresses near a tax boundary and document the sourcing rule.
Evaluate this in my workflow →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