User Tools

Site Tools



en:yld_maksegraafik

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:yld_maksegraafik [2022/09/09 15:34] – [2. Example of a payment schedule] triinpen:yld_maksegraafik [2022/09/21 10:55] (current) – [2. Example of a payment schedule] triinp
Line 8: Line 8:
 {{:et:triinp20220908-134431.png}} {{:et:triinp20220908-134431.png}}
  
-Opens a schedule, which first row is filled with the invoice (order) **sum to be paid** and **due date**:+Opens a payment schedule, which first row is filled with the invoice (order) **sum to be paid** and **due date**:
 {{:et:triinp20220908-134525.png}} {{:et:triinp20220908-134525.png}}
  
Line 17: Line 17:
 **Reason**- reason for partial sum. Allows partial sums to be marked with a reason identifier (reason code), if necessary. Not required. This column occurs when reason codes are set. Reason codes are created by the Directo customer according to their needs. Reason codes can be configured ''Settings -> System settings -> Payment graph reason codes'': **Reason**- reason for partial sum. Allows partial sums to be marked with a reason identifier (reason code), if necessary. Not required. This column occurs when reason codes are set. Reason codes are created by the Directo customer according to their needs. Reason codes can be configured ''Settings -> System settings -> Payment graph reason codes'':
  
-{{:et:triinp20220909-110226.png}}+{{:et:triinp20220921-100927.png}}
  
 **Reason codes** can be used, for example, in situations where an invoice or purchase invoice is received/paid in parts and important partial sums should be highlighted.  **Reason codes** can be used, for example, in situations where an invoice or purchase invoice is received/paid in parts and important partial sums should be highlighted. 
-For example, **deposit retention** in construction or **down payment** in installment sales, etc. Reason codes can also be used to organize the payment of purchase invoices in such a way that only sums corresponding or not corresponding to a specific reason are paid. [[et:or_aru_tasu_ennustus|Tasumisennustus]]+For example, **retention of deposit** in construction or **deposit** payment in installment sales, etc. Reason codes can also be used to organize the payment of purchase invoices in such a way that only sums corresponding or not corresponding to a specific reason are paid. [[et:or_aru_tasu_ennustus|Tasumisennustus]]
  
  
 ==== 1.1. Creating a payment schedule ==== ==== 1.1. Creating a payment schedule ====
  
-A payment schedule can be created on a document by pressing in Payment term. When the schedule opens, the first line of the invoice (order) is filled in with **sum to be paid** and **payment term**.+A payment schedule can be created on a document by pressing in Payment term. When the schedule opens, the first line of the invoice (order) is filled in with **sum to be paid** and **due date**.
  
 {{:et:triinp20220909-113337.png}} {{:et:triinp20220909-113337.png}}
  
-In the following lines, the graph installments must be entered in such way that the percentage of the installment from the total amount or the sum of the installment is entered. When entering each new line, the installment of that line and the percentage are subtracted from the first (initial) line. If you enter a **percentage** in the line, the corresponding **installment** is automatically calculated and vice versa.  +The schedule installments must be entered in the following lines as a percentage of the installment from the total amount or as the sum of the installment. When entering each new line, the installment of that line and the percentage are subtracted from the first (initial) line. If you enter a **percentage** in the line, the corresponding **installment** is automatically calculated and vice versa.  
-When saving the graph, Directo checks whether the percentages and installments add up to the whole (100%) and may correct the row installments sums or percentages.  +When saving the schedule Directo checks whether the percentages and installments add up to the whole (100%) and may correct the row installments sums or percentages.  
-If it is desired that some entered value (% or amount) does not change during such recalculation (for examplefixed amounts are agreed with the customer or supplier regardless of the accuracy of the percentage), then double-click in the corresponding number field. As a result, the sums or % in the field becomes bold and does not change when saved.\\+If it is desired that some entered value (% or sum) does not change during such recalculation (for example fixed amounts are agreed with the customer or supplier  
 +regardless of percent accuracy), then double-click the corresponding number in the field. As a result, the sums or % in the field becomes bold and does not change when saving.\\
 When saving, the schedule is sorted by deadlines. When saving, the schedule is sorted by deadlines.
  
-{{:et:jane:maksegraafik_taida.png|}}+{{:et:triinp20220921-101228.png}}
  
-:?: +:?: \\
   * The payment schedule can also be changed on the confirmed document;   * The payment schedule can also be changed on the confirmed document;
-  * The payment schedule lines can be used on the printed form of the invoice (also print payment schedule on the invoice). +  * The payment schedule lines can be used on the printed form of the invoice (print the payment schedule to the invoice). 
- +:!: \\
-:!:+
   * Using the payment schedule does not affect the document financial transaction;   * Using the payment schedule does not affect the document financial transaction;
-  * In the **Sales ledger and Purchase ledger** reports the invoice sums are reflected based on the payment term on the invoice (not according to schedule payment terms).  +  * In the **Sales ledger and Purchase ledger** reports the invoice sums are reflected based on the payment terms of the invoice (not according to schedule payment terms).  
-  * Based on the payment terms of the schedule can view invoices in the reports **Unpaid invoices and Payment forecast**: [[et:or_aru_tasu_ennustus|Tasumisennustus]] and [[en:mr_aru_arved_maksmata|Unpaid invoices]].+  * Based on the schedule payment terms can view invoices in the reports **Unpaid invoices and Payment forecast**: [[et:or_aru_tasu_ennustus|Tasumisennustus]] and [[en:mr_aru_arved_maksmata|Unpaid invoices]].
   * The invoice or purchase invoice cannot be marked as received or paid in installments of the selected schedule. If the invoice is received or partially paid, Directo marks the sums in the schedule as received/paid in chronological order from the earliest.   * The invoice or purchase invoice cannot be marked as received or paid in installments of the selected schedule. If the invoice is received or partially paid, Directo marks the sums in the schedule as received/paid in chronological order from the earliest.
- 
 :?: If the payment schedule is not saved, check the payment term type - it must be filled in. :?: If the payment schedule is not saved, check the payment term type - it must be filled in.
 ==== 1.2. Creating a payment schedule in Excel ==== ==== 1.2. Creating a payment schedule in Excel ====
Line 58: Line 57:
 :!: If the payment according to the schedule has been agreed in installments according to the sums, it is possible to fill in only the sums in the payment schedule. In this case can avoid cents in installment sums arising from %-rounding. :!: If the payment according to the schedule has been agreed in installments according to the sums, it is possible to fill in only the sums in the payment schedule. In this case can avoid cents in installment sums arising from %-rounding.
  
-{{:et:triinp20220909-122956.png}}+{{:et:triinp20220921-103555.png}}
  
 :!: The percentage and sum columns no longer need to be filled, when importing a graph.  :!: The percentage and sum columns no longer need to be filled, when importing a graph. 
Line 68: Line 67:
  
 As an example, rounding the sums when creating a payment schedule. As an example, rounding the sums when creating a payment schedule.
-{{:et:triinp20220909-153453.png}}+ 
 +{{:et:triinp20220921-104013.png}} 
 +{{:et:triinp20220921-105529.png}}
  
  
en/yld_maksegraafik.1662726895.txt.gz · Last modified: 2022/09/09 15:34 by triinp

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki