decídalo
Documentation
Ask AI
Search Results for

    Show/Hide Table of Contents

    Time Recording Setup

    Note: Time recording is currently a beta feature and is being rolled out with pilot customers. If you would like to take part, please get in touch with us.

    This page covers what an administrator sets up before anyone can record time, in the order it needs doing. The per-project part of the setup is not done here. It is done by whoever runs the project, on the project itself; see Setting Up Time Recording on a Project.

    Switching the feature on

    Time recording is enabled per company by decídalo and is not a self-service setting. If you would like it switched on, get in touch with us.

    Because the feature is still in beta, users additionally need the Beta Features permission. Without it the time recording and finance pages stay hidden even after the feature is enabled for your company. In the menu the pages are marked with a beta chip.

    System settings

    Four settings for time recording are maintained under Administration → System settings → Feature settings. They only appear once time recording is enabled for your company.

    Setting Description What to choose
    Manual working-time recording “When enabled, users can record their daily working time (start, end and pause) by hand in My timesheet; when disabled, the day's working time is derived from the recorded entries.” Leave it off unless attendance genuinely has to be entered by hand. With it off there is one less thing for users to fill in, and the working time still adds up from their entries.
    Time recording approval “When enabled, recorded time must be confirmed before it can be issued; when disabled, recorded time can be issued without an approval step.” Turn it on if someone should check recorded hours before they reach a customer. With it off, recorded time flows into billing unchecked.
    Restrict time recording to valid dates “When enabled, time cannot be recorded on a day that lies outside the valid dates of the selected project, work package or order, and the entry is rejected; when disabled, such an entry is only marked with a warning.” Turn it on where recording outside a project's window is genuinely an error. Left off, people can still record it and only see a warning, which suits projects whose dates are not kept exact.
    Automatic project setup “When enabled, whoever creates a project can decide whether it gets the activity types of the default project configuration right away.” Turn it on once the activity types a new project should get are chosen, so new projects can be recorded on from the start. The same switch is on the page that holds those choices, see Defaults for New Projects and Orders.

    All four take effect for everyone. Note the disclaimer on that page: some settings only take effect after users log out and back in.

    Note: Confirming is done on the project's Delivery tab (see Confirming recorded time).

    Note: Time recording approval only makes the approval step available; each project then decides whether to use it, under Approval required for recorded time on its Accounting tab. With the setting on, everyone hands in their recorded time once it is final; a project that does not require approval (the default) confirms it at that moment, one that does waits for an approver. See Handing in your time and When confirmation is needed.

    Feature settings list with the four time recording options: manual working time, approval, valid dates and automatic project setup

    Activity types

    Administration → Time recording → Activity types.

    Activity types are the company-wide catalogue of what kind of work an entry was: development, consulting, travel, project management, and so on. Every project then picks which of them may be recorded against it.

    The grid shows Code, Name, Billable by default, Active, Target system code and Activity type category.

    • Code is a short identifier and must be unique. If it is already taken you get “Another activity type already uses this code.”
    • Name is maintained per language, so each user sees the catalogue in their own language.
    • Billable by default decides whether time recorded against this activity type can end up on a servicesheet. Individual projects, work packages and order positions can override it.
    • Active controls whether it can still be chosen. An inactive activity type cannot be recorded against, even on projects where it is still listed. There it is marked Globally inactive.
    • Target system code is optional free text naming the external system that time recorded on this activity type is exported to, not a second code for the activity type itself, which is what Code is. Give every activity type that feeds the same system the same value, and an export can then ask for exactly that system's entries. It changes nothing inside decídalo; leave it empty where nothing is exported.
    • Activity type category is optional free text naming a bucket the receiving system totals by: a cost centre, a service line. Where Target system code says where the time goes, this says how it is grouped once it arrives, so several activity types share one value on purpose. It changes nothing inside decídalo; leave it empty where nothing is exported.

    Use Create activity type to add one, and the row actions to edit or delete.

    Note: Once time has been recorded against an activity type it can no longer be deleted: “This activity type can't be deleted because time has already been recorded against it. Deactivate it instead.” Clearing Active is the right way to retire it, and it leaves existing entries untouched.

    Activity types grid scrolled to the target system code and activity type category, filled on the billable types and empty on the internal ones

    Create activity type dialog with the translation language picker, code, name, billable by default, target system code and activity type category

    General activities

    Administration → Time recording → General activities.

    General activities are for work that belongs to no project: internal meetings, training, administration, and also vacation and sick leave. They are maintained exactly like activity types, with Code, Name, Active and the optional Target system code, and they are created with Create general activity.

    There is no billable column here: general activities are never billable and can never appear on a servicesheet.

    The same rule applies as above: once time has been recorded against a general activity it cannot be deleted, only deactivated.

    Note: A general activity for vacation or sick leave records how time was spent, and that time counts towards the calculated working time like any other entry. It is not an absence and has no effect on availability, capacity or the resource plan. See Working Time Patterns, Absences & Availability.

    General activities grid listing non-project activities such as vacation and training, with a target system code on some of them

    Recording types

    Recording types live under Administration → Time recording → Recording types. A recording type is a value an entry can carry beside its time (travel time, a travel distance), and each one is its own column on every timesheet that offers it.

    The grid lists each type by Name and Code, what it Records, its Unit and whether it is Active.

    Creating one

    Field Description
    Code Required, unique. Also decides the internal column name, so it cannot be changed later.
    Records Working time, Travel time or Travel distance. Decides how the value is entered and stored, and is fixed once created.
    Unit Travel distance only: "km", "miles". Free text: the unit belongs to your type, so no setting elsewhere has to agree with it. It is fixed once the type is created, because the recorded numbers carry no unit of their own, and relabelling km as miles would change what every existing value and every rate agreed per km means, rather than convert it.
    Name The label shown as the column heading, per language. Languages you leave blank are machine-translated from the one you filled in.

    A Working time or Travel time type is entered as hh:mm, exactly like the timesheet's own time columns: type 1:30, or a plain 1.5 for an hour and a half. A Travel distance is entered as a number in your locale's format.

    Time itself is in the list and cannot be deleted or deactivated: it is the recorded time, and a timesheet without it has nothing to record. Nothing marks it out in the grid; each action refuses with its own message: “The default recording type can't be deleted. It is the recorded time itself.” and “The default recording type can't be deactivated. It is the recorded time itself.”

    Activating and deactivating

    A type's Active switch is on its detail drawer and is saved with the rest of the form. Deactivating hides its column everywhere in the application (the timesheet, the recording drawer and the servicesheet composer), and the column is no longer offered in the show/hide menu at all.

    Deactivating never deletes anything. Values already recorded are kept and still count for billing; the drawer says so before you save. Reactivating brings the column, and those values, straight back.

    Deactivating decides what people are offered, not what may exist. If your organization transfers recorded time from another system, that interface keeps reading and writing the type's values while it is inactive, so nothing it has already sent is lost and a correction still arrives. Stop a subject recording the type instead if values should no longer be entered for it, see Where they are switched on.

    Deleting

    Deleting a recording type removes its column and every value in it, so it is refused once anything has been recorded against it; deactivate it instead.

    It is refused for a second reason too, which applies even when nothing has been recorded: if any order position prices the type, or prices another type as a fraction of it, deleting it would take an agreed price with it. Remove those prices first, or deactivate the type. The grid disables the action and says which reason applies.

    Recording types grid with time, travel distance and travel time types, their unit and active status

    Create recording type dialog for a travel distance with code, name, unit and active toggle

    Edit recording type drawer with the active switch off, a note that recorded values are kept, and names per language

    Where they are switched on

    Creating a type does not make it recordable. It is enabled per subject, and each surface has its own list:

    • a general activity: on its drawer under Administration
    • a project's activity types: on the project's Recordable activities tab
    • an order position: per activity type, on the project's Recordable activities tab or in the position's drawer

    See Setting up time recording on a project. Which recording types a new project's activity types record is part of its defaults (see Defaults for new projects and orders).

    Billing them

    What a recorded value is worth is set on the order position, which prices each recording type it records (see Pricing the other recording types). How the values are shaped before they reach a servicesheet is set per type in the servicesheet policies.

    Defaults for new projects and orders

    Two more pages under Administration → Time recording decide what a new project starts with: Who can record time by default?, which also sets who may record directly on a new order, and Default project configuration, which sets the activity types a project starts with, and what each of them records. Both are described in Defaults for New Projects and Orders.

    Timesheet export templates

    The timesheet export writes recorded time into an Excel template of your company. The templates are kept per language on Administration → Time recording → Timesheet export templates, which needs the Template management permission rather than one of the time recording permissions below. How to write a template, and every placeholder it can use, is described in Timesheet Export Templates.

    Rates

    Rates live under Administration → Billing → Rates. This is the tenant-wide catalogue of priced labels (a role, a service) that orders and framework agreements draw on.

    Like a rate card, a rate here is reference data for prices: picking or prefilling it copies its figures, so changing a rate later never moves a price already agreed on an order. Picking it for an order position under Rate from catalog also links the position to the rate. The link stays: connected systems receive the rate's code with the position's recorded time, and the rate is locked once time has been recorded there (see the note below). Where a rate card is a named bundle you prefill as a set, this catalogue is the flat list the bundles and the orders are built from.

    A rate has one price per currency, so the same role can cost 150.00 EUR per hour and 160.00 USD per hour. Each price has an amount and a unit, Hour or Person day: the catalogue prices time. A travelled distance is priced on the order position itself, in its own unit such as kilometres. A rate needs at least one price, and a currency can appear only once. Enter the prices when you create the rate. Afterwards, open the rate: its Prices section lists one row per currency, and a changed amount, currency or unit is saved as soon as it is valid. Add starts a row in a currency the rate has no price in yet, which is saved once you enter its amount. The delete icon removes a price after you confirm it; the last price cannot be removed.

    A rate's drawer with its code, its rate category and two prices, one in euros and one in US dollars, each per person day

    A position is priced in its order's currency, so picking the rate on an order in US dollars prefills its USD price. A rate without a price in that currency can still be picked; see Adding positions.

    Each rate also carries an optional Rate category: free text naming a bucket an external finance system totals by, so several rates share one value on purpose. It is not the rate's identifier, which is what Code is, and it changes nothing inside decídalo; leave it empty where nothing is exported.

    Note: Once time has been recorded on an order position priced from a rate (one that picked it under Rate from catalog), only the rate's Active switch can still be changed. Its drawer shows Label, Code and Rate category as plain text with the reason on hover, and lists the Prices with nothing to change and the same reason beneath them: “This value can't be changed because time has already been recorded on an order position priced from this rate. Deactivate this rate and create a new one instead.” That covers every price: none can be added, changed or removed, in any currency, not even one that no order uses. Code and rate category are locked as well because connected systems receive both with every recorded entry, so changing them would relabel work they already hold. Deactivating the rate and creating a new one is how it changes from then on. A rate that order positions or rate cards use cannot be deleted. See Prices once time has been recorded.

    Rates catalogue with label, code, a rate category on some of the rates, active status and how many order positions and rate cards use each rate

    Orders and order positions

    Orders are not maintained centrally. They belong to the commercial side of a project and are created and edited by whoever manages its billing, under Orders in the Finance area of the menu or on the project's Accounting tab. There is nothing for an administrator to switch on before they can be used. Orders that another system transfers through the import interface are maintained in that system instead: decídalo keeps them read-only, apart from their positions, projects and servicesheet rules. See Imported orders.

    Two things about them matter for time recording, which is why they appear on this page at all:

    • An order position is one of the things people can record time against, either directly or through a work package it is connected to. Which activity types a position allows is set per project (see Setting Up Time Recording on a Project).
    • The position carries the rate, so it decides what the recorded time is worth. See Where the rate comes from.

    An order can serve several projects, and it holds its own rates on its Rates tab. How orders, positions and framework agreements fit together is described in the Billing concept, and managing them step by step in Orders & Positions.

    Order data fields

    Orders are driven by the data field configuration, so which fields appear on an order and in the orders grid is up to you. Configure them under Administration → Data fields for the Order entity (see Data Fields).

    Rate cards

    Rate cards live under Administration → Billing → Rate cards. A rate card is a named price list that acts as reference data: its entries are copied into a framework agreement when you prefill the agreement from it while creating it, and the copy is independent afterwards. Editing a rate card therefore does not change agreements that were already created from it. An order carries its own rates on its Rates tab, which can be filled by hand or prefilled from the framework agreement.

    The grid lists each card by Name with the number of Rates it holds. Open a card to maintain its Rates section: Add puts a rate from the catalogue on the card, and each entry shows:

    Field Description
    Label What is being priced, typically a role such as "Senior Consultant".
    Code The rate's code, where it has one.
    Prices Every price of the rate, one per currency, each per Hour or Person day. A person day is billed as eight hours.

    Deleting a card asks “Delete rate card ‘{name}’ and all its entries?” The agreements prefilled from it keep their copies.

    Where the cards are used is described in Framework Agreements; for how a rate feeds a servicesheet, see the Billing concept.

    Rate cards list with an opened card showing its rates with their codes and prices in a side drawer, one rate priced in two currencies

    Servicesheet policies

    Administration → Billing → Servicesheet policies.

    A servicesheet policy is a named set of servicesheet rules. The rules do not change what people record. They decide how the recorded work is turned into what goes onto a servicesheet, so that what reaches the customer follows your company's billing conventions rather than the raw stopwatch. A policy holds the rules for the time itself, the duration rules, and a rule set for each further recording type your company records, such as travel time or a travel distance.

    Duration rules

    The rules for the time itself have four settings:

    Setting What it does
    Minimum minutes per subject and day If one subject's time on a day adds up to less than this, it is not billed at all.
    Round up to The combined time is rounded up to the next multiple of this step, once per subject and day, not per entry.
    Maximum hours per day The most that may be billed for one person on one day.
    Above the maximum What happens to time beyond the maximum: Cap at maximum (“Excess time is cut off.”) or Continue the next day (“Excess time is moved to the person's next working day.”).

    “Subject” is the same combination the timesheet shows: project, work package, order position and activity type. All of one person's entries on one subject on one day count as a single piece of work: the minimum judges their combined time, rounding lifts that combined time once, and if the rules bill them they prefill as a single servicesheet line. Someone who records the same task five times in a day is therefore treated exactly like someone who recorded it once. Different subjects stay separate lines, unless the daily maximum runs out on that day. Then everything recorded on that day prefills together as one line, because what each subject bills depends on what the others took.

    Rules per recording type

    Every further recording type is billed on servicesheet lines of its own (see Recording types on a servicesheet), and its rules are its own too. Each type is judged separately: a minimum for travel time never removes working time, and the daily maximum limits the time itself only.

    Each type's rules start with Bill this recording type. Switch it off to keep recording the type without ever charging for it: wherever the policy applies, no servicesheet line is generated for that type, and its recorded values stay visible all the same. The time itself has no such switch, because whether time may be charged is the activity type's setting.

    The settings below the switch depend on what the type records:

    The type records Settings
    Working time or Travel time Minimum minutes per subject and day and Round up to, as for the time itself. There is no daily maximum.
    Travel distance Minimum per subject and day, in the type's unit, and then Above the minimum: Charge by quantity, optionally rounded with Round up to in the type's unit, or Charge a flat amount.

    Like the duration rules, these judge one person's values on one subject on one day together. The minimum is measured on what was recorded, before any rounding: 45 km stay below a minimum of 50 km even with a rounding step of 10 km. Rounding then lifts the combined value once.

    Charge a flat amount bills a fixed amount once for every person, subject and day that reaches the minimum, instead of the quantity times the rate: nothing below 50 km, and one fixed amount from there on, for example. The amount itself is money, so it is entered on the order, in the order's currency. A policy, and a project's own rules, only decide that a flat amount is charged: “The amount is set on the order, where the currency is known.” Until the order states one, the flat amount is zero.

    Creating and changing a policy

    Create opens a dialog with the Name, Use as default and the duration rules. Use Add recording type to give a further type rules of its own, and Remove these rules to take them off again. Opening an existing policy shows every active recording type under Rules per recording type, including those without rules.

    The grid shows one column per rule and recording type, with the type in brackets, such as Round up to (Travel time). Bill this recording type (Travel time) reads Yes or No. Every column can be sorted and filtered.

    Deactivating a recording type removes it from the dialog, the drawer and the grid, but not from billing: the values recorded while it was active are still owed, and its rules still shape them.

    Servicesheet policies grid, one policy marked default, with the column menu open listing one column per rule and recording type, the type in brackets

    Create servicesheet policy dialog with the duration rules, rules of their own for travel time, and the Add recording type picker at the end

    An opened policy under Rules per recording type: the time itself, a travel distance billed at a flat amount from 50 km, and travel time from 30 minutes

    Where a policy applies

    Mark one policy Use as default: “This is the default policy. New orders and projects start with its rules.” Individual orders and projects can then follow a different policy or define their own rules, on the order's detail page and on the project's Accounting tab under Servicesheet rules. There each recording type has a section of its own, the time first, and Expand all opens them together. Changing a value there makes the rules the order's or project's own, shown as Custom *, unless they then match a policy again. Entering an order's flat amount does not count as a change, because a policy only decides that a flat amount is charged. Choosing a policy copies its rules: editing the policy later leaves the orders and projects that chose it unchanged, and they then read Custom *.

    Where rules have changed the outcome, the project's Delivery tab shows it per entry, so the effect is visible before anything is billed: After rules, Billable after rules and Excluded by rules for the time, and a column such as Travel time on the servicesheet for each recording type. An entry is shaped by the rules of the order it is priced from; the project's own rules apply to time recorded straight to the project or to a work package.

    Note: The rules prefill a servicesheet, they do not fix it. Whoever composes the servicesheet still sees the proposed quantities and can change them: adjust what a line bills, combine or split lines, or include something the rules excluded. The policy decides the starting point, the person doing the billing has the last word.

    Permissions

    These are the permissions that govern time recording and billing. Most of them sit in the Time recording & billing group on the Resource based and Project based tabs of the Permissions page, with a value per permission profile. The three over the timesheets themselves are the exception: they are scoped over people rather than over projects, so they are listed under Profiles.

    Permission Unlocks
    Timesheet view Opening timesheets. None also hides the user's own timesheet.
    Timesheet editing Creating, changing and deleting entries.
    Timesheet cancellation Cancelling entries that have been submitted to the accounting system.
    Manage activity types and general activities All three catalogues on this page.
    Configure project time recording A project's Recordable activities tab.
    Approve project time recording Confirming recorded time on a project.
    Cancel project time recording Cancelling submitted time on a project. Either this or Timesheet cancellation is enough.
    Manage project billing and orders Orders and the project's Accounting and Delivery tabs.
    Manage accounting Rates, rate cards and framework agreements, plus orders on all projects.
    Manage billing Servicesheets, servicesheet policies and billable work, plus each project's Delivery tab in reduced form (its servicesheets only).

    Two things affect who ends up with these rights beyond the permission profile itself:

    • Project contact types can grant the project-scoped rights (Configure time recording, Approve time recording, Cancel time recording and Manage billing and orders) on the individual projects a person is a contact for.
    • Substitutes act with the reach of the person they stand in for; see Delegations.

    Resource based permissions scrolled to the time recording and billing group with values per permission profile

    In This Article
    Version history Back to top Copyright © data assessment solutions · decidalo.com