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 unresolved
The responsibility service kept the direct liability, documented facilitator remittance and unknown responsibility in separate amounts. The unresolved amount blocked the package writer in the exception replay.
What this execution establishes
Synthetic explicit responsibility facts; no real facilitator account, remittance or registration was verified.
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: marketplace facilitators and sellers. Source review: 2026-10-21. Transaction date: 2026-07-26.
Make it your test
Bring one direct sale and one marketplace statement with responsibility evidence.
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