Computer Software & SaaS · Indiana

Indiana 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 Indiana, the state's sales and use tax rules present unique challenges that can significantly impact financial operations and compliance requirements. Unlike some states with more straightforward approaches, Indiana maintains distinct tax treatments for different categories of software and technology services based on critical factors such as delivery method, customization level, and service classification.

Indiana's approach to taxing technology is particularly nuanced – the state generally taxes prewritten (canned) software regardless of delivery method, while exempting custom software as a professional service. Perhaps most notably for modern technology companies, Indiana currently offers a temporary exemption for remotely accessed software (SaaS) through June 30, 2024, creating both immediate tax planning opportunities and future compliance challenges when this provision expires.

Purpose of This Guide

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

  • Nexus Considerations: Understanding when businesses must register and collect Indiana sales tax due to physical or economic presence, including Indiana's revised $100,000 economic nexus threshold that applies to all retail sales (without the transaction count threshold that existed prior to January 1, 2024).
  • Taxability of Software & Services: Clarifying the tax treatment of prewritten vs. custom software, cloud computing services, and related technology offerings, with particular attention to Indiana's unique temporary SaaS exemption under IC 6-2.5-4-16.7.
  • Sourcing Rules: Determining how and where transactions are taxed based on customer location and method of software delivery under Indiana's destination-based sourcing approach.
  • Audit Considerations: Identifying common tax audit triggers and best practices for compliance, including documentation requirements specific to Indiana's software classification standards.
  • Voluntary Disclosure Agreements (VDAs): Explaining the process for businesses to rectify past noncompliance while mitigating penalties and limiting back-tax liability through Indiana's formal disclosure program.

Why This Matters for Technology Companies

Indiana's sales tax laws have direct financial and operational implications for software companies, SaaS providers, and technology firms in multiple ways:

  • Sales Tax Collection Requirements: Technology businesses selling to Indiana customers face a duty to collect and remit sales tax at the rate of 7% on taxable transactions, potentially creating significant tax liability if misclassified.
  • Cloud Computing & SaaS Complexity: Indiana's treatment of SaaS is particularly complex due to the temporary exemption ending June 30, 2024 (under IC 6-2.5-4-16.7), creating a compliance timeline that businesses must actively prepare for.
  • "Incidental" Service Determinations: Indiana's unique 10% threshold for determining when software is "incidental" to a service requires careful transaction structuring and documentation.
  • Documentation Requirements: Indiana auditors specifically look for clear separation of taxable and non-taxable elements on invoices and contracts, with failure to properly document potentially resulting in taxation of the entire transaction.
  • Compliance Risks: Failure to correctly assess and collect sales tax can result in significant penalties (typically 10% of unpaid tax), interest (currently charged at variable rates published quarterly by the DOR), and extended audit exposure.

This comprehensive guide walks through Indiana's specific sales tax rules governing software, SaaS, and technology-related services while referencing applicable statutes, administrative rules, and Indiana Department of Revenue (DOR) guidance. Throughout the guide, official Indiana Department of Revenue sources are linked for further reference, providing authoritative support for the tax positions discussed.

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 Indiana to require the collection and remittance of sales tax. The determination of nexus is critical because businesses with nexus must comply with Indiana'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.

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

Physical Presence Nexus in Indiana

Physical presence nexus occurs when a business has a tangible footprint in Indiana. 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 Indiana may establish nexus.

For example, a SaaS company with a server farm located in Indiana 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 Indiana Department of Revenue.

Economic Nexus in Indiana

Indiana enforces an economic nexus standard, requiring remote sellers to collect and remit sales tax if they have more than $100,000 in annual sales into Indiana. This threshold applies to the calendar year in which the retail transaction is made or the calendar year preceding the calendar year in which the retail transaction is made.

Importantly, Indiana's economic nexus law applies to all types of sales, including digital products, SaaS, and other non-tangible products, as these are considered retail transactions under Indiana law when they are taxable. Prior to January 1, 2024, Indiana had both a sales threshold ($100,000) and a transaction threshold (200 transactions), but the transaction threshold has been removed.

For more details on Indiana's economic nexus law, visit the Indiana Department of Revenue's Nexus Information Page.

Marketplace Facilitator Rules in Indiana

Indiana has specific marketplace facilitator rules that require platforms such as Amazon, eBay, and Shopify to collect and remit sales tax on behalf of third-party sellers. Under Indiana law, a marketplace facilitator is an entity that facilitates a retail sale by listing or advertising products and processing transactions for sellers. Marketplace facilitators with more than $100,000 in annual sales into Indiana must collect and remit sales tax on behalf of their sellers.

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.

For more details on Indiana's marketplace facilitator rules, visit the Indiana Department of Revenue's Marketplace Facilitator Information Page.

Compliance Obligations and Registration

Businesses that establish nexus through physical presence, economic thresholds, or marketplace sales must register for sales tax collection with the Indiana Department of Revenue. Once registered, businesses are required to collect the applicable state and local sales tax on taxable transactions and remit these amounts to the state. Registration can be completed online through Indiana's INBiz portal.

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

Conclusion: Proactive Nexus Management

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

To ensure compliance, businesses should:

  • Regularly assess their business activities in Indiana.
  • Register for sales tax collection if they meet physical presence or economic nexus criteria.
  • Monitor regulatory changes that could introduce expanded economic nexus requirements.
  • Maintain accurate sales records and consult tax professionals to ensure compliance.

