Is SaaS Taxable in Vermont? A Developer's Guide to the 2026 Rules

Vermont SaaS Sales Tax at a Glance

Product Taxability Rules

State Registration & Economic Nexus Triggers

Which types of software does Vermont tax?

Vermont eliminates artificial tax distinctions based on delivery mechanisms. Under 32 V.S.A. § 9701(7), prewritten computer software is defined as tangible personal property regardless of whether it is downloaded, delivered on optical media, or accessed via an off-site hosted cloud infrastructure.

Business apportionment and exemption certificates in Vermont

Vermont is a full member state of the Streamlined Sales and Use Tax Agreement (SSUTA). The Streamlined Sales Tax Governing Board officially repealed the Multiple Points of Use (MPU) exemption certificate under SSUTA Section 312. As a result, Vermont does not accept an SST MPU certificate to apportion cloud software subscriptions across multi-state workforces.

Enterprise buyers that require multi-state tax apportionment must hold an official Direct Pay Permit issued under 32 V.S.A. § 9745a, shifting remittance obligations directly to the buyer.

If your customers qualify as tax-exempt entities (e.g., 501(c)(3) nonprofits or educational institutions), your billing system must collect and validate standard state exemption documentation. You can manage exemption certificates within your checkout workflows to maintain compliance.

How do you charge the correct sales tax rate for SaaS in Vermont?

Vermont assesses a baseline state sales tax rate of 6.0%. However, municipalities authorized under 24 V.S.A. § 138 levy an additional 1.0% Local Option Tax, generating a 7.0% combined rate across roughly 35 jurisdictions (including Burlington, Montpelier, Rutland, South Burlington, Stowe, and Williston).

Because Vermont municipal tax boundaries do not align with 5-digit USPS ZIP codes, ZIP-based tax lookup tables miscalculate rates on cross-border addresses. Under SSUTA destination sourcing codified at 32 V.S.A. § 9707(b), SaaS transactions must be sourced to the customer's primary address of receipt or the business address maintained in your billing records.

Engineering teams have two options for calculating that rate: call a real-time sales tax API, or manually build and maintain an internal rate engine.

Option 1: Automate calculation with the Ziptax Sales Tax API

The Ziptax Sales Tax API resolves rooftop coordinates and municipal boundaries to return the precise 6.0% or 7.0% rate in real time.

To calculate a live rate against a Vermont address, issue a GET request using the v60 endpoint:

Bash

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=149 Church St, Burlington, VT, 05401"

To verify complete payload structures, explore the REST API documentation.

When integrating the API response into your billing stack:

1. Calculate Using Combined Rates: Apply taxCombined directly to taxable line items rather than calculating municipal and state components separately to prevent penny-rounding variances.
2. Assign Product Classifications Dynamically: If your platform bundles SaaS with custom onboarding or data migration, do not rely on static category flags. You can search for the correct product code and review Taxability Information Codes (TICs) to automate invoice-level tax logic.
3. Persist Transaction Geocodes: Store the returned jurisdiction identifier, tax rate, and transaction timestamp in your database to ensure audit defense trails remain intact if local option boundaries shift.
4. Automate End-to-End Compliance: To automate threshold monitoring, tax filing, and remittance after your sales scale, you can set up merchant management via TaxCloud integration.

Option 2: Build and maintain an internal tax billing engine in-house

If you engineer an internal calculation engine for Vermont, your architecture must support four statutory requirements:

1. Rooftop Geocoding vs. ZIP Codes: A single 5-digit ZIP code frequently covers both a Local Option Tax town and an unincorporated non-taxing district. Your database must map polygon coordinates or exact parcel addresses to determine whether the 1.0% local levy applies.
2. Dynamic Ordinance Tracking: Municipalities adopt or repeal the 1.0% local tax semi-annually (typically effective January 1 or July 1). An unmonitored municipal database creates under- and over-collection liabilities.
3. Bundling Engine Rule Logic: In accordance with 32 V.S.A. § 9701(33), your checkout logic must require separate line items for implementation, consulting, and maintenance. If your system outputs single-sum invoices for hybrid contracts, the logic must classify the entire amount as taxable at 6.0% or 7.0%.
4. Continuous Rolling 12-Month Accumulator: Nexus tracking must compute gross sales and total transactions on a trailing 365-day rolling loop, rather than resetting on January 1 of each calendar year.

Five things to watch out for if you choose this path:

1. Assuming SaaS is still exempt. Vermont exempted remotely accessed software from 2015 through June 30, 2024. If any part of your system, a cached taxability flag, a hardcoded rule, a stale integration, still reflects that older rule, it's been wrong since July 1, 2024.
2. ZIP-based shortcuts for the Local Option Tax. The 1% Local Option Tax applies town by town, and Vermont town boundaries don't line up cleanly with ZIP code boundaries. A flat ZIP lookup can put a customer in the wrong bucket in either direction.
3. Treating the Local Option Tax town list as fixed. The list has changed multiple times in the past two years, including at least one town rescinding the tax, with more towns scheduled to add it. Build a refresh process, not a one-time import.
4. Assuming only tangible-personal-property sales count toward the nexus threshold. Several other states exclude pure SaaS revenue from their economic nexus threshold because it isn't tangible personal property there. Vermont's 2024 law makes software, including remotely accessed SaaS, tangible personal property by definition, and its guidance counts electronically transferred products toward the all-sales threshold. A pure-SaaS seller can likely cross Vermont's $100,000/200-transaction threshold on subscription revenue alone.
5. Stopping collection once a slow period puts you back under the threshold. Vermont's own guidance states that once you cross the threshold, you must collect and remit on all sales going forward, including sales below the threshold. Crossing it isn't a one-time check you can undo.

