You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Objectifs

Cette procédure a pour objectif de définir les rôles et responsabilités de chacun des acteurs, les délais réglementaires à respecter et l’organisation de la déclaration de TIPP (TICPE).

Champ d’application et date d’effet 

Cette procédure s’applique à Rhodia Opérations à compter du . Il convient aussi de rappeler que la procédure peut être remise à jour en fonction de l'évolution de la réglementation.

Evénements déclencheurs

La vente aux clients français de l’EOLYS et du REGEFLEX, nomenclature 3811 90 00 90 fabriqués sur le site de La Rochelle et destinés à être incorporés dans du gazole ou tout autre huile minérale dont le taux de taxe intérieure de consommation est celui du gazole. 

Responsabilités

La responsable transport de ROP et l’administratrice des ventes de ce produit sont en charge du calcul de la taxe. Elles se consultent pour savoir qui fait la déclaration pour un mois donné. Le calcul se fait suivant les modalités suivantes :  

  • collecte papier de toutes les factures émises aux clients français sur un mois entier
  • calcul manuel du montant cumulé versé au titre de la TIPP (sert pour vérification ; sera légèrement supérieur au montant de TIPP calculé automatiquement par ISOPE)
  • calcul manuel du poids net expédié cumulé (à renseigner sur la déclaration en ‘masse nette’)
  • calcul manuel du nombre d’hectolitres expédiés en divisant le montant cumulé de TIPP par le taux de TIC, soit 41,69 (à renseigner sur la déclaration en ‘unité de perception’)

La déclaration via ISOPE sera faite par Cécile KIECKEN - Responsable pôle Taxes Salaires et Immobilisations à Saint Fons Delta.

Le pôle TSI a la responsabilité de s’assurer de la déclaration et du paiement effectif de la TIPP.

Le responsable team costing de la plateforme comptabilité Rhodia a la responsabilité du virement auprès du bureau des douanes de La Rochelle-Pallice. Afin de permettre le paiement, le pôle TSI établit une demande de paiement manuel signée par Cécile KIECKEN et/ou Elodie PARET. La déclaration est jointe à cette demande.

En même temps, le personnel administratif en charge des collectes d’information pour la déclaration de TIPP (TICPE) à la Rochelle-Pallice CRD sera informé du moment de la télédéclaration par un envoi d’une copie de la déclaration par courriel (contact : Véronique FOUSSE: veronique.fousse@douane.finances.gouv.fr) par le pole tsi.

Scope


La Rochelle

Frequency


 

References


 

There is no content with the specified labels

There is no content with the specified labels

Attachments


 

 

Before any creation or modification, please make sure that the customer does not already exist in the database.

Always use "Customers (general)" criteria

 

 

1. General Data

Error rendering macro 'include-content'

Couldn't find page: ZWOC06T - Create Customer - general data

 

2. Commercial Data

 

Error rendering macro 'include-content'

Couldn't find page: ZW0C06T - Create customer - Commercial data

 

To give you some help

 

  • You can visualize your customer’s account group and the name or ID of the person who created customer. Visualize customer. Go to the “Unloading points” section. Click above on “Extras” and “Administrative Data”.
  • You can check if a customer is blocked or has a deletion flag. Visualize customer. Go to the “Unloading points” section. Click above on “Extras” and “Blocking Data”. If you see “01” in box “Order block – All Sales Areas”, your customer is blocked. For deletion flags, click above on “Extras” and “Deletion flags”. If boxes are ticked, customer is blocked. Still in “Extras” click on “Texts”: comments are indicated in “Internal notes” (for example: customer already existing, please use xxxxxxx)
  • If you want to visualize all modification made on your customer and they author, visualize customer. Go to the “Unloading points” section. Click above on “Environment”, “Account changes” and “All fields”. All modification appears on your screen. If you want to know who made a modification, double-click on the line concerned. One or more modifications appear listed by date. Then double-click on the required line to see following information about modification: date, hour, author’s name or ID, nature of the modification.

 

4.1   Periodic invoicing: Invoicing rule

Defines the mode of grouping of the deliveries on one invoice.

Extras, Additional data of Sold to or Payer customer. 

BLANK : All deliveries shipped in the period (defined in the Invoicing Dates field on the Billing Screen) are grouped together   into one single Invoice (for a same shipping point and ship to party) 

001: One Invoice per Delivery 

002: One invoice for all deliveries linked to a sales order 

003: Not used at the moment. Only one invoice per sales order once the last delivery output is done

004: equivalent to rule 002 ; this rule is specifically adapted to order type ZOR for monthly invoicing of despatches to a         customer ‘on consignment’ ;  at invoice output Invoice quantity is accumulated per material from all the deliveries that have been Goods Issued (no delivery reference is printed) 

005: this rule is specially adapted to order type ZOR for stock adjustment to cover stock sent in advance ; it  allows at invoice output :

to suppress the invoice line where the Order and PO references appear  to link to one material, one invoice quantity = accumulation of all Goods Issues from all deliveries in the period and to print a line giving batch details in the format ’Batches XXXXXX - CCCCCC - DDDDDD... ‘ ; these batches are from the delivery documents associated with the ZOR

to print at the foot of the invoice, B/L references in the format ‘BL n° aaaa - bbbb - cccc.... ‘These B/L references are taken from the Order references for each ZOR. It is in effect the B/L eferences from the stockiest 

006: All deliveries shipped in the period are grouped together into one single invoice but at the opposite of default rule (BLANK), they are also grouped even if they are realized by different shipping points and for different ship to parties. Deleted in 2010 March

007: Equivalent to rule 006 but at invoice output (not at display), quantities are accumulated per material. Used by US 

008: All deliveries shipped in the period and linked to a same contract are grouped into one single invoice ), they are also grouped even if they are realized by different shipping points and for different ship to parties. Used by US

 

4.2   Periodic invoicing : invoicing dates

Defines the rhythm of invoicing

zone blank: daily invoicing (all the deliveries of the day for the same article, the same division of delivery, the same customer)

VM: monthly invoicing in working days (do not use)

AM: monthly invoicing in calendar days

VD: period of 10 days invoicing

VQ: fortnight invoicing

VV: invoicing on Fridays

...etc

 

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels