Tenable Protective Serv. v. Bit E-Technologies, L.L.C., 89958 (8-21-2008)

2008 Ohio 4233
CourtOhio Court of Appeals
DecidedAugust 21, 2008
DocketNo. 89958.
StatusUnpublished
Cited by6 cases

This text of 2008 Ohio 4233 (Tenable Protective Serv. v. Bit E-Technologies, L.L.C., 89958 (8-21-2008)) is published on Counsel Stack Legal Research, covering Ohio Court of Appeals primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Tenable Protective Serv. v. Bit E-Technologies, L.L.C., 89958 (8-21-2008), 2008 Ohio 4233 (Ohio Ct. App. 2008).

Opinion

JOURNAL ENTRY AND OPINION *Page 3
{¶ 1} Appellant Tenable Protective Services ("Tenable") appeals the trial court's decision granting Bit E-Technologies, LLC's ("Bit E") motion for judgment on the pleadings. For the following reasons, we affirm the trial court's decision.

{¶ 2} On March 7, 2005, Tenable, an Ohio based provider of security and safety services, entered into a written agreement with Bit E, a Georgia based limited liability company engaged in software development and systems integration. Pursuant to the agreement, Bit E agreed to provide Tenable with an automated personnel and payroll system. Bit E also agreed to provide support and maintenance of Tenable's time tracking and scheduling applications for a period of five years.

{¶ 3} In addition, Bit E agreed to maintain and resolve application issues 24 hours per day. In exchange, Tenable agreed to pay Bit E $48,000 to create the integrated web based time keeping and billing software. Upon execution of the agreement, Tenable tendered payment of $9,600 to initiate Bit E's performance. On August 9, 2005, Tenable tendered the remaining $38,400.

{¶ 4} On August 22, 2006, Tenable filed suit against Bit E, and against the company's principals, Vedad Arslanagic and Timur Mehmedbasic, in their individual capacities. Tenable's suit alleged several causes of action including, breach of contract, breach of warranty, misrepresentation and fraud. In its complaint, Tenable specifically alleged that the software as delivered never functioned as represented by Bit E. Tenable also alleged that as a result of Bit E's breach, the entire contract cost haDbeen wasted, as well as the cost associated with lost time spent training the employees to operate the system. *Page 4

{¶ 5} On February 13, 2007, Arslanagic and Mehmedbasic filed their respective answers. On March 5, 2007, Bit E filed for bankruptcy protection, and as a result, the trial court stayed the proceedings.

{¶ 6} On March 21, 2007, Arslanagic and Mehmedbasic filed a motion for judgment on the pleadings. In their motion, Arslanagic and Mehmedbasic argued that, as individuals, they could not be held liable for the obligations of a limited liability company ("LLC").

{¶ 7} On March 26, 2007, Tenable filed its motion in opposition to Arslanagic and Mehmedbasic's motion for judgment on the pleadings. Tenable also attached an affidavit from Camille Felder to detail the allegations that they were defrauded by Arslangic and Mehmedbasic.

{¶ 8} On April 9, 2007, Tenable filed a motion for leave to amend its complaint. On May 27, 2007, the trial court granted Arslanagic and Mehmedbasic's motion for judgment on the pleadings and denied Tenable's motion for leave to amend its complaint. Tenable appeals and assigns the following errors for our review:

"[1.] The trial court erred in granting defendant-appellee's [sic] motion for judgment on the pleading.

"[2.] The trial court erred and abused its discretion in failing to grant plaintiff-appellant's motion for leave to amend complaint."

Judgment on the Pleadings
{¶ 9} In the first assigned error, Tenable argues the trial court erred in granting Arslanagic and Mehmedbasic's motion for judgment on the pleadings. We disagree.

{¶ 10} We begin by observing that Civ. R. 12(C) provides: *Page 5

"After the pleadings are closed but within such time as not to delay the trial, any party may move for judgment on the pleadings."

{¶ 11} A Civ. R. 12(C) motion for judgment on the pleadings has been characterized as a belated Civ. R. 12(B)(6) motion for failure to state a claim upon which relief can be granted.1

{¶ 12} A motion for judgment on the pleadings pursuant to Civ. R. 12(C) presents only questions of law, and the standard of review is de novo.2 Determination of a motion for judgment on the pleadings is restricted solely to the allegations in the pleadings and any writings attached to the complaint.3 Dismissal is appropriate under Civ. R. 12(C) when, after construing all material allegations in the complaint, along with all reasonable inferences drawn therefrom in favor of the nonmoving party, the court finds that the plaintiff can prove no set of facts in support of its claim that would entitle it to relief.4

{¶ 13} In the instant case, Tenable argues that both Arslanagic and Mehmedbasic should be held personally liable for the obligations of Bit E. We are not persuaded.

{¶ 14} Under Ohio law, as elsewhere, an LLC is neither a corporation nor a partnership, as those concepts are commonly understood. Instead, an LLC is a hybrid in that *Page 6 it is a form of legal entity that has attributes of both a corporation and a partnership but is not formally characterized as either one.5

{¶ 15} Initially, we recognize that Bit E is a limited liability company, and Arslanagic and Mehmedbasic are members and senior managers of the company. Pursuant to R.C. 1705.48(B),

"[N]either the members of the limited liability company nor any managers of the limited liability company are personally liable to satisfy any judgment, decree, or order of a court for, or are personally liable to satisfy in any other manner, a debt, obligation, or liability of the company solely by reason of being a member or manager of the limited liability company."

{¶ 16} Thus, under R.C. 1705.48(B), Arslanagic and Mehmedbasic's status in the limited liability company does not, by itself, make them personally liable for the obligations of Bit E.6

{¶ 17} A review of Tenable's complaint and the attached contract identified as "Exhibit A" indicates that the agreement was between Bit E and Tenable. The attached contract does not set forth any representation, obligations, or liabilities on the part of Arslanagic or Mehmedbasic. Consequently, pursuant to R.C. 1705.48, Arslanagic and Mehmedbasic are not liable for the obligations of Bit E.7 Nonetheless, Tenable argues that Ohio law does not govern the contract. We are not persuaded. *Page 7

{¶ 18} A review of the contract reveals that the agreement specifically indicated that Ohio law would govern any disputes. The agreement provided in pertinent part as follows:

"Governing Law and Jurisdiction . This Agreement and performance hereunder will be governed by the laws of the State of Ohio, without regard to its conflict of laws rules. Company and Client hereby

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Estate of Kelley v. Wuliger & Wuilger, L.L.C.
2025 Ohio 2450 (Ohio Court of Appeals, 2025)
Osborne v. J.T.O., Inc.
2024 Ohio 2070 (Ohio Court of Appeals, 2024)
Woodside Mgt. Co. v. Bruex
2020 Ohio 4039 (Ohio Court of Appeals, 2020)
Paulozzi v. Rodstrom
2019 Ohio 4157 (Ohio Court of Appeals, 2019)
Pincus v. Pincus
127 N.E.3d 393 (Court of Appeals of Ohio, Eighth District, Cuyahoga County, 2018)
McNair v. City of Brecksville
2017 Ohio 7401 (Ohio Court of Appeals, 2017)

Cite This Page — Counsel Stack

Bluebook (online)
2008 Ohio 4233, Counsel Stack Legal Research, https://law.counselstack.com/opinion/tenable-protective-serv-v-bit-e-technologies-llc-89958-8-21-2008-ohioctapp-2008.