What’s in a Name? Why a Delivery Fee May Still Be Part of the Price

A business owner sits at their desk late at night, staring at an invoice template that refuses to feel “done.” On one line is a fuel surcharge meant to recover rising shipping costs. On another is a retail delivery fee, a state-required charge that must be labeled and listed correctly if passed through and collected. The owner knows both amounts matter, but figuring out how to list them without creating tax exposure feels exhausting.

They replay the same questions on a loop. Should these fees be combined or separated? Are they both taxable? Does wording matter more than function? What happens if an auditor decides the invoice is wrong?

By the time they finally shut down their laptop, they have not solved the issue. Instead, they fall asleep thinking about audit notices, penalties, and state reviewers questioning every line item. The fear is not theoretical. It is personal, and it is familiar to anyone responsible for sales tax decisions.

If this scenario feels close to home, the Sales Tax Institute’s May webinar, Is It a Tax or a Fee? How Classification Shapes the Sales Tax Base is designed for exactly these situations. Register here to learn the difference between fees and taxes, and why that distinction is so important.

Situations like this are becoming more common as states introduce new fees and businesses layer on their own charges to manage rising costs. What used to be a simple invoice is now a mix of seller-imposed fees and state-specific obligations, each with its own rules, risks, and audit consequences. Understanding how these charges differ, and why that difference matters, is quickly becoming as critical as the tax calculations themselves.

Seller Imposed Fees: What They Are and Why Businesses Use Them

Seller-imposed fees are charges created by the business, not required by statute. Common examples include delivery surcharges, service fees, processing fees, handling charges, environmental recovery fees, and convenience fees. Businesses often add them to offset costs that are difficult to absorb into base pricing, especially when margins are tight or expenses fluctuate.

The purpose of these fees varies. A delivery surcharge may recover carrier rate increases. A service fee may support staffing or technology costs. An environmental fee may reflect internal sustainability initiatives rather than a state mandate. Whatever the motivation, the key feature is that the seller controls whether the fee exists and how it is calculated.

This control is also where risk begins. Because the fee is seller-imposed, state tax authorities usually look past the label and examine what the charge is connected to. If the fee is required to complete a taxable sale, many states consider it part of the sales price. Separately stating it does not automatically remove it from the tax base.

Before imposing a seller-created fee, businesses should step back and ask several questions:

• What is the fee intended to recover?
• Is the fee mandatory to the customer?
• How is the fee calculated?
• How does state law define sales price?
• How will the fee appear across systems?

Seller-imposed fees often start as operational decisions, but once they appear on an invoice, they become tax decisions often with no input from or knowledge by the tax function. Without a clear classification framework, these charges can quietly expand audit exposure.

Retail Delivery Fees: State Specific Charges With Unique Obligations

Government imposed retail delivery fees are fundamentally different. These are not charges created by the seller. They are fees established by state or local authorities, often to fund things like transportation or infrastructure initiatives as fuel tax revenues decline.

Colorado’s retail delivery fee is one of the clearest examples. The fee applies per order when at least one taxable item is delivered by motor vehicle to a Colorado location. When sellers choose to pass the fee on to customers, the law requires it to be separately stated on the invoice or receipt as “Retail Delivery Fee.”

The purpose of this fee is not to recover costs for the seller. It is a statutory obligation imposed on the transaction. That distinction matters because it affects who is responsible for the fee, how it must be disclosed, and how it should be reported.

Retail delivery fees also introduce operational complexity. Minnesota’s retail delivery fee highlights this complication. The fee applies only when delivered items meet certain price thresholds and unlike Colorado’s fee, can be imposed on items that are exempt from sales tax such as clothing but not apply to items subject to sales tax such as infant items. Collection from the purchaser is optional, not mandatory. Marketplace responsibility depends on prior-year sales levels, meaning sellers cannot assume the platform will handle the obligation. And for both Colorado and Minnesota, they have a higher threshold for when a seller is subject to the retail delivery fees than their sales tax economic nexus thresholds.

