...
| Field | Description | Remarks |
|---|---|---|
| Name | An internal name to identify the rule when configuring the rounding rule on project level. | |
| Minimum Slice | This is the minimum "time slice" used for rounding, i.e. we are always rounding up to e.g. 15 min or 30 min. | You can't configure this. We offer 15 min and a multiple of 15 min. This way, time format can easily be converted into a decimal format for billing purposes. |
| Round Up | This is the limit between rounding down and rounding up. Starting with the value entered, we are rounding up. | |
| Enabled | You can enable/disable rounding rules here. | If a rounding rule gets obsolete, this way you can hide it from the project configuration (as you won't be able to delete it if it had been used already). |
...
- If you log 3 minutes of time, we would round down to 0 minutes, i.e. in the respective report, nothing would appear to be charged.
- If you log 6 minutes, we would round up to 30 minutes, i.e. you would charge 30 minutes.
- If you log 8 minutes, we would round up to 30 minutes, i.e. you would charge 30 minutes.
- If you log 34 minutes, we would round down to 30 minutes.
- If you log 38 minutes, we would round up to one hour.
| Tip |
|---|
It is obvious that applying rounding rules does not make much sense (or is not fair) within e.g. a development project, because the rounding rule - of course depending on configuration - adds a time overhead to your real time spent. This But this is fair for certain situations; a three-minute phone call might have a monetary value far beyond three minutes; if you get disturbed a couple of time a day for a couple of minutes, this justifies charging more than the effective time. |
...