Offices; Multibranch Parties - ISDA Provision

ISDA Anatomy™ →Go uptown In a Nutshell™ Section 10: 10. Offices; Multibranch Parties 10(a) If this Section applies, whenever a party enters a Transaction through a branch Office, it represents that recourse against it will be the same as if it had entered through its head office (subject to any Waiting Period for an Illegality or a Force Majeure Event). 10(b) If a party is a Multibranch Party it may, subject to clause 10(c) below, enter into and book Transactions and make and receive payments through Office listed for that party in the Schedule. 10(c) The Office through which a party enters into a Transaction will be specified in the Confirmation or, if not specified, that party’s head office. The specified Office will also be the Office in which that party books and makes and receives payments and deliveries under Transaction. Except to make a Transfer to Avoid Termination Event neither party may change its specified Office for a Transaction without the the other’s prior written consent. view template 2002 ISDA full text of Section 10: 10. Offices; Multibranch Parties 10(a) If Section 10(a) is specified in the Schedule as applying, each party that enters into a Transaction through an Office other than its head or home office represents to and agrees with the other party that, notwithstanding the place of booking or its jurisdiction of incorporation or organisation, its obligations are the same in terms of recourse against it as if it had entered into the Transaction through its head or home office, except that a party will not have recourse to the head or home office of the other party in respect of any payment or delivery deferred pursuant to Section 5(d) for so long as the payment or delivery is so deferred. This representation and agreement will be deemed to be repeated by each party on each date on which the parties enter into a Transaction. 10(b) If a party is specified as a Multibranch Party in the Schedule, such party may, subject to clause (c) below, enter into a Transaction through, book a Transaction in and make and receive payments and deliveries with respect to a Transaction through any Office listed in respect of that party in the Schedule (but not any other Office unless otherwise agreed by the parties in writing). 10(c) The Office through which a party enters into a Transaction will be the Office specified for that party in the relevant Confirmation or as otherwise agreed by the parties in writing, and, if an Office for that party is not specified in the Confirmation or otherwise agreed by the parties in writing, its head or home office. Unless the parties otherwise agree in writing, the Office through which a party enters into a Transaction will also be the Office in which it books the Transaction and the Office through which it makes and receives payments and deliveries with respect to the Transaction. Subject to Section 6(b)(ii), neither party may change the Office in which it books the Transaction or the Office through which it makes and receives payments or deliveries with respect to a Transaction without the prior written consent of the other party. view template Click here for the text of Section 10 in the 1992 ISDA Index: Click ᐅ to expand: ISDA Navigation See ISDA Comparison for a comparison between the 1992 ISDA and the 2002 ISDA. The Varieties of ISDA Experience Subject 2002 (wikitext) 1992 (wikitext) 1987 (wikitext) Preamble Pre Pre Pre Interpretation 1 1 1 Obligns/Payment 2 2 2 Representations 3 3 3 Agreements 4 4 4 EODs & Term Events 5 Events of Default: FTPD • Breach • CSD • Misrep • DUST • Cross Default • Bankruptcy • MWA Termination Events: Illegality • FM • Tax Event • TEUM • CEUM • ATE 5 Events of Default: FTPD • Breach • CSD • Misrep • DUST • Cross Default • Bankruptcy • MWA Termination Events: Illegality • Tax Event • TEUM • CEUM • ATE 5 Events of Default: FTPD • Breach • CSD • Misrep • DUSS • Cross Default • Bankruptcy • MWA Termination Events: Illegality • Tax Event • TEUM • CEUM Early Termination 6 Early Termination: ET right on EOD • ET right on TE • Effect of Designation • Calculations; Payment Date • Payments on ET • Set-off 6 Early Termination: ET right on EOD • ET right on TE • Effect of Designation • Calculations • Payments on ET • Set-off 6 Early Termination: ET right on EOD • ET right on TE • Effect of Designation • Calculations • Payments on ET Transfer 7 7 7 Contractual Currency 8 8 8 Miscellaneous 9 9 9 Offices; Multibranch Parties 10 10 10 Expenses 11 11 11 Notices 12 12 12 Governing Law 13 13 13 Definitions 14 14 14 Schedule Schedule Schedule Schedule Termination Provisions Part 1 Part 1 Part 1 Tax Representations Part 2 Part 2 Part 2 Documents for Delivery Part 3 Part 3 Part 3 Miscellaneous Part 4 Part 4 Part 4 Other Provisions Part 5 Part 5 Part 5 Tell me more Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

Section 10 of the ISDA Master Agreement allows parties to specify whether they are Multibranch Parties. Electing “Multibranch Party” status allows you to transact out of the named branches of the same legal entity. Details fans will immediately note that, from the point of view of legal and corporate philosophy — surely a subject dear to every attorney’s heart — the differing branches of a legal entity have no distinct legal personality any more than does a person’s arm or leg have different personality from her head. So being a “multibranch” party seems immaterial.

====Taxation==== Those details fans will have overlooked the strange, parallel universe of taxation. Here physical presence and not legal personality is what matters. Specifying that your counterparty may trade from its offices in, for example, Prague, Kabul or The Sudan may impact the tax payable on payments under the relevant transactions under the ISDA. Where both parties are multibranch parties and have numerous overseas branches, a complex multilateral analysis of all the different permutations is assured.

Quoth, elegantly, a wise man (now departed):

“The risk for a counterparty is essentially a withholding tax gross-up risk. If withholding tax arises in relation to a payment made to a counterparty through our NYK office, and the counterparty hasn’t provided us with evidence of an exemption from withholding, the counterparty may argue that we may be obliged to gross-up the payment on the basis that, but for our failure to disclose to them that payments may be made from NYK, they would have provided evidence of their exemption. So, by failing to disclose that USD payments will originate in NYK, we make a misrepresentation by omission of something that may be material to the counterparty.”

“So you end up in a double-jeopardy, in that counterparties may refuse to make a US Payee Tax Representation on the grounds that, in the absence of the disclosure that NYK is our settlement centre, there’s nothing to convince them that payments will be made to them (as Payee) from NYK. So, no Payee Tax Representation (or W-8BEN form) + no multibranch election = potential withholding tax gross up by us. And/or a possible Misrepresentation Event of Default”.

“Of course there are other ways to get around it: disclosure of the branch in a Confirmation (operational risk, and of no use in electronically booked txns), or more detailed reps in Part 5 - but none is as simple or uncomplicated as simply putting “New York” in the Multibranch election”

Must you complete onboarding in each jurisdiction though?

Yes — and no. A case where the operational reality trumps the legal theory. If you have a Multibranch ISDA that lists, say, Prague, The Sudan and Wellington, do you need to onboard the client in each of those jurisdictions? Students of onboarding will recognise this as a collossal disincentive to adding branches willy-nilly, but that legal implication will typically depend on an operational setup in the broker’s systems without which it won’t be possible to book a trade in that jurisdiction whatever the legal docs say. So look upon the legal contract as permissive; the thing that will drive your KYC obligations and trigger the onboarding onslaught will be opening an account in your systems at a later date.

====Netting==== While, by dint of the legal personality, it wouldn’t make any difference under English or New York law, and really shouldn’t anywhere else, there are those jurisdictions which are not so theoretically pure in their conceptualisation of the corporate form. Your counterparty may have the misfortune to be incorporated in such a place.

If so, the validity of close-out netting against that entity may indeed depend on the branch from which it transacts - and indeed there is a possibility that the governing law of the jurisdiction of the branch may endeavour to intervene (particularly relevant if it has assets). Another reason, perhaps, to disapply the “multibranch party” for a counterparty incorporated in such a jurisdiction. The way to check this is at the netting opinion review sheet contains the following question:

Does the opinion confirm that close-out netting under the agreement is enforceable notwithstanding the inclusion of branches in non-netting jurisdictions? Yes/No

See also

• Onboarding