By proactively managing their sales tax obligations, businesses can avoid unexpected liabilities and maintain compliance with Indiana's tax laws. More details on Indiana's nexus rules and registration requirements can be found on the Indiana Department of Revenue website.

3. General Rules and Compliance Considerations

Introduction

Determining the taxability of software, cloud computing, and related technology services in Indiana 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. Indiana's tax laws provide distinct rules for prewritten and custom software, maintenance agreements, information services, and bundled transactions.

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

3.1 Computer Hardware

The sale or lease of computer hardware is subject to Indiana sales tax. The tax is based on the total purchase price charged, including charges for internalized instruction codes that control the basic computer operations, instructional materials, and installation charges. An exemption exists for computer hardware used in manufacturing.

Computer hardware is the machinery and equipment that comprise a computer's assembly, including:

  • Central processing units
  • Keyboards
  • Mice
  • Video monitors
  • Data storage devices
  • Processors
  • Output units
  • Card readers
  • Printers
  • Terminals
  • Modems
  • The internalized instruction code that controls the basic operations of the computer

Example: A business purchases new server hardware for its office in Indianapolis. The entire purchase is subject to Indiana sales tax, including any installation charges.

Relevant Guidance: Sales Tax Information Bulletin #8

3.2 Prewritten (Canned) Software

Prewritten, or "canned," software refers to standardized software developed for sale to multiple customers without significant modification. In Indiana, prewritten computer software is taxable as tangible personal property, even if some modification to the program is required for a customer's particular computer.

Indiana's treatment of prewritten software is governed by IC 6-2.5-1-24, which defines prewritten computer software as "computer software that is not designed and developed by the author or other creator to the specifications of a specific purchaser." The law clarifies several important points:

  • Combining two or more prewritten software programs does not create custom software
  • A person who modifies someone else's software is considered the creator only of their own modifications
  • Software created for a specific customer becomes prewritten software when sold to others

Example: A software retailer sells prepackaged accounting programs for use with home television game consoles or other personal computer equipment for $59.99. Since this is standardized software available to multiple customers, the entire $59.99 is subject to Indiana's 7% sales tax regardless of whether it's delivered on physical media or electronically.

Example: An Indiana software firm develops and sells prewritten application programs for inventory management. The programs are available for sale to any customer for $1,500 per license. Even though the company might make minor adjustments during installation, these sales remain taxable as prewritten software.

Example: An Indiana manufacturing business pays an annual fee of $25,000 to access a suite of prewritten computer programs maintained on a third party's computer servers located outside of Indiana. The software, including any documents created with the software, is housed on the third party's server. The resident never receives the software in a tangible medium, but has control of and uses the software. Through June 30, 2024, this transaction is exempt under IC 6-2.5-4-16.7. After that date, unless the exemption is extended, this transaction would constitute a taxable lease of software.

Relevant Statute: IC 6-2.5-1-24 Relevant Guidance: Sales Tax Information Bulletin #8

3.3 Custom Software

Custom software is not subject to Indiana sales tax. When modified prewritten software is sold, and the seller separately states a charge for the modification on the customer billing, the modification is not prewritten computer software and is exempt.

Custom software is computer software that is designed and developed to meet a customer's specific needs. A person that modifies computer software created by another person is the creator only of his or her own modifications.

Example: A business contracts with a developer to create a unique inventory management system specifically designed for their operations. This transaction is exempt from sales tax as a professional service.

Relevant Guidance: Sales Tax Information Bulletin #8

3.4 Information Services & Professional Services

  • Indiana distinguishes between informational software sales and professional services. However, in Indiana, neither is generally taxable.

Example: A company hires an IT consultant to provide technical support for their systems. This service is exempt from sales tax as a professional service.

3.5 Maintenance and Support Agreements

The taxability of software maintenance agreements in Indiana depends on the structure of the contract and the nature of the services provided.

Software maintenance agreements or optional warranties are generally taxable because a presumption exists that software updates will be transferred under the agreements. A computer software maintenance contract is a contract that obligates a person to provide a customer with future patches, updates, upgrades, or repairs of computer software.

Example: A company purchases a mandatory software maintenance plan that includes both phone support and software patches provided on physical media. Since it involves tangible personal property, the contract is taxable.

Relevant Guidance: Sales Tax Information Bulletin #8

3.6 Software Incidental to Services

A purchaser may buy services, and, as part of those services, also receive tangible personal property in the form of software. If the software provided to the customer is merely incidental to the services (less than 10% of the total price of the transaction), then the service transaction may not be subject to sales tax.

Example: An Indiana business contracts with a service provider that will perform the business's information technology (IT) functions. The Indiana business downloads the service provider's prewritten software onto the business's computer, and the service provider uses the software remotely in order to perform its IT services. The business does not use the software. The cost of the software is incidental (less than 10% of the total price of the transaction) to the service, so the transaction with the business customer is exempt.

Relevant Guidance: Sales Tax Information Bulletin #8

3.7 Cloud Computing (SaaS, IaaS, PaaS)

The taxability of cloud computing in Indiana depends on the category under which the activity is classified. Cloud computing describes the delivery of computing resources, including software applications, development tools, storage, and servers over the Internet. Cloud computing offerings are generally divided into three categories:

  • Software as a Service (SaaS): Under the SaaS model, a consumer purchases access to a software application that is owned, operated, and maintained by a SaaS provider. The consumer accesses the application over the Internet. The software is located on a server that is owned or leased by the SaaS provider. The software is not transferred to the customer, and the customer does not have the right to download, copy, or modify the software.

