Documentation Index
Fetch the complete documentation index at: https://docs.commenda.io/llms.txt
Use this file to discover all available pages before exploring further.
Understanding registration thresholds
A registration threshold is the point at which a seller must register to collect and remit indirect tax in a given jurisdiction. Historically, this obligation was based primarily on physical presence. However, following the 2018 South Dakota v. Wayfair Supreme Court decision in the US, jurisdictions can now require remote sellers to collect and remit indirect tax based on their economic activity — commonly referred to as “economic thresholds.” This concept applies globally: VAT and GST jurisdictions also set thresholds that determine when a business must register and begin collecting tax.How jurisdictions define thresholds
Each jurisdiction sets its own rules for determining when you must register, including:- Threshold amounts: Jurisdictions establish different sales and/or transaction thresholds that trigger a registration obligation. For example, one jurisdiction may have a USD 100,000 sales threshold, while another sets a EUR 10,000 threshold.
- Threshold types: Some jurisdictions consider only sales revenue, some consider only the number of transactions, and some consider both.
- Evaluation periods: The period over which economic activity is measured varies. Common periods include the previous calendar year, the current or previous calendar year, or a rolling 12-month period.
Threshold tracking
Commenda automatically tracks your progress toward registration thresholds in each jurisdiction based on the transactions you post to the/transactions endpoint.
You can use the registration threshold API endpoint to get a comprehensive overview of your threshold status across all jurisdictions, taking into account each jurisdiction’s specific rules.
Default response (US states)
By default, theGET /nexus endpoint returns US-state-level threshold data. The response contains a states array where each object represents your exposure in one US state.
The default response uses field names like
is_nexus_breached and states for backward compatibility. These fields represent registration threshold status — is_nexus_breached indicates whether you have exceeded the registration threshold in a given jurisdiction.Global response (v2=true)
Pass v2=true as a query parameter to get global jurisdiction-level threshold data. This covers US, Canada, UK, and EU jurisdictions, including support for multiple exposure rules per jurisdiction (for example, EU Union OSS, Non-Union OSS, and IOSS).
The v2 response uses a jurisdictions array instead of states, and includes additional fields such as jurisdiction_id, exposure_type, exposure_rule_id, subdivision, and currency.
Recommended registration
Each jurisdiction in the v2 response includes arecommended_registration_content_ids field: an array of content IDs that link directly to the V2 Registration API. When a threshold is breached (or approaching breach), use these IDs to discover the appropriate registration options via the Available Registrations endpoint.
Key differences from the default response
| Field | Default | V2 (v2=true) |
|---|---|---|
| Top-level array | states | jurisdictions |
| Jurisdiction identifier | state (US state code) | jurisdiction_id, subdivision |
| Currency | Implicitly USD | Explicit currency field |
| Exposure rule metadata | Not included | exposure_type, exposure_rule_id, jurisdiction_type |
| Calculation fields | total_sales, total_transactions, etc. | included_sales, included_transactions, etc. |
| Registration recommendation | Not included | recommended_registration_content_ids |
| Supported jurisdictions | US states only | US, Canada, UK, EU (country-level and tradebloc) |