Differences

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

--- en:yld_hankija [2022/08/03 15:12] – [1.3.3. Examples] triinp
+++ en:yld_hankija [2024/05/29 12:07] (current) – vilja
@@ Line 1: / Line 1: @@
 ====== Suppliers ======
@@ Line 7: / Line 8: @@
 :!: The supplier register is separate from the [[et:yld_klient|Klientide registrist]].
+===== 1. Suppliers register =====
-===== 1. Supplier register =====
+The suppliers register is located in '' Purchase -> DOCUMENTS -> ** Suppliers ** ''
-The suppliers register is located in '' Purchase -> DOCUMENTS -> ** Suppliers ** ''.
 Clicking on the word **Suppliers** opens the register of suppliers:
-Directo's supplier register stores suppliers (vendors) contact information and other supplier-related attributes necessary for smooth operation. New suppliers are also added through the supplier register.
+{{:et:kellylytom20240522-093939.png}}
+Directo's supplier register stores suppliers contact information and other supplier-related attributes necessary for smooth operation. New suppliers are also added through the supplier register.
 To open an existing suppliers card, click on the suppliers code in the register and to create a new one, press the button {{:et:triinp20220630-122432.png}} \\
 In the first case, the existing suppliers card is opened for viewing and if the corresponding right exists, also for modification ([[et:group_rights|Kasutajaõigused]]). In the second case, a blank card opens to enter a new suppliers data.
 ===== 2. Suppliers card =====
@@ Line 25: / Line 26: @@
 The suppliers card stores the data of one supplier and the attributes necessary for Directo to work:
 {{:et:triinp20220630-122933.png}}
 The suppliers card is divided into tabs: **General info, Contacts, Bank Accounts, Actions, Changes, Automation, Transport**.
 {{:et:triinp20220630-123145.png}}
@@ Line 35: / Line 38: @@
 The General information tab stores the suppliers basic data and attributes. The meanings of the fields are as follows:
