Monday, July 31, 2023

IRS - Republication - Tax considerations for people who are separating or divorcing


IRS

 

Republication

 

Tax Tip 2023-97: Tax considerations for people who are separating or divorcing

 

July 31, 2023

 

 

Issue Number:  Tax Tip 2023-97

 

Tax considerations for people who are separating or divorcing

 

When couples separate or divorce, the change in their relationship status affects their tax situation. The IRS considers a couple married for tax filing purposes until they get a final decree of divorce or separate maintenance.

 

Update tax withholding


When a taxpayer divorces or separates, they usually need to update their proper tax withholding by filing with their employer a new 
Form W-4, Employee's Withholding Certificate. If they receive alimony, they may have to make estimated tax payments. Taxpayers can figure out if they’re withholding the correct amount with the Tax Withholding Estimator on IRS.gov.

 

Tax treatment of alimony and separate maintenance

  • Amounts paid to a spouse or a former spouse under a divorce decree, a separate maintenance decree or a written separation agreement may be alimony or separate maintenance for federal tax purposes. 
  • Certain alimony or separate maintenance payments are deductible by the payer spouse, and the recipient spouse must include it in income.

 

Rules related to dependent children and support


Generally, the parent with custody of a child can claim that child on their tax return. If parents split custody fifty-fifty and aren't filing a joint return, they'll have to decide which parent claims the child. If the parents can’t agree, taxpayers should refer to the tie-breaker rules in 
Publication 504, Divorced or Separated Individuals. Child support payments aren't deductible by the payer and aren't taxable to the payee.

 

Not all payments under a divorce or separation instrument – including a divorce decree, a separate maintenance decree or a written separation agreement – are alimony or separate maintenance. Alimony and separate maintenance doesn’t include:

  • Child support
  • Noncash property settlements – whether in a lump-sum or installments
  • Payments that are your spouse's part of community property income
  • Payments to keep up the payer's property
  • Use of the payer's property
  • Voluntary payments

 

Child support is never deductible and isn't considered income. Additionally, if a divorce or separation instrument provides for alimony and child support and the payer spouse pays less than the total required, the payments apply to child support first. Only the remaining amount is considered alimony.

 

Report property transfers, if needed


Usually, if a taxpayer transfers property to their spouse or former spouse because of a divorce, there’s no recognized gain or loss on the transfer. People may have to report the transaction on a gift tax return.

 

More information:
Topic No. 452 Alimony and Separate Maintenance

 

 

Tuesday, July 18, 2023

U.S. Court of Appeals for the Second Circuit, UPS Supply Chain Solutions, Inc. v. EVA Airways Corporation, Docket No. 21-2867


Personal Jurisdiction

 

Treaty Jurisdiction

 

Montreal Convention

 

International Convention

 

 

 

 

Appeal from the United States District Court for the Southern District of New York No. 20-cv-2818

 

 

Appellant UPS Supply Chain Solutions, Inc. was sued in the Southern District of New York and filed a third-party complaint against Appellee EVA Airways Corporation, seeking indemnification and contribution. The district court granted EVA’s motion to dismiss for lack of personal jurisdiction. UPS now appeals, arguing that EVA was subject to specific personal jurisdiction based on both New York’s long-arm statute and the Montreal Convention. We hold that UPS has failed to allege the in-state injury required for specific jurisdiction in New York, that the Montreal Convention does not confer personal jurisdiction, and that the record does not establish that EVA consented to personal jurisdiction in light of the Convention or its contract with UPS. Accordingly, we AFFIRM.

 

 

The Montreal Convention, a multilateral treaty which entered into force in 2003, governs claims arising out of the international transportation of persons, baggage, and cargo by air.1 The treaty includes jurisdictional articles providing where such claims can be brought. This appeal presents a question of first impression: whether the Montreal Convention confers personal jurisdiction.

 

1 Convention for the Unification of Certain Rules for International Carriage by Air, May 28, 1999, T.I.A.S. No. 13,038.

 

 

In particular, we must determine whether by enabling actions arising under the treaty to be brought in the courts of certain countries, the Montreal Convention provides those courts with personal jurisdiction over the parties. Consistent with our decisions interpreting the Montreal Convention’s predecessor, we conclude that it does not. The Montreal Convention’s jurisdictional provisions place a limit on when courts of the United States, as opposed to courts of other signatory nations, may exercise jurisdiction over a claim arising under the treaty. Under U.S. law, this is referred to as treaty jurisdiction, which is a form of subject-matter jurisdiction. The Montreal Convention does not, however, alter our domestic personal jurisdiction requirements, which must be independently established. Because the Montreal Convention does not confer personal jurisdiction, and because Appellant has not otherwise established a basis for personal jurisdiction over Appellee in this action, we affirm the district court’s dismissal for lack of personal jurisdiction.

 

 