In Indiana, there is currently conflicting guidance regarding SaaS. According to Indiana Code IC 6-2.5-4-16.7, which expires on July 1, 2024, transactions in which an end user remotely accesses prewritten computer software over the Internet are not considered retail transactions and thus are exempt from sales tax. However, the Indiana Department of Revenue's Information Bulletin #8 indicates that SaaS is ostensibly taxable in Indiana. Until this conflict is resolved, businesses should approach SaaS transactions with caution.

  • Infrastructure as a Service (IaaS): IaaS providers sell access to storage, networks, equipment, and other computing resources that the provider operates and maintains.

In Indiana, a transaction for IaaS is not taxable if the customer does not purchase, lease, or rent the equipment. Remote storage, web hosting, and web design (as long as tangible personal property is not transferred) are generally not taxable.

  • Platform as a Service (PaaS): Under the PaaS model, the provider sells access to a platform and software development tools that a consumer uses to create its own applications.

In Indiana, the taxability of PaaS depends on the nature of the software rights. The determination of whether a transaction constitutes PaaS is based on facts and circumstances, including how the software was used and the amount of access the taxpayer had.

Example: A business subscribes to a cloud-based project management software hosted on remote servers. According to IC 6-2.5-4-16.7 (effective through June 30, 2024), this transaction is not considered a retail transaction and is not subject to Indiana sales tax.

Relevant Statutes: IC 6-2.5-4-16.7 Relevant Guidance: Sales Tax Information Bulletin #8

3.8 Bundled Transactions

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

If a business sells a package that includes prewritten software (taxable) and non-taxable custom modifications or consulting services, and does not separately state the charges, the entire amount may be subject to sales tax. If the invoice separately states taxable and non-taxable components, only the taxable portion is subject to sales tax.

Example: A company sells a software implementation package for $10,000, which includes prewritten software ($7,000) and consulting services ($3,000). If the invoice separately states these charges, only the $7,000 software portion is taxable. If the charges are not separately stated, the entire $10,000 may be subject to tax.

Conclusion

Understanding Indiana's tax rules on software and technology services is essential for compliance. Businesses should:

  • Properly classify software as prewritten or custom to determine taxability.
  • Structure invoices to separately state taxable and non-taxable components.
  • Review maintenance contracts to determine their taxability.
  • Stay updated with Indiana Department of Revenue guidance on evolving digital tax policies.

For official sales tax information, visit the Indiana Department of Revenue Sales and Use Tax Page.

4. Specific Exemptions

Introduction

Indiana 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, custom software, and certain services, referencing applicable Indiana statutes and rulings.

4.1 Exemption for Custom Software

Custom software developed exclusively for a single customer is exempt from Indiana sales tax. 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.

When modified prewritten software is sold, and the seller separately states a charge for the modification on the customer billing, the modification is not considered prewritten computer software and is exempt.

Example: A business hires a software firm to create a tailored accounting program for its internal use. Since the software is uniquely designed and not resold to multiple customers, the transaction is exempt.

Relevant Guidance: Sales Tax Information Bulletin #8

4.2 Manufacturing Exemption for Computer Hardware

Indiana provides a sales tax exemption for computer hardware used directly in the manufacturing process. This exemption applies to computers and related equipment that are an integral part of the manufacturing operation.

To qualify for the exemption, the computer equipment must be directly used in the production process, not merely for administrative or record-keeping functions.

Example: A manufacturing company purchases computers that control automated assembly line equipment. Since these computers are directly involved in the production process, they qualify for the manufacturing exemption.

Relevant Guidance: Sales Tax Information Bulletin #8

4.3 Software Incidental to Services

When software is provided as part of a service transaction and represents less than 10% of the total transaction value, the entire transaction may be exempt from sales tax. This applies when the true object of the transaction is the service rather than the software.

Example: An Indiana business contracts with a service provider to perform payroll obligations. As part of the service, the Indiana business accesses the service provider's prewritten software from a web browser to input data for the service provider's use. If the cost of the software is incidental (less than 10% of the total price of the transaction) to the service, the transaction is exempt from sales tax.

Relevant Guidance: Sales Tax Information Bulletin #8

4.4 Computer Time and Data Processing

The sale or lease of computer time is a nontaxable service providing the charge for the use is billed separately from other charges. Sales of statistical reports, graphs, diagrams, or any other information produced or compiled by a computer are not taxable if the customer provided the data for compilation.

Example: A business contracts with a data processing center to analyze customer information and generate statistical reports. Since the business provided the data and is purchasing computer time and data processing services, the transaction is exempt from sales tax.

Relevant Guidance: Sales Tax Information Bulletin #8

4.5 Remote Storage and Web Hosting

Remote storage is a form of Infrastructure as a Service (IaaS) and involves providing digital space to store or back up a customer's data and information. Consideration received for the remote storage of a customer's own software, data, or information is not taxable. Data transfer charges are also not taxable.

Similarly, web hosting services and web design services (as long as tangible personal property is not transferred as part of the transaction) are not subject to sales tax in Indiana.

Example: A company subscribes to a cloud-based data backup service. Since this is considered remote storage and no tangible personal property is transferred, the service is exempt from sales tax.

Relevant Guidance: Sales Tax Information Bulletin #8

4.6 Temporary SaaS Exemption (Through June 30, 2024)

