Unified Data Systems, Inc. v. Almarc Corp. (In Re Almarc Corp.)

94 B.R. 361, 20 Collier Bankr. Cas. 2d 616, 1988 Bankr. LEXIS 2083, 18 Bankr. Ct. Dec. (CRR) 1253, 1988 WL 139194
CourtUnited States Bankruptcy Court, E.D. Pennsylvania
DecidedDecember 14, 1988
Docket19-10529
StatusPublished
Cited by28 cases

This text of 94 B.R. 361 (Unified Data Systems, Inc. v. Almarc Corp. (In Re Almarc Corp.)) is published on Counsel Stack Legal Research, covering United States Bankruptcy Court, E.D. Pennsylvania primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Unified Data Systems, Inc. v. Almarc Corp. (In Re Almarc Corp.), 94 B.R. 361, 20 Collier Bankr. Cas. 2d 616, 1988 Bankr. LEXIS 2083, 18 Bankr. Ct. Dec. (CRR) 1253, 1988 WL 139194 (Pa. 1988).

Opinion

MEMORANDUM OPINION

BRUCE I. FOX, Bankruptcy Judge:

An adversary proceeding initiated by Unified Data Systems, Inc. (UDS) has triggered a motion to dismiss from the debtor-defendant. In its complaint, UDS alleges that Almarc Corp. (Almarc) has breached a post-petition contract, thereby entitling UDS to a judgment in excess of $30,000.00. Almarc contends that this complaint should be dismissed for lack of subject matter jurisdiction.

I.

On May 28, 1982, Almarc filed a voluntary petition in bankruptcy under chapter 11. UDS had no prepetition relationship with Almarc. On August 11, 1982, though, the parties entered into a “service agreement” by which UDS agreed to provide monthly computer services to the debtor, and the debtor agreed to pay for such services within thirty days of invoicing. (Complaint, Exhibit B.) The parties agree that in September, 1982, this court ap *363 proved of this contractual arrangement pursuant to an application filed by Almarc. 1

The parties also agree that on September 10, 1986 this court entered an order confirming Almarc’s chapter 11 plan of reorganization. (The plan itself has been attached to the complaint as Exhibit A.) Article XIII of the plan called for the retention of jurisdiction by this court. In relevant part, it stated that:

The court shall retain jurisdiction of this case until the Plan has been fully consummated, including, but not limited to, the following mátters:
[[Image here]]
B. To adjudicate all controversies concerning the classification or allowance of any claim;
[[Image here]]
F. To adjudicate all claims or controversies arising out of any purchases, sales or contracts made or undertaken by the debtor during the pendency of these proceedings ....

The Service Agreement itself contained the following provisions:

15. Exclusive Jurisdiction
Client [the debtor] consents to the jurisdiction of the Courts of Common Pleas of Philadelphia, Pennsylvania and/or the United States District Court for the Eastern District of Pennsylvania in any action or proceeding pursuant hereto....
18. Complete Agreement
This agreement sets forth the entire understanding of the parties.. It shall not be changed or terminated orally....

UDS alleges, and for the purposes of resolving this motion I accept as true, see Satz v. ITT Financial Corp., 619 F.2d 738 (8th Cir.1980); Wood v. Santa Barbara Chamber of Commerce, Inc., 507 F.Supp. 1128 (D.Nev.1980), that Almarc has failed to pay for computer services billed in October 1987 through February 1988. The parties acknowledge that no final decree has been entered pursuant to Bankr.Rule 3022.

II.

UDS contends that the retention of jurisdiction provision found in the confirmed plan provides subject matter jurisdiction for this court to resolve this proceeding. Almarc counters that the plan, by its terms, does not confer jurisdiction over this dispute; moreover, even if it so attempted, Almarc argues that such a provision is improper. Neither party has addressed the jurisdictional provision found in the contract itself.

A.