This case began with the shipment of 24 pallets of vitamins from Chicago to South Korea. National Union Fire Insurance Company of Pittsburgh, PA insured the vitamins, and UPS Supply Chain Solutions, Inc. contracted for them to be carried by EVA Airways Corporation, an airline headquartered in Taiwan. EVA carried the shipment on non-stop flights from Chicago to Taiwan and then from Taiwan to South Korea. The vitamins allegedly arrived damaged, and this litigation ensued.

 

 

Next, we must answer whether the Montreal Convention provides a separate basis for exercising personal jurisdiction over EVA in this action. The Montreal Convention sets forth the types of claims that can be brought relating to international air carriage. It is well established that the treaty “preempts state law and provides the sole avenue for damages claims that fall within the scope of its provisions.” Cohen v. Am. Airlines, Inc., 13 F.4th 240, 246 (2d Cir. 2021). The treaty also includes jurisdictional provisions dictating where such claims can be brought. Pointing to these jurisdictional provisions, UPS argues that in enabling certain nation-states’ courts to adjudicate a claim arising under the treaty, the Montreal Convention provides those courts with personal jurisdiction over the defendant against whom the claim is brought. By this logic, UPS contends that because the treaty authorizes it to bring a third-party claim against EVA for indemnification and contribution, and because it authorizes courts in the United States to hear that third-party claim, we should interpret the Montreal Convention to establish personal jurisdiction over EVA in this action. For the reasons explained below, we hold that the Montreal Convention’s jurisdictional provisions speak only to treaty jurisdiction as a form of subject-matter jurisdiction, not personal jurisdiction. Therefore, the Montreal Convention does not confer personal jurisdiction on United States courts in actions arising under the treaty. The power to assert jurisdiction over a claim is distinct from the power to assert jurisdiction over a party, which must be separately established.

 

 

“The interpretation of a treaty, like the interpretation of a statute, begins with its text.” Medellín v. Texas, 552 U.S. 491, 506 (2008). The Montreal Convention’s primary jurisdictional provision, Article 33, provides that “an action for damages must be brought, at the option of the plaintiff, in the territory of one of the States Parties . . . before the court of” [1] the carrier’s domicile, [2] the carrier’s principal place of business, [3] the place where the contract was made, [4] the place of destination, or [5] in certain actions, a passenger’s principal and permanent residence. Montreal Convention art. 33(1)–(2). Article 33 also dictates that “questions of procedure shall be governed by the law of the court seised of the case.” Id. art. 33(4). Where one carrier (the “contracting carrier”) contracted with a party to provide air carriage and a different carrier (the “actual carrier”) performed the actual carriage, the Montreal Convention permits either carrier to implead the other in the event that it is sued. See id. art. 45 (authorizing “the defendant carrier to seek to have the remaining carrier joined in the proceedings according to the procedural requirements of the forum in which the action is brought”). A special jurisdictional provision, Article 46, applies in actions involving carriage arranged by a contracting carrier. Article 46 provides that such actions “must be brought, at the option of the plaintiff, in the territory of one of the States Parties, either before a court in which an action may be brought against the contracting carrier, as provided in Article 33, or before the court having jurisdiction at the place where the actual carrier has its domicile or its principal place of business.” Id. art. 46. In effect, Article 46 expands Article 33’s list of fora to encompass both the contracting carrier’s and actual carrier’s domicile and principal place of business.

 

 

An examination of this treaty text leads us to conclude that its jurisdictional provisions pertain to treaty jurisdiction. In the United States, federal courts have subject-matter jurisdiction over claims arising under the Montreal Convention pursuant to 28 U.S.C. § 1331, which gives federal courts subject-matter jurisdiction over “all civil actions arising under . . . treaties of the United States.” Articles 33 and 46 operate as a limit on this treaty jurisdiction. By stating where a damages action “must be brought,” the provisions delimit which nation-states’ courts can hear a claim arising under the treaty. Specifically, the provisions dictate that for the courts of a given nation-state to have jurisdiction over a claim arising under the treaty, the nation-state must be both one of the “States Parties” to the Convention and one of the fora listed in Article 33 (or Article 46, when applicable). Therefore, in a damages action governed by the Montreal Convention, if the United States is not one of the designated fora, then courts in the United States cannot exercise treaty jurisdiction over the action.

 

 