These fees require careful classification because they are neither traditional taxes nor purely optional charges. Treating them like ordinary seller-imposed fees can create reporting and documentation problems almost immediately.

Audit Risk When Fees Are Misclassified or Misreported

The real danger arises when seller-imposed fees and state-specific fees collide on an invoice.

Imagine a Colorado retailer that adds a line item called “delivery surcharge” to recover shipping costs. The retailer also collects the Colorado retail delivery fee. To simplify invoicing, both amounts are combined into one line on the invoice.

From a customer perspective, the invoice may still show a single delivery-related charge. From a compliance perspective, the setup is flawed. Colorado requires the retail delivery fee, when passed on to the customer, to be shown separately and clearly identified as “Retail Delivery Fee.”

The issue is not just wording. Combining the fees makes it difficult to support several critical compliance questions. If an auditor reviews the invoice, the business now bears the burden of untangling that one line item. Without clear separation, documentation, and system logic, the audit can expand quickly. Penalties may apply if fees were collected but not remitted correctly, or if tax was undercollected due to misclassification.

This scenario shows how easily a good-faith invoicing choice can turn into a compliance problem when seller-imposed and state-mandated fees are blended together.

When Separate Statement Still Was Not Enough: Big Sky Resort

A real-world case from Montana reinforces why labels alone do not control sales tax outcomes.

Big Sky Resort charged guests a mandatory “Resort Services Fee,” which was separately stated on customer invoices. The resort believed this presentation supported exclusion from accommodations sales tax. During an audit, the Montana Department of Revenue disagreed and assessed additional tax, interest, and penalties on the fee.

The dispute ultimately reached the Montana Supreme Court. The court held that the resort services fee was subject to accommodations sales tax, despite being separately listed. The deciding factor was not how the fee appeared on the invoice. It was the nature of the fee and its relationship to the taxable lodging transaction. The resort service fee was deemed to be part of the accommodation service and the fact that it was separately stated didn’t qualify it to be excluded from the accommodation price. (Boyne USA, Inc. v. State of Montana, Department of Revenue, Montana Tax Appeal Board, Case No. SPT-2018-24 (June 12, 2019)).

The takeaway from Big Sky Resort is not that every fee will be taxed. The lesson is that a separate statement does not override statutory definitions. Auditors and courts focus on substance over form, especially when a fee is mandatory and inseparable from the underlying sale.

For professionals responsible for sales tax decisions, this case is a reminder that invoices are evidence, not authority. The authority comes from state law and how the charge functions within the transaction.

Clarity Before the Audit, Not During It

Seller-imposed fees and state-specific fees often appear side by side on an invoice, but they do not play by the same rules. They exist for different reasons, draw authority from different sources, and create different types of audit exposure. Treating them as interchangeable can leave gaps that only become visible once an auditor starts asking questions.

Audits rarely stop at invoice language. State reviewers look at policies, contracts, system setup, checkout logic, and how amounts flow through returns. When a business cannot clearly explain why a fee exists, how it was classified, or under what authority it was collected, the scope of the review tends to expand. What looked like a simple line item can turn into a broader compliance issue.

That risk grows when tax is asked to weigh in after fees are already live. By then, fixing invoice design, system logic, and customer communications is far more disruptive. The professionals who avoid that scramble are the ones who understand the distinction between seller discretion and statutory obligation early enough to influence how fees are structured and disclosed.

Separately stated does not always mean separately taxed. The real safeguard is defensible classification backed by state law, transaction facts, and consistent system treatment. For the business owner staring at that unfinished invoice late at night, the difference between combining those fees and treating them correctly is not just formatting, it is the line between confidence and exposure.

If questions about fees are keeping you up at night or making you uneasy, the Sales Tax Institute’s May webinar, Is It a Tax or a Fee? How Classification Shapes the Sales Tax Base will help you evaluate seller-imposed charges and state-mandated fees with confidence. Reserve your spot now so you can sharpen your judgment today, before scrutiny arrives.