-**Priority fields:**
+  * **Code** - supplier ID for Directo. It can be created by the user entering an appropriate character, which can contain both numbers and letters. However, the code can also be generated by Directo after saving the supplier card, giving the next indication in the queue. In the [[en:yld_settings|System settings]] can specify which number range is used to create the supplier code or the supplier's registry code is also used as the supplier's code. If the user decides to enter the code, it is not recommended to use punctuation marks and specific computer symbols in it. Directo's recommendation is that the code is generated by the program according to the system settings specified by the administrator, because this feature is only needed to create connections and the user does not need it in daily work.
-  * **Code** - supplier ID for Directo. It can be created by the user entering an appropriate character, which can contain both numbers and letters. However, the code can also be generated by Directo after saving the supplier card, giving the next indication in the queue. In the [[en:yld_settings|System settings]] can specify which number range is used to create the supplier code or the supplier`s registry code is also used as the supplier`s code. If the user decides to enter the code, it is not recommended to use punctuation marks and specific computer symbols in it. Directo's recommendation is that the code is generated by the program according to the system settings specified by the administrator, because this feature is only needed to create connections and the user does not need it in daily work.
+  * **Class** - supplier's group. The class must be selected from the classes register that opens with a double click on this field or Ctrl-Entre.
-  * **Name** - supplier`s name
+  * **Object** - supplier-related object or financial dimension(s). It is used when you want certain [[et:objekt|objects]] to be placed in the header of the same document when the supplier is placed on the document.
+  * **Stock** - The stock to which the goods are to be ordered. Can be selected with a double-click or Ctrl+Enter.
   * **Type** - type of legal entity of the procurer. Selection: **Company, Private person, State institution**.
-:!: Choosing correct supplier`s type is important for generating the correct VAT report.\\
+:!: Choosing correct supplier's type is important for generating the correct VAT report.\\
-  * **Reg.no 1** - supplier register code
-:!: Filling in the supplier's register code is important for generating the correct VAT report.\\
-:?: If the register code field is filled in and the supplier's card is saved, the title of the field changes to a hyperlink and clicking on it may open given supplier`s credit register page. Which service provider and with which options depends on the system setting ''External customer information request URL'' and your contract with the corresponding service provider.\\
-:?: Previous fields will be filled in automatically if  Business Register help is used when creating the supplier's card.\\
-**Other fields:**
-  * **Class** - supplier`s group. The class must be selected from the classes register that opens with a double click on this field or Ctrl-Entre.
-  * **Object** - supplier-related object or financial dimension(s). It is used when you want certain [[et:objekt|objects]] to be placed in the header of the same document when the supplier is placed on the document.
   * **Closed** - allows to close the supplier to prevent further use. This option is used, for example, if the supplier has ceased operations. In this case, it is not correct to delete the supplier's card, but to close it, because the historical transactions with the supplier must remain. At the same time, closing ensures that this supplier can no longer be selected to new documents. Reports also show closed supplier information.
+  * **Name** - supplier's name
   * **Street, postal code, city and country** - supplier's legal or business address fields.
-:?: Address fields will be filled in automatically if  Business Register help is used when creating the supplier's card.\\
+:?: Address fields will be filled in automatically if  Business Register help is used when creating the supplier's card;
-  * **County** - complements other address fields. A selection of counties. The counties register can be supplemented or changed: ''Settings → General settings → Counties''.
-  * **Country** - complements other address fields. Selection from the register of countries. The countries register can be complemented or changed: ''Settings -> Stock settings -> Location''.
-  * **Representative** - primary supplier`s contact person. Double-click or Ctrl-Enter opens a selection from the contact register.
-  * **Phone** - supplier's primary contact telephone number
-  * **e-mail** - supplier's primary email address
-  * **Directo-to-Directo** - indicates whether the supplier also uses Directo. If so, it is possible to automatically exchange documents between Directos via the Directo to Directo transport module if desired.
+  ***County** - complements other address fields. A selection of counties. The counties register can be supplemented or changed: ''Settings → General settings → Counties''.
+  ***Country** - complements other address fields. Selection from the register of countries. The countries register can be complemented or changed: ''Settings -> Stock settings -> Location''.
+  ***Representative** - primary supplier's contact person. Double-click or Ctrl-Enter opens a selection from the contact register.
+  ***Phone** - supplier's primary contact telephone number
+  ***e-mail** - supplier's primary email address
+  ***Reference** - supplier invoice reference number
+  ***Mandatory** - selecting this option makes the reference number mandatory
-==== 1.2. Bank Accounts ====
+**Bank**
+  ***SWIFT** - bank swift. Placed when the bank is placed
+  ***Bank account/IBAN** - supplier's bank account
+  ***Code** - bank code. Selection from the bank register
+  ***Name** - bank name. Placed when the bank is placed
+  ***Name in bank** - supplier's name at the given bank. Text input
+  ***Address in bank** - address field
+  ***Pay Term** - supplier invoice payment terms. Can be entered manually or set with a double-click.
+  ***e-invoice import prefers data above**
+  ***Costs** - selections SEPA, split, our, their
+  ***Payment type** -  selections SEPA, Normal, Urgent, Extra Urgent. Default is SEPA.  Choose Normal, Urgent or Extra Urgent to send Luminor bank payments to the bank. The selection assigned to the supplier is added to the payment row.
+  ***Corresponding bank** - bank code. Selection from the bank register.
-If the supplier has several bank accounts they can be managed in this tab. \\
+**Info**
+  ***Del Mode** - delivery mode. Indicates how the ordered products are delivered. E.g., by ship. Can be changed with a double-click or Ctrl+Enter.
+  ***Del term** - delivery term
+  ***Directo-to-Directo** - indicates whether the supplier also uses Directo. If so, it is possible to automatically exchange documents between Directos via the Directo to Directo transport module if desired.
+  ***Payee** - possible to place a payee. Double-click or Ctrl+Enter opens the selection from the supplier register.
+  ***Vat reg no** - supplier's VAT registration number
+  ***Language** - double-click or Ctrl+Enter opens the selection from the language register
+  ***Reg no 1** - supplier register code.  \\
+:!: Filling in the supplier's register code is important for generating the correct VAT report.\\
+:?: If the register code field is filled in and the supplier's card is saved, the title of the field changes to a hyperlink and clicking on it may open given supplier's credit register page. Which service provider and with which options depends on the system setting External customer information request URL and your contract with the corresponding service provider.
+:?: Previous fields will be filled in automatically if Business Register help is used when creating the supplier's card.\\
+  ***VAT code** - VAT code
+  ***Currency** - shows the currency of the invoice. Double-click or Ctrl+Enter opens a selection from the currency register
+  ***PP account** - prepayment account
+  ***Debt Acc** - gives the possibility to place a debt account on the supplier
+  ***SR Account** - expense account
+  ***VAT Zone** - selection from a dropdown menu. Specifies the VAT zone associated with the transaction. For example: Domestic, EU, Non-EU, etc
+  ***Credit limit** - limit amount
+  ***Customer** - possible to place a customer
+  ***Consignment Country** - selection from a dropdown menu.
+  ***Default Del Time**
+  ***Tran. Cost** - shows the cost of transportation. Linked to the purchase recommendation report, Supplier+selection.
+  ***Deal type** - a dropdown menu from which the appropriate deal type can be selected. Required for export or import.
+  ***Worker** - supplier, who performs activities related to the project
+  ***Discount %** - discount applied to the supplier. Amount of discount in percentage
+  ***Purchasing group** - double click or Ctrl+enter opens a selection of purchasing groups.
+**Default proceeder(s)**
+  ***Users** - user register opens
+  ***added** - selection from the dropdown menu is added or replaced
+  ***Template** - selection from the dropdown menu
+==== 1.2. Bank Accounts ====
+=== 1.2.1. Fields ===
 {{:et:triinp20220704-091748.png}}
-:!: This part of the supplier card replaces the old solution, where different accounts were defined as supplier`s data fields which code was set in the system settings.
+If the supplier has several bank accounts they can be managed in this tab. \\
+:!: This part of the supplier card replaces the old solution, where different accounts were defined as supplier's data fields which code was set in the system settings.
   * **Bank acc** - bank account
   * **Code** - bank code. Selection from bank register
   * **Name** - bank name. Placed when placing the bank
   * **SWIFT** - bank swift. Placed when placing the bank
-  * **Address in bank** - bank address
+  * **Address in bank** - address in bank
-  * **Name in bank**- supplier`s name in the bank. Text //input//\\
+  * **Name in bank**- supplier's name in the bank. Text //input//\\
 :?: The previous fields serve the same purpose and behave in the same way as the corresponding fields on the supplier card front page.
   * **Payment term class** - for class-based payment term filtering
@@ Line 79: / Line 131: @@
 The bank accounts in the Bank accounts tab can be mass imported separately in ''Table -> Supplier's bank accounts''.
-**Use**\\
+=== 1.2.1. Use ===
 Bank accounts can be placed to the **Account** field on [[en/or_arve|purchase invoice]], [[et/otell_tellimus|ostutellimuse]], [[en/or_tasumine|payment]] and on [[et/fin_valjavote|väljavõtte]] documents. In addition to the described bank accounts, the placer also shows the account on the supplier's main page and its information.
 When placed on the purchase invoice, the corresponding **Bank code** is placed together with the bank account. \\
 :?: Payment term class entered on the document is used as an additional filter on purchase invoice and purchase order documents, which allows to define the supplier's bank accounts options more narrowly.
 ==== 1.3. Automation ====
-After creating a purchase invoice from received e-invoice, the purchase invoice line supplement functionality i.e. **Supplier`s automation** is applied automatically.
+There are two tables on the suppliers automation page. \\
-The purpose of the supplier`s automation is to enrich the purchase invoice lines information formed from the e-invoice in such a way that the user has as little work as possible in supplementing the invoice information and making the accounting document valid. This functionality also allows significant time savings, especially for multi-line purchase invoices (for example mobile phone invoices, etc.). **Supplier automation** allows to set up rules that look for a certain text segment in the e-invoice line and, upon detection, apply the desired account, objects, project and user to the line. In addition, there is a possibility that, together with a specific text section, some connection with the personnel register must also be valid, in order to identify the person/employee related to the invoice line and, based on this, to ensure that the above-mentioned fields are filled in.
+  *Table 1 named “__Supplement for rows (e-invoice)
+__” is meant for **creating automatic posting rules for e-invoices**.\\
+  *Table 2 named “__Content (from PDF)__” is meant for **identifying fields of purchase invoices imported as PDFs**  from attachments.:!: __Directo no longer develops__ data field identification from PDF invoices because it would never be able to reach even close to the same level of accuracy as an e-invoice. Therefore, we recommend starting to accept e-invoices, where data field identification is 100% accurate due to the standardized solution. Additionally, with e-invoices, it is possible to create automatic posting rules, which cannot be done with PDF invoices.
+{{:et:kellylytom20240521-134642.png}}
+**The automation of supplier e-invoices.**\\
-If the e-invoice, received in Directo, is changed to a purchase invoice entry, the purchase invoice fields are filled in as if user would do it manually. For example, if supplier is placed on purchase invoice manually, then the LS account and VAT code from the supplier's card is also placed on the purchase invoice line.
+After creating a purchase invoice from received **e-invoice**, the purchase invoice **row** supplement functionality i.e. **Supplier's automation** is applied automatically. The purpose of the supplier's automation is to enrich the purchase invoice liness information formed from the e-invoice in such a way that the user has as little work as possible in supplementing the invoice information and making the accounting document valid. This functionality also allows significant time savings, especially for multi-line purchase invoices (for example mobile phone invoices, etc.). **Supplier automation** allows to set up rules that look for a certain text segment in the e-invoice line and, upon detection, apply the desired account, objects, project and user to the line. In addition, there is a possibility that, together with a specific text section, some connection with the personnel register must also be valid, in order to identify the person/employee related to the invoice line and, based on this, to ensure that the above-mentioned fields are filled in.
-The same happens first when Directo creates a purchase invoice from an e-invoice. But it is important that the Content of the purchase invoice line is combined from the corresponding fields of the e-invoice line, i.e. a lot of important information is gathered in the Content, which is in text form. Once this part is done applies **Supplier Automation**. The supplier automation is largely based on searching for what is needed from the information gathered in the Content field of the purchase invoice line and acting accordingly.
+If the e-invoice, received in Directo, is changed to a purchase invoice entry, the purchase invoice fields are filled in as if user would do it manually. For example, if supplier is placed on purchase invoice manually, then the SR account and VAT code from the supplier's card is also placed on the purchase invoice line. The same happens first when Directo creates a purchase invoice from an e-invoice. But it is important that the Content of the purchase invoice line is combined from the corresponding fields of the e-invoice line, i.e. a lot of important information is grouped in the Content, which is in text form. Once this part is done applies **Supplier Automation**. The supplier automation is largely based on searching for what is needed from the information gathered in the Content field of the purchase invoice line and acting accordingly.
 === 1.3.1. Settings ===
-Supplier automation is set up supplier-specific, i.e. separately for each supplier whose e-invoices it is desired (or makes sense) to apply. To describe the rules, it is helpful to open the e-invoice XML sent by a specific supplier to see what information the e-invoice contains. The e-invoice XML can be viewed by opening the **Document transport** window and pressing the **XML** button from there. The setting is done in the Automation tab of the corresponding supplier's card:
+**Supplier automation** is set up supplier-specific, i.e. separately for each supplier whose e-invoices it is desired (or makes sense) to apply. To describe the rules, it is helpful to open the e-invoice XML sent by a specific supplier to see what information the e-invoice contains. The e-invoice XML can be viewed by opening the **Document transport** window and pressing the **XML** button from there. The setting is done in the Automation tab of the corresponding supplier's card:
-{{:et:triinp20220704-092239.png}}
+{{:et:vilja20231027-093354.png}}
   * **Content** - text field that is searched from purchase invoice Content line (from the imported e-invoice line).
   * **Item** - text field that is searched among the item codes identified in the e-invoice. Looking for content.
-  * **Reference** - text field that is searched among the reference number identified in the e-invoice. Exact match is searched for the financial recipe, otherwise is searched for content.
+  * **Reference** - text field that is searched among the reference number identified in the e-invoice. Exact match is searched for the finance recipe, otherwise is searched for content.
   * **Quantity** - number that is searched for in the invoice line of the e-invoice. Looking for an exact match. The quantity can also recognize > and < signs i.e. if >5 then applies if the quantity is >5.
-  * **Row sum** - number that is searched for in the invoice line of the e-invoice. Looking for an exact match.
+  * **Row sum** - number that is searched for in the invoice row of the e-invoice. Looking for an exact match.
-  * **Personnel** - relation of the rule to the personnel register. The connection can be created through the personnel card sub-registers **Documents, Assets and Linked Persons** row types. The drop-down menu shows the row types that are configured in the ''Settings -> Personnel settings -> Data types''. Use of data types in the context of personnel look in the corresponding manual. For example, if type Phone is created under Assets, then from purchase invoice line Content is searched does it contain a phone number, that is in the line of some person's personnel card tab Assets, that is with type Mobile phone on the Comment field. If it is found, the person is identified by it. Look Operation.
+  * **Row sum to** - Enables filtering out invoice sums within a specified range when Row sum is also filled
+  * **Personnel** - relation of the rule to the personnel register. The relation can be created through the personnel card sub-registers **Documents, Assets and Linked Persons** row types. The drop-down menu shows the row types that are configured in the ''Settings -> Personnel settings -> Data types''. Use of data types in the context of personnel look in the corresponding manual. For example, if type Phone is created under Assets, then from purchase invoice line Content is searched does it contain a phone number, that is in the line of some person's personnel card tab Assets, that is with type Mobile phone on the Comment field. If it is found, the person is identified by it. Look Operation.
   * **Account** - the account corresponding to the result of the rule. In other words, this account is applied to the purchase invoice line corresponding to the rule. This is the first preference of the rule. But it can also remain empty, then a different logic for finding an account is applied. Look Operation.
   * **VAT code** - the VAT code corresponding to the result of the rule.
@@ Line 113: / Line 174: @@
   * **Customer** - customer code corresponding to the result of the rule.
   * **Content** - text that corresponds to the result of the rule in the invoice line content cell. If it is filled, the content of the line is overwritten with exactly this text. If it is unfilled, the e-invoice line content is written to the invoice content.
-  * **Finance recipe** - the financial recipe corresponding to the result of the rule, which is applied when creating the purchase invoice. Only one finance recipe can be used in one invoice.
+  * **Finance recipe** - the finance recipe corresponding to the result of the rule, which is applied when creating the purchase invoice. Only one finance recipe can be used in one invoice.
+  * **Group** - Dropdown menu with Document and Row. The Document option groups the entire invoice into one line. The Row option groups the lines corresponding to the filters of a specific automation.
+  * **Confirm** - When the checkbox is ticked and all invoice rules are fulfilled, invoices are confirmed automatically
+  * **C. sum and C. sum to** - these fields are viewed when the Confirm checkbox is ticked. They help define when the invoice is set for automatic confirmation. In essence, this is the so-called tolerance range – meaning the invoice will only be confirmed if the sum falls within the specified range. For example, you can group certain invoice lines into one line or specify the sum of a specific line, and the invoice will be confirmed only if all lines with the Confirm checkbox ticked and within the range of C. sum values match.
+Rules are established through the fields **Content**, **Item**, **Reference**, **Quantity**, **Row sum** and **Personnel** and **Account**, **VAT code**, **Object**, **Project**, **User**, **Item**, **Customer**, **Content**, **Finance recipe** are fields that are applied if the rule is valid.
-Rules are established through the fields **Content**, **Item**, **Reference**, **Quantity**, **Row sum** and **Personnel** and **Account**, **VAT code**, **Object**, **Project**, **User**, **Item**, **Customer**, **Content**, **Financial recipe** are fields that are applied if the rule is valid.
 === 1.3.2. Operation ===
@@ Line 128: / Line 191: @@
   * **Description** contains the **Content** field description of some **Documents** type rule. The content of the rule can be empty and this is a so-called positive answer and the rule according to this condition matches the purchase invoice line;
-  * **Description** contains a value corresponding to the **Documents** __type__ of the Personnel sub-register, which is selected from among the valid entries in the Doc No. field (purchase invoice date is between the beginning and the end of the corresponding entry in the Documents register or is equal). More precisely, it identifies the person to whom the purchase invoice line is related.\\
+  * **Description** contains a value corresponding to the **Documents** __type__ of the Personnel sub-register, which is selected from among the valid entries in the Doc No. field (purchase invoice date is between the beginning and the end of the corresponding entry in the Documents register or is equal). More precisely, it identifies the person to whom the purchase invoice lnie is related.\\
 For example, the **Description** of a purchase invoice created from an e-invoice is as follows: ''95 miles; DateTime: 03.01.2018 16:40; Station: Circle K Laagri; Country: EE; Sum: 56.87 Gid:704483382122005476''\\
@@ Line 174: / Line 237: @@
   * Directo code of identified **User** is placed in the purchase invoice line field.
