Anrok hard-codes city tax rules
Michelle Valentine, co-founder and CEO of Anrok, on the modularization of the SaaS finance stack
This reveals that Anrok wins by hard coding software tax edge cases into the product, instead of asking finance teams to model them manually. In practice, that means a SaaS invoice is not treated like a generic sale. The system tracks product type, buyer type, billing changes, and city level quirks like Chicago software rules, then applies the right tax automatically inside the billing workflow.
-
Home rule cities matter because local software taxability can diverge from the state. Anrok’s product is built to calculate those exceptions in real time on each invoice, while generalist systems often require manual rule setup for software taxability, subscription scenarios, and city specific treatment.
-
That specialization fits how SaaS billing actually works. Software invoices can change with seat counts, usage, refunds, and true ups, so tax has to update as the invoice changes. A retail oriented system built around fixed product sales has a harder time handling those moving parts cleanly.
-
The broader pattern is vertical tax software replacing bundled or legacy tools once a company gets more complex. Stripe Tax works best when all revenue stays inside Stripe. Avalara covers many industries, but software companies often need more configuration. That creates room for a SaaS native tax engine.
Going forward, the advantage will compound as more software and digital services become taxable across more jurisdictions. The vendors that own the underlying data model for SaaS billing and local tax logic will be able to expand from US sales tax into global VAT, GST, and hybrid software plus hardware workflows without forcing customers back into manual configuration.