Search Tips

RULE 22. INTERPLEADER

Effective Date: 3/1/2011

(a) Grounds.

(1) By a Plaintiff. Persons with claims that may expose a plaintiff to double or multiple liability may be joined as defendants and required to interplead. Joinder for interpleader is proper even though:
(A) the claims of the several claimants, or the titles on which their claims depend, lack a common origin or are adverse and independent, rather than identical; or
(B) the plaintiff denies liability in whole or in part to any or all of the claimants.
(2) By a Defendant. A defendant exposed to similar liability may seek interpleader through a crossclaim or counterclaim.

(b) Relation to Other Rules. This rule supplements, and does not limit, the joinder of parties allowed by Rule 20.

Rule 22 was amended, effective March 1, 1990, March 1, 2011.

This rule is derived from Fed.R.Civ.P. 22.

A provision derived from N.D.R.C. 1943 § 28-0224 that allowed interpleader by substitution was deleted, effective March 1, 2011.

Rule 22 was amended, effective March 1, 2011, in response to the December 1, 2007, revision of the Federal Rules of Civil Procedure. The language and organization of the rule were changed to make the rule more easily understood and to make style and terminology consistent throughout the rules.

Rule 22 was amended, effective March 1, 1990. The amendments are technical in nature and no substantive change is intended.

SOURCES: Joint Procedure Committee Minutes of September 25, 2008, pages 19-20; April 20, 1989, page 2; December 3, 1987, page 11; September 20-21, 1979, page 14; Fed.R.Civ.P. 22(a)

CROSS REFERENCE: N.D.R.Civ.P. 13 (Counterclaim and Cross-Claim), N.D.R.Civ.P. 14 (Third-Party Practice), N.D.R.Civ.P. 20 (Permissive Joinder of Parties), and N.D.R.Civ.P. 25 (Substitution of Parties).

Effective Date Obsolete Date
03/01/2011 View
03/01/1990 03/01/2011 View

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>