-**4.** Rules related to searching only **text**, **item**, **reference**, **quantity** and **sum** content from the e-invoice line information are filled in. Rules where none of the Personnel and Financial Recipe lines are in use. The purchase invoice lines are reviewed consecutively and checked whether the line description contains the **Content** field description of some previous rule. In this case, the **Content** field of the rule must have some searchable text.
+**4.** Rules related to searching only **text**, **item**, **reference**, **quantity** and **sum** content from the e-invoice line information are filled in. Rules where none of the Personnel and Finance Recipe lines are in use. The purchase invoice lines are reviewed consecutively and checked whether the line description contains the **Content** field description of some previous rule. In this case, the **Content** field of the rule must have some searchable text.
 If a purchase invoice line to which applies the condition is found i.e. the Description of the purchase invoice line contains the Content of the rule, then:
@@ Line 195: / Line 258: @@
 It is important to create such so-called general rules at the end of the table, because otherwise they would be applied first, and specific rules "wouldn't have time" to be applied. In the case of the previous rule example, if you add % as the last line of the description and 3333 as the account, then the rules PETROL and PETROL 95 would be applied first in the purchase invoice to be created and for all the remaining lines (which do not contain PETROL and PETROL 95) account 3333 would be determined.
+=== 1.3.3. Examples ===
-=== 1.3.3. Examples ===
 == 1.3.3.1. Always to a specific account and automatic confirmation ==
-The supplier's purchase invoices always go to the agreed account and are automatically confirmed. %-sign in the content line means "everything else".
+The supplier's purchase invoices always go to the agreed account and are automatically confirmed. %-sign in the content field means "everything else".
+{{:et:kellylytom20240521-150253.png}}
-{{:et:triinp20220803-134049.png}}
 ==1.3.3.2. The purchase invoice is confirmed only with a certain sum, otherwise it is not confirmed ==
-Example: A purchase invoice to be received on the basis of a permanent IT service contract, contract sum 150 euros per month.
+A purchase invoice to be received on the basis of a permanent IT service contract, contract sum 150 euros per month.
 The purchase invoice is confirmed only if the purchase invoice line is exactly 150 euros. If the sum differs, the purchase invoice is created but not confirmed.
-{{:et:triinp20220803-134918.png}}
+{{:et:kellylytom20240521-153721.png}}
+== 1.3.3.3. The purchase invoice is confirmed if the sum falls within the specified range, otherwise it is not confirmed ==
-== 1.3.3.3. Under certain conditions an automatically confirmed purchase invoice ==
+The purchase invoice received under the IT contract, the contract sum varies slightly from month to month. The purchase invoice is confirmed only if the sum of the purchase invoice is between 150 - 160 euros. If the sum differs, the purchase invoice is created but not confirmed.
-Directo permanent services invoice needs to be confirmed automatically, additional services invoice needs to be checked before confirmation. // All the permanent service items on the purchase invoice should be marked to the automation. Instead of additional services items, write the %-sign and do not mark confirmation.// By marking the sum behind the item, the permanent services purchase invoice will be confirmed only if the given sum corresponds exactly to the article and content.
+{{:et:kellylytom20240521-153655.png}}
-{{:et:triinp20220803-142315.png}}
+== 1.3.3.4. The purchase invoice has multiple lines and contains various permanent services. The invoice is confirmed if they remain within certain sums, otherwise it is not confirmed ==
-== 1.3.3.4. The the purchase invoice has multiple lines, wish to receive a single-line purchase invoice ==
+"IT service" has to be exactly 200 euros and "Internet" 300 euros, otherwise the invoice will not be confirmed.
-Only one purchase invoice line instead of all the Directo permanent services purchase invoice lines. // Mark checkmark to the cell "Group". Additional services invoice as additional lines. //
+{{:et:kellylytom20240521-152330.png}}
-:!: In this example one line has a different object. It should be taken into account that when "Group" is marked, the object of the first line is written on the document, i.e. a two-line purchase invoice is not made.
-{{:et:triinp20220803-144957.png}}
+==1.3.3.5. The purchase invoice has multiple lines and contains various permanent services. The invoice is confirmed if they fall within the range of specified sums, otherwise it is not confirmed  ==
+The sum of "IT service" can be between 200 - 250 euros and "Internet" between 300 - 350 euros, otherwise the invoice will not be confirmed.
-==1.3.3.5. Purchase invoice line grouping under certain conditions ==
+{{:et:kellylytom20240521-153537.png}}
+If the invoice sums exceed the established rules, the invoice will not be approved, and in the Int comment column you will see a comment on the lines that caused the invoice not to be approved, which can be read in full using a speech bubble.
+{{:et:kellylytom20240522-140821.png}}
+== 1.3.3.6. Purchase invoice automatically confirmed under certain conditions ==
+Directo's permanent service invoices need to be automatically confirmed, while additional service invoices need to be checked before confirmation. //Add all permanent service articles on the purchase invoice to the automation. Instead of additional service articles, write '%' and do not tickle Confirm checkbox.// By specifying the sum next to the item, the permanent service purchase invoice is confirmed only when the sum matches exactly with the specified content
+{{:et:kellylytom20240522-143703.png}}
+== 1.3.3.7. The purchase invoice has many lines, wish to receive a single-line purchase invoice ==
+Only one purchase invoice line instead of all the Directo permanent services purchase invoice lines. // Select "Document" from the Group filter. Additional service invoices should be added as extra lines. //
+:!: In this example one line has a different object. It should be taken into account that when "Group" is marked, the object of the first line is written on the document, i.e. a two-line purchase invoice is not made.
+{{:et:kellylytom20240522-143754.png}}
+==1.3.3.8. Purchase invoice line grouping under certain conditions ==
 For example, a purchase invoice from car service company, where are always 10-15 lines and all the actions are clearly described. Will need a one-line invoice with the explanation "car repair".
