Last verified with: 10.8.6.0
Overview #
Tax Exemptions in LogiSense Billing give businesses a structured way to control when taxes should not be applied to an account, a service, or a specific category of tax obligation.
This is important because exemption handling is rarely just a simple yes or no decision. Some customers are fully exempt. Some are exempt only for certain services. Others may be exempt only at specific tax levels, for certain tax types, or in particular jurisdictions.
The platform is designed to support that reality while keeping exemption handling tied directly to billing and taxation workflows.
What Tax Exemptions Are #
At a business level, a Tax Exemption tells the platform that taxes should not be charged in situations where the customer or service qualifies for exempt treatment.
That exempt treatment may apply:
- to the entire account,
- to a specific service,
- to all taxes,
- or, in supported tax configurations, only to certain tax levels, tax types, or jurisdictions.
This allows the business to reflect real customer tax status in billing rather than relying on manual adjustments after the fact.
How They Work #
From a business perspective, the model is straightforward:
- A taxable charge is created for a service, package, usage event, or manual transaction.
- The platform determines which tax rules apply based on the account, service, usage class, tax category, and tax address.
- Before taxes are finalized, the platform checks whether a relevant Tax Exemption exists.
- If an exemption applies, the exempt taxes are removed or not charged.
- The invoice or transaction then reflects only the taxes that remain applicable.
This means Tax Exemptions are not handled as a separate side process. They are part of the actual tax decision.
Main Exemption Models #
The platform supports more than one business pattern for exemption handling.
Account-Level Tax Exemptions #
An Account-Level Tax Exemption applies to the customer relationship as a whole.
This is the right model when the customer itself qualifies for exemption based on who they are, what type of organization they are, or what certificate or exemption status they hold.
Examples:
- a nonprofit customer,
- a government entity,
- a reseller,
- or a business with a valid exemption certificate.
Benefit:
- Keeps exemption handling tied to the customer instead of repeating the same setup across many services.
- Helps ensure taxes are handled consistently across the account.
- Reduces manual tax correction work.
Service-Level Tax Exemptions #
A Service-Level Tax Exemption applies to a specific service rather than to the account as a whole.
This is useful when a service should always be treated as exempt regardless of the rest of the account’s tax posture.
Examples:
- a service that is non-taxable by design,
- a regulated charge that must not be taxed,
- or a product that is exempt in the tax model being used.
Benefit:
- Gives the business a precise product-level control.
- Avoids over-exempting the entire account when only one service should be exempt.
- Supports cleaner product tax governance.
Granular Exemptions #
One of the more powerful aspects of the platform is that exemptions can be more granular when the tax configuration supports it.
Exemptions By Tax Level #
An exemption can be configured to apply only to certain tax levels, such as:
- federal,
- state,
- county,
- or local.
This is valuable when a customer is exempt from one layer of tax but not from others.
Benefit:
- Supports real-world tax complexity.
- Prevents over-exempting taxes that should still apply.
- Helps businesses comply with more nuanced customer tax treatments.
Exemptions By Tax Type #
In supported tax models, an exemption can also target a particular type of tax instead of applying to everything.
Examples:
- exempt from E911 taxes,
- exempt from excise taxes,
- or exempt from one specific usage-related tax while still paying others.
Benefit:
- Supports highly specific tax obligations.
- Helps businesses reflect certificate-driven or product-driven exemptions more accurately.
- Improves precision in regulated markets such as Telecom and IoT.
Exemptions By Jurisdiction #
The platform can also support exemptions tied to a particular tax jurisdiction.
That means a customer may be exempt in one state, county, or local area, while remaining taxable elsewhere.
Benefit:
- Supports geographically specific exemption rules.
- Important for organizations operating across many tax regions.
- Helps taxation reflect where the charge is actually being taxed.
Why Tax Address Matters #
Tax Exemptions only work properly when the system knows which tax address is being used for taxation.
That matters because exemption handling can depend on the jurisdiction of the taxed transaction. If taxes are being calculated based on the invoicer account’s tax address, then the exemption settings on that invoicer context may be the ones that matter. If taxes are being calculated based on the sub-account or service context, then those exemption settings may apply instead.
In other words, exemption handling is not just about the exemption record itself. It also depends on the tax address and tax context used during calculation.
Differences By Tax Engine #
This is an important concept for customers to understand.
The platform supports multiple taxation approaches, and exemption behavior can differ depending on which tax engine is being used.
Local Taxing #
When using the local LogiSense tax engine, exemption handling is simpler. In that model, exemptions are effectively treated as a complete tax exemption decision rather than a deeply granular tax-by-tax exemption model.
Benefit:
- Straightforward for simpler tax environments.
- Easier to manage where broad tax exemption treatment is sufficient.
AvaTax-Oriented Exemption Models #
When using AvaTax-based taxation, the platform can support more detailed exemption handling depending on the integration pattern.
This includes support for exemption behavior tied to:
- account context,
- service context,
- tax levels,
- tax types,
- and jurisdiction-specific logic,
where that tax model supports those distinctions.
For AvaTax Sales specifically, exemption handling is typically simpler at the account level and centers on passing the exemption reference needed for AvaTax to honor the exemption.
Benefit:
- Supports more sophisticated tax compliance needs.
- Better aligns with enterprise and regulated-market tax requirements.
- Makes it possible to manage complex exemption scenarios inside the billing flow.
Business Benefits #
Tax Exemptions provide value in several important ways:
- Better tax accuracy. Taxes are reduced or removed based on defined exemption rules instead of relying on manual corrections.
- Reduced billing friction. Customers do not need to dispute taxes that should never have been charged in the first place.
- Better compliance support. The platform can reflect customer tax treatment more closely to documented exemption status.
- More precise handling of complex tax scenarios. Businesses can model exemptions by account, service, level, type, or jurisdiction where supported.
- Less manual crediting and rebilling. Correct treatment happens earlier in the process, which reduces downstream cleanup work.
- Better control across large customer portfolios. Exemptions can be configured and reused consistently instead of being handled ad hoc.
Telecom Examples #
Exemption From Specific Regulatory Taxes #
A telecom provider may have a customer who is exempt from a specific regulatory or communications-related tax, but not from all other taxes.
Benefit:
- Supports industry-specific tax rules.
- Prevents unnecessary over-exemption.
- Helps align billing to customer-specific telecom tax treatment.
Jurisdiction-Specific Exemptions #
A provider may need to exempt a customer from certain state or local taxes in one location while continuing to charge taxes in other regions.
Benefit:
- Supports geographically complex taxation.
- Important for multi-state and multi-jurisdiction telecom operations.
- Helps ensure exemption treatment follows the taxed location.
Service-Level Exemption For Specific Charges #
A telecom business may offer a service or charge type that should always be treated as exempt.
Benefit:
- Keeps exemption logic attached to the product itself.
- Avoids account-wide over-exemption when only one service qualifies.
- Makes tax treatment more maintainable across many customer accounts.
SaaS Examples #
Nonprofit Or Government Customer Exemption #
A SaaS provider may have customers whose organization type qualifies them for tax-exempt treatment at the account level.
Benefit:
- Supports common B2B software tax scenarios.
- Avoids repetitive service-by-service exemption setup.
- Helps account taxation stay aligned to customer status.
Exempt Service Within A Mixed Invoice #
A software business may sell a combination of taxable and exempt items on the same account.
Benefit:
- Allows exempt and taxable services to coexist cleanly.
- Improves invoice accuracy.
- Reduces the need to split customers across artificial account structures just for tax handling.
Jurisdiction-Aware Exemption Handling #
A SaaS provider selling across multiple regions may need different exemption treatment depending on where the taxed transaction is sourced.
Benefit:
- Supports broader geographic expansion.
- Aligns tax handling to regional obligations.
- Reduces risk when the same customer operates in different jurisdictions.
Why Customers Value This Capability #
Customers value Tax Exemptions because they help ensure taxes are applied correctly without forcing finance or billing teams into constant exception handling.
The capability is especially important when customers have documented exemption status, when only some taxes should be removed, or when taxation depends on where a customer or service is located. In those cases, accurate exemption handling protects customer trust, reduces disputes, and lowers the operational burden of tax correction work.
For providers, the larger value is control. Tax Exemptions allow the billing system to reflect real tax obligations more accurately, support more sophisticated tax scenarios, and scale taxation processes without turning every exception into a manual process.