Worked example: Overtime in Brazil
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Overtime calculator.
Below is a worked example of overtime calculation in Brazil using DocketMath’s overtime calculator with jurisdiction-aware rules for BR (Brazil).
Note: This example demonstrates how to use DocketMath and interpret outputs. It’s not legal advice, and overtime eligibility can depend on the employment contract, collective agreement (CCT/ACT), job role, and factual details.
Scenario (weekly-based example)
Assume an employee works the following hours in a given workweek:
- Regular hours scheduled: 44 hours
- Overtime worked: 8 hours total in the week
- Overtime day type: mix of weekdays and Saturdays
- Overtime rate assumption: time-and-a-half (1.5x) for “typical” overtime; higher rates may apply for Sundays/holidays (if applicable)
- Absences / leave: none in the week
- DocketMath mode: hourly overtime (not monthly)
Inputs you would enter into DocketMath (/tools/overtime)
Use these inputs as the concrete values for this example:
- Jurisdiction: BR
- Base hourly wage: R$ 25.00
- Regular weekly hours: 44
- Overtime hours worked: 8
- Overtime classification: “Typical overtime” for the 8 hours (i.e., not Sunday/holiday)
- Overtime multiplier for typical overtime: 1.5
- Currency formatting: BRL (R$)
If your overtime includes Sundays/holidays, model those hours separately in DocketMath by splitting overtime hours by day type, so the BR-specific category handling can apply correctly.
Quick reference table (what the inputs mean)
| Input | Example value | What it controls in the calculation |
|---|---|---|
| Base hourly wage | R$ 25.00 | Determines the base for the overtime premium |
| Regular weekly hours | 44 | Defines the threshold after which worked time becomes overtime (in this example) |
| Overtime hours | 8 | The count of hours receiving overtime premium |
| Overtime multiplier | 1.5 | Sets the premium rate applied to the overtime hours |
| Overtime classification | Typical | Ensures the correct overtime rate rules are applied for BR |
Example run
Open the calculator: /tools/overtime.
Then run the overtime calculation using the inputs listed above.
Run the Overtime calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Compute overtime premium per hour
- Base hourly wage = R$ 25.00
- Typical overtime multiplier = 1.5
- Overtime pay per overtime hour = R$ 25.00 × 1.5 = R$ 37.50
Step 2: Multiply by overtime hours
- Overtime hours = 8
- Total overtime pay = R$ 37.50 × 8 = R$ 300.00
Step 3: Separate base vs. premium (useful for pay breakdowns)
Many payroll workflows need to separate “regular wages” from “overtime premium.” With a 1.5x multiplier:
- Regular portion embedded in overtime pay = R$ 25.00 × 8 = R$ 200.00
- Premium portion = Total overtime pay − embedded regular portion
- Premium portion = R$ 300.00 − R$ 200.00 = R$ 100.00
Output summary (what DocketMath would typically display)
| Output line | Value | How to read it |
|---|---|---|
| Overtime hours | 8.00 | Hours treated as overtime under the selected scenario |
| Overtime pay | R$ 300.00 | Total pay attributed to overtime hours |
| Embedded regular portion | R$ 200.00 | The “base wages” component within overtime pay |
| Overtime premium | R$ 100.00 | The extra amount due to the overtime multiplier |
Practical interpretation
In this scenario:
- The employee’s overtime pay is R$ 300.00 for the week.
- If your payroll system tracks premiums separately, you can use the premium portion (R$ 100.00) for reporting.
Minimal “sanity check” before you finalize
- Does total hours (regular + overtime) match the timesheet reality?
- Regular = 44, overtime = 8 → total = 52 hours for the week.
- Does the overtime classification match the days worked?
- Since we labeled this as “typical overtime,” the 1.5x multiplier should match your classification setup.
Pitfall: If your 8 overtime hours include Sundays or holidays, using a “typical overtime” multiplier can understate or overstate pay. In DocketMath, split overtime by day type when your inputs allow it, so BR-specific category rules apply correctly.
Sensitivity check
Now let’s see how small input changes affect the overtime result. This helps confirm you configured DocketMath correctly for BR overtime.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Sensitivity 1: Change hourly wage (R$ 25.00 → R$ 28.00)
Keeping overtime hours = 8 and multiplier = 1.5:
- Overtime pay per hour = R$ 28.00 × 1.5 = R$ 42.00
- Total overtime pay = R$ 42.00 × 8 = R$ 336.00
Impact vs. base scenario:
- Base overtime pay = R$ 300.00
- New overtime pay = R$ 336.00
- Difference = +R$ 36.00
Sensitivity 2: Change overtime hours (8 → 6)
Keeping hourly wage = R$ 25.00 and multiplier = 1.5:
- Total overtime pay = R$ 37.50 × 6 = R$ 225.00
Impact:
- Base = R$ 300.00
- New = R$ 225.00
- Difference = −R$ 75.00
- Interpretation: in this setup, each overtime hour costs R$ 37.50.
Sensitivity 3: Switch multiplier (1.5 → 2.0) for a different overtime category
Sometimes overtime categories use higher multipliers. Suppose DocketMath is configured so that your scenario should use 2.0x.
- Overtime pay per hour = R$ 25.00 × 2.0 = R$ 50.00
- Total overtime pay = R$ 50.00 × 8 = R$ 400.00
Impact:
- Base (1.5x) = R$ 300.00
- New (2.0x) = R$ 400.00
- Difference = +R$ 100.00
Sensitivity results table
| Change | Assumption kept | New overtime pay | Delta vs. R$ 300.00 |
|---|---|---|---|
| Hourly wage R$25 → R$28 | Hours 8, multiplier 1.5 | R$ 336.00 | +R$ 36.00 |
| Overtime hours 8 → 6 | Wage R$25, multiplier 1.5 | R$ 225.00 | −R$ 75.00 |
| Multiplier 1.5 → 2.0 | Wage R$25, hours 8 | R$ 400.00 | +R$ 100.00 |
How to use this check in practice
Try this workflow each time you calculate:
- Confirm your base hourly wage matches payroll values (not a rounded estimate).
- Confirm your overtime hours count matches your timesheet overtime after applying the schedule threshold you’re modeling.
- Ensure the overtime classification/day type matches your worked hours.
- Run a quick sensitivity shift on:
- hourly wage (wage rounding mistakes are common),
- overtime hours (timesheet boundaries can be off),
- multiplier/category (day-type misclassification is often the biggest conceptual error).
Warning: Overtime treatment in Brazil can be influenced by scheduling rules and classification categories. If your timesheet includes multiple day types (weekday vs. Saturday vs. Sunday/holiday), model them separately rather than averaging them into one “typical overtime” bucket.
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