The certificate must cover the date.
Does exemption evidence match this customer, state and transaction date?
$0.00 with effective evidence · expired request refused
The fixture customer was marked exempt and linked to an active synthetic certificate. The calculation returned .00 on its last effective date. The next-day request returned exemption_certificate_not_found (422).
What this execution establishes
The effective-to date is a synthetic record boundary, not a general Virginia certificate expiration rule. Real certificates require authorized review and correct scope.
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: Virginia Tax: exemption certificates. Source review: 2026-10-21. Transaction date: 2026-07-26.
Make it your test
Bring a certificate with a date or scope question, through the private workflow.
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