To begin, nothing in the text of the Montreal Convention says or implies that it gives rise to personal jurisdiction—that is, a court’s power to exercise control over a particular party. While Articles 33 and 46 state that actions “must be brought” in one of the specified fora, they do not state that the courts of those fora must entertain such actions without regard for other potential barriers to jurisdiction. To the contrary, as noted above, Article 33 specifies that “questions of procedure shall be governed by the law of the court seised of the case.” Montreal Convention art. 33(4). Likewise, while Article 45 allows a defendant contracting carrier to implead an actual carrier, or vice versa, the provision explicitly states that “the procedure and effects” remain “governed by the law of the court seised of the case.” Id. art. 45. The inclusion of these clauses indicates that while the Montreal Convention permits claims arising under the treaty to be brought in particular nations, it does not guarantee plaintiffs the unconditional right to litigate in those nations’ courts. Rather, the treaty expressly leaves room for nation-states to impose their own venue, jurisdictional, or other procedural requirements. We conclude that personal jurisdiction is such a requirement.

 

 

In sum, based on our analysis of the Montreal Convention’s text and our Warsaw Convention precedent, we conclude that the Montreal Convention speaks to jurisdiction only in the treaty sense. In cases arising under the Montreal Convention, personal jurisdiction must be separately established in accordance with domestic laws and practice.

 

 

 

LOHIER, Circuit Judge, concurring: I join the Court’s opinion in full. I write separately to emphasize that, while UPS failed to meet its burden of showing a “meeting of the minds” in this case, Majority Op. at 23, our decision does not definitively foreclose a contract-based theory of consent to personal jurisdiction under the Montreal Convention. There may be cases in which the defendant carrier impliedly or expressly consented to personal jurisdiction in, for example, “the court of the domicile of the carrier” or “the court at the place of destination” by doing business as an international air carrier governed by the treaty. See Montreal Convention, art. 33.

 

 

 

(U.S. Court of Appeals for the Second Circuit, July 19, 2023, UPS Supply Chain Solutions, Inc. v. EVA Airways Corporation, Docket No. 21-2867)

 

 

 

Tuesday, July 11, 2023

Licensing Agreements (Swiss Law) - IP Rights Transfer - Softwares


Contrats de licence (droit suisse)

 

Cession des droits de propriété intellectuelle (not. le droit d’auteur)

 

Logiciels

 

Application de l’art. 5 al. 1 let. a CPC

 

 

 

4A_372/2022  

Arrêt du Tribunal fédéral suisse, du 11 juillet 2023  

 

 

 

 

1.La doctrine s'accorde à dire que les actions contractuelles fondées sur l'inexécution ou la mauvaise exécution des contrats de licence ou de cession des droits de propriété intellectuelle entrent dans le champ d'application de l'art. 5 al. 1 let. a CPC (SUTTER-SOMM/SEILER, in Handkommentar zur Schweizerischen Zivilprozessordnung, 2021, n° 6 ad art. 5 CPC; HAAS/SCHLUMPF, in Schweizerische Zivilprozessordnung, Kurzkommentar, 3 e éd. 2021, n° 4 ad art. 5 CPC; PATRICK STOUDMANN, in Code de procédure civile, Petit commentaire, 2020, n° 5 ad art. 5 CPC; VOCK/NATER, in Basler Kommentar [ZPO], 3 e éd. 2017, n° 4 ad art. 5 CPC; RAINER WEY, in Kommentar zur Schweizerischen Zivilprozessordnung [ZPO], 3 e éd. [Sutter-Somm et alii éd.] 2016, n° 11 ad art. 5 CPC; THEODOR HÄRTSCH, in Schweizerische Zivilprozessordnung [ZPO], Stämpflis Handkommentar, 2010, n° 6 ad art. 5 CPC).

 

 

 

4.2.1. La doctrine distingue entre le logiciel standard ( Standardsoftware) d'une part, destiné à une pluralité d'utilisateurs, qu'il s'agisse du grand public (par exemple le traitement de texte Word, le tableur Excel) ou d'un nombre indéfini de clients dans un secteur particulier (médecins, avocats, hôpitaux, etc...), et le logiciel individualisé ou spécifique (Individualsoftware) d'autre part, conçu pour résoudre le problème spécifique d'un client (NEFF/ARN, in Schweizerisches Immaterialgüter- und Wettbewerbsrecht [SIW], vol. II/2 Urheberrechtlicher Schutz der Software, 1998, p. 119; MICHAEL MARTINEK, Moderne Vertragstypen, vol. III, 1993, p. 7 s.). Il existe aussi des formes intermédiaires: le fournisseur adapte un logiciel standard aux nécessités particulières d'un client. Le travail peut aller de la simple installation à une véritable personnalisation (« Customizing »), en passant par le paramétrage du programme standard (GIANNI FRÖHLICH-BLEULER, Softwareverträge, 2 e éd. 2014, n. 19 et 1667).

 

 

