en:asset
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
en:asset [2022/08/17 09:09] – [Fixed assets] triinp | en:asset [2023/02/06 14:24] – [2.2.1. Fiscal data] triinp | ||
---|---|---|---|
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 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 278: | Line 278: | ||
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 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 820: | Line 814: | ||
=== 8.3.1. Relation between assets and personnel assets === | === 8.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 '' | + | 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 829: | ||
- | === 8.3.2. Setting: | + | === 8.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 851: | Line 845: | ||
{{: | {{: | ||
- | === 8.3.3. System setting: Asset and personnel | + | === 8.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 859: | Line 853: | ||
- | Option ** No relation ** is intended for use, when the system setting '' | + | Option ** No relation ** is intended for use, when the system setting '' |
Line 870: | Line 864: | ||
- | 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 |
{{: | {{: |
en/asset.txt · Last modified: 2023/05/23 09:38 by triinp