In Indiana, effective July 1, 2018, through June 30, 2024, a transaction in which an end user purchases, rents, leases, or licenses the right to remotely access prewritten computer software over the Internet, over private or public networks, or through wireless media, is not considered to be a transaction in which prewritten computer software is delivered electronically, and does not constitute a retail transaction. As such and until July 1, 2024, remotely accessed prewritten computer software delivered electronically is exempt from sales and use tax.

Example: A business subscribes to an online accounting software platform accessible via web browser. Under the temporary exemption, this SaaS transaction is not subject to Indiana sales tax through June 30, 2024.

Relevant Statute: IC 6-2.5-4-16.7

Conclusion

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

  • Custom software, which is treated as a professional service and exempt from tax.
  • Computer hardware used directly in manufacturing processes.
  • Software that is incidental to service transactions (less than 10% of the total price).
  • Computer time and data processing services.
  • Remote storage and web hosting services.
  • Temporarily (through June 30, 2024), SaaS transactions.

Understanding and applying these exemptions correctly can help businesses reduce unnecessary sales tax liabilities and ensure compliance with Indiana's tax laws. For additional guidance, refer to the Indiana Department of Revenue Sales and Use Tax Page.

5. Sourcing Rules

Introduction

Sourcing rules determine which sales are subject to Indiana sales tax based on the location where a taxable transaction is deemed to occur. Indiana follows a destination-based sourcing approach for most taxable sales, meaning that the applicable tax rate is determined by the customer's delivery location. 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 Indiana's sourcing rules as they apply to software transactions, digital services, and multi-state business operations.

5.1 Destination-Based Sourcing for Software Sales

In Indiana, the default rule for sourcing taxable transactions is that sales tax is applied based on the destination where the customer takes possession of the product. This applies primarily to tangible personal property, such as prewritten software delivered on a physical medium.

  • Taxable Sales: If a software product is sold and shipped to an Indiana address on a tangible medium (e.g., a USB drive, CD, or hard disk), Indiana sales tax applies based on the customer's location.
  • Non-Taxable Sales: Custom software or exempt digital services are not subject to sales tax regardless of the customer's location.

Example: A business sells prewritten software on a USB drive to a customer in Indianapolis. Since the software is delivered physically, the sale is subject to Indiana sales tax at the rate applicable to the customer's location in Indianapolis.

Relevant Guidance: Indiana Department of Revenue Sourcing Rules

5.2 Sourcing Rules for Electronically Delivered Software and Digital Products

For electronically delivered software that is considered taxable in Indiana, the transaction is sourced to the customer's location. Since Indiana's tax treatment of electronically delivered software has specific nuances, particularly with the temporary exemption for remotely accessed prewritten software through June 30, 2024, businesses must carefully determine the taxability of the transaction before applying sourcing rules.

  • Prewritten Software: When taxable, electronically delivered prewritten software is sourced to the customer's location.
  • SaaS and Cloud Services: Through June 30, 2024, remotely accessed prewritten software is not considered a retail transaction and is thus not subject to sales tax.

Example: An Indiana business downloads accounting software directly from the vendor's website. This transaction is sourced to the business's location in Indiana.

Relevant Statute: IC 6-2.5-4-16.7

5.3 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. Indiana businesses purchasing taxable software or digital products from out-of-state vendors may be required to self-assess use tax if the transaction would have been taxable had it occurred within Indiana and the seller did not collect Indiana sales tax.

  • Use Tax: If an Indiana business purchases taxable software from an out-of-state vendor that does not collect Indiana sales tax, the business must remit use tax on the purchase.
  • Multi-State Allocation: If software is licensed for use in multiple states, businesses must document how the software is used across different locations to determine the portion of the purchase subject to Indiana tax.

Example: A company headquartered in Indiana purchases enterprise software, with 70% of the licenses used in Indiana and 30% in Ohio. Indiana use tax applies to the 70% allocated to Indiana, while the remaining portion is subject to Ohio's tax rules.

Relevant Guidance: Indiana Department of Revenue Use Tax Information

5.4 Marketplace Facilitator Sourcing

Indiana's marketplace facilitator rules require qualifying marketplaces to collect and remit sales tax on behalf of their sellers. For these transactions, the marketplace facilitator is responsible for determining the proper sourcing of the sale based on the delivery location of the product or service.

  • Remote Sales: Marketplace facilitators must apply destination-based sourcing rules to determine the applicable tax rate for sales delivered to Indiana customers.
  • Digital Products: For taxable digital products sold through marketplaces, the customer's location determines the sourcing of the transaction.

Example: A software developer sells their application through a major app marketplace. The marketplace is responsible for collecting and remitting Indiana sales tax on taxable sales to Indiana customers, based on the customers' locations.

Relevant Guidance: Indiana Department of Revenue Marketplace Facilitator Information

Conclusion

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

  • Destination-Based Taxation: Sales of tangible software are taxed based on the customer's delivery location.
  • Electronic Delivery: For taxable electronically delivered software, the customer's location determines the sourcing of the transaction.
  • Temporary SaaS Exemption: Through June 30, 2024, remotely accessed prewritten software is not considered a retail transaction and is thus not subject to sales tax.
  • Use Tax Applies to Out-of-State Purchases: Indiana businesses must remit use tax on taxable software purchases when vendors do not collect sales tax.

Businesses should carefully evaluate their software sales and service transactions to ensure compliance with Indiana's sourcing rules. For additional information, visit the Indiana Department of Revenue Sales and Use Tax Page.

6. Audit Considerations

Introduction

Sales tax audits are a critical aspect of compliance for businesses operating in Indiana, particularly in the software, SaaS, and technology industries. The Indiana Department of Revenue (DOR) routinely conducts audits to ensure businesses are correctly collecting and remitting sales tax, with technology companies increasingly becoming audit targets due to the complex classification issues involved with digital products and services.

Software and technology companies face particularly high audit risk in Indiana due to several factors:

  • The distinct classification rules for prewritten versus custom software
  • The temporary exemption for remotely accessed prewritten software (expiring June 30, 2024)
  • The need to properly document "incidental" software (under the 10% threshold)
  • The frequent bundling of taxable products with exempt services

While properly structured technology transactions may be partially or fully exempt from Indiana sales tax, failing to maintain adequate documentation or misclassifying transactions can lead to substantial assessments, penalties, and interest charges. The Indiana DOR typically conducts a three-year lookback during audits, but this period can be extended if the auditor suspects significant non-compliance.

This section outlines the key aspects of Indiana 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. Understanding these elements is essential for technology companies to minimize tax exposure and ensure proper compliance with Indiana's evolving tax landscape.

6.1 Common Audit Triggers for Software and Technology Businesses

According to the Indiana Department of Revenue's own published guidance and audit practices, technology businesses are frequently targeted for audits due to specific risk factors. The most common audit triggers include:

  • Failure to Register After Establishing Nexus: Companies that exceed Indiana's economic nexus threshold of $100,000 in sales but fail to collect and remit sales tax. This is particularly relevant for out-of-state SaaS providers who may incorrectly believe their products are universally exempt in all states.
  • Improper Classification of Transactions: Mischaracterizing taxable transactions as non-taxable, such as:
  • Claiming prewritten software with minor modifications is "custom software"
  • Treating bundled hardware/software packages as fully exempt
  • Failing to charge tax on software maintenance agreements that include updates
  • Bundled Transactions Without Separation of Charges: Businesses that sell both taxable and non-taxable services in a single contract or invoice without separately stating the charges could be assessed tax on the entire amount. The Indiana DOR specifically looks for clear itemization on invoices.
  • Inadequate Documentation for Exempt Sales: The burden of proving exempt status falls on the seller. Common documentation failures include:
  • Not obtaining properly completed exemption certificates
  • Lacking contracts that clearly define custom software development scope
  • Missing evidence that software modifications exceed 10% of transaction value
  • Insufficient proof of electronic delivery for software
  • Omissions in Use Tax Reporting: Technology companies often purchase taxable software, IT equipment, or cloud services for internal use from out-of-state vendors without paying Indiana sales tax or self-assessing use tax.
  • Misapplying the Temporary SaaS Exemption: Incorrectly applying the temporary exemption for remotely accessed prewritten software (effective through June 30, 2024) to other types of transactions, or failing to prepare for the exemption's expiration.

Example: An Indiana-based IT consulting firm sells a $25,000 software implementation package that includes $15,000 of prewritten software with $10,000 in customization services. On their invoices, they simply list "Software Solution: $25,000" without itemizing the components. During an audit, the Indiana DOR would likely assess sales tax on the entire $25,000 since the business failed to separately state the taxable software and exempt customization services. This would result in additional tax of $1,750 (7% of $25,000), plus penalties and interest, when properly documented invoices would have limited the tax to $1,050 (7% of $15,000).

Relevant Guidance: Indiana Department of Revenue Audit Manual

6.2 The Indiana Sales Tax Audit Process

The Indiana Department of Revenue follows a structured, multi-phase audit process that typically spans several months. Understanding each stage of this process is essential for technology businesses to prepare effectively and minimize potential tax exposure.

Phase 1: Audit Initiation & Notification

  • Initial Contact: You'll receive an official Audit Commencement Letter from the Indiana DOR identifying the assigned auditor and requesting specific records.
  • Scope Definition: The standard audit period covers 36 months (3 years) but may be extended to 6 years if the DOR suspects significant non-compliance.
  • Deadlines: Indiana typically requires records to be produced within 30 days of the initial notice.

Phase 2: Information Gathering & Document Production

  • Required Documentation: For technology companies, the Indiana DOR specifically requests:
  • Sales and use tax returns with all supporting schedules
  • General ledgers and trial balances
  • Sample invoices for all types of software and service sales
  • Customer contracts showing delivery methods and service terms
  • Exemption certificates for all exempt sales
  • Documentation of electronic delivery for software
  • Software license agreements
  • Maintenance and support agreements
  • Format Requirements: The DOR increasingly requests records in electronic format through secure file transfer protocols.

Phase 3: Field Examination & Sampling

  • Statistical Sampling: For businesses with high transaction volumes, Indiana auditors typically use statistical sampling methods to select representative transactions for detailed review.
  • Targeted Examination: Special attention is directed toward:
  • Classification of software as prewritten vs. custom
  • Documentation of electronic delivery
  • Verification of exempt sales
  • Proper application of the temporary SaaS exemption
  • Bundled transactions and whether charges are properly separated
  • Extrapolation: Errors found in the sample are systematically projected across the entire audit period using statistical methods.

Phase 4: Preliminary Assessment & Response

  • Working Papers: The auditor shares preliminary findings through detailed working papers showing proposed adjustments.
  • Response Period: Businesses typically have 30 days to review the findings and provide additional documentation or explanations.
  • Negotiation Opportunity: This phase represents the best opportunity to resolve disputed items before formal assessment.