When does a SaaS business have to collect sales tax in Vermont?

Tax collection obligations are established through physical presence or economic nexus. Your compliance workflow should track these two operational rules for Vermont specifically:

Rule 1: Monitor registration triggers (nexus)

A SaaS business must register with the Vermont Department of Taxes before collecting tax. You have collection obligations if you meet either condition:

• Physical Presence Nexus: Maintaining an office, co-working space, distribution point, owned servers, or remote employees residing in Vermont.
• Economic Nexus: You can check economic nexus thresholds to verify status. Under 32 V.S.A. § 9701(9)(F), an out-of-state vendor is an obligated retailer if, during the preceding 12-month period, it had:

• Gross sales exceeding $100,000 into Vermont; OR
• 200 or more individual retail sales transactions delivered into Vermont; AND
• Regularly, systematically, or seasonally solicited sales in the state.

Because SaaS subscriptions are statutory sales of tangible personal property under 32 V.S.A. § 9701(7), subscription charges and volume count directly toward both the $100,000 and 200-transaction limits.

Rule 2: Apply continuous collection logic

• Immediate Collection Mandate: Because Vermont's SaaS taxability rule is already in effect and not scheduled to change, there's no future-state logic to build toward. Once you have nexus, your billing system needs to calculate, collect, and remit tax on SaaS subscriptions and all other prewritten software sales starting immediately, using Vermont's 6% state rate plus the 1% Local Option Tax for any of the participating towns.
• Irrevocable Collection Obligation: Under Vermont Department of Taxes enforcement rules, once you cross an economic nexus threshold, you remain liable for tax collection on all subsequent sales. You cannot terminate collection simply because transaction counts dip below 200 during a subsequent quarter.

Where Ziptax helps

Engineering teams building subscription billing, marketplace platforms, or multi-tenant ERPs do not need bloated enterprise tax software to maintain compliance.

Ziptax provides a fast, developer-first sales tax infrastructure:

• Rooftop Accuracy: Resolves rates across 12,000+ US. tax jurisdictions using coordinate-level precision, isolating Vermont’s town-by-town Local Option Tax boundaries.
• Sub-Millisecond Response Times: Built for high-throughput billing systems, recurring checkout workflows, and modern web application stacks.
• Usage-Based Pricing: Simple, transparent pricing that scales with your API call volume without enterprise sales lock-ins.
• Automated Remittance Path: When transaction volume warrants hands-off tax returns, link your account to TaxCloud for automated monthly filings and state remittances.

Get Vermont SaaS tax rates from an API

Address-level rates for every Vermont jurisdiction, plus the rest of the US, Canada, and select other markets. Free starter plan, then view Ziptax pricing for usage-based rates as you scale.

Frequently Asked Questions

Does a single SaaS sale require immediate tax registration in Vermont?

No. Out-of-state SaaS vendors with no physical presence establish tax collection obligations only after exceeding $100,000 in gross revenue or 200 retail transactions in Vermont over the trailing 12 months. However, because Vermont defines SaaS as tangible personal property under 32 V.S.A. § 9701(7), recurring subscription invoices count toward both threshold metrics.

Does Vermont tax downloaded software differently than cloud-hosted SaaS?

No. Prior to July 1, 2024, Vermont taxed downloaded prewritten software while exempting cloud-hosted SaaS. 2024 Act 183 eliminated that delivery distinction. All prewritten software—whether accessed remotely via cloud infrastructure, downloaded to local drives, or delivered on physical media—is taxed uniformly at the 6.0% state rate plus applicable local option taxes.

Can an address be safely taxed based on its 5-digit ZIP code?

No. Vermont's 1.0% Local Option Tax is levied at the municipal boundary level under 24 V.S.A. § 138. Several ZIP codes in Vermont span multiple municipalities, containing areas subject to a 6.0% combined rate and areas subject to a 7.0% combined rate. Charging sales tax based on ZIP codes alone results in systematic tax errors.

Are custom software development and onboarding services taxable when sold with SaaS?

Custom software developed exclusively for a single client and professional services (such as setup, consulting, and training) are exempt from Vermont sales tax. However, under 32 V.S.A. § 9701(33), if taxable SaaS subscriptions and exempt professional services are bundled into a single invoice charge without itemization, the entire amount becomes taxable. Professional services must be itemized at commercially reasonable market rates to maintain their tax-exempt status.

Sources

1. Vermont General Assembly: 32 V.S.A. § 9701 - Sales and Use Tax Definitions
2. Vermont General Assembly: 2024 Act 183 (H.887) Enacted Statutory Text
3. Vermont Department of Taxes: Prewritten Computer Software Guidance
4. Vermont General Assembly: 32 V.S.A. § 9707 - General Sourcing Rules
5. Vermont General Assembly: 24 V.S.A. § 138 - Local Option Tax Authorization
6. Vermont Department of Taxes: Remote Sellers and Marketplace Facilitators (Wayfair) Guidance
7. Vermont Department of Taxes: Municipal Local Option Tax Overview and Listings
8. Streamlined Sales Tax Governing Board: Vermont State Membership Directory