United States: Federal District Court Holds OTCs Not Liable For Georgia Hotel Taxes For Prior Transactions
Last Updated: September 27 2012
Article by Grant Thornton's Washington National Tax Office

The U.S. District Court of the Northern District of Georgia has ruled that online travel companies (OTCs) that facilitate hotel reservations were not liable for taxes on the amounts paid by consumers to book the rooms for transactions taking place on or before May 16, 2011.1 However, had the municipalities seeking the tax presented evidence to compute the damages, the Court may have granted them with respect to the OTCs' failure to collect proper tax amounts on "breakage transactions" that occurred on or prior to May 16, 2011.2

Background

Municipalities in Georgia filed a suit against a group of OTCs for failure to identify taxes charged and paid by hotel guests and for failure to remit the taxes. The municipalities subsequently filed a motion for summary judgment based on the Georgia Supreme Court's decision, City of Atlanta v. Hotels.com,3 which held that the OTCs were not liable for back taxes. In a partial settlement agreement, the parties agreed to pay the difference between the hotel occupancy tax calculated on the wholesale rate versus the tax calculated on the retail rate for all hotel occupancies occurring after May 16, 2011.

Online Travel Companies

OTCs book hotel rooms and make other travel arrangements for customers over the Internet under what has been labeled the "merchant model" of business. OTCs first enter into contracts with individual hotels and negotiate a discounted rate for each hotel room, commonly termed the wholesale rate. OTCs then offer reservations of the rooms to the public at a rate that includes the amount paid to the hotel operator plus taxes and service fees. When a customer books and pays the total amount to an OTC, the OTC pays the wholesale rate and hotel occupancy taxes to the hotel. After customers complete their stay at a hotel, the hotel remits the taxes to the appropriate taxing authorities.

Hotel Occupancy Tax

Georgia's excise tax on rooms, lodging, and accommodations (the Enabling Statute) authorizes a municipality to impose and collect an excise tax on accommodations furnished by a person or legal entity licensed by, or required to pay business or occupation taxes to, the municipality for "operating a hotel ... or accommodations," which "are regularly furnished for value."4

Under the Enabling Statute, the hotel occupancy tax is imposed on "any person or legal entity licensed by or required to pay a business or occupation tax to the governing authority imposing the tax for operating a hotel ... or accommodations ... and shall apply to the furnishing for value of any room, lodging, or accommodation."5

With respect to the tax base, the tax applies to "the lodging charges actually collected, or if the amount of taxes collected from the hotel or motel guest is in excess of the total amount that should have been collected, the total amount actually collected must be remitted."6 The Enabling Statute provides that the person or entity collecting the tax is required to remit the tax to the governing authority.7

The Georgia Supreme Court, in City of Atlanta and City of Columbus,8 determined that the Enabling Statute required OTCs to remit hotel occupancy taxes based on the retail rate on a prospective basis "so long as" they continued to voluntarily collect and remit the taxes, but that the OTCs were not required to pay back taxes. According to the Georgia Supreme Court, if the OTCs ceased to collect the tax, then the issue would be "moot." The Georgia Supreme Court also found that the enforcement provisions of the Enabling Statute only applied to "innkeepers" or "hotel operators" and that the OTCs were neither. Therefore, the municipalities did not have a remedy for back taxes.

Claims for Back Taxes

The municipalities made several arguments to allege that they were entitled to back taxes (taxes which would have been incurred on or prior to May 16, 2011) because the OTCs violated the Enabling Statute by failing to collect and remit the proper amount of hotel occupancy taxes based on the retail rate.

Third-Party Tax Collectors

The municipalities argued that they were entitled to back taxes because the OTCs were third-party tax collectors. According to the municipalities, City of Atlanta established that OTCs were third-party tax collectors under the Enabling Statute and as such, they were required to collect tax on the full rental rate charged to the consumer. They also maintained that City of Atlanta had retroactive effect, permitting a remedy for back taxes.

The Court disagreed, stating that it was bound by the state's interpretation of its own laws. Judicial decisions generally have retroactive effect, but state courts may "limit the retroactive operation of their own interpretations of the law."9 This is precisely what the Georgia Supreme Court accomplished in City of Atlanta by explicitly holding that municipalities do "not have a remedy for back taxes." The Georgia Supreme Court found that the collection provisions of the Enabling Statute applied prospectively and that only the enforcement provisions applied retroactively. The Court followed the Georgia Supreme Court's interpretation and determined that the enforcement provisions applied to "innkeepers and hotel operators" and did not apply to third-party tax collectors.

Innkeepers and Operators

The municipalities also argued that the OTCs were liable for back taxes because they were subject to the enforcement provisions of the Enabling Statute as "innkeepers and operators." In support of this argument, the municipalities asserted that the OTCs were innkeepers and operators since they assumed the role of hotels in "virtually every aspect of dealing with consumers leading up to the taxable transaction." The Court rejected this argument, pointing to the Georgia Supreme Court's holding, in City of Atlanta, that OTCs are not innkeepers or operators as a matter of law. The Court followed this decision and found that the enforcement provisions of the Enabling Statute did not apply.

Taxes Collected but Not Remitted

As an alternative argument, the municipalities took the position that the OTCs were liable for back taxes because they collected and failed to remit excess taxes. Pursuant to the Enabling Statute, any person or entity collecting the hotel occupancy tax is required to remit "lodging charges actually collected" or any taxes collected "in excess of the total amount that should have been collected."10

According to the municipalities, in non-breakage transactions, the OTCs collected tax on the retail rate of a room while remitting tax only on the wholesale rate, and in breakage transactions, the OTCs charged consumers for taxes and fees but failed to remit any taxes to the hotels or the municipalities.11

With respect to the non-breakage transactions, the Court did not find that the OTCs collected excess taxes. Although the OTCs presented taxes and service fees as a combined charge on customer invoices, there was no authority showing that such combined charges "were actually collected only as taxes." Furthermore, the cases that the municipalities relied upon stated the rule that substance controls over form when it came to the characterization of an underlying transaction. In the present case, the issue was characterizing the amounts collected from a consumer (and not the underlying transaction).

With respect to the breakage transactions, however, the Court found that the OTCs were liable for taxes based on the retail rate for transactions occurring after May 16, 2011. Georgia law requires the OTCs to pay taxes "actually collected" or any taxes collected "in excess of the amount that should have been collected,"12 and the evidence showed that the OTCs did, in fact, collect excess taxes on breakage transactions. When a hotel failed to invoice an OTC, the OTC collected amounts, at least some of which represented "taxes" that were not remitted to the municipalities or the hotels. Even if the hotels ultimately remitted the hotel occupancy taxes to the municipalities for a consumer stay, the OTCs have still collected and failed to remit hotel occupancy taxes.

Despite the fact that OTCs have collected excess taxes on breakage transactions, the Court refrained from requiring the payment of back taxes because the municipalities did not present a "sufficient computation of breakage damages." Moreover, the municipalities failed to provide either a formula for computation or documents or information required to calculate damages. As a result, under the applicable rules of procedure,13 the Court issued sanctions against the municipalities. Thus, it excluded the municipalities' evidence of past breakage damages and, consistent with the partial settlement agreement, only granted damages for breakage transactions that occurred after May 16, 2011.

Common Law and UDTPA Claims

The municipalities also asserted Uniform Deceptive and Unfair Trade Practices Act (UDTPA) and common law claims. In particular, they claimed that the OTCs violated the UDTPA based on the contention that the OTCs wrongfully retained hotel occupancy taxes, and brought forth conversion, unjust enrichment and breach of constructive trust claims. The Court held that these claims failed as a matter of law.

Prospective Taxes/Declaratory Relief

Pursuant to the parties' partial settlement agreement, the OTCs agreed to pay an initial lump sum for the "Incremental Tax for all Hotel Occupancies occurring after May 16, 2011 through the month ending after the Class Report is filed...."

The Court had already decided, as a matter of law, that the municipalities were not entitled to damages for transactions occurring on or before May 16, 2011. However, with respect to transactions occurring after May 16, 2011, the proper tax base was still at issue. The municipalities argued for an adjustment to the partial settlement agreement (which applied the tax to the retail rate of the room) based on an "alternative base rate," which deems the applicable tax to have been collected as part of the lump sum charge to customers.

The Court rejected the municipalities' argument and stated that the retail rate was the proper tax base. It cited to the Georgia Supreme Court decisions and the trial court decision in City of Columbus.14 Based on the language of the Enabling Statute, the retail rate for breakage transactions occurring after May 16, 2011 was proper because it was the rate that was "represented" to the consumer.

Commentary

This decision is unique with respect to the plethora of recent decisions addressing OTCs and their hotel tax liabilities because the partial settlement agreement was a significant factor for consideration, and the interpretation of the language of the applicable state hotel tax statute was already made at the state court level.

The Court (a federal court) was required to respect the Georgia Supreme Court's interpretation of Georgia's laws. Deciding on motions for summary judgment, the Court's role was limited to the resolution of reasonable doubts about the facts viewed in favor of the non-moving party. The Court did not decide whether the Enabling Statute applied to the OTCs because it respected the Georgia Supreme Court's findings on these issues.

Moreover, since the partial settlement agreement provided that the OTCs would pay the municipalities for the tax not remitted on the retail rate of rooms for transactions after May 16, 2011, the issue before the Court was whether the OTCs owed any hotel taxes for transactions prior to or on May 16, 2011. By entering into the agreement, the OTCs had conceded that they owed tax on the retail rate of rooms on a going-forward basis.

Note that the Court treated breakage transactions differently from non-breakage transactions. The treatment of breakage transactions was an issue that was reserved for litigation (after the parties entered into their partial settlement agreement), and the Court suggested that if the municipalities produced evidence, sufficient to compute the damages for back taxes associated with breakage transactions, the Court would have awarded those particular back taxes. The back taxes for breakage transactions, unlike the back taxes for non-breakage transactions, would have been permitted because the Enabling Statute required entities collecting the hotel tax to remit the hotel tax and there was sufficient evidence to show that excess hotel tax was collected on the breakage transactions where the OTCs did not remit any payment amounts to the hotels or the municipalities. The sole reason the back taxes for breakage transactions were not granted was the failure by the municipalities to provide a means to calculate the damages. As a result, the Court disallowed the request for damages.

Interestingly, while the Court held that the "enforcement provisions" of the Enabling Statute did not apply to the OTCs since they were not innkeepers or hotel operators, it did not address the possibility that the OTCs could fall under the enforcement provisions as "agents of" innkeepers or hotel operators. The enforcement provisions explicitly apply to an innkeeper's agent. They read, "[i]t shall be unlawful for any innkeeper to fail, neglect, or refuse to collect the tax provided in this article [Excise Tax on Lodging], either by himself or herself or through his or her agents or employees."15 The failure to address the agency argument could be viewed as a missed opportunity for municipalities that were seeking recovery from OTCs.

In addition, the case significantly points out that the OTCs are only liable for remittance of tax on the retail rate of rooms, on a prospective basis, if they voluntarily choose to collect the tax. If they do not choose to collect the tax, then under Georgia law, the issue would be moot. Therefore, as applied to OTCs that were not party to this suit or OTCs that did not enter into a settlement agreement with the municipalities, the case allows these non-party OTCs to refrain from "collecting" taxes altogether.

This case illustrates the growing need for authorities dictating the proper hotel tax collection requirements for OTCs. While the case instructs the OTCs that were defendants in the case, its application does not necessarily extend to non-part OTCs. Georgia and its municipalities, as well as other taxing jurisdictions with outdated hotel occupancy tax laws that are seeking additional revenue, may consider revisions to their statutes and codes to explicitly tax an OTC's charge to its customers. Meanwhile, OTCs continue to seek federal legislation that would propose federal pre-emption for all state and local hotel taxes imposed on hotel rooms purchased through OTC Web sites.

Footnotes

1 Order Entered by Judge Harold L. Murphy on July 9, 2012, City of Rome, Georgia, et al. v. Hotels.com, L.P., U.S. District Court for the Northern District of Georgia, Rome Division, Civil Action File No. 4:05-CV-249-HLM. The liability resulting from transactions on or prior to May 16, 2011 was at issue because the parties only agreed to the payment of taxes after that date.

2 In a "breakage transaction," the customer prepays the OTC for a room, including the hotel occupancy taxes, but the OTC does not remit any money to the hotel or municipality. Breakage transactions occur either: (i) when the hotel fails to timely submit an invoice to an OTC or (ii) when a consumer cancels a prepaid room booked through an OTC. In the first type of transaction, the OTC fails to remit tax to the hotels because the hotels do not invoice the OTC. In the second type of transaction, the consumer books and prepays for a room with an OTC, but fails to show up or cancel.

3 710 S.E.2d 766 (Ga. 2011).

4 GA. CODE ANN. § 48-13-51(a)(1)(A).

5 GA. CODE ANN. § 48-13-51(a)(1)(B)(i).

6 Id.

7 GA. CODE ANN. § 48-13-51(a)(1)(B)(ii).

8 See City of Atlanta v. Hotels.com, 710 S.E.2d 766 (Ga. 2011) and Expedia, Inc. v. City of Columbus, 681 S.E.2d 122 (Ga. 2009).

9 The Court cited Findley v. Findley, 629 S.E.2d 222, 226 (Ga. 2006).

10 GA. CODE ANN. § 48-13-51(a)(1)(B).

11 This is due to the hotel's failure to invoice the OTC or the consumer's failure to use a prepaid room reservation.

12 Id.

13 Specifically, the Court cited to the Federal Rules of Civil Procedure 26(a)(1)(A)(iii) and 37(c).

14 Expedia, Inc. v. City of Columbus, 681 S.E.2d 122, 125 (Ga. 2009).

15 GA. CODE ANN. § 48-13-59(a) (emphasis added).

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

 
In association with
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert
Email Address
Company Name
Password
Confirm Password
Mondaq Topics -- Select your Interests
Accounting and Audit
Anti-trust/Competition Law
Consumer Protection
Corporate/Commercial Law
Criminal Law
Employment and HR
Energy and Natural Resources
Environment
Family and Matrimonial
Finance and Banking
Food, Drugs, Healthcare, Life Sciences
Government, Public Sector
Immigration
Insolvency/Bankruptcy, Re-structuring
Insurance
Intellectual Property
International Law
Litigation, Mediation & Arbitration
Media, Telecoms, IT, Entertainment
Privacy
Real Estate and Construction
Strategy
Tax
Transport
Wealth Management
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.