Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/www/katchka/romille/wp-includes/functions.php on line 6121

Deprecated: Required parameter $message follows optional parameter $type in /home/www/katchka/romille/wp-content/plugins/co-marquage-service-public/includes/message.class.php on line 34

Deprecated: Required parameter $message follows optional parameter $type in /home/www/katchka/romille/wp-content/plugins/co-marquage-service-public/includes/message.class.php on line 48

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the post-expirator domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/www/katchka/romille/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the profile-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/www/katchka/romille/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultimate-addons-for-gutenberg domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/www/katchka/romille/wp-includes/functions.php on line 6121
Particuliers – Ville de Romillé

Particuliers


Warning: Undefined array key "lienweb" in /home/www/katchka/romille/wp-content/plugins/co-marquage-service-public/templates/models/r.php on line 3

Warning: Trying to access array offset on value of type null in /home/www/katchka/romille/wp-content/plugins/co-marquage-service-public/templates/models/r.php on line 3

Warning: Trying to access array offset on value of type null in /home/www/katchka/romille/wp-content/plugins/co-marquage-service-public/templates/models/r.php on line 3

Warning: Trying to access array offset on value of type null in /home/www/katchka/romille/wp-content/plugins/co-marquage-service-public/templates/models/r.php on line 3

Modèle de document

Désigner un responsable unique en cas de chèque sans provision sur compte joint ou indivis (Modèle de document)

Vérifié le 06 janvier 2022 - Direction de l'information légale et administrative (Première ministre)

Indiquez vos nom et prénom, adresse et numéro de compte joint.

À lieu, le date

Objet : Désignation d'un responsable en cas d'incident de paiement

Madame, Monsieur,

Nous sommes cotitulaires du compte joint référencé ci-dessus.

Veuillez noter que, d'un commun accord et comme le permet l'article L131-80 du code monétaire et financier, nous décidons de désigner l'un d'entre nous c'est-à-dire nom et prénom de la (personne désignée) comme responsable unique en cas d'émissions de chèque sans provision qui surviendrait sur notre compte joint.

Nom et prénom sera donc désormais seul(e) interdit d'émettre des chèques sur l'ensemble de ses comptes si un tel incident survenait.

Cordialement,

Signature de chaque cotitulaire du compte joint

Pour toute explication, consulter les fiches pratiques :

Retour en haut