Mandates and sub-mandates in timeSensor LEGAL

Mandates and sub-mandates in timeSensor LEGAL

General
In a client’s dossier, you can create an unlimited number of mandates. The mandates can be organized hierarchically as a mandate tree with any level of depth.

Creating a Hierarchical Mandate Structure

The following illustration shows a dossier with a hierarchical mandate tree.      


Mandates can be arranged vertically via drag & drop with the mouse. By indenting to the right or left, the desired hierarchy of mandates is created.
  1. You can move mandates using the keyboard shortcut Cmd/Ctrl + Right Arrow or Cmd/Ctrl + Left Arrow
  2. You can right-click on a mandate and choose Indent Mandate Right or Indent Mandate Left from the context menu

Displaying Mandates

Each indented mandate has a Mandate Name and a Mandate Path. Let us consider the fifth mandate, named "Civil Law" in the example above:
  1. The mandate name is Civil Law
  2. The mandate path is ALPHA / Contracts / Civil Law
Depending on the context, timeSensor LEGAL displays either the mandate name or the mandate path. 
  1. In the mandate folder, the mandate path is displayed so that mandates with the same name can be distinguished within the ALPHA, BETA, and GAMMA sections:


  2. In invoicing, only the mandate name is displayed, as this is generally sufficient for the client (but it is also possible to include the mandate path in a print template).

Structuring Mandates

When creating a mandate structure, some mandates may serve only as structural elements and should not appear in the timesheet, as they are not directly billable. In our example, these are the mandates:
  1. ALPHA, BETA, GAMMA
  2. ALPHA / Contracts
  3. BETA / Contracts
  4. GAMMA / Contracts
To prevent users from booking services to these structuring mandates, select the Mandate Invisible in Timesheet option in the mandate settings under Invoicing.

Consolidated Invoices

You can transfer the accumulated services of subordinate mandates to a higher-level mandate to create a consolidated invoice. For example, in our case, you could create a consolidated invoice for ALPHA, one for BETA, and one for GAMMA. How to create consolidated invoices is explained in a separate FAQ article. In the consolidated invoice, timeSensor LEGAL displays the mandate names by default and not the mandate paths.