en:asset
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:asset [2022/07/04 11:32] – [8.2.1 Setup and usage options] triinp | en:asset [2023/05/23 09:38] (current) – [9.3.3. System setting: Asset and Employee relation] triinp | ||
---|---|---|---|
Line 9: | Line 9: | ||
* The Asset inventory | * The Asset inventory | ||
- | The Asset Card and the Fixed Asset Card can not be used at the same time, the data does not move correctly and Directo does not correct errors due to incorrect use. | + | :!: The Asset Card and the Fixed Asset Card can not be used at the same time, the data does not move correctly and Directo does not correct errors due to incorrect use. |
Line 85: | Line 85: | ||
====2.2.1. Fiscal data==== | ====2.2.1. Fiscal data==== | ||
- | * **Start date**: date from which the depreciation is calculated. Usually fixed asset purchase date. Related to the date of purchase. The start of the calculation can be in the same month in the past compared to the date of purchase. Future can be used. | + | * **Start date**: date from which the depreciation is calculated. Usually fixed asset purchase date. Related to the date of purchase. The start of the calculation can be in the same month in the past compared to the date of purchase. Can be in the past until to the purchase invoice op. date. Future can be used. |
* **Purchase price**: fixed asset original purchase price (the purchase price may also be negative) | * **Purchase price**: fixed asset original purchase price (the purchase price may also be negative) | ||
* **Value corrections**: | * **Value corrections**: | ||
Line 181: | Line 181: | ||
==== 2.4. Value corrections ==== | ==== 2.4. Value corrections ==== | ||
- | * **Date**: date - start of calculation | + | * **Date**: date - start of calculation. Can be in the past until to the purchase invoice op. date. |
* **Value correction**: | * **Value correction**: | ||
* **Object**: object or list of objects with commas | * **Object**: object or list of objects with commas | ||
Line 275: | Line 275: | ||
- | ==== 3.3 Creating a fixed asset card from the stock depreciation document ==== | + | ==== 3.3. Creating a fixed asset card from the stock depreciation document ==== |
After confirming the stock depreciation, | After confirming the stock depreciation, | ||
+ | |||
+ | :!: Necessary fine-tuning on the stock depreciation document **Asset creation** - Yes | ||
==== 3.4. Creating a fixed asset card from register==== | ==== 3.4. Creating a fixed asset card from register==== | ||
Line 338: | Line 340: | ||
- | ===== 4. The asset card is editable ===== | + | ==== 3.7. Fixed asset code numbering ==== |
+ | |||
+ | One or multiple fixed asset code ranges can be used for fixed assets. | ||
+ | * One range is used for all fixed assets | ||
+ | |||
+ | If one range is in use, when creating the next fixed asset card, the next range code is taken as the fixed asset code (For example, FA1 - when creating the next card, the fixed asset code is set to FA2). | ||
+ | |||
+ | * Multiple ranges are used for all fixed assets | ||
+ | |||
+ | If multiple ranges are in use, when creating the next fixed asset card, double-click on the code and select the range that is used. | ||
+ | |||
+ | :!: If you want to use numbers in ranges - for example FA00001, a number must be added before the number part of the code - for example FA10001. Using the code FA00001, the program offers FA2 as the next code. If the code is FA10001, the program will offer FA10002 as the next code. | ||
+ | ===== 4. The fixed asset card is editable ===== | ||
System settings – '' | System settings – '' | ||
- | **YES** - all changes can be made directly on the asset card, but reports for an earlier period cannot be taken later - who was in charge etc. | + | **YES** - all changes can be made directly on the fixed asset card, but reports for an earlier period cannot be taken later - who was in charge etc. |
\\ | \\ | ||
- | **NO** - changes can only be made on the additional documents. Changes are saved and they can be reported in the past. Option **NO** allows to make changes in fixed assets and low value assets fields, which are not closed on asset card. | + | **NO** - changes can only be made on the additional documents. Changes are saved and they can be reported in the past. Option **NO** allows to make changes in fixed assets and low value assets fields, which are not closed on fixed asset card. |
- | If System setting '' | + | If System setting '' |
Following fields are locked on the **Fixed asset card**: | Following fields are locked on the **Fixed asset card**: | ||
Line 354: | Line 368: | ||
* Type | * Type | ||
* Calculation method | * Calculation method | ||
- | * Fiscal data (all the fiscal data on asset card) | + | * Fiscal data (all the fiscal data on fixed asset card) |
- | * Accounts (all the accounts on asset card) | + | * Accounts (all the accounts on fixed asset card) |
* Department | * Department | ||
* User | * User | ||
Line 366: | Line 380: | ||
* Cost project | * Cost project | ||
- | |||
- | Following fields are locked on the **Low value asset card**: | ||
- | |||
- | * Code | ||
- | * Type | ||
- | * Value correction | ||
- | * Purchase price total | ||
- | * Start date | ||
- | * Purchase price | ||
- | * End date | ||
- | * Purchased | ||
- | * Quantity | ||
- | * Location | ||
- | * Department | ||
- | * User | ||
- | * In charge | ||
- | * Object | ||
- | * Customer | ||
- | * Project | ||
- | |||
===== 5. Asset card confirmation ===== | ===== 5. Asset card confirmation ===== | ||
Line 413: | Line 407: | ||
:!: If the asset module has already been used and the assets have been depreciated, | :!: If the asset module has already been used and the assets have been depreciated, | ||
- | === 5.2 Confirmation use === | + | === 5.2. Confirmation use === |
== 5.2.1. Fixed asset is purchased with purchase invoice == | == 5.2.1. Fixed asset is purchased with purchase invoice == | ||
Line 530: | Line 524: | ||
* **Range**- transaction range in which the transaction must be made (usually comes automatically); | * **Range**- transaction range in which the transaction must be made (usually comes automatically); | ||
* **Asset**- | * **Asset**- | ||
- | * **Class** - depreciation can be calculated by class; | + | * **Class** - depreciation can be calculated by class; it is possible to add classes as a comma-separated list; |
* **Object** - depreciation can be calculated by objects or by object combinations class; | * **Object** - depreciation can be calculated by objects or by object combinations class; | ||
* **Project** - depreciation can be calculated by projects; | * **Project** - depreciation can be calculated by projects; | ||
Line 560: | Line 554: | ||
- | === 6.2.1.Estimated depreciation end time and last transaction === | + | === 6.2.1. Estimated depreciation end time and last transaction === |
The FISCAL DATA tab on the fixed asset card shows the expected end of depreciation, | The FISCAL DATA tab on the fixed asset card shows the expected end of depreciation, | ||
Line 651: | Line 645: | ||
Allows to share depreciation cost between multiple object and/or projects at the same time over a given period. | Allows to share depreciation cost between multiple object and/or projects at the same time over a given period. | ||
- | === 6.4.1.Setting the first proportion === | + | === 6.4.1. Setting the first proportion === |
* **Proportion**: | * **Proportion**: | ||
Line 696: | Line 690: | ||
- | === 6.6.1.Diminishing balance method- depreciation calculated in advance=== | + | === 6.6.1. Diminishing balance method- depreciation calculated in advance=== |
{{: | {{: | ||
Line 724: | Line 718: | ||
\\ | \\ | ||
\\ | \\ | ||
- | ===== 7. Address on fixed asset and low value asset card ===== | ||
- | ==== 7.1. Setting the addresses ==== | + | |
+ | ===== 7. Value corrections ===== | ||
+ | |||
+ | |||
+ | ==== 7.1. Influence of value corrections to depreciation ==== | ||
+ | |||
+ | * Value corrections is used when the fixed asset needs to be revalued (for example, an extra was purchased or there is significant maintenance work that must increase the current price of the fixed asset and must also depreciate). Similar to the creation of a fixed asset card, the additional amount can be added either through a related purchase invoice or directly to the fixed asset card. | ||
+ | |||
+ | * From the date of value correction depreciation is calculated on the increased amount. | ||
+ | |||
+ | * Entering value corrections does not change previously made depreciation transactions, | ||
+ | |||
+ | * If a value correction has been indicated on the fixed asset, and **depreciation has been calculated on this amount, this value correction can no longer be deleted** (row is locked). If the depreciation transactions are deleted, it is possible to delete the value correction. | ||
+ | |||
+ | * A negative value correction can also be entered. For negative amounts, enter the amount with a minus sign. This lowers the current price and the monthly amortization amount decreases. Cannot enter a minus sum that exceeds the current price - the system informs **" | ||
+ | |||
+ | * If the value correction needs to be entered in the past, but depreciation has already been calculated for that period, the system warns **"The asset has later changes" | ||
+ | |||
+ | |||
+ | ==== 7.2. Influence of value correction entry dates on depreciation ==== | ||
+ | |||
+ | * If the monthly depreciation transaction has been made (eg March 2023) and the value correction is added with the last date of the given month (e.g. 31.3.2023), then value correction goes into the depreciation calculation starting from the next month, i.e. April. If the value correction is added up to the date of the last month (e.g. with a date between 1-30.3.2023), | ||
+ | |||
+ | * If the current price of the fixed asset is 0 and a value correction is added to the fixed asset, then in order for depreciation to be calculated from the same month, the beginning of the calculation must be set to the 1st day of the month. If you want to start calculating depreciation from the next month, put the last date of the month. | ||
+ | |||
+ | * If the current price of the fixed asset is above 0 and a value correction is added to the fixed asset on any date of the month, it will be included in the depreciation calculation for the same month. | ||
+ | |||
+ | |||
+ | ==== 7.3. Examples of entering value corrections ==== | ||
+ | |||
+ | **Example 1**: if the residual value of the fixed asset is 0 and a value corrections is added to the fixed asset, then a new depreciation % must be calculated so that the added value correction is amortized for the required time. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **Example 2**: if the residual value of the fixed asset is 0 and a value correction is added to the fixed asset in the case of fixed assets depreciated using the Units of Production method, then a new usage limit must be calculated so that the added value correction is amortized by the end of the new usage limit. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **Example 3**: if the calculation end date is changed on the fixed asset card (a new date is entered in the "End date" field), the data in the Amort % field is not automatically updated. To do this, you need to press the button " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | ===== 8. Address on fixed asset and low value asset card ===== | ||
+ | |||
+ | ==== 8.1. Setting the addresses ==== | ||
Line 741: | Line 782: | ||
- | ==== 7.2. Entering addresses location codes ==== | + | ==== 8.2. Entering addresses location codes ==== |
Line 761: | Line 802: | ||
- | ==== 7.3. Use of address location codes ==== | + | ==== 8.3. Use of address location codes ==== |
Line 772: | Line 813: | ||
- | ==== 7.4. Display location fields on the Fixed Asset and Low Value Asset card ==== | + | ==== 8.4. Display location fields on the Fixed Asset and Low Value Asset card ==== |
The location code is in the data group ** LOCATION ** on the fixed asset card. More fields of the location code can be displayed under the Fixed Asset card fine-tuning - '' | The location code is in the data group ** LOCATION ** on the fixed asset card. More fields of the location code can be displayed under the Fixed Asset card fine-tuning - '' | ||
- | ===== 8. User management ===== | + | ===== 9. User management ===== |
Fixed assets can be linked to users with purpose to have an overview who owns or is responsible for the asset. Users are managed using the fields ** User ** and ** In charge ** on the asset main page or in the tab** Users **: | Fixed assets can be linked to users with purpose to have an overview who owns or is responsible for the asset. Users are managed using the fields ** User ** and ** In charge ** on the asset main page or in the tab** Users **: | ||
Line 783: | Line 824: | ||
{{: | {{: | ||
- | ==== 8.1 Simple user management ==== | + | ==== 9.1. Simple user management ==== |
Line 792: | Line 833: | ||
- | ==== 8.2 Detailed user management ==== | + | ==== 9.2. Detailed user management ==== |
Line 816: | Line 857: | ||
{{: | {{: | ||
- | ==== 8.3. Setup and usage options ==== | ||
- | === 8.2.1.1. Relation between assets | + | ==== 9.3. Setup and usage options ==== |
- | It is necessary to set the assets **Types**, in order to save assets lines to **Assets** tab in Employee card. A list of asset types is created '' | + | === 9.3.1. Relation between assets and personnel assets === |
+ | |||
+ | It is necessary to set the assets **Types**, in order to save assets lines to **Assets** tab in Employee card. A list of asset types is created '' | ||
{{: | {{: | ||
Line 835: | Line 877: | ||
- | === 8.2.1.2. Setting: | + | === 9.3.2. Setting: |
- | '' | + | |
+ | '' | ||
specifies whether there can be multiple end-dated rows in the Users tab at one time or not. In other words, can there be multiple users at the same time. Setting options: yes, no: | specifies whether there can be multiple end-dated rows in the Users tab at one time or not. In other words, can there be multiple users at the same time. Setting options: yes, no: | ||
Line 850: | Line 893: | ||
{{: | {{: | ||
- | === 8.2.1.3. System setting: Asset and personnel | + | === 9.3.3. System setting: Asset and Employee |
- | Option **user** and **in charge** is intended for use, when the system setting '' | + | Option **user** and **in charge** is intended for use, when the system setting '' |
Line 858: | Line 901: | ||
- | Option ** No relation ** is intended for use, when the system setting '' | + | Option ** No relation ** is intended for use, when the system setting '' |
- | ==== 8.3. Reports ==== | + | **Column names of the Users tab table** |
+ | |||
+ | The name of the user column in the table depends on the system setting "Asset and Employee relation" | ||
+ | |||
+ | |||
+ | If " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | If "In charge" | ||
+ | |||
+ | {{: | ||
+ | ==== 9.4. Reports ==== | ||
ON TÄIENDAMISEL !!\\ | ON TÄIENDAMISEL !!\\ | ||
Line 868: | Line 925: | ||
- | Therefore, it is reasonable to turn on the system settings ** Asset and Personnel | + | Therefore, it is reasonable to turn on the system settings ** Asset and Employee |
{{: | {{: | ||
- | ===== 9. Asset actions ===== | + | |
+ | ===== 10. Asset actions ===== | ||
[[en: | [[en: | ||
Line 879: | Line 937: | ||
- | ===== 10. Fixed Assets register ===== | + | ===== 11. Fixed Assets register ===== |
| | ||
Line 900: | Line 958: | ||
:!: Asset history report still shows future periods depreciation, | :!: Asset history report still shows future periods depreciation, | ||
- | ===== 11. Frequently Asked Questions ===== | + | ===== 12. Frequently Asked Questions ===== |
- | ==== 11.1. How do I get rid of a draft? ==== | + | ==== 12.1. How do I get rid of a draft? ==== |
* If a draft is left from document, cannot be saved and reports an error, then the error message can be removed by closing the asset card, reopening it and pressing **Discard**. | * If a draft is left from document, cannot be saved and reports an error, then the error message can be removed by closing the asset card, reopening it and pressing **Discard**. | ||
Line 916: | Line 974: | ||
- | ==== 11.2. Why can't the draft be saved? ==== | + | ==== 12.2. Why can't the draft be saved? ==== |
* If the document does not have an active save button, may some fields contain code, that does not exist in Directos. | * If the document does not have an active save button, may some fields contain code, that does not exist in Directos. |
en/asset.1656923535.txt.gz · Last modified: 2022/07/04 11:32 by triinp