Computer Software & SaaS · Michigan

Michigan Computer, Software, and SaaS Tax Guide

ByGerald J. Donnini II, Esq.·Tax Attorney

Table of Contents

  • Introduction
  • Nexus Considerations
  • General Rules and Compliance Considerations
  • Specific Exemptions
  • Sourcing Rules
  • Audit Considerations
  • Voluntary Disclosure Agreements (VDAs)
  • Conclusion
  • References & Resources

1. Introduction

For software companies, SaaS providers, and technology firms conducting business in Michigan, the state's sales and use tax rules present unique challenges. Unlike some states that treat digital products and cloud-based services uniformly, Michigan distinguishes between prewritten (canned) software, custom software, and various technology services based on their method of delivery and level of customization. Michigan's tax treatment of software and technology-related services depends on multiple factors, including whether software is prewritten or custom, delivered on tangible media or electronically, and whether the hardware qualifies for manufacturing or industrial processing exemptions.

Purpose of This Guide

This guide is designed to help businesses navigate Michigan's sales and use tax rules related to software and technology services. It focuses on:

  • Nexus Considerations: Understanding when businesses must register and collect Michigan sales tax due to physical or economic presence.
  • Taxability of Software & Services: Clarifying the tax treatment of prewritten vs. custom software, cloud computing services, and related technology offerings.
  • Sourcing Rules: Determining how and where transactions are taxed based on customer location and method of software delivery.
  • Audit Considerations: Identifying common tax audit triggers and best practices for compliance.
  • Voluntary Disclosure Agreements (VDAs): Explaining the process for businesses to rectify past noncompliance while mitigating penalties and limiting back-tax liability.

Why This Matters for Technology Companies

Michigan's sales tax laws impact software companies, SaaS providers, and technology firms in multiple ways:

  • Complex Sales Tax Obligations: Businesses that sell software or related services to Michigan customers have specific collection and remittance responsibilities that vary based on product classification. Michigan's 6% sales tax applies to all prewritten software regardless of delivery method, creating broader tax obligations than states that exempt electronically delivered software.
  • Hardware Exemption Complexities: Michigan provides various exemptions for computer hardware used in manufacturing or industrial processing, but these require precise documentation and proper application.
  • Cloud Computing & SaaS Uncertainty: Michigan's Department of Treasury has provided some guidance on SaaS taxation, but the area continues to evolve, creating compliance challenges for cloud service providers.

Compliance Risks: Failure to correctly assess and collect sales tax can result in significant penalties, interest, and extended audit exposure, particularly given Michigan's taxation of prewritten software regardless of delivery method.

This guide will walk through Michigan's specific sales tax rules governing software, SaaS, and technology-related services while referencing applicable statutes, administrative rules, and Michigan Department of Treasury guidance. Throughout the guide, official Michigan Department of Treasury sources will be linked for further reference.

2. Nexus Considerations

Understanding Nexus and Its Impact on Sales Tax Obligations

Nexus is a legal standard that determines whether a business has a sufficient connection to Michigan to require the collection and remittance of sales tax. The determination of nexus is critical because businesses with nexus must comply with Michigan's sales tax regulations, including registration, collection, and remittance. If a business fails to recognize or act upon its nexus obligations, it could be exposed to audits, back taxes, interest, and penalties.

Michigan establishes nexus primarily through physical presence and economic activity. Businesses selling into Michigan must assess whether their activities create a taxable presence under existing statutes.

Physical Presence Nexus in Michigan

Physical presence nexus occurs when a business has a tangible footprint in Michigan. This includes maintaining a location, such as an office, store, warehouse, or storage facility, or employing individuals who work within the state. Additionally, businesses that hold inventory, attend trade shows, or have independent contractors conducting business in Michigan may establish nexus.

For example, a SaaS company with servers located in Michigan or a remote workforce within the state may be considered to have physical presence nexus and must register to collect sales tax. Businesses meeting physical presence nexus criteria must register with the Michigan Department of Treasury through the Michigan Treasury Online (MTO) system.

Example: A software company based in Illinois sends sales representatives to Michigan for two multi-day trade shows each year to demonstrate their products and solicit sales. Even though the company has no permanent location in Michigan, these regular in-state activities establish physical presence nexus, requiring the company to register for and collect Michigan sales tax on its taxable sales to Michigan customers.

Economic Nexus in Michigan

Michigan enforces an economic nexus standard, requiring remote sellers to collect and remit sales tax if they have more than $100,000 in annual sales or 200 or more separate transactions into Michigan. This threshold applies to the previous calendar year.

Importantly, unlike some states that only count taxable sales toward the threshold, Michigan counts all sales (both taxable and non-taxable) when determining if a seller has exceeded the economic nexus threshold. This means that even businesses selling primarily non-taxable services must carefully track their Michigan sales volume.

Example: An out-of-state software company with no physical presence in Michigan made $125,000 in sales to Michigan customers last year, including $75,000 in custom software (exempt) and $50,000 in prewritten software (taxable). Even though less than half of its sales were taxable, the company exceeds Michigan's $100,000 economic nexus threshold based on total sales and must register to collect and remit sales tax on its taxable prewritten software sales.

For more details on Michigan's economic nexus law, visit the Michigan Department of Treasury's Sales and Use Tax.

Marketplace Facilitator Rules in Michigan

Michigan has marketplace facilitator rules that require platforms such as Amazon, eBay, and Shopify to collect and remit sales tax on behalf of third-party sellers if the marketplace facilitator meets the economic nexus thresholds.

This impacts software companies that sell digital products or software through such platforms. If sales occur exclusively through a marketplace facilitator, the facilitator is responsible for tax collection, and the seller does not need to collect tax separately. However, businesses that sell both through a marketplace and independently must still determine whether they have nexus for their direct sales.

Example: A small developer sells custom software applications through their own website and also lists prewritten software plugins on a major online marketplace. For sales made through the marketplace, the marketplace facilitator collects and remits Michigan sales tax on the taxable prewritten software. For direct sales made through the developer's website, the developer must determine whether they have nexus in Michigan and collect tax accordingly.

Compliance Obligations and Registration

Businesses that establish nexus through physical presence, economic thresholds, or marketplace sales must register for sales tax collection with the Michigan Department of Treasury. Once registered, businesses are required to collect the applicable state sales tax (6%) on taxable transactions and remit these amounts to the state.

Registration can be completed online through Michigan Treasury Online (MTO) at the Michigan Department of Treasury's Business Tax Registration page.

Failure to comply with Michigan's sales tax requirements can result in back taxes, penalties, and interest. Businesses should ensure they remain updated on Michigan's evolving tax policies to avoid compliance issues.

Conclusion: Proactive Nexus Management

Understanding and managing nexus is essential for sales tax compliance in Michigan. With Michigan's economic nexus threshold of $100,000 in annual sales or 200 transactions, businesses must track their revenue and transaction volume carefully.

To ensure compliance, businesses should:

  • Regularly assess their business activities in Michigan, including direct sales, marketplace sales, employee activities, and inventory locations.
  • Register for sales tax collection if they meet physical presence or economic nexus criteria.
  • Monitor regulatory changes that could affect nexus requirements, as Michigan's guidelines have evolved over time.
  • Maintain accurate sales records, distinguishing between taxable and non-taxable transactions, to ensure proper reporting and remittance.
  • Consult tax professionals familiar with Michigan tax law to ensure compliance, especially for complex technology transactions.

By proactively managing their sales tax obligations, businesses can avoid unexpected liabilities and maintain compliance with Michigan's tax laws, which treats prewritten software as taxable regardless of delivery method—a significant difference from states that exempt electronically delivered software.

3. General Rules and Compliance Considerations

Introduction

Determining the taxability of software, cloud computing, and related technology services in Michigan requires careful analysis of how products and services are structured, delivered, and classified under state law. Unlike traditional tangible goods, digital products and software transactions can involve both taxable and non-taxable components. Michigan's tax laws provide distinct rules for computer hardware, prewritten and custom software, maintenance agreements, and various technology services.

This section provides an in-depth analysis of Michigan's tax treatment of these transactions, with examples, relevant statutes, and links to Michigan Department of Treasury resources for further clarification.

3.1 Computer Hardware

Computer hardware is generally subject to Michigan sales and use tax as tangible personal property at the 6% state rate. However, Michigan provides important exemptions for hardware used in specific business contexts, particularly manufacturing.

  • Taxable: Most computer hardware purchases, including desktop computers, laptops, servers, tablets, and peripherals are subject to Michigan's 6% sales tax when purchased for general business or personal use.
  • Exempt (Manufacturing): Michigan provides specific exemptions under MCL 205.54t, 205.54y, and 205.94o for computers used in qualified industrial processing activities, including:
  • Computers used in operating industrial processing equipment
  • Equipment used in computer-assisted manufacturing systems
  • Computer-assisted design or engineering systems integral to industrial processes
  • Computer equipment used in certain production environments

Example: Automotive Supplier Inc. purchases computer workstations for $25,000 to control automated assembly equipment in their manufacturing facility. Under Michigan's industrial processing exemption, these computers qualify for sales tax exemption because they directly control manufacturing equipment. In contrast, the same company's purchase of computers for its administrative offices would be fully taxable.

Relevant Guidance: Revenue Administrative Bulletin 2023-10

3.2 Prewritten (Canned) Software

Michigan's approach to taxing prewritten software differs from many states in that it taxes such software regardless of delivery method. Prewritten, or "canned," software refers to standardized software developed for sale to multiple customers without significant modification.

  • Taxable Regardless of Delivery: All prewritten software is subject to Michigan's 6% sales tax whether delivered on physical media (CDs, USB drives) or electronically (downloads, email delivery). Michigan specifically defines prewritten computer software as tangible personal property under MCL 205.51a(p) and 205.92b(n).
  • Separately Stated Charges: Importantly, Michigan allows an exemption for separately stated charges for modifying prewritten software. When such modifications are separately itemized on invoices, only the base software is taxable.

Example: Michigan Business Services purchases accounting software through a download for $5,000 with $2,000 in customization fees separately stated on the invoice. The $5,000 for the prewritten software is taxable (even though delivered electronically), while the $2,000 for customization is exempt if separately stated on the invoice.

Example: A Michigan retailer purchases inventory management software for $10,000. The software is delivered via email download and no physical media is provided. Despite the electronic delivery, the entire $10,000 is subject to Michigan's 6% sales tax because Michigan considers all prewritten software to be tangible personal property regardless of delivery method.

Relevant Guidance: Revenue Administrative Bulletin 2023-10

3.3 Custom Software

Custom software is software that is specifically developed and tailored for a single customer's needs. Michigan treats custom software development as a service rather than a sale of tangible personal property.

  • Non-Taxable: Custom software development, including modifications made specifically for a client, is exempt from Michigan sales tax under MCL 205.54d(g).
  • Documentation Requirements: To support custom software exemption claims during an audit, businesses should maintain detailed documentation showing that the software was specifically designed for a single customer's needs and not available to other customers without significant modification.

Example: A healthcare provider contracts with a software development firm to create a specialized patient management system tailored specifically to their unique workflows and procedures for $50,000. Since this software is developed exclusively for this customer and not offered to others, the entire transaction is exempt from Michigan sales tax as custom software.

Example: A developer creates a custom inventory tracking system specifically designed for a Michigan manufacturing company's unique production process. The $35,000 charge is exempt from Michigan sales tax as custom software, even though it performs similar functions to prewritten inventory software available on the market.

Relevant Guidance: Revenue Administrative Bulletin 2023-10

3.4 Maintenance and Support Agreements

The taxability of software and hardware maintenance agreements in Michigan depends on the structure of the contract, whether it relates to taxable or exempt software, and whether the agreement is mandatory or optional.

Hardware Maintenance Contracts:

  • Taxable: Mandatory hardware maintenance contracts bundled with hardware sales are taxable as part of the gross proceeds of the total sale.
  • Non-Taxable: Optional hardware maintenance contracts that are separately stated from hardware sales are not subject to tax. However, parts or materials used in fulfilling the optional maintenance contract are taxable.

Software Maintenance Contracts:

  • Taxable: Maintenance contracts for prewritten software that include upgrades and new releases are taxable. When a maintenance contract includes both tangible personal property (such as upgrades) and intangible support services in a lump sum, the entire amount is taxable.
  • Non-Taxable: Maintenance contracts for custom software are considered services and are not taxable. Technical support services that are separately stated are not subject to tax.
  • Mixed Contracts: If billing for a maintenance contract is separately itemized between taxable elements (upgrades, releases) and exempt elements (phone support, troubleshooting), only the taxable portion is subject to sales tax.

Example: A Michigan accounting firm purchases prewritten tax preparation software for $5,000 with an annual maintenance contract for $1,000 that includes software updates and telephone support. Since the maintenance contract is for prewritten software and includes taxable upgrades, the entire $1,000 maintenance fee is subject to Michigan sales tax.

Example: A company purchases an optional 3-year hardware maintenance contract for $3,000 for their server equipment, with the charge separately stated from the hardware purchase. The maintenance contract itself is not subject to Michigan sales tax, but any replacement parts provided under the contract would be taxable.

Relevant Guidance: Revenue Administrative Bulletin 2023-10

3.5 Cloud Computing and SaaS

Michigan's approach to taxing cloud computing has developed gradually, and while there’s clear guidance in some areas, others still lack formal rules.

Software as a Service (SaaS)

In general, SaaS is not subject to Michigan sales tax—as long as the customer doesn't download or receive any part of the software code. If users access software entirely through a web browser and there’s no local installation or transfer of code, it’s considered a non-taxable service.

Example: A Michigan retailer pays $12,000 a year for an inventory management platform accessed entirely online through a browser. Since there's no download involved, this would typically be non-taxable under current Treasury guidance.

IaaS and PaaS

For Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) models—where customers rent access to servers, storage, or development platforms—Michigan hasn’t issued specific tax guidance yet. But based on the general rule that sales tax applies to tangible personal property, these services are likely not taxable if there’s no transfer of software code or physical goods.

Think of IaaS and PaaS as renting computing power or developer tools in the cloud. As long as the service doesn’t include downloads or on-premise components, it likely falls outside Michigan’s sales tax scope—for now.

Mixed Transactions

Things get trickier when a service includes both online access and something downloadable (like a desktop app). In those cases, Michigan may treat the downloaded portion as taxable prewritten software—even if the cloud access alone wouldn’t be.

Example: A law firm subscribes to a legal research service for $20,000, which includes both browser access and a downloadable desktop app. If those pieces aren’t broken out on the invoice, Michigan may consider the entire charge taxable. If they are separately listed, only the downloadable component would be subject to tax.

Takeaways for Businesses

  • If you're offering SaaS in Michigan, make sure no code is delivered to keep it non-taxable.
  • Itemize your invoices if you're combining downloadable software with remote services.
  • Keep in mind that the rules around IaaS and PaaS are still evolving, so it’s smart to stay on top of future state guidance.

Key Reference:

  • Revenue Administrative Bulletin 2023-10 – The primary source for Michigan’s current position on software and cloud services.

3.6 Bundled Transactions

When taxable and non-taxable items are sold together as a single transaction, the taxability may depend on how charges are structured on the invoice.

  • Lump Sum Charges: If a business sells a package that includes both taxable items (such as prewritten software) and non-taxable items (such as custom services) for a lump sum, the entire amount may be subject to sales tax if the primary purpose of the transaction is the taxable component.
  • Separately Stated Charges: If the invoice separately states taxable and non-taxable components, only the taxable portion is subject to sales tax.
  • Primary Purpose Test: In some cases, Michigan may look to the "primary purpose" of a bundled transaction to determine taxability when charges are not separately stated.

Example: A Michigan company purchases a comprehensive IT solution for $50,000 that includes prewritten software ($30,000), custom modifications ($10,000), and training services ($10,000). If the invoice separates these charges, only the $30,000 for prewritten software is taxable. If billed as a single lump sum of $50,000, the entire amount may be subject to Michigan sales tax unless the taxpayer can demonstrate that the primary purpose was the non-taxable components.

Example: A technology consulting firm offers a "Digital Transformation Package" to a Michigan manufacturer for $75,000, which includes both prewritten software applications and substantial consulting services. If the invoice lists the prewritten software at $25,000 and consulting services at $50,000 as separate line items, only the $25,000 software component is subject to Michigan sales tax.

Conclusion

Understanding Michigan's tax rules on computer hardware, software, and technology services is essential for compliance. Michigan's approach differs from many states in that it taxes prewritten software regardless of delivery method, while exempting custom software as a service. Businesses should:

  • Properly classify software as prewritten or custom to determine taxability.
  • Structure invoices to separately state taxable and non-taxable components.
  • Document exempt transactions, particularly for industrial processing exemptions and custom software.
  • Review maintenance contracts to determine whether they include taxable elements.
  • Stay updated with Michigan Department of Treasury guidance on evolving digital tax policies.

For official sales tax information, visit the Michigan Department of Treasury Sales and Use Tax page.

4. Specific Exemptions

Introduction

Michigan provides various exemptions from sales tax for specific types of software, technology services, and related activities. Understanding these exemptions is crucial for businesses to properly structure transactions and avoid unnecessary tax liabilities. This section outlines key exemptions, including tax treatment for manufacturing operations, custom software, and specific technology-related services, referencing applicable Michigan statutes and rulings.

4.1 Exemption for Custom Software

Custom software developed exclusively for a single customer is exempt from Michigan sales tax under MCL 205.54d(g). Since the transaction is considered a professional service rather than a sale of tangible personal property, no tax is imposed on the charges associated with custom software development.

For software to qualify as "custom," it must be:

  • Originally designed for the exclusive use of a specific purchaser
  • Created to address the unique needs of that purchaser
  • Not previously created, prepared, or used by the seller for another purchaser

Example: A Michigan healthcare provider hires a software developer to create a tailored patient management system for its specific workflows, regulatory requirements, and integration with proprietary medical devices. The developer designs the software from scratch based on detailed specifications provided by the healthcare provider. Since the software is uniquely designed for this customer, the entire $85,000 development fee is exempt from Michigan sales tax.

Real-World Application: To support the custom software exemption during an audit, businesses should maintain documentation showing:

  • Requirements specifications unique to the customer
  • Design documents specific to the customer's needs
  • Contracts explicitly stating the custom nature of the software
  • Evidence that the software was not previously developed for or sold to other customers

Relevant Statute: Michigan Compiled Laws Section 205.54d(g)

4.2 Manufacturing and Industrial Processing Exemptions

Michigan provides comprehensive sales tax exemptions for computers and equipment used in qualified manufacturing and industrial processing operations under MCL 205.54t and 205.94o. These exemptions can be significant for technology companies serving the manufacturing sector.

The industrial processing exemption applies to:

  • Computers used in operating industrial processing equipment
  • Equipment used in computer-assisted manufacturing systems
  • Equipment used in computer-assisted design or engineering systems integral to industrial processes
  • Computer-integrated industrial processing systems
  • Computer equipment used in production control

Example: Automotive Parts Manufacturing Co. implements a new computer-integrated production system costing $500,000, which includes networked computers that control automated assembly equipment, monitor quality control systems, and manage production scheduling. Since these computers are used directly in industrial processing activities, the entire purchase qualifies for Michigan's industrial processing exemption and is exempt from sales tax.

Example: A manufacturer purchases specialized computer equipment and software for $250,000 to operate CNC machines on its production floor. Both the computers and the software controlling the machines qualify for the industrial processing exemption, even though the software is prewritten, because it is used directly in an industrial processing function.

Documentation Requirements: To claim this exemption, purchasers typically need to provide:

  • A completed Michigan Form 3372 (Michigan Sales and Use Tax Certificate of Exemption)
  • Documentation showing how the computer equipment is used in qualified industrial processing activities
  • Records demonstrating the percentage of exempt use if equipment has mixed exempt and taxable uses

Relevant Statute: Michigan Compiled Laws Sections 205.54t and 205.94o

4.3 Exemption for Software Development Tools

Michigan provides a specific exemption under MCL 205.54t for equipment used in the production of computer software that is offered for general sale to the public or customized for specific users.

  • Scope of Exemption: The exemption applies to equipment used to develop software that is either:
  • Offered for general sale to the public, or
  • Modified or adapted to users' needs by the seller, if the software is available from a seller of software on an as-is basis or as an end product without modification

Example: Software Development Inc., a Michigan-based company, purchases $100,000 worth of high-performance computers, servers, and specialized equipment to develop commercial software applications that will be sold to the general public. This equipment qualifies for the exemption and is not subject to Michigan sales tax because it is used directly in the production of software offered for general sale.

Example: A game development studio invests $75,000 in specialized computers, graphics cards, and development equipment to create video games for commercial release. Since this equipment is used to produce software offered for general sale to the public, it qualifies for the exemption under MCL 205.54t.

Relevant Statute: Michigan Compiled Laws Section 205.54t

4.4 Exemption for Technical Support Services

Michigan does not impose sales tax on technical support services when these services are separately stated on an invoice or billing statement.

  • Non-Taxable: Specific, separately stated charges for technical support, troubleshooting, or help desk services are exempt from sales tax.
  • Documentation Requirements: To ensure this exemption is maintained, invoices should clearly separate technical support services from any taxable software or hardware components.

Example: A Michigan business subscribes to an enterprise resource planning (ERP) system and pays $10,000 for the prewritten software license (taxable) and $5,000 for technical support services (non-taxable). By separately stating these charges on the invoice, the company only pays sales tax on the $10,000 software license, while the support services remain exempt.

Example: A software company offers a technical support package that includes 24/7 phone support, troubleshooting assistance, and training for customers using their prewritten software. When billed separately from the software, these support services are exempt from Michigan sales tax.

Relevant Guidance: Revenue Administrative Bulletin 2023-10

4.5 Exemption for Separately Stated Software Modifications

Michigan provides an exemption under MCL 205.54d(f) and 205.94a(c) for charges related to adapting or modifying prewritten software to meet a customer's specific needs, as long as these charges are separately stated on the invoice.

  • Non-Taxable: Separately stated charges for modifying prewritten, standard, or canned computer software programs to a purchaser's needs or equipment are exempt from sales tax.
  • Taxable Base Software: The underlying prewritten software remains taxable even if modifications are made to it.

Example: A Michigan manufacturing company purchases prewritten ERP software for $100,000 and requires $50,000 in modifications to integrate with their existing systems and processes. The vendor's invoice separately itemizes the base software ($100,000, taxable) and the customization services ($50,000, exempt). Michigan sales tax applies only to the $100,000 base software price.

Example: A retailer purchases prewritten point-of-sale software for $25,000 with $15,000 in modifications to accommodate their specific loyalty program and inventory management requirements. When these charges are separately stated on the invoice, only the $25,000 for the base prewritten software is subject to sales tax.

Documentation Best Practices: To support this exemption, businesses should:

  • Clearly separate modification charges from base software charges on invoices
  • Maintain documentation describing the specific modifications performed
  • Retain contracts or statements of work outlining the customization requirements

Relevant Guidance: Revenue Administrative Bulletin 2023-10

Conclusion

Michigan provides several key sales tax exemptions for software and technology services, including:

  • Custom software development, which is treated as a professional service and exempt from tax.
  • Computers and equipment used in manufacturing and industrial processing.
  • Equipment used in software development for general sale.
  • Technical support services that are separately stated.
  • Software modification services that are separately stated.

Understanding and properly documenting these exemptions can help businesses reduce unnecessary sales tax liabilities and ensure compliance with Michigan's tax laws. The key to successfully claiming these exemptions is maintaining proper documentation and clearly separating exempt and taxable charges on invoices.

For additional guidance, refer to the Michigan Department of Treasury Sales and Use Tax and Categorical Exemptions pages.

5. Sourcing Rules

Introduction

Sourcing rules determine which sales are subject to Michigan sales tax based on the location where a taxable transaction is deemed to occur. Michigan follows a destination-based sourcing approach for most taxable sales, meaning that the applicable tax rate is determined by the customer's delivery location or where the customer receives the benefit of the service. This is particularly important for businesses that sell software, cloud services, and digital goods, as different sourcing rules may apply depending on whether the product is physically delivered, downloaded, or accessed remotely.

This section outlines Michigan's sourcing rules as they apply to software transactions, digital services, and multi-state business operations.

5.1 Destination-Based Sourcing for Tangible Products

In Michigan, the general rule for sourcing tangible personal property, including hardware and software delivered on physical media, is destination-based. Sales tax is applied based on the location where the customer takes possession of the product.

  • Taxable Hardware Sales: When a business sells computer hardware or software on tangible media to a Michigan location, the sale is subject to Michigan's 6% sales tax regardless of where the seller is located.
  • Out-of-State Deliveries: If a Michigan seller delivers computer hardware or software on physical media to a customer located outside Michigan, the sale is generally not subject to Michigan sales tax (though it may be subject to the destination state's tax).

Example: A Michigan-based computer retailer sells a server system to a customer with offices in both Michigan and Indiana. The equipment delivered to the Michigan office is subject to Michigan's 6% sales tax, while the equipment delivered to the Indiana office is not subject to Michigan sales tax (though it may be subject to Indiana sales tax).

Example: A national technology vendor ships prewritten software on USB drives to customers in multiple states, including Michigan. The vendor must collect Michigan sales tax on shipments delivered to Michigan addresses, regardless of where the vendor is located, assuming the vendor has nexus in Michigan.

5.2 Sourcing Rules for Prewritten Software

Michigan taxes prewritten software regardless of delivery method. For electronically delivered software, Michigan also follows destination-based sourcing principles, with the tax based on the location where the purchaser receives the software or where the purchaser makes first use of the software.

  • Electronic Delivery to Michigan Customers: When selling prewritten software electronically to customers in Michigan, sales tax applies based on the customer's location, assuming the seller has nexus in Michigan.
  • Multiple Points of Use: For software intended for use in multiple states, Michigan provides for apportionment based on percentage of users in Michigan versus other states.

Example: A software vendor sells a $50,000 prewritten software license to a company with operations in both Michigan and Ohio. The software is downloaded from the vendor's server. If 60% of the users are located in Michigan offices, Michigan sales tax would apply to $30,000 (60% of the purchase price), assuming proper documentation of the allocation.

Example: A Michigan business purchases accounting software through electronic download for $10,000. Even though the software is delivered electronically with no physical media involved, the entire amount is subject to Michigan's 6% sales tax because Michigan taxes prewritten software regardless of delivery method.

5.3 Sourcing Rules for Cloud-Based Services

For cloud-based services and remotely accessed software, Michigan's approach depends on how the transaction is classified. As noted earlier, the Michigan Department of Treasury has advised that access to software over the Internet without the delivery of "the code that enables the program" to operate or a "desktop client" is generally not taxable.

  • SaaS Sourcing Considerations: For non-taxable SaaS offerings, sourcing is less critical from a tax collection standpoint. However, businesses should still track the location of users for nexus determination purposes.
  • Mixed SaaS and Prewritten Software: When a transaction includes both SaaS elements and downloadable prewritten software components, the taxable portions would be sourced based on the customer's location in Michigan.

Example: A cloud service provider offers a database management solution that includes both cloud-based access (SaaS, generally non-taxable) and a downloadable administrative tool (prewritten software, taxable). For Michigan customers, the provider would need to collect sales tax only on the portion attributable to the downloadable software component.

Example: A Michigan medical practice subscribes to a healthcare management platform that is accessed entirely through web browsers. No software is downloaded to the practice's computers or servers. Based on Michigan Department of Treasury guidance, this pure SaaS offering would generally not be subject to Michigan sales tax since no software code is transferred to the customer.

5.4 Multi-State Transactions and Use Tax Considerations

When software and digital products are sold to businesses with multi-state operations, determining the appropriate tax jurisdiction can become complex. Michigan purchasers buying taxable software from out-of-state vendors that do not collect Michigan sales tax may be required to self-assess use tax at the same 6% rate.

  • Use Tax Obligations: If a Michigan business purchases taxable prewritten software or computer hardware from an out-of-state vendor that does not collect Michigan sales tax, the business must remit use tax on the purchase.
  • Multiple Points of Use Documentation: For software used in multiple states, businesses should maintain documentation showing the allocation method used (e.g., number of users, locations, or other reasonable method) to support the portion subject to Michigan tax.
  • Direct Pay Permits: Some larger businesses may qualify for direct pay authorization, allowing them to self-assess and pay use tax directly to the state rather than having vendors collect sales tax.

Example: A Michigan company with operations in multiple states purchases enterprise software for $200,000 from a vendor that does not collect Michigan sales tax. If 40% of the software users are located in Michigan, the company must self-assess and remit use tax on $80,000 (40% of the purchase price).

Example: A multi-state corporation with significant Michigan operations purchases server equipment and prewritten software from various vendors, some of which do not collect Michigan tax. The corporation obtains a direct pay permit from Michigan, allowing it to self-assess tax on the Michigan portion of its purchases rather than having vendors collect tax.

5.5 Documentation Requirements for Sourcing

Proper documentation is essential for supporting sourcing positions, especially for multi-state businesses and those with complex software deployments. Michigan businesses should maintain:

  • User Location Records: Documentation of the number of users and their physical locations for software with multiple points of use
  • License Agreements: Contracts specifying where software will be used
  • Deployment Documentation: Records showing where software is installed or accessed
  • Allocation Methodologies: Written explanations of any allocation methods used to determine the Michigan portion of multi-state software use

Example: A Michigan-headquartered corporation with locations in five states implements an enterprise-wide software system costing $500,000. The company maintains detailed records showing the number of licensed users in each state, with 45% in Michigan. The company provides this allocation documentation to the vendor, who collects Michigan sales tax on $225,000 (45% of the purchase price).

Conclusion

Understanding Michigan's sourcing rules is crucial for software businesses and digital service providers. The key takeaways include:

  • Destination-Based Taxation: Sales of tangible personal property and taxable digital products are generally taxed based on the customer's location.
  • Prewritten Software Is Taxable Regardless of Delivery: Unlike some states, Michigan taxes prewritten software whether delivered physically or electronically.
  • SaaS May Be Non-Taxable: Pure SaaS offerings without downloadable components may not be subject to Michigan sales tax.
  • Use Tax Applies to Out-of-State Purchases: Michigan businesses must remit use tax on taxable purchases when vendors do not collect sales tax.
  • Documentation Is Critical: Proper allocation and documentation are essential for supporting multi-state use.

Businesses should carefully evaluate their software sales and service transactions to ensure compliance with Michigan's sourcing rules, particularly since Michigan taxes prewritten software regardless of delivery method—a notable difference from states that exempt electronic deliveries.

For additional information, visit Sales And Use Taxation Of Computer Software And Digital Goods.

6. Audit Considerations

Introduction

Sales tax audits are a critical aspect of compliance for businesses operating in Michigan, particularly in the software, SaaS, and technology industries. The Michigan Department of Treasury routinely conducts audits to ensure businesses are correctly collecting and remitting sales tax. Since Michigan taxes prewritten software regardless of delivery method but exempts custom software and certain cloud services, businesses operating in this space must be vigilant about proper classification and documentation.

This section outlines the key aspects of Michigan sales tax audits as they relate to the software and technology sector, including common audit triggers, the audit process, and best practices for managing an audit successfully.

6.1 Common Audit Triggers for Software and Technology Businesses

Michigan's approach to taxing software and technology services creates several specific audit risk areas that technology companies should be aware of:

  • Misclassification of Prewritten Software as Custom Software: Since prewritten software is taxable but custom software is exempt, misclassifying software to avoid taxation is a significant audit trigger. Auditors specifically look for evidence that supposedly "custom" software was actually prewritten software that was merely configured or minimally modified.
  • Failure to Collect Tax on Electronically Delivered Software: Unlike many states, Michigan taxes prewritten software regardless of delivery method. Companies that incorrectly treat electronic delivery as non-taxable are at high risk for audit assessments.
  • Improper Application of Industrial Processing Exemptions: Michigan offers valuable exemptions for computer hardware and software used in manufacturing, but improper application of these exemptions can trigger audits.
  • Bundled Transactions Without Separation of Charges: Businesses that sell both taxable and non-taxable items (such as prewritten software and exempt services) in a single contract or invoice without separately stating the charges could be assessed tax on the entire amount.
  • Inconsistent Treatment of Software Maintenance Contracts: Maintenance contracts for prewritten software that include upgrades are taxable, while those for custom software are not. Inconsistent application of these rules can trigger audits.
  • Failure to Register After Establishing Nexus: Companies exceeding Michigan's economic nexus threshold of $100,000 in sales or 200 transactions but failing to register and collect sales tax face significant audit risk.
  • Use Tax Compliance Issues: Businesses that purchase taxable software or IT equipment from out-of-state vendors without paying Michigan sales tax must self-assess and remit use tax. Failure to do so is a common audit trigger.

Example: A Michigan software company sells what it classifies as "custom software" to various clients. However, during an audit, the Michigan Department of Treasury discovers that the company starts with a core prewritten software package and makes only minor modifications for each client. Since the base software is prewritten, the company should have collected sales tax on at least a portion of these sales, leading to a significant tax assessment.

Example: A technology consulting firm has been purchasing software licenses from out-of-state vendors for use in Michigan client projects without paying sales or use tax, incorrectly believing that electronic delivery exempts the purchases from taxation. During an audit, these untaxed purchases are discovered, resulting in use tax assessments, penalties, and interest.

6.2 The Michigan Sales Tax Audit Process

The Michigan Department of Treasury follows a structured audit process. Understanding the specific steps and timelines can help businesses prepare effectively.

  • Audit Selection & Initial Contact
  • Businesses are selected for audit based on various risk factors, including industry, size, past compliance issues, and random selection.
  • The Michigan Department of Treasury typically issues a formal audit notification letter specifying the audit period, records requested, and initial meeting date.
  • The standard audit lookback period in Michigan is four years, though it can extend further if fraud or substantial underreporting is suspected.
  • Pre-Audit Conference & Information Gathering
  • Auditors typically hold a pre-audit conference to explain the process and specify required documentation.
  • For software and technology companies, auditors typically request:
  • Sales and purchase journals
  • Sales and use tax returns
  • Sample invoices for both sales and purchases
  • Contracts for software sales and purchases
  • Documentation supporting exempt sales
  • Software license agreements
  • Documentation of delivery methods for software
  • Field Audit & Sampling Methodologies
  • For businesses with high transaction volumes, auditors typically use statistical sampling rather than reviewing every transaction.
  • The sample results are projected across the entire audit period to determine total liability.
  • Technology companies should negotiate appropriate sampling methodologies, as standard approaches may not accurately reflect their specific transaction types.
  • Preliminary Findings & Response Period
  • Auditors issue preliminary findings, giving the business an opportunity to provide additional documentation or explanations.
  • This response period is critical for technology companies to address any misclassifications or misunderstandings about the taxability of specific software or services.
  • Final Assessment & Appeal Options
  • After considering the taxpayer's response, the Michigan Department of Treasury issues a final assessment, which includes tax, interest, and any applicable penalties.
  • Businesses have appeal rights, including requesting an informal conference with the Department of Treasury or appealing to the Michigan Tax Tribunal or Michigan Court of Claims.

Timeline Considerations: The entire audit process typically takes several months to complete, from initial notification to final assessment. Businesses should be prepared for this extended timeline and allocate resources accordingly.

6.3 Michigan-Specific Documentation Requirements

Michigan has specific documentation requirements that are particularly relevant for software and technology companies:

  • Custom Software Documentation: To support custom software exemption claims, businesses should maintain:
  • Detailed requirements specifications unique to the customer
  • Design documents and project plans
  • Contracts explicitly stating the custom nature of the software
  • Evidence that the software was not previously developed for or sold to other customers
  • Industrial Processing Exemption Documentation: For computer hardware or software claimed under the industrial processing exemption:
  • Completed Michigan Form 3372 (Michigan Sales and Use Tax Certificate of Exemption)
  • Documentation showing how the equipment is used in industrial processing
  • Records demonstrating the percentage of exempt use if equipment has mixed uses
  • Software Delivery Documentation: Since taxability in some cases depends on delivery method:
  • Records showing method of software delivery (physical media vs. electronic)
  • Documentation of software downloads or access methods
  • Evidence of user locations for multi-state software deployment
  • Separately Stated Charges: For bundled transactions:
  • Invoices clearly separating taxable and non-taxable components
  • Contracts breaking down charges for various elements of technology solutions

6.4 Best Practices for Managing a Michigan Sales Tax Audit

Being proactive in compliance and documentation is the best way to minimize audit risk and successfully navigate an audit when it occurs. Technology companies should implement the following best practices:

  • Maintain Detailed Records: Keep comprehensive sales and purchase documentation for at least the four-year statute of limitations period:
  • Contracts and license agreements
  • Detailed invoices showing what was sold and delivery methods
  • Exemption certificates
  • Documentation supporting classification decisions (custom vs. prewritten)
  • Implement Clear Invoice Practices:
  • Separately state charges for taxable and non-taxable components
  • Clearly document software delivery methods
  • Include detailed descriptions of products and services sold
  • Regular Internal Audits:
  • Conduct periodic self-audits of sales and use tax compliance
  • Review classification of products and services
  • Verify proper tax collection on all taxable sales
  • Ensure use tax is being accrued on taxable purchases when vendors don't collect tax
  • Staff Training:
  • Educate sales, accounting, and IT staff on Michigan's unique software taxation rules
  • Ensure contract and billing teams understand the tax implications of how they structure transactions
  • Engage Professional Assistance:
  • Work with tax professionals familiar with Michigan's specific approach to technology taxation
  • Consider engaging specialists for audit defense when facing a Michigan audit
  • Document Taxability Decisions:
  • Maintain written explanations of tax treatment decisions, especially for complex transactions
  • Document the basis for treating software as custom rather than prewritten
  • Keep records of any Michigan Department of Treasury guidance relied upon

Example: A software company implements a comprehensive record-keeping system that preserves all contracts, statements of work, requirements documents, and invoices for at least 5 years. When audited, the company is able to quickly provide documentation supporting its classification of certain software as custom, showing the unique development process and client-specific requirements, successfully defending its exempt treatment of these sales.

Example: A technology consulting firm conducting an internal review discovers it has not been paying use tax on prewritten software purchased from out-of-state vendors. Rather than waiting for an audit, the firm considers a voluntary disclosure agreement to address past liabilities while minimizing penalties.

6.5 Penalty and Interest Considerations

Michigan imposes various penalties and interest for sales and use tax noncompliance:

  • Failure to File: 5% of the tax due for the first two months, then an additional 5% per month up to a maximum of 25%.
  • Failure to Pay: 5% of the tax due if paid within two months, increasing by 5% per month to a maximum of 25%.
  • Negligence Penalty: 10% of the deficiency for negligent underpayment.
  • Intentional Disregard: 25% penalty for intentional disregard of the law.
  • Fraud: 100% penalty for fraudulent avoidance of tax.
  • Interest: Accrues from the original due date until the tax is paid, at rates adjusted periodically.

Penalty Mitigation Strategies:

  • Demonstrate reasonable cause for noncompliance
  • Show good faith efforts to comply with complex tax rules
  • Maintain documentation of tax research and positions taken
  • Consider voluntary disclosure before being contacted for audit

Conclusion

Michigan sales tax audits can be complex and challenging for software and technology companies, particularly given Michigan's broad taxation of prewritten software regardless of delivery method. By understanding common audit triggers, preparing for the audit process, and implementing strong compliance practices, businesses can minimize tax liabilities and reduce risk.

Key takeaways:

  • Ensure proper classification of software as prewritten or custom, recognizing Michigan's specific definitions
  • Collect sales tax on all prewritten software, regardless of delivery method
  • Maintain comprehensive documentation supporting exempt sales and purchases
  • Separately state charges for taxable and non-taxable items on invoices
  • Conduct regular internal reviews of sales and use tax compliance

For more information on Michigan's audit process, visit the Michigan Department of Treasury Tax Compliance page.

7. Voluntary Disclosure Agreements (VDAs)

Introduction

A Voluntary Disclosure Agreement (VDA) allows businesses with past-due tax liabilities to come forward voluntarily and resolve unpaid taxes while potentially reducing penalties and limiting the audit lookback period. For software and technology businesses in Michigan, a VDA can be particularly useful when a company has established nexus but failed to collect and remit sales tax on taxable transactions, such as sales of prewritten software.

This section explains Michigan's VDA program and its relevance to software and SaaS businesses, including eligibility requirements, benefits, and best practices for successful participation.

7.1 Michigan's VDA Program Overview

Michigan's Voluntary Disclosure Program is designed to encourage businesses to voluntarily comply with tax laws before being contacted by the Michigan Department of Treasury for an audit. The program offers significant benefits to eligible businesses:

  • Limited Lookback Period: Standard Michigan audits can look back four years, but the VDA program typically limits the lookback period to four years from the date of application.
  • Penalty Waiver: The program generally waives all penalties that would otherwise apply to late filing and payment.
  • Interest Reduction: While full interest is generally not waived, the limited lookback period results in less interest accumulation.
  • Audit Protection: Acceptance into the VDA program generally protects businesses from audit for periods prior to the lookback period.
  • Anonymity During Initial Process: Businesses can initially explore VDA eligibility anonymously through a representative.

7.2 Eligibility for Michigan's VDA Program

To qualify for Michigan's Voluntary Disclosure Program, businesses typically must meet these criteria:

  • No Previous Contact: The business must not have been previously contacted by the Michigan Department of Treasury regarding the specific tax type and periods covered by the disclosure.
  • No Previous Registration: The business must not be currently registered for the tax type being disclosed.
  • No Criminal Investigation: The business must not be currently under criminal investigation.
  • Non-Filers Only: The program is generally designed for non-filers rather than businesses that have filed returns but underreported tax.
  • Good Faith Disclosure: The business must make a complete and accurate disclosure of all tax liabilities.

7.3 When Should a Software Business Consider a VDA?

Software and technology companies should consider Michigan's VDA program in the following situations:

  • Exceeded Michigan's Economic Nexus Threshold Without Registering: Businesses that surpassed the $100,000 sales threshold or 200 transactions but failed to register and collect sales tax.
  • Failed to Collect Tax on Electronically Delivered Software: Companies that incorrectly treated electronic delivery of prewritten software as non-taxable when Michigan requires collection of tax regardless of delivery method.
  • Misclassified Prewritten Software as Custom: Businesses that may have incorrectly classified prewritten software as custom to avoid taxation and now realize the error.
  • Missed Use Tax Payments on Business Purchases: Companies that purchased taxable software or IT equipment from out-of-state vendors without paying Michigan sales tax or self-assessing use tax.
  • Recently Discovered Historical Tax Obligations: If a company recently determined it had historical sales or use tax obligations in Michigan, perhaps through a nexus study or tax review.

Example: A software company based in California has been selling prewritten software electronically to Michigan customers for three years, with annual Michigan sales of approximately $150,000. The company incorrectly believed that electronic delivery exempted its sales from Michigan tax. After learning that Michigan taxes electronically delivered prewritten software, the company decides to pursue a VDA to address its past liability while minimizing penalties.

Example: An out-of-state SaaS provider recently discovered that some of its offerings include downloadable components that Michigan considers taxable prewritten software. The company has exceeded Michigan's economic nexus thresholds for the past two years but has not registered or collected tax. A VDA would allow the company to come into compliance while limiting exposure for earlier periods.

7.4 The Michigan VDA Process

The process for participating in Michigan's Voluntary Disclosure Program involves specific steps designed to protect taxpayer confidentiality while ensuring proper disclosure:

  • Anonymous Initial Application
  • Businesses typically apply through a tax professional or attorney who acts as an intermediary.
  • The representative submits a written request to the Michigan Department of Treasury outlining the general facts without identifying the business.
  • This initial application should describe the business activities, nexus-creating factors, types of taxes owed, and estimated liability.
  • Tentative Agreement
  • If the Michigan Department of Treasury determines the business qualifies, it will issue a tentative agreement specifying the terms, including lookback period and waived penalties.
  • The business then decides whether to accept these terms and proceed with formal disclosure.
  • Formal Disclosure & Agreement
  • Once the terms are acceptable, the business identifies itself and submits a formal disclosure with detailed information about past activities and tax liabilities.
  • This includes complete records of Michigan transactions during the lookback period and calculation of tax due.
  • The Michigan Department of Treasury reviews the disclosure and finalizes the agreement.
  • Payment of Tax and Interest
  • The business must pay all disclosed tax and interest within the timeframe specified in the agreement (typically 30 days from final approval).
  • Payment is required for the agreement to become final and binding.
  • Registration and Future Compliance
  • As part of the agreement, the business must register for applicable Michigan taxes and commit to future compliance.
  • Failure to comply with future filing and payment obligations could potentially invalidate the VDA benefits.

Timeline Considerations: The entire VDA process typically takes 2-4 months from initial anonymous submission to final agreement, though complex cases may take longer.

7.5 Documentation and Calculation Requirements

For software and technology companies, proper documentation and calculation of tax liability are critical components of a successful VDA application:

  • Sales Records: Detailed records of all sales to Michigan customers during the lookback period, categorized by taxable and non-taxable transactions.
  • Product and Service Documentation: Clear descriptions of all products and services sold, demonstrating which were taxable prewritten software versus exempt custom software or services.
  • Delivery Method Documentation: Evidence of how software was delivered (physically or electronically), though in Michigan this doesn't affect taxability of prewritten software.
  • Nexus-Creating Activities: Documentation of when nexus was established in Michigan, such as when economic nexus thresholds were exceeded or physical presence was established.
  • Exemption Documentation: Copies of any valid exemption certificates received from customers.
  • Use Tax Liability Calculation: For businesses with use tax obligations, documentation of taxable purchases from vendors who did not collect Michigan tax.

Calculation Methodology: The tax calculation should include:

  • Base sales/purchase amount
  • Applicable Michigan sales/use tax rate (6%)
  • Interest calculated from the original due date to expected payment date
  • Breakdown by filing period (typically monthly or quarterly)

7.6 Best Practices for a Successful Michigan VDA

To maximize the benefits of a VDA and ensure a smooth process, businesses should follow these best practices:

  • Conduct a Thorough Pre-Disclosure Review:
  • Perform a comprehensive analysis of all Michigan activities and transactions
  • Identify all potential tax liabilities, not just those initially recognized
  • Consider all tax types, not just sales/use tax (income tax, withholding, etc.)
  • Quantify the potential liability before approaching the state
  • Work with Experienced Tax Professionals:
  • Engage professionals familiar with Michigan's VDA program and technology taxation
  • Use representatives who can maintain anonymity during the initial process
  • Consider both legal and accounting expertise for complex situations
  • Prepare Complete and Accurate Records:
  • Gather detailed transaction data for the entire lookback period
  • Organize information in formats that clearly demonstrate tax liability
  • Be prepared to support classifications of software as prewritten or custom
  • Be Thorough and Transparent:
  • Disclose all relevant facts about Michigan activities
  • Don't attempt to minimize exposure by selective disclosure
  • Address all tax types and periods where obligations exist
  • Implement Strong Compliance Processes:
  • Establish systems to ensure correct classification and taxation going forward
  • Develop clear invoicing practices that properly document taxable and non-taxable components
  • Create processes for regularly reviewing nexus in all states, including Michigan

Example: A technology company preparing for a Michigan VDA conducts a comprehensive review of all its products and services, carefully categorizing each as taxable or non-taxable under Michigan law. For each taxable sale to Michigan customers during the lookback period, the company compiles detailed transaction data and calculates the precise tax liability plus applicable interest. This thorough preparation results in a smooth VDA process and accurate settlement.

7.7 Alternatives to the VDA Program

In some cases, businesses may not qualify for Michigan's Voluntary Disclosure Program or may find other compliance options more appropriate:

  • Voluntary Tax Payments: Businesses that don't qualify for the formal VDA program may still make voluntary payments for past liabilities, though this approach doesn't provide the same penalty waivers or lookback limitations.
  • Registration and Prospective Compliance: Some businesses with minimal past exposure may choose to simply register and comply going forward, though this approach carries risk for past periods.
  • Managed Audits: In certain situations, Michigan offers managed audit programs where businesses identify and calculate their own liabilities under Treasury supervision.

Conclusion

For software and technology companies, Michigan's Voluntary Disclosure Program offers a strategic opportunity to resolve past sales and use tax liabilities while minimizing penalties and limiting exposure for older periods. Given Michigan's approach to taxing prewritten software regardless of delivery method, technology companies that have not properly collected or remitted tax should carefully consider this option.

Key takeaways:

  • A VDA helps businesses resolve past-due tax liabilities while securing penalty relief and a limited lookback period.
  • Software companies should be particularly attentive to Michigan's taxation of electronically delivered prewritten software.
  • Thorough preparation and accurate disclosure are essential for a successful VDA.
  • Working with tax professionals experienced in Michigan's technology taxation rules can greatly facilitate the process.

For additional details and to apply for Michigan's Voluntary Disclosure Program, visit the Michigan Department of Treasury VDA Program page.

8. Conclusion

Navigating Michigan's Sales and Use Tax for Software and Technology

Navigating Michigan's sales and use tax laws for software, SaaS, and technology services requires a deep understanding of transaction classification, sourcing rules, and compliance obligations. Michigan's approach differs from many states in that it taxes prewritten software regardless of delivery method, while exempting custom software as a professional service. This key distinction creates both compliance challenges and planning opportunities for technology businesses operating in or selling into Michigan.

Key Takeaways

The complexity of Michigan's tax rules means that businesses must take a proactive approach to compliance. Companies exceeding Michigan's $100,000 economic nexus threshold or 200 transactions must register and collect sales tax, even if they are located outside the state. Similarly, businesses with a physical presence in Michigan—whether through employees, inventory, or business activities—must also comply with sales tax obligations.

Understanding what is taxable and what is exempt is essential for technology companies operating in Michigan:

  • Prewritten Software: Taxable regardless of delivery method (physical or electronic), creating broader tax obligations than states that exempt electronic delivery.
  • Custom Software: Exempt from sales tax as a professional service when designed exclusively for a specific customer's needs.
  • Computer Hardware: Generally taxable unless it qualifies for manufacturing or industrial processing exemptions.
  • Software Maintenance: Taxable for prewritten software when it includes upgrades; exempt for custom software or when limited to technical support.
  • Cloud Computing/SaaS: Generally not taxable when no software is delivered to customers, though Michigan's guidance in this area continues to evolve.

Businesses must also understand Michigan's documentation requirements and sourcing rules. For multi-state companies using software across various locations, proper allocation and documentation are essential to support tax positions. Michigan follows destination-based sourcing, with tax applying based on where customers receive and use the software or service.

Audit risks arise when businesses fail to properly classify software as prewritten versus custom, incorrectly treat electronically delivered software as non-taxable, or omit use tax reporting on taxable business purchases. To mitigate these risks, businesses should maintain comprehensive records, separately state taxable and non-taxable charges on invoices, and regularly review compliance across all jurisdictions where they operate.

For businesses that discover past compliance issues, Michigan's Voluntary Disclosure Program offers an opportunity to address historical liabilities while limiting penalties and the lookback period. This program can be particularly valuable for technology companies that may have misunderstood Michigan's broad taxation of prewritten software.

Next Steps for Technology Companies

As the technology sector continues to evolve, Michigan's approach to taxing software and digital services may also change. Businesses must stay ahead by monitoring regulatory updates, conducting internal tax reviews, and seeking professional guidance when necessary. Specific action items include:

  • Conduct a Nexus Analysis: Determine whether your business has physical or economic nexus in Michigan requiring tax registration.
  • Review Product and Service Classifications: Carefully assess whether your offerings are prewritten software (taxable) or custom software/services (exempt).
  • Evaluate Invoicing Practices: Ensure invoices clearly separate taxable and non-taxable components to avoid taxation of entire bundled transactions.
  • Implement Use Tax Compliance Procedures: Establish systems to self-assess use tax on taxable purchases when vendors don't collect Michigan tax.
  • Consider Historical Exposure: For businesses with past compliance gaps, evaluate whether a Voluntary Disclosure Agreement would be beneficial.
  • Monitor Regulatory Developments: Stay informed about Michigan Department of Treasury guidance, particularly regarding cloud computing and digital services.

Ensuring compliance with Michigan's sales tax laws is not just about avoiding penalties—it's about creating a sound foundation for growth and stability in an increasingly complex digital economy.

For further details on Michigan's tax regulations, businesses should refer to official resources:

By staying informed and proactive, businesses can confidently manage their Michigan sales tax obligations, reduce risk, and maintain compliance in an evolving digital landscape.

9. References & Resources

Michigan Department of Treasury Resources

Audit & Compliance

Key Michigan Statutory & Regulatory References

  • Michigan Compiled Laws (MCL) Section 205.51a: Definitions related to sales tax, including computer software
  • MCL Section 205.92b: Definitions related to use tax, including computer software
  • MCL Section 205.54d: Exemptions for certain services and software
  • MCL Section 205.54t: Exemptions for industrial processing
  • MCL Section 205.94a: Exemptions from use tax for certain services
  • MCL Section 205.94o: Exemptions from use tax for industrial processing

Notable Michigan RABs and Guidance on Software & SaaS

  • RAB 2023-10 – Provides comprehensive guidance on the taxation of computer software, distinguishing between prewritten and custom software
  • RAB 2000-4 – Offers examples of computers that qualify for the industrial processing exemption
  • Various Technical Advice Letters – Interpretations of how Michigan applies tax laws to digital products and software transactions

Additional Guidance & Compliance Support

Armed with these Michigan-specific tools and resources, businesses can:

  • Mitigate Risk: Understand which transactions are taxable, which might be exempt, and how to structure invoices to minimize compliance pitfalls.
  • Maintain Impeccable Documentation: Keep thorough records (contracts, itemized invoices, exemption certificates) to defend tax positions in the event of an audit.
  • Ensure Compliance: Stay current on Revenue Administrative Bulletins and administrative rules, especially as technology evolves and new rulings are issued.

If you ever need personalized assistance—whether for setting up a Voluntary Disclosure Agreement, responding to a sales tax audit, or clarifying complex software tax classifications—our team at Sales Tax Helper is here to help you save time and protect your bottom line.

Disclaimer: This guide is intended as an overview and does not constitute legal or tax advice. Always consult a qualified tax professional or attorney for advice specific to your business situation.

Get answers for your Michigan software and SaaS questions

Create a free Sales Tax Helper account to check your nexus exposure and keep your Michigan compliance on track. Need a hand? Our attorneys, CPAs, and former state auditors are ready to help.

Need Expert Help?

Our team of attorneys, CPAs, and former state auditors handles exactly these situations. Free consultation — no obligation.

Get Started FreeContact Us