Phase 5: Final Assessment & Appeal Options

  • Proposed Assessment: If disagreements remain, the DOR issues a Proposed Assessment with detailed tax calculations.
  • Appeal Rights: Businesses can challenge findings through:
  • Request for Rehearing (must be filed within 60 days)
  • Formal protest to the DOR's Protest Section
  • Appeal to the Indiana Tax Court (if administrative remedies are exhausted)
  • Payment Terms: Unpaid assessments begin accruing interest (currently at variable rates published quarterly by the DOR) and may be subject to collection actions.

Example: A SaaS provider undergoing an Indiana audit initially received a preliminary assessment of $85,000 in unpaid sales tax. By providing contracts demonstrating that its software was remotely accessed (qualifying for the temporary exemption through June 30, 2024) and properly documenting custom software modifications, the company was able to reduce the final assessment to $12,000, representing only the truly taxable transactions.

Relevant Guidance: Indiana Department of Revenue Audit Procedures

6.3 Best Practices for Handling an Audit

Technology companies can substantially reduce audit risk and potential assessments by implementing structured compliance practices specifically tailored to Indiana's tax rules. Based on successful audit defense strategies and Indiana DOR guidance, we recommend the following comprehensive approach:

Pre-Audit Preparation

  • Implement Robust Documentation Systems
  • Maintain all records for at least 7 years (Indiana's statute of limitations for fraudulent non-reporting)
  • Create transaction categorization systems that align with Indiana's tax categories
  • Establish a central repository for all exemption certificates, electronic delivery confirmations, and contracts
  • Document delivery methods for all software (physical media vs. electronic delivery)
  • Transaction Structure & Invoice Design
  • Clear Itemization: Structure all invoices with separate line items for:
  • Prewritten software (taxable)
  • Custom software development (exempt)
  • Installation services (may be exempt if separately stated)
  • Training services (exempt)
  • Maintenance agreements (typically taxable if they include updates)
  • Documentation Language: Include specific language on invoices and contracts such as:
  • "Custom software developed to customer specifications per contract dated [DATE]"
  • "Software electronically delivered via [METHOD] on [DATE]"
  • "Remotely accessed software - No download to customer"
  • Regular Self-Audits
  • Conduct quarterly internal reviews of sales tax compliance
  • Sample transactions from each business segment to verify proper tax treatment
  • Address any discrepancies immediately through amended returns

Active Audit Management

  • Initial Response Protocol
  • Designate a primary audit coordinator with decision-making authority
  • Request an opening conference to clarify audit scope and timeline
  • Negotiate reasonable timeframes for document production
  • Consider engaging tax professionals for audits covering significant periods or revenue
  • Strategic Documentation Presentation
  • Organize records by transaction type rather than chronologically
  • Prepare explanatory narratives for complex transaction structures
  • Create visual aids explaining your business model and software delivery methods
  • Provide examples of electronic delivery confirmation records
  • Proactive Issue Resolution
  • Address preliminary findings immediately with supporting documentation
  • Request regular status meetings throughout the audit process
  • Submit written positions on contested items with citation to relevant Indiana statutes
  • Consider voluntary disclosure of known errors to demonstrate good faith

Example: During an Indiana audit, a software company selling both prewritten and custom software maintained detailed documentation showing which customers received purely electronic delivery. For a $150,000 implementation project, their contract and invoices clearly separated the $75,000 prewritten software component (taxable), $50,000 custom modification component (exempt), and $25,000 training services (exempt). The company provided screenshots documenting electronic delivery and maintained certificates for exempt sales. When audited, the clear documentation resulted in zero adjustments to their reported tax, while a competitor with similar sales but poor documentation received a $32,000 assessment.

Practical Compliance Checklist:

  • [ ] Update invoice templates to separately state taxable and exempt components
  • [ ] Implement electronic delivery confirmation system with automated documentation
  • [ ] Develop process for validating and storing exemption certificates
  • [ ] Create tax decision matrix for product and service offerings
  • [ ] Schedule quarterly internal compliance reviews
  • [ ] Monitor Indiana's temporary SaaS exemption status (expires June 30, 2024)
  • [ ] Consult with tax professionals on complex transactions

Relevant Guidance: Indiana Department of Revenue Audit Best Practices

6.4 Specific Audit Risks for Software and Technology Companies

Software and technology companies face unique audit risks in Indiana, including:

  • SaaS Transactions Post-Exemption: Companies must plan for the potential expiration of the temporary exemption for remotely accessed prewritten software on July 1, 2024.
  • Incidental Software Determination: Proving that software provided as part of a service is "incidental" (less than 10% of the transaction value) requires clear documentation and pricing structures.
  • Software Maintenance Contracts: The taxability of maintenance agreements can be complex, and auditors often scrutinize these contracts to ensure proper tax treatment.
  • Multi-State Transactions: For businesses operating across multiple states, auditors may review how software licenses and digital services are allocated among different jurisdictions.

Conclusion

Indiana sales tax audits can be complex, particularly for software and SaaS providers navigating the state's evolving tax rules for digital products. 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 tax classification of software, hardware, and services.
  • Maintain clear documentation of exemption claims and nexus compliance.
  • Separate taxable and non-taxable elements in bundled transactions.
  • Stay informed about temporary exemptions and their expiration dates.
  • Regularly review compliance with Indiana DOR sales tax regulations.

For additional audit guidance, visit the Indiana Department of Revenue Audit and Enforcement 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 Indiana, 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 tangible software or bundled transactions that include taxable components.

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

7.1 When Should a Software Business Consider a VDA?

Indiana's VDA program is designed to encourage businesses to voluntarily comply with tax laws before being contacted by the Indiana Department of Revenue for an audit. Software and technology companies should consider a VDA if they:

  • Exceeded Indiana's Economic Nexus Threshold Without Registering: Businesses that surpassed the $100,000 sales threshold but failed to register and collect sales tax.
  • Incorrectly Classified Software or Bundled Transactions: If taxable software or hardware was sold but mistakenly classified as exempt, a VDA can help correct the error before an audit occurs.
  • Missed Use Tax Payments on Business Purchases: Companies that purchased taxable software or IT equipment from out-of-state vendors without paying Indiana sales tax.
  • Need to Resolve Historical Noncompliance: If a company recently discovered it had sales tax obligations in Indiana for past periods, a VDA can help mitigate penalties and limit exposure.
  • Uncertain About SaaS Taxability: Given the temporary exemption and conflicting guidance, companies with potential past liabilities related to SaaS transactions may benefit from a VDA.

7.2 Benefits of Indiana's VDA Program

By entering into a VDA, businesses can benefit from:

  • Limited Lookback Period: Indiana's standard audit lookback period is generally three years, but the VDA program may offer a more favorable lookback period.
  • Penalty Relief: In many cases, penalties for late registration and uncollected tax may be waived or reduced.
  • Interest Reduction: While interest generally cannot be waived completely, partial interest reduction may be available in some cases.
  • Reduced Risk of Audit Assessments: Voluntarily addressing tax issues prevents the possibility of a full audit with additional penalties and interest.
  • Confidential Process: The VDA process allows businesses to initially approach the DOR anonymously through a representative.

7.3 The Indiana VDA Process

Indiana's Voluntary Disclosure Agreement process follows a structured protocol designed to encourage compliance while providing businesses with a degree of certainty about their tax exposure. For technology companies concerned about past software and SaaS transaction treatment, the VDA process offers a controlled pathway to compliance.

Phase 1: Anonymous Initial Contact & Eligibility Verification

  • Anonymous Preliminary Application
  • Businesses must apply through a third-party representative (typically a CPA or attorney)
  • The representative submits an anonymous letter describing:
  • Nature of the business and transactions
  • States in which the business operates
  • Period for which disclosure is sought
  • Estimate of potential tax liability
  • No identifying information is shared during this phase
  • Eligibility Confirmation
  • The Indiana DOR's Voluntary Disclosure Program Administrator reviews the application to verify:
  • The business is not currently under audit by Indiana
  • The business has not been previously contacted about the disclosed tax issues
  • The business is not registered for the tax type being disclosed
  • The disclosure involves genuine uncertainty rather than deliberate non-compliance
  • Preliminary Terms Negotiation
  • Look-back period determination (typically 3 years, but negotiable)
  • Penalty waiver confirmation
  • Interest calculation methodology
  • Filing requirements clarification

Phase 2: Formal Agreement Development & Execution

  • Formal Agreement Preparation
  • The DOR prepares a formal VDA outlining:
  • Tax types covered
  • Look-back period
  • Penalty waiver provisions
  • Payment terms
  • Filing requirements
  • Registration procedures
  • Business Identification & Agreement Execution
  • The business is formally identified to the DOR
  • Both parties execute the VDA
  • The business completes necessary registration with the Indiana DOR

Phase 3: Compliance Implementation & Payment

  • Tax Return Filing
  • Businesses must file all returns for the covered periods within 60 days of executing the agreement
  • Returns must include detailed transaction schedules and supporting documentation
  • Tax and Interest Payment
  • Full payment of agreed-upon tax and interest is typically required within 90 days of agreement execution
  • Payment plans may be available for large assessments (subject to DOR approval)
  • Registration for Future Compliance
  • Businesses must register with the Indiana DOR
  • All future filing and payment obligations must be met on a timely basis

Example Scenario: A SaaS provider had been operating in Indiana for 5 years without collecting sales tax, believing all its products were exempt. After consulting with a tax advisor, the company discovered that some bundled offerings might be taxable. Through the VDA process, the company:

  • Anonymously disclosed the situation through their attorney
  • Negotiated a 3-year lookback period instead of 5 years
  • Received full penalty waiver (saving approximately $8,500)
  • Paid $42,000 in back taxes plus interest
  • Implemented proper tax collection procedures going forward

The entire process took approximately 5 months from initial contact to resolution, compared to what could have been a multi-year audit with full penalties if discovered by the Indiana DOR.

Relevant Guidance: Indiana Department of Revenue Taxpayer Advocate

7.4 VDA Considerations for Software and SaaS Companies

Software and SaaS companies in Indiana face unique considerations when participating in the VDA program:

  • Changing Taxability Rules: The temporary exemption for remotely accessed prewritten software (through June 30, 2024) may create uncertainty about past liabilities.
  • Classification Challenges: Determining whether software was prewritten or custom, or whether services were taxable or exempt, requires careful analysis.
  • Bundled Transactions: If software was bundled with taxable hardware or services without separately stating taxable and non-taxable components, complex calculations may be needed to determine the correct tax liability.
  • Multi-State Operations: Companies operating across multiple states must consider how their VDA in Indiana will affect their compliance position in other states.

Example: A software company discovers it should have been collecting sales tax on prewritten software delivered on physical media to Indiana customers. Through the VDA program, the company can voluntarily disclose these past liabilities, potentially receiving penalty relief and a limited lookback period.

7.5 Best Practices for a Successful VDA Submission

To maximize the benefits of a VDA and ensure a smooth process, businesses should:

  • Conduct an Internal Review: Assess all past sales transactions, exemptions, and nexus-triggering activities.
  • Properly Classify Transactions: Verify whether sales should have been taxed based on Indiana's tax rules.
  • Document Exemption Claims: Gather documentation supporting exempt sales and transactions.
  • Engage a Tax Professional: An experienced tax advisor can help navigate the VDA process and negotiate favorable terms.
  • Prepare for Future Compliance: Implement procedures to collect and remit sales tax correctly moving forward to avoid recurring liabilities.
  • Monitor Regulatory Changes: Stay informed about upcoming changes, such as the expiration of temporary exemptions.

Conclusion

For software and technology companies, Indiana's Voluntary Disclosure Program offers a strategic opportunity to resolve past sales tax liabilities while minimizing penalties and audit risks. Businesses that failed to register for sales tax, misclassified transactions, or omitted use tax payments should consider utilizing a VDA to become compliant without facing severe penalties.

Key takeaways:

  • A VDA helps businesses resolve past-due tax liabilities while securing penalty relief.
  • Software and SaaS providers face unique challenges related to Indiana's evolving tax rules.
  • Anonymous initial disclosure allows businesses to assess their liability before formal identification.
  • Proper preparation and professional guidance are essential for a successful VDA process.

For additional details and to apply, visit the Indiana Department of Revenue Voluntary Disclosure Program Page.

8. Conclusion

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

Navigating Indiana's sales and use tax laws for software, SaaS, and technology services requires a deep understanding of transaction classification, sourcing rules, and compliance obligations. Indiana's approach to taxing software and digital services involves important distinctions between prewritten and custom software, physical and electronic delivery methods, and various service classifications. Failure to properly classify transactions, maintain exemption documentation, or track nexus thresholds can result in unexpected tax liabilities and audit exposure.

Key Takeaways

The complexity of Indiana's tax rules means that businesses must take a proactive approach to compliance. Companies exceeding Indiana's $100,000 economic nexus threshold must register and collect sales tax. Similarly, businesses with a physical presence in Indiana—whether through employees, inventory, or business activities—must also comply with sales tax obligations.

Understanding what is taxable and what is exempt is essential:

  • Computer hardware is generally taxable unless used directly in manufacturing.
  • Prewritten (canned) software is taxable as tangible personal property, even when delivered electronically.
  • Custom software is exempt as a professional service.
  • Software maintenance agreements are generally taxable due to the presumption that updates will be transferred.
  • Through June 30, 2024, remotely accessed prewritten software (SaaS) is not considered a retail transaction and is exempt from sales tax.
  • Professional services related to software, including consulting and IT support, are generally exempt.

Indiana follows destination-based sourcing for tangible software transactions, with sales tax applied based on the customer's location. For multi-state operations, careful allocation of software licenses may be required to determine the appropriate tax jurisdiction.

Audit risks arise when businesses fail to properly document tax-exempt sales, misclassify taxable software as exempt, or omit use tax reporting on taxable business purchases. Keeping thorough records, separating taxable and non-taxable elements in invoices, and maintaining exemption documentation can significantly reduce the risk of assessments during an audit. In cases where past compliance issues arise, Indiana's Voluntary Disclosure Agreement (VDA) program offers an opportunity to correct errors, limit penalties, and reduce tax exposure before an audit occurs.

Next Steps

As the technology sector continues to evolve, Indiana's approach to taxing software and digital services may change. The scheduled expiration of the temporary exemption for remotely accessed prewritten software on July 1, 2024, represents a significant upcoming change that businesses must prepare for. Companies must stay ahead by monitoring regulatory updates, conducting internal tax reviews, and seeking professional tax guidance when necessary.

Ensuring compliance with Indiana'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 Indiana's tax regulations, businesses should refer to official resources:

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

9. References & Resources

Indiana Department of Revenue Resources

Audit & Compliance

  • Indiana Sales Tax Audits: Information on the Indiana Department of Revenue's audit process, taxpayer rights, and procedures for disputed assessments – Indiana DOR Audit Process
  • Voluntary Disclosure & Compliance Program: Official page detailing how to proactively disclose past liabilities, often reducing penalties and limiting look-back periods – Indiana DOR VDA Program

Key Indiana Statutory & Regulatory References

  • Indiana Code § 6-2.5: General provisions on sales and use tax, including definitions of taxable goods and services
  • Indiana Code § 6-2.5-4-16.7: Temporary exemption for remotely accessed prewritten computer software (expires July 1, 2024)
  • Sales Tax Information Bulletin #8: Application of Sales Tax to the Sale, Lease, or Use of Computer Hardware, Computer Software, and Digital Goods
  • Indiana Administrative Code 45 IAC 2.2: Sales and use tax regulations

Digital Products and Software-Specific Resources

  • Sales Tax Information Bulletin #8: Comprehensive guidance on computer hardware, software, and digital goods – SIB #8
  • Economic Nexus Information: Details on Indiana's economic nexus thresholds – Remote Seller Information
  • Marketplace Facilitator Guidance: Information for marketplaces selling software and digital products – Marketplace Facilitators

Additional Guidance & Compliance Support

Armed with these Indiana-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 information bulletins and administrative rules, especially as technology evolves and new rulings are issued.

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 Indiana software and SaaS questions

Create a free Sales Tax Helper account to check your nexus exposure and keep your Indiana 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