Inputs you need for Overtime in Brazil
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Overtime calculator.
To calculate overtime in Brazil with DocketMath (jurisdiction: BR), you’ll want a complete set of inputs that capture both time worked and the rules that determine overtime eligibility and premium rates. The goal is to give the calculator enough context to classify hours correctly (regular vs overtime) and apply the right premium behavior.
Use this checklist to collect the minimum data needed for the overtime calculator:
Prefer breaking overtime out by date (or at least into distinct blocks) so weekly/daily limits and any special periods (weekend/holiday) can be handled by your configuration.
This baseline is used to determine which hours are treated as overtime versus regular time.
Many setups distinguish between ordinary overtime and special premiums (for example, weekend/holiday or other premium categories your payroll policy tracks).
If overtime overlaps with night hours, premium calculations can change because night-work treatment may be handled differently depending on how you configure the BR rules in DocketMath.
Output can change depending on whether the hours fall on Saturday/Sunday and whether your rule selection treats those days differently.
If you track dates that are treated as holidays in your payroll policy, marking holiday hours improves accuracy of premium classification.
If your organization uses toggles for different agreements or internal policies, these selections can alter how overtime premiums are applied.
You need the correct pay period start/end dates so the calculator assigns hours to the correct payroll context.
The calculator needs a consistent way to convert working time into pay. Provide either:
Pitfall: If you enter overtime as a single total number of hours without dates (or without weekend/holiday/night context), you may lose the information that drives premium categorization—so the calculated overtime amount may not match your expected breakdown.
A practical “minimum viable” input set for a first pass is usually:
Where to find each input
Gathering inputs is easier when you know where each one typically lives in your systems. Here’s a practical map from what you need to where it’s usually found:
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Time and schedule inputs
Worked hours (by day)
Look in your:Standard weekly schedule
Common places:
Overtime classification inputs
Night work overlap
Typically sourced from:Weekend and holiday indicators
You can often derive this from dates, but you still need:
Pay rate inputs
- Hourly rate or monthly salary + hours baseline
Period and formatting inputs
Pay period start/end dates
Currency
In general, if you already run payroll each period, your “best” inputs are the ones already used to create pay statements—DocketMath then helps you compute overtime consistently from the information you provide.
Run it
Once your inputs are collected, run the DocketMath overtime calculator.
Enter the inputs in DocketMath and run the Overtime calculation to generate a clean breakdown: Run the calculator.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
Step-by-step workflow (practical)
- Open the tool: /tools/overtime
- Set:
- Jurisdiction: Brazil (BR)
- Pay period: the dates you’re calculating for
- Enter time inputs:
- Provide worked hours (ideally by day, or in the breakdown your overtime configuration expects)
- Provide rate inputs:
- Enter hourly rate or monthly salary + standard hours so the hourly conversion is consistent
- Choose the overtime rule configuration:
- Select the premium/rule toggles that match how your organization treats overtime types (ordinary vs weekend/holiday, and night overlap if applicable)
- Submit and review outputs:
- The calculator will compute (based on your configuration):
- Total overtime hours (as determined relative to your schedule baseline)
- Overtime pay amount using the configured premium behavior
- Any subtotals available in the tool (e.g., ordinary vs special categories)
How the outputs change when you change inputs
| Input you change | Typical effect on overtime output |
|---|---|
| Increase overtime hours on a weekend/holiday | Overtime pay can increase due to a higher premium category |
| Provide night overlap for the same hours | Overtime pay may increase if night-related premiums apply in your configuration |
| Use a different standard weekly schedule baseline | Some hours may shift from “regular” to “overtime,” changing both hours and pay |
| Use monthly salary vs hourly rate incorrectly | The calculator’s conversion may produce a different implied hourly rate, changing the final overtime amount |
Quick validation checklist before you finalize numbers
Gentle note: DocketMath calculations are only as accurate as the inputs and rule selections you provide. This is not legal advice—treat it as a practical calculation aid and validate your configuration against your internal policy and payroll practice.
Related reading
- Why Overtime results differ in Philippines — Troubleshooting when results differ
- Worked example: Overtime in Philippines — Worked example with real statute citations
- How to run Overtime in DocketMath for Philippines — Step-by-step platform walkthrough
