The matching process

Fluida records user timestamps and reports any anomalies, comparing inputs and outputs with the times in which the user must actually be present.

This process that Fluida carries out automatically is called matching.

The attendance rules allow you to better manage timestamps in some particular cases, preventing an anomaly from being generated.

Activate the feature

First, make sure the Timestamp feature is turned on ("Company" > "Settings" > "Timestamp").

If you are using Fluida as a free trial, or if you have signed up for a plan that includes the Presence Management feature, make sure that this feature has also been activated ("Company" > "Settings" > "Presence Management").

When both features are active, you can access the Attendance Rules.

To activate this advanced configuration, from the "Home" page, click "Company" > "Settings" > "Presence management" > "Rounding"> "Enable feature."

On this page, you can activate one or more settings (Rebates, Deferrals, Overtime) among those that make up the functionality.

Note: any changes made to this menu are applied starting from the following midnight.


The allowances section allows you to set rules that allow users not to justify any minutes not worked during the day.

If allowances are active, you must set two values: the single timestamp allowance and the maximum daily allowance.

  • The value you set as a single timestamp allowance determines how many minutes late a user can timestamp clocking in with respect to the entry time, or how many minutes before the exit, without an anomaly being detected.

  • The value you set as the maximum daily allowance is equal to the threshold in minutes of the total of the individual allowances. In other words, Fluida sums up all the unexcused absence time detected by a user's timestamps during the day: the total must not exceed the value set as the maximum daily allowance; otherwise, an anomaly is generated.


Deferrals allow you to set a level of flexibility that is applied to a user's entry and exit times. Based on the parameters set, the user can enter before or after the time assigned to him or her. The exit time will be brought forward or postponed accordingly.

Note: deferrals are not applied to set breaks.

If the deferral feature is active, you can set three values: the early start limit, the late start limit and the rounding up.

  • The value you set as the early start limit indicates the maximum number of minutes in advance a user can timestamp clocking in and leave early.

  • The value you set as the late start limit indicates the maximum number of late minutes a user can timestamp clocking in and make up for by leaving later than the set leaving time.

  • The value you set as rounding up indicates a time frame that affects the user's expected exit time, rounding it up.
    For example: if the rounding up is set to 15 minutes, the contract user must work from 9:00 to 18:00. With a timestamp between 8:31 and 8:44, he or she will have to leave at 17:45; if the contract user timestamps clocking in between 9:16 and 9:29, he or she will have to leave at 18:30.


The Overtime section allows you to set a value below which all the extra minutes detected by the timestamp will not be considered as non-matching attendance.

Note: the user must justify any overtime considered as an nonmatching attendance by entering an Overtime justification.

If overtime has been activated, be sure to set the minimum overtime value:

  • The value in minutes that you set as the minimum overtime duration indicates the required amount of extra continuous work for it to be considered non-matching attendance.

Please note: each of the settings has priority one over the other, following the order "Rebates Deferrals Overtime": for example, deferrals are triggered after the allowance minutes have elapsed, if they have been set.

Did this answer your question?