User Tools

Site Tools



en:fin_kanne

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:fin_kanne [2025/03/07 10:21] – [3.3.6 Object level requirement] kellylytomen:fin_kanne [2026/10/20 10:34] (current) – [6. Bulk insert] lauratam
Line 200: Line 200:
   *If there is no object in the corr. account, but object levels have been set, the account object will appear in the field.{{:et:kellylytom20250307-101939.png}}   *If there is no object in the corr. account, but object levels have been set, the account object will appear in the field.{{:et:kellylytom20250307-101939.png}}
  
-**Account subject to periodization**+**Object of account subject to periodization**
   *If the account is missing an object but it has object levels, the corr. account object will be placed there. {{:et:kellylytom20250307-100102.png}}   *If the account is missing an object but it has object levels, the corr. account object will be placed there. {{:et:kellylytom20250307-100102.png}}
 +
 +**Error messages**
 +  *If the level of the object in the field does not match, the field will be red and transactions cannot be created. This also means that objects with a different level cannot be placed. {{:et:kellylytom20250307-102902.png}}
 +  *The error field has the following explanatory tooltips:
 +  ***'object is invalid'** ⇒ such an object does not exist at alL
 +  ***'object with required level is missing'** ⇒ the account has a specified level, but an object with that level has not been added
 +  ***'invalid object level'** ⇒ the entered object level is not allowed in the account
 ===== 4. Periodization of the transaction (OLD DESIGN) ===== ===== 4. Periodization of the transaction (OLD DESIGN) =====
 Periodization of a transaction can be started from a saved transaction by pressing the „Periodize“ button in the header. Periodization of a transaction can be started from a saved transaction by pressing the „Periodize“ button in the header.
Line 285: Line 292:
  
  
 +===== 6. Fine-tuning =====
 +
 +Button {{:et:evelint20211117-151117.png}} on the right side of the header opens the fine-tuning settings. 
 +{{:et:evelint20211122-161715.png}}
 +
 +  * **Currency rate by row date** - if this setting is activated, the exchange rate is set according to the row date. If this setting is not activated, the rate is set according to the date in the header.
 +  * **Attachment preview** - whether and where a preview of the attachment attached is displayed. Options are missing, right and bottom.
 +
 +===== 7. Bulk insert =====
 +
 +You can create transaction rows in Excel and bulk insert them directly to the transaction.
 +
 +  *If the account number is specified and the description box is empty, the account name is placed in the Description box
 +  *Amounts are placed on the transaction with both a plus and a minus sign
 +  *Only one amount can be bulk inserted, either in the debit or credit column
 +  *Zero is not a number, i.e. it is possible to insert amounts from an Excel table with Debit 0.00 and Credit 40.00. After importing, only Debit (empty) and Credit 40.00 remain.
 +
 +===== Frequently asked questions =====
 +
 +==== Saving a new transaction fails because the account is missing levels... ====
 +
 +When you save a transaction, Directo shows this message if:
 +  * object levels are marked as mandatory on the [[en:konto|financial account]], or
 +  * the level is marked as mandatory for the transaction document on the [[en:obj_tase|object level]] card.
 +
 +{{:et:lauratam20261020-102758.png}}
 +
 +
 +If you have seen this message on both the old and the new design transaction, you may have noticed some differences:
 +  * The new transaction is __not saved__ if the document doesn't meet the set requirements.
 +  * The old transaction notified you of what was missing but still __saved the incomplete transaction__.
 +
 +When you save a transaction, Directo records it in the accounts immediately. The new transaction makes sure that a transaction that doesn't meet the requirements doesn't end up in your reports.
 +
 +If you used to enter the transaction first and add the objects later, we **recommend** the following:
 +  * When you create a new transaction, save the document first so that it gets a document number.
 +  * Fill in the document.
 +  * If saving fails, Directo keeps the draft of the document. You can add the required objects later without losing the information you have already entered.
 +
 +:!: The draft version of a document is kept for 7 days from the last change to the document.
 +
 +==== Differences between the new and old transaction periodization ====
 +
 +:?: The new transaction periodization works the same way as **sales invoice** and **purchase invoice** periodization. This means that before you start periodizing, you enter the //income or expense account// whose amount you want to distribute over periods on the transaction (:!: //in the old design, you had to enter the corresponding account first//).
 +
 +Example: periodizing the premises insurance expense over a full year.
 +
 +  * Before you press **Periodize**, enter the account you want to periodize on the transaction.
 +
 +{{:et:lauratam20261020-103228.png}}
 +
 +  * In the periodization window, select the **Corr. account** and the other periodization conditions.
  
 +{{:et:lauratam20261020-103359.png}}
  
 +  * When you periodize, Directo replaces the periodized account with the corresponding account and distributes the amounts over the selected periods, decreasing the corresponding account and increasing the original account of the transaction.
  
 +{{:et:lauratam20261020-103434.png}}
en/fin_kanne.1741335663.txt.gz · Last modified: 2025/03/07 10:21 by kellylytom

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki