| |
| en:wiki:referentiel:delaispaiement [2025/06/24 19:16] – créée - modification externe 127.0.0.1 | en:wiki:referentiel:delaispaiement [2026/10/23 21:23] (Version actuelle) – Automatic push translation eneuville |
|---|
| ====== Payment terms ====== | ====== ======Payment Terms |
| FIXME A1 proofreading not yet effective for this page. In the meantime, you can ask any questions on the [[https://forum.gestan.fr|forum]]. | |
| |
| This screen is used to set invoice payment terms. | This screen allows you to configure customer payment terms. |
| |
| ===== Using the screen ===== | Using the screen |
| |
| //Access via : Tools->Administration->Reference->Payment terms// | ===== =====//**Access:** Tools -> Admin -> Repository -> Payment Terms// |
| |
| {{:en:wiki:referentiel:delaipaiement_en_01.png?nolink|}} | {{fr:wiki:referentiel:delaipaiement_01.png?nolink|}} |
| |
| The **condition type** is the calculation method used to calculate the delay. | The **condition type** is the calculation method used to determine the payment term. |
| |
| There are the following possibilities: | The following options are available: |
| * **Net delay**: in this method, we simply add a number of days to today's date. For example, for an invoice on 10/08, a deadline of 30 days would give an invoice due date on 10/09 (August 10 + 30 days). | * **Net term** : in this method, a number of days is simply added to the current date. For example, for an invoice dated 10 August, a 30-day payment term would result in the invoice being due on 10 September (10 August + 30 days). |
| * **Quarter of the month **: in this method, the invoice is due on the xth day of the month. For example, for an invoice dated 08/10 with a number of days of 30 and for a date of 15, the due date would be 09/15 (the "15" following the gross due date, which was on 10/09. | * **Date of the month** : with this method, the invoice is due on the xth day of the month. For example, for an invoice dated 10/08 with a term of 30 days and a due date of the 15th, the due date would be 15 September (the ‘15th’ following the gross due date, which was 10 September). |
| * **Delay + quantime**: in this method, we apply a deadline, and then take the date of the month. For example, for our invoice for 10/08, if we set a deadline of 30 days on the 5th, it will be due on 5/10 (10/08 + 30 days = 10/09, and the next 05 of the month is on month 05/10) | * **Time limit + due date** : in this method, a payment period is applied, and then the specific date of the month is taken. For example, for our invoice dated 10/08, if we set a 30-day payment period starting on the 5th, it will be due on 5/10 (10/08 + 30 days = s 10/09, and the next 5th of the month is in October (5/10)) |
| * **Split**: in this method, we will choose a number of deadlines and a frequency. For example, if you choose a number of 12 and a monthly frequency, you will have payment in 12 monthly installments. You may not provide any indication for the number of due dates and/or frequency: in this case, these two elements will be specified when generating the invoice payment schedule, when creating the invoice. the bill. If you set the number of due dates to zero, then you can enter any number of due dates when attaching the schedule to the invoice. On the other hand, if you specify a specific number of due dates at the splitting level, the schedule attached to the invoice will necessarily have the same number of due dates. | * **Instalments** : with this method, you select a number of instalments and a frequency. For example, if you choose 12 instalments and a monthly frequency, you will have 12 monthly payments. You do not need to specify the number of instalments and/or the frequency: in this case, these two details will be determined when the payment schedule for the invoice is generated, at the time the invoice is created. If you set the number of instalments to zero, you will be able to enter any number of instalments when linking the payment schedule to the invoice. However, if you specify a particular number of instalments in the instalment breakdown, the payment schedule linked to the invoice will necessarily have the same number of instalments. |
| * **End of year**: in this case, the due date will be the end of the financial year. | * **End of financial year** : in this case, the due date will be the end of the financial year. |
| |
| |
| :TIP: For month-end deadlines (e.g. 30-day month-end), simply check the "Month-end" box. In this case, the due date of our invoice of 10/08 would be 30/09. | :TIP: To set end-of-month payment terms (for example, 30 days to the end of the month), simply tick the “End of month” box. In this case, the due date for our invoice dated 10/08 would be 30/09. |
| |
| :TIP: The "cash" payment term (ID=1) cannot be deleted, as it is used in certain Gestan functions. | :TIP: The “cash” payment term (ID=1) cannot be deleted, as it is used in certain functions within Gestan. |
| |
| |
| |
| |
| The Gestan settings screen allows you to specify the default payment term (as well as the default validity term for quotations). It is not possible to delete a payment term if it is the default payment term; it must first be modified in Gestan settings. | The default payment term (as well as the default validity period for quotations) is specified via the [[en:wiki:parametrage:general:pieces|general settings]]. |
| | |
| | It is not possible to delete a payment term if it is the default payment term; you must first amend it in the general settings. |
| |
| ----------------- | ----------------- |
| {{:wiki:tags:voir_aussi.gif?nolink |}}**Other "Referential "** articles | {{wiki:tags:voir_aussi.gif?nolink |}}**Other “Reference” articles** |
| |
| <nspages en:wiki:referentiel -nbCol=2 -textPages="" -h1 -r -simpleLineBreak > | <nspages fr:wiki:referentiel -nbCol=2 -textPages="" -h1 -r -simpleLineBreak > |
| |
| |