Skip to main content
Nine of the 23 enacted states have more than one rule, and the rules differ by who is paying whom. The engine represents each rule as a tier of the state record, and the transaction’s transaction_type selects the tier.

The vocabulary

Send one of these in transaction_type. The default is retail. A type that no tier covers, and that the base rule’s accepted_transaction_types does not list, is out_of_scope for that rule and falls through to the next level.

How a tier resolves

A tier matches when its transaction_type equals the request’s type or its transaction_types list includes it. The first matching tier in the record wins. A tier carries its own method, obligation, citation, effective date, sunset, activation conditions and small-total rule, so two tiers of one state can differ on every one of those.

The tiered states

Florida also carries a FL-CH538 tier for secondary metals recyclers. The remaining enacted states carry one rule; most cover retail and government_retail, Hawaii, Maryland and Nebraska add wages, and Alabama covers retail only because it excludes payments to governmental entities.

What the response shows

The tier id and citation are also sealed in statutory_basis.
If a POS cannot distinguish a tax payment from a retail sale, it should send retail and say so in its integration notes. Sending the wrong type produces a sealed record that cites the wrong section. The engine cannot tell the difference from the amounts.