Skip to content

Asset transactions

An asset transaction records that an asset changed hands or went out for service. Every transaction is saved as a document in the Check in / Check out section, so you can always see who did what with an asset and when. Each transfer document has its own number; the numbering format is set in Company settings.

The Check in / Check out / Transfers page: the Check in, Check out, Transfer, and Check-out by booking buttons, a search box, the Recorded by filter, and the document list with the Document No., Date, Operation type, Movement, Planned return date, Number of assets, and Author columns

Besides the documents a storekeeper creates, the list includes self-service documents — the ones employees create themselves when they take or return an asset. They carry a Self-service tag, and the Recorded by filter above the list on the right shows either Staff or Self-service documents. If the Booking module is enabled, there’s also a Check-out by booking button above the list.

At any moment an asset has exactly one holder: either an employee or a location. An asset can’t be with an employee and in a location at the same time — every transaction moves it from one to the other.

The current holder decides which transactions are available. If the asset is with an employee, you can check it in, send it for service, or write it off. If it’s in a location, you can check it out to an employee, transfer it to another location, send it for service, or write it off. That’s why the Action menu on the asset card shows only the operations that fit the asset’s current state.

An asset is always in one place, and UNIO24 makes sure every move starts where the asset actually is:

  • An asset at a service center can’t be checked out, checked in, or transferred until it comes back from repair. On the card of such an asset, the Action menu has only Return from service. If the asset is part of another one (for example, a power supply in a kit), the rule applies to the whole kit.
  • You can’t transfer an asset to the location it’s already in — UNIO24 asks you to pick a different destination.
  • A document that lists an asset in the wrong location — not where it actually is — won’t save, and UNIO24 names those assets.

Before a check-out or transfer, UNIO24 checks the asset: is its calibration overdue, does it have expired documents or open inspection defects, is it booked for someone else? Anything it finds is shown as a warning right in the form. When you save, UNIO24 asks “Check them out anyway?” (for a transfer, “Move them anyway?”). If company rules forbid the check-out — for example, an open critical defect or overdue calibration in Block mode — the Save button is unavailable.

If an inspection at check-out and check-in is set up for the asset type, the form shows an inspection block: a required inspection has to be carried out before you can save.

UNIO24 has five types of transactions.

  • Check out — hand an asset from a location to an employee. After check-out, the employee is the holder.
  • Check in — take an asset back from an employee into a location. After check-in, the location is the holder.
  • Transfer — move an asset from one location to another. The holder is still a location, only the location changes; no employee is involved.
  • Sent to service — send an asset to a service center.
  • Returned from service — take an asset back from a service center.

You can check out, check in, and transfer assets either from the Check in / Check out section or right from the asset card. Sending for service, returning from service, and writing off are done only from the asset card — the Check in / Check out section has no buttons for them. Employees with the Self-service role take and return assets on their own — see Self-service.

The same check-out, check-in, and transfer operations work not only for assets but also for license seats: a seat can be checked out to an employee or an asset, checked back in, and transferred. For details, see Licenses.

When an asset is checked in or transferred between locations, its Condition is recorded — for example, Good or Damaged. This is the actual physical condition, separate from the lifecycle status. The current condition is shown on the asset card. The list of conditions is set up in Asset statuses and conditions; conditions are also assessed during an audit.

Whether the condition must be entered is up to the administrator, on the Settings → Transfer settings page, in the Asset condition on check-in and transfer block:

  • Don’t ask — the forms have no Condition field;
  • Optional — you can enter the condition or leave it empty;
  • Required — check-ins and transfers won’t save without a condition for every asset. This is the default.

The Transfer settings page: the Asset condition on check-in and transfer block and the Asset condition on a self-service return block, each with the Don’t ask, Optional, and Required options

The second block on this page — Asset condition on a self-service return — does the same for self-service. If all conditions are turned off in your company, Required works like Optional.

When an asset goes out for repair or maintenance, this is recorded with the Sent to service and Returned from service transactions (on the asset card they are the Send to service and Return from service actions). When you send an asset for service, you choose one of two modes in the Service options block.

The Service window with the Service options block (Take out of use / Record in history only) and their hints, the Expected return date, Service center, and Fault description fields, and the Materials used block

Take out of use. The asset’s lifecycle status becomes In Maintenance and it’s unavailable for other operations. You enter a Expected return date. While the asset is in this status, the card offers Return from service instead of Send to service: the return closes the service and makes the asset available again. Use this mode for repairs that take the asset out of use.

Record in history only. The asset’s status doesn’t change and it stays available; only a service record is created. You enter both dates up front (Date sent for repair and Return date), so no separate return is needed. Use this mode to record a repair that’s already done, or maintenance that didn’t take the asset out of use.

In both modes, the Service center is required — you pick it from the Service centers list, and if the one you need isn’t there, you can add it right from the list. The record can also include a Fault description, Repair cost, Repair notes from the service center, and the inventory items used.

Sending assets for service and returning them requires the Repairs permission. While an asset is at a service center, it can’t be sent for repair again — it has to come back first. If an asset has no scheduled return date and the repair runs longer than two weeks, you get a reminder about the stalled repair.

A repair can be part of a work order: if a service center does the work, the asset is sent for service when the work order moves to In progress, and the return from service completes the work order on its own.

All service records are collected on the Service tab of the asset card (if the Maintenance module is enabled, the tab is called Maintenance). The switch at the top of the tab shows the asset’s repairs, work orders, and tickets, so you can see its full repair history.

At the end of its life, an asset is written off: on the asset card, open the Action menu, choose Write off, and select a write-off location. The asset moves there, its lifecycle status becomes Pending Disposal, and its card no longer offers operations. If the asset was in repair at that moment, the open repair is closed.