-//To the content cell should be written "car repair" and checkmark to the cell "group".//
+//To the content field should be written "car repair". Select "Document" from the Group filter and tickle Confirm checkbox.//
+{{:et:kellylytom20240522-144121.png}}
+== 1.3.3.9. Multi-line invoice where some lines are filtered by sums ==
+A multi-line invoice, where fixed services (full IT service and Internet) are posted in separate lines, but the lines of smaller sums(marked with %), if they fall between 1-20 euros, are grouped to the account with the content "Small services" and the invoice is confirmed. If the invoice also has sums that go beyond these rules, the invoice will not be confirmed.
+Supplier automation:
+{{:et:kellylytom20240522-145801.png}}
+Sample invoice lines:
+{{:et:kellylytom20240524-130758.png}}
+The transaction is like this, but the invoice is not confirmed, because the "Additional service" in the sum of 300 euros on the last row exceeds the limits established by the rules.
+{{:et:kellylytom20240523-130252.png}}
+== 1.3.3.10. How can I add leasing invoices to automation? ==
+The leasing company sends e-invoices where each customer has the same reference number and line explanation on the invoices. Vehicles could be identified with automation if using the contract number field.
+  - Write "Interest" and "Installment" to the field Content in the different lines and fill in the Fields, which are filled in if the rules match on all leasing contract purchase invoices.
+  - Write a leasing contract number to the field Content in a separate line and fill in the line fields, which are filled in differently depending on the match of the rules.
+{{:et:triinp20220803-154320.png}}
+//
+//
+== 1.3.3.11. An invoice where some rows need to be grouped and parts need to be shown row by row and confirm ==
+A multi-row invoice that requires **more complex automation** for correct posting and automatic confirmation:
+  *some rows need to be grouped and posted according to a finance recipe
+  *some rows need to be posted row to row
+  *some rows need to be linked to personnel documents (e.g., fuel cards)
+  *some rows need to be linked to personnel assets (e.g., leased cars)
+  *some rows need to be grouped based on sums or sum range
+  *to confirm the purchase invoice, the range of the allowed sum is required (ie, the so-called tolerance)
+Sample invoice:
+{{:et:kellylytom20240524-131718.png}}
+How to describe supplier automation for posting such an invoice:
+{{:et:kellylytom20240522-160156.png}}
+Transaction:\\
+In the internal comment column, on the rows that caused the invoice not to be confirmed, you will see a comment that can be read in its entirety using a speech bubble.
+{{:et:kellylytom20240522-161909.png}}
+{{:et:kellylytom20240522-161700.png}}
+== 1.3.3.12. The lines of the invoice are in blocks, where each block has an intermediate line with the reference number of the corresponding contract ==
+The invoice contains the same products, but according to the reference number of the contract, they must be posted for specific objects.
+Sample invoice PDF:
+{{:et:kellylytom20240523-105714.png}}
+How to describe supplier automation for posting such an invoice:
+{{:et:kellylytom20240523-110018.png}}
+Transaction:
+{{:et:kellylytom20240523-111000.png}}
-{{:et:triinp20220803-151203.png}}
 ==== 1.4. Transport ====
@@ Line 251: / Line 395: @@
 [[et:directo2directo|Directost Directosse transport]]