Almarc correctly notes that a federal court, in deciding a motion to dismiss for lack of subject matter jurisdiction, presumptively lacks jurisdiction over a proceeding unless the plaintiff affirmatively demonstrates that jurisdiction exists. Commodity Futures Trading Comm’n v. Nahas, 738 F.2d 487 (D.C.Cir.1984). Accord, e.g., Lucas v. Gulf & Western Industries, Inc., 666 F.2d 800, 805 (3d Cir.1981). This proposition is no less true for bankruptcy courts which, despite their expanded jurisdictional grant now found in 28 U.S.C. § 1334, remain courts of limited jurisdiction. 2 See Pacor, Inc. v. Higgins, 743 F.2d 984 (3d Cir.1984); In re Chargit, Inc., 81 B.R. 243, 247 (Bankr.S.D.N.Y.1987). “The burden of establishing the requisite jurisdictional facts rests on the plaintiff as the party alleging their existence.” Lucas v. Gulf & Western Industries, Inc., 666 F.2d at 805. See also Hirsch v. Blue Cross, Blue Shield of Kansas City, 800 F.2d 1474 (9th Cir.1986); Dadzie on Behalf of Int’l *364 Kal-Sakara Corp. v. Leslie, 550 F.Supp. 77 (E.D.Pa.1982).

In presenting those facts necessary to establish jurisdiction, plaintiff is free to go outside the pleadings, see, e.g., Save Our Cemeteries, Inc. v. Archdiocese of New Orleans, Inc., 568 F.2d 1074 (5th Cir.1978), cert. denied, 439 U.S. 836, 99 S.Ct. 120, 58 L.Ed.2d 133 (1978), by utilizing discovery tools, and by submitting affidavits. See Satz v. ITT Financial Corp.; Midwest Elevator Systems, Inc. v. St. Paul Fire and Marine Ins. Co., 508 F.Supp. 578 (D.Kan.1981). Here, the plaintiff appears to be relying solely upon the pleadings and their documentary attachments.

B.

Just recently, in In re Cinderella Clothing Industries, Inc., 93 B.R. 373 (Bankr.E.D.Pa.1988) I had occasion to address the jurisdiction of bankruptcy courts post-confirmation until entry of the final decree, which occurs after the estate has been fully administered and which closes the case. See Bankr.Rule 3022. Bankruptcy courts retain jurisdiction over a chapter 11 case, after confirmation,

to protect its [confirmation] decree, to prevent interference with the execution of the plan, and to aid otherwise in its operation.

In re Dilbert’s Quality Supermarkets, Inc., 368 F.2d 922, 924 (2d Cir.1966). Accord, e.g., In re Pittsburgh Terminal Coal Corp., 183 F.2d 520 (3d Cir.1950), cert. denied, 340 U.S. 904, 71 S.Ct. 280, 95 L.Ed. 654 (1950); In re New York, N.H. & H.R. Co., 169 F.2d 337 (2d Cir.1948), cert. denied, 335 U.S. 867, 69 S.Ct. 138, 93 L.Ed. 412 (1948); In re Lombard-Wall, Inc., 44 B.R. 928, 935 (Bankr.S.D.N.Y.1984),

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

Related

D.E. Frey Group, Inc. v. FAS Holdings, Inc.
387 B.R. 799 (D. Colorado, 2008)
Access Care, Inc. v. Sten-Barr Network Solutions, Inc.
333 B.R. 706 (E.D. Pennsylvania, 2005)
Shuman v. Kashkashian (In Re Shuman)
277 B.R. 638 (E.D. Pennsylvania, 2001)
In Re Continental Airlines, Inc.
236 B.R. 318 (D. Delaware, 1999)
Walnut Associates v. Saidel
164 B.R. 487 (E.D. Pennsylvania, 1994)
Grimes v. Graue (In Re Haws)
158 B.R. 965 (S.D. Texas, 1993)
Eubanks v. Esenjay Petroleum Corp.
152 B.R. 459 (E.D. Louisiana, 1993)
In Re Bankeast Corp.
142 B.R. 12 (D. New Hampshire, 1992)
In Re Jordan Manufacturing Co.
138 B.R. 30 (C.D. Illinois, 1992)

Cite This Page — Counsel Stack

Bluebook (online)
94 B.R. 361, 20 Collier Bankr. Cas. 2d 616, 1988 Bankr. LEXIS 2083, 18 Bankr. Ct. Dec. (CRR) 1253, 1988 WL 139194, Counsel Stack Legal Research, https://law.counselstack.com/opinion/unified-data-systems-inc-v-almarc-corp-in-re-almarc-corp-paeb-1988.