Fixed assets

The module for property that serves for years and loses value gradually: vehicles, buildings, equipment. The difference from stock is fundamental: goods sit at their cost until they are sold, while a fixed asset becomes cheaper every month on its own, without a single movement. It is that "on its own" the module turns into postings.

The second trait is that there are hardly any documents here. The module holds exactly one document (disposal); all the movements are made by services: commissioning and depreciation. The asset card creates no postings — it accumulates their result in the residual value.

Video walkthrough: Fixed assets in ERPJS step by step — buying a van, the asset card, commissioning, depreciation.

The route: an asset's life from purchase to disposal

Purchase → the money sits on the capital investment account
        ↓
Asset card (category → type + depreciation model, inventory number)
        ↓
Commissioning (service): capital investments → the type's balance account
        ↓
Depreciation (service, monthly): wear to the type's accounts, residual value falls
        ↓
Disposal: sale or write-off — cost and accumulated depreciation are closed
        ↓
Asset history remembers every step

Category — the card's template: it holds the type and the depreciation models together, so creating a new card comes down to picking one category instead of three fields.
Asset card — one object: inventory number, acquisition cost, department, and a classification if needed.
Commissioning — the service puts the asset on the balance sheet and fills in the "in use since" date. Until then the card is just an entry in the register.
Asset depreciation — the charging step: each run charges one period of the model — a month, quarter, year or day (a monthly run of a daily model charges one day's amount); the posting lands on the type's accounts.
Disposal — a sale or a write-off: it removes the original cost, closes the accumulated depreciation and charges the residual value to the account you name.
Asset histories keeps the log of all this by itself.

What is worth understanding

The accounts are known by the type, not by the card. The type says: balance — 105, depreciation — 131, expense — 921. So "why did the depreciation land on the wrong account" is almost always answered in the type, not in the card.

Three grouping references, easy to confuse. The category is a template (type + model), the type carries the accounts, the classification is just a label with no effect on the books. The fourth, the department, answers "where the asset lives" and works as a filter for the batch services.

An asset does not start wearing out on the purchase date. Charging starts with the period after the "Used with" date (set by commissioning), and later after the last charge ("Depreciation date"): in the commissioning month a monthly model charges nothing. The "Set Asset Depr. Start Date" switch in the Assets Setting only fills in the "Oper. Date" of the service window (commissioning date, last day of the month, quarter or year); with "None" the "Depreciation" item of the fixed asset card menu does not open the service window — it only warns, while from the module menu the service opens with an empty date; the same setting holds the account where capital investments accumulate before commissioning.

The services skip whatever is not ready. Depreciation passes over closed assets, ones not yet commissioned, and ones already depreciated to their salvage value. So "nothing was charged" more often means an uncommissioned asset than a calculation error. The exception is the "Depreciation 100%" model: it does not wait for a new period and writes off the whole residual value (down to the salvage value) already in the commissioning month. It does need a commissioning date, like the others: an uncommissioned asset is not charged by it either.

A mistake can be rolled back, but only the last one. Delete Last Depreciation cancels precisely the last charge, and delete asset commissioning undoes a premature commissioning. These are narrow corrections, not "editing the past".

Hire equipment is a fixed asset too. The rental module sees it as a hire unit with a status and running hours, while here the same machine lives its accounting life — cost and depreciation.

Where to start in a new database

Assets Setting — the capital investment account, the date the depreciation service fills in, and the default model.
Asset types — balance, depreciation and expense accounts for each kind of property.
Depreciation models — method, useful life, step.
Asset Categories — bind a type to its models so cards are created with one choice.
Asset departments — if you need batch operations per unit; then the first cards and commissioning.

Common tasks

You need	Where to go
register a new asset	Fixed assets
put it on the balance sheet	Asset commissioning
charge the monthly depreciation	Asset depreciation
sell or write off	Disposal of fixed assets
see what was sold or written off in a period	Journal Disposal Fixed Assets
get a list of fixed assets	List of Fixed Assets
see the depreciation for a period	Information on depreciation of fixed assets
look at one asset in full	Fixed assets report · asset histories
run a stocktake	Asset Inventory — a count sheet for the committee
correct a wrong charge	Delete Last Depreciation
undo a premature commissioning	Delete asset commissioning

Everything in the module

Documents: disposal of fixed assets

References: fixed assets · asset categories · asset types · depreciation models · asset classifications · asset departments

Logs: asset histories

Settings: Assets Setting

Reports: information on depreciation of fixed assets · fixed assets report · asset inventory · list of fixed assets · journal disposal fixed assets

Maintenance: asset commissioning · asset depreciation · delete last depreciation · delete asset commissioning

Where to look next

Nominal ledger — the accounts depreciation lands on.
Rental — the same machines seen from the hire side.
Stock — property bought for resale rather than for service.