# Monitoring {% embed url="" %} Walkthrough of the Monitoring feature in Sphere {% endembed %} ## Overview Our Monitoring feature extracts data from both your billing and HRIS provider to give you a view of where you are exposed around the world from an indirect tax compliance perspective. We sync your data on a daily basis so that your exposure is kept up to date vs having to pay for expensive, periodic nexus studies from tax advisors / accountants. We explain below the key items and concepts that constitute the Monitoring feature below. ## Regions A region is anywhere you register and file for indirect tax: :flag\_us: **United States** * Each individual state is a region * Home rule states (like CO, AZ, AK, LA, AL) count as one region each as we file via a centralized system * The only state which requires multiple registrations is Illinois as Chicago has a seperate form of indirect tax (specific to software) called the PPLTT which requires its own registration / filing. :flag\_ca: **Canada** * GST / HST (federal level tax) = 1 region * PST (provincial taxes in British Columbia, Manitoba, Saskatchewan, Quebec) = each count as 1 region as they require seperate registrations / filings. :flag\_eu: **Europe** = 1 region as we file via the One Stop Shop scheme (which allows us to report all EU transactions and tax via 1 member state) :earth\_americas: **Rest of World** = typically each country is 1 region (although there are exceptions) *** ## Nexus An entity is generally subject to a region’s sales and use tax requirements if that entity has ‘*nexus*’ with the jurisdiction. Generally, nexus is the minimum necessary connection that an entity has with a region that allows that region to impose a tax or, in the case of sales and use tax, a collection obligation on that entity (nexus is largely equivalent to the VAT concept of “permanent establishment”). Nexus is generally obtained, or triggered, by either a physical in-state presence or an economic presence. ### Physical presence A physical presence can be triggered by several factors, including the presence of property or payroll in a region. Property, for example, can be considered as maintaining an office, warehouse, distribution center, or a manufacturing plant, whether leased or owned. Property can also be considered as maintaining, using, or storing fixed assets or inventory. Payroll can be considered as maintaining employees or independent contractors, whether full-time, part-time, or temporarily in the region. Sphere integrates with your HRIS provider to track your FTEs and contractors around the world to see where you have physical presence. This is denoted in the *Physical Presence* column in the Monitoring feature.

### Economic presence An economic presence can be triggered by maintaining a certain sales volume within a region, based on customer location. This sales volume is typically measured by either a gross sales volume (measured in local curency) or a transactional sales volume (measured by count of sales transactions), on an annual basis. Though it can vary greatly from region to region, the typical threshold for an economic presence in the US is $100,000 or 100 sales transactions over a calendar year period. There are some regions that maintain a higher gross sales volume threshold, maintain no sales transaction threshold, or measure their determination period on a rolling annual basis. Sphere keeps track of all of these economic thresholds globally and integrates with your various billing systems to track where you are approaching or have breached these thresholds. If a region has an *Approaching Exposure* status (see definitions [below](#monitoring-statuses)), we will show you your progress towards the threshold via the *Nexus Tracker* column. Note that *Volume ($)* and *Volume (#)* denotes volume over a specific determination period that is specific to the region (this can be the prior calendar year, rolling last twelve months etc).

Economic nexus calculation and tracking in Monitoring

### Tax liabilities If your product is taxable in a region and you breach either economic or physical nexus, you will start accumulating a tax liability from the day you first breached nexus. Sphere provides you with the exact date where you breach nexus and calculates the tax liability you owe from that date (via the *Nexus Triggered Date* and *Estimated Tax Liability* column, respectively).

{% hint style="info" %} Note that the *Estimated Tax Liability* column **does not include** the following additional costs: * Late filing penalties - these can be either a % of the tax liability or a flat fee per filing * Interest on tax liability - usually % applied to the tax liability which compounds over time {% endhint %} ## Monitoring statuses Each region is assigned a Monitoring status based on your exposure in that region:

Status	Explanation
	No sales in the region
	You have breached economic or physical nexus Your products are NOT taxable in the region Technically you are meant to register and file $0 returns in these regions but a lot of businesses opt not to as there is NO tax liability associated with the region
	You are approaching the nexus threshold (we will provide a progress bar that shows how close you are to breaching the threshold) Your products ARE taxable in the region We suggest registering once you pass 60% exposure in these regions OR you know you will hire someone in the region in the next month
	You have breached the either economic or physical nexus and are accumulating a tax liability Your products ARE taxable in the region We suggest registering in these regions ASAP as you will both need to pay the liability + associated penalties and interest
	You have registered in the region but you have NOT enabled auto filing
	You have registered in the region and HAVE enable auto filing

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.getsphere.com/features/monitoring.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.