en:yld_hankija
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:yld_hankija [2022/07/07 15:41] triinp |
en:yld_hankija [2022/08/03 15:24] triinp [1.3.3. Examples] |
||
|---|---|---|---|
| Line 57: | Line 57: | ||
| * **Phone** - supplier's primary contact telephone number | * **Phone** - supplier's primary contact telephone number | ||
| * **e-mail** - supplier's primary email address | * **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 [[et/directo2directo|Directost Directosse transaport]] module if desired. | + | * **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. |
| Line 73: | Line 73: | ||
| * **SWIFT** - bank swift. Placed when placing the bank | * **SWIFT** - bank swift. Placed when placing the bank | ||
| * **Address in bank** - bank address | * **Address in bank** - bank address | ||
| - | * **Name in bank**- supplier`s name in the bank. Text field\\ | + | * **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. | :?: 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 | * **Payment term class** - for class-based payment term filtering | ||
| Line 196: | Line 196: | ||
| + | === 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". | ||
| + | |||
| + | {{: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. | ||
| + | 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}} | ||
| + | |||
| + | |||
| + | == 1.3.3.3. Under certain conditions an automatically confirmed purchase invoice == | ||
| + | |||
| + | 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:triinp20220803-142315.png}} | ||
| + | |||
| + | |||
| + | == 1.3.3.4. The the purchase invoice has multiple lines, wish to receive a single-line purchase invoice == | ||
| + | |||
| + | 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. // | ||
| + | |||
| + | :!: 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. 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".// | ||
| + | |||
| + | {{:et:triinp20220803-151203.png}} | ||
| + | |||
| + | |||
| + | == 1.3.3.6. 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. | ||
| ==== 1.4. Transport ==== | ==== 1.4. Transport ==== | ||
| Line 213: | Line 255: | ||
| **Automatically generated document after e-invoice arriving** - options Purchase invoice/Stock Receipt. With this setting, you can determine which document is created automatically from the received e-invoice. It means if the given supplier's e-invoice arrives in the ''Documents transport'' register, the document specified here is automatically created from the e-invoice. It allows to conveniently convert e-invoices into documents if the supplier always sends the same type of documents and does not have to do this manually by one e-invoice; | **Automatically generated document after e-invoice arriving** - options Purchase invoice/Stock Receipt. With this setting, you can determine which document is created automatically from the received e-invoice. It means if the given supplier's e-invoice arrives in the ''Documents transport'' register, the document specified here is automatically created from the e-invoice. It allows to conveniently convert e-invoices into documents if the supplier always sends the same type of documents and does not have to do this manually by one e-invoice; | ||
| + | [[et:directo2directo|Directost Directosse transport]] | ||