4.2.2. La mise à disposition des droits d'utilisation d'un logiciel (« Softwareüberlassung ») met en cause trois domaines juridiques: la propriété intellectuelle, le droit des obligations et les droits réels (LUKAS MORSCHER, Software-Überlassungsverträge, Teil I [...], in Softwareverträge, [Hans Rudolf Trüeb éd.] 2004, p. 62). L'autonomie des parties règne en la matière. Au besoin, il faudra interpréter le (s) contrat (s) selon les méthodes habituelles et en tenant compte du but de la mise à disposition (« Zweckübertragungstheorie »), théorie de la finalité développée en droit d'auteur (WILLI EGLOFF, in Le nouveau droit d'auteur, 4e éd. 2021, nos 25-26 ad art. 16 LDA; FRÖHLICH-BLEULER, op. cit., n. 820-821).

 

 

4.2.3. Les parties peuvent notamment convenir d'un contrat de licence pour une certaine durée moyennant paiement de redevance (s); un tel accord peut avoir pour objet un logiciel standard ou un logiciel individualisé (FRÖHLICH-BLEULER, op. cit., n. 2368 et 2501). Selon que le fournisseur est tenu d'installer le programme informatique pour le client, voire de le paramétrer en profondeur, il aura un devoir accessoire ou une obligation principale relevant du contrat d'entreprise (FRÖHLICH-BLEULER, op. cit., n. 2392). Ce type d'accord ne prévoit a priori aucune cession des droits d'utilisation (FRÖHLICH-BLEULER, op. cit., n. 2528 s.; voir aussi IVAN CHERPILLOD, Protection des logiciels et des bases de données: la révision du droit d'auteur en Suisse, in RSPI 1993, p. 57) : le fournisseur concède un droit relatif, limité dans le temps, à utiliser le logiciel. Les parties peuvent convenir d'un contrat de durée déterminée ou fixer un délai pour opérer une résiliation ordinaire, le cas échéant après une durée minimale (FRÖHLICH-BLEULER, op. cit., n. 2942-2944). Lorsque ce contrat prend fin, le client n'est plus autorisé à utiliser le software - ce qui est souvent précisé dans le contrat. S'il continue à le faire, il enfreint le droit d'auteur (FRÖHLICH-BLEULER, op. cit., n. 2954 et 2984) : il doit restituer le software ou le détruire. Le contrat exige parfois qu'il confirme cette destruction par écrit (FRÖHLICH-BLEULER, op. cit., n. 2967 et 2986).

 

 

4.2.4. Lorsque le fournisseur remet au client un logiciel spécifique, il faut adopter la prémisse qu'il lui confère une simple autorisation d'utiliser le produit sans lui transférer ses droits. Ceci dit, il faut en premier lieu déterminer si le contrat réglemente ce point, et le cas échéant l'interpréter (FRÖHLICH-BLEULER, op. cit., n. 19 et 819 ss; CHERPILLOD, op. cit., p. 57). Certains indices plaident pour une véritable cession des droits, en particulier lorsque le logiciel est issu d'un développement entièrement nouveau. Il faut aussi examiner dans quelle mesure le programme contient des secrets d'affaire du client, si ce dernier veut éviter que des concurrents puissent utiliser ce produit, respectivement dans quelle mesure sa collaboration et son savoir-faire ont été nécessaires dans la confection du logiciel, s'il a assumé l'intégralité des frais de développement ou s'il a obtenu un fort rabais, etc... (FRÖHLICH-BLEULER, op. cit., n. 822-824; URSULA WIDMER, Der urheberrechtliche Schutz von Computerprogrammen, in RDS 1993 I 258 sous-note 82; CHERPILLOD, op. cit., p. 57).

 

 

4.2.5. La remise du code-source au client ne signifie pas impérieusement qu'il s'est fait céder les droits d'auteur sur le logiciel, même si cela peut constituer un indice(JACQUES DE WERRA, in Commentaire romand, Propriété intellectuelle, 2013, n° 53 ad art. 16 LDA et le même, in Urheberrechtsgesetz (URG), Commentaire Stämpfli, 2 e éd. 2012, n° 51 ad art. 16 LDA; FRÖHLICH-BLEULER, op. cit., n. 825 et la réf. à l'ATF 125 III 263; GEORG RAUBER, in Urhebervertragsrecht, [Magda Streuli-Youssef éd.] 2006, p. 198 s. et p. 243 s.; CHERPILLOD, op. cit., p 57 i.f. -58; arrêt de la Cour de justice genevoise du 14 novembre 2008 [ACJC/1372/2008] consid. 5.4, in sic! 2010 p. 25).

 

 

4.3. (…) Telle est pourtant l'essence d'un contrat de licence - même assorti d'une prestation principale afférente au contrat d'entreprise: le preneur doit s'acquitter d'une ou plusieurs redevances, sans pour autant acquérir la propriété du bien protégé par le droit d'auteur.