Skip to main content

ChapterFixed Assets & Depreciation

Chapter 7 — Transferring an asset from one site to another

A computer goes from the head office to the branch: it travels, someone dispatches it, someone receives it. The transfer keeps track of every step, of the asset's condition on departure and on arrival, and of who gave their approval.

In this chapter

  • Requesting a transfer
  • The type, deduced from the two places
  • The workflow and who moves it forward
  • Dispatch, receipt, and what happens to the assignment
  • The transfer slip
  1. Request
  2. Validation
  3. Dispatch
  4. Receipt
  5. Closure
Book contents

Requesting a transfer

  1. Click New transfer (or Transfer in the register's ⋯ menu).
  2. In Assets to transfer, tick the assets. They all leave from the same site, 50 at most per transfer. An asset with no location must be assigned first: the page says so before sending.
  3. Choose the Destination and the Reason (the list of reasons is set in Settings › Transfer reasons).
  4. Choose what happens On arrival (see below), and if needed the Wanted date, the Transport and a Comment.
  5. Click Send the request.
The transfer request: the assets, the destination and the reason
  1. 1. Assets to transfer: tick the assets, all from the same site.
  2. 2. The counter: 50 assets at most per transfer.
  3. 3. The destination: any active location of the firm.
  4. 4. The reason is chosen from the firm's list.
  5. 5. On arrival: the assignee follows the asset, or the asset is assigned to the arrival location.
  6. 6. Send the request.

The type is deduced

You do not choose a transfer's type: it is deduced from the two places.

TypeWhen
InternalDeparture and arrival in the same site, whatever the places
Between sitesFrom one site to another
Site → depotTo a depot of another site
Depot → siteFrom a depot to another site
Between depotsFrom a depot to a depot of another site

An internal transfer is recorded and closed automatically: the assets change place at once. All the others follow the workflow.

The workflow

StatusNext actionWho
Awaiting validationValidate or RefuseManagement, or the manager of the departure or arrival site
ValidatedDispatchA user with the Edit right
In transitReceiveA user with the Edit right
Closed——

Cancel the transfer remains possible as long as it has not been dispatched, by whoever requested it or by management. In transit, the assets are travelling: they are received.

An asset still held by a work order (in progress or on hold) blocks the dispatch: complete the order before dispatching.

Dispatching and receiving

Dispatch sends the assets off: they become In transfer and the sender notes their Condition at departure.

Receive places them at the destination: they get back their previous status, and the receiver notes their Condition on arrival. Receipt also settles their assignment, according to the choice made in the request:

On arrivalWhat happens
Depending on the destinationTo a depot, the asset is assigned to the depot; elsewhere, its assignee follows it.
The assignee follows the assetThe asset keeps its assignee; only its location changes (an asset assigned to a location is always assigned to the arrival location).
The asset is assigned to the arrival locationIts current assignment ends; it is entrusted to the arrival location.

An assignment to another site, created from Assignments, waits for this receipt to take effect (chapter 6).

A transfer's page

It shows the route (origin, destination), the assets with their condition on departure and on arrival, the linked assignments, and the Transfer workflow step by step, read from its log. An internal transfer shows « Closed automatically ».

Transfer slip prints an A4 PDF numbered TR-YYYY-NNNN: the route, the assets and three signatures: dispatched by, transported by and received by.