How to calculate Overtime in Brazil
9 min read
Published April 15, 2026 • By DocketMath Team
Quick takeaways
Run this scenario in DocketMath using the Overtime calculator.
- In Brazil, overtime pay is typically driven by collective bargaining agreements (convenções coletivas), alongside baseline working-time concepts in the CLT (Consolidação das Leis do Trabalho).
- In many standard scenarios, you calculate overtime as: (hours worked above the applicable normal/contract workday) × (hourly rate) × (overtime premium).
- The overtime premium is often 50% (i.e., a 1.5× multiplier), but some situations—such as Sundays/public holidays or other contract-specific arrangements—may use a different premium (sometimes effectively 100%, i.e., 2.0×).
- DocketMath (the overtime calculator for Brazil (BR)) helps you structure the calculation: define your work schedule, identify overtime hours, choose the premium(s), and compute totals.
- The two most common sources of mistakes are:
- How many hours you classify as overtime (baseline vs actual hours), and
- Which premium applies (weekday vs Sunday/holiday, and any special rule mapping).
Note: This guide explains how overtime calculations are commonly structured in Brazil. It’s not legal advice. Your collective agreement can change what counts as overtime, the premium rate(s), and whether overtime is offset through an hours bank (banco de horas).
Inputs you need
To calculate overtime in Brazil using DocketMath, collect inputs that let the calculator apply jurisdiction-aware logic for BR: which hours count as overtime and which premium multiplier applies to each category.
Use this intake checklist as your baseline for Overtime work in Brazil.
- jurisdiction selection
- key dates and triggering events
- amounts or rates
- any caps or overrides
If any of these inputs are uncertain, document the assumption before you run the tool.
1) Pay period and hours
You’ll typically need:
- Pay period (example: “April 2026” or exact dates like 2026-04-01 to 2026-04-30)
- Your standard work schedule baseline, such as:
- Standard weekly hours (e.g., a 44-hour week), or
- Standard daily hours that sum to the weekly requirement
- Actual hours worked, ideally:
- Per day, or at least per week
- Overtime start/end logic (how you treat:
- partial days,
- breaks, and
- rounding—if your policy or system rounds)
Output impact: If your baseline is higher than what you enter, fewer hours become overtime; if the baseline is lower, more hours become overtime.
2) Overtime rule set (premium selection)
You’ll usually choose or provide one or more premium options. Common baseline expectation:
- 50% premium for overtime in many standard arrangements (1.5× multiplier)
But you may need premium changes for:
- Sundays
- Public holidays
- Night work overlap (which may interact with rules like adicional noturno depending on how you model it)
- Any special collective agreement overtime provisions
Output impact: If you apply a single premium to all hours when your rule set requires different treatment for Sunday/holiday, your overtime total can be materially off.
3) Hours bank (Banco de Horas) / compensation approach
Brazil frequently uses an hours bank arrangement, meaning overtime can be compensated with time off rather than immediately paid as overtime.
If you have an hours bank, gather:
- Is overtime paid or compensated?
- If compensated: the offset window (the period during which the banked hours can be offset before payout/settlement)
- What happens at settlement (if the bank is not fully offset by the deadline, what is paid out)
Output impact: With an hours bank, your “worked overtime hours” may not equal “overtime pay.” DocketMath can reflect this—but only if you provide the bank/offset behavior accurately.
Practical reminder: the most common mismatch is calculating overtime hours correctly while forgetting that the hours bank converts some overtime into time-off, reducing what is actually paid.
4) Rate and scaling inputs
To compute money amounts, DocketMath generally needs an hourly basis:
- Hourly wage (or monthly wage plus a divisor/approach to derive an hourly rate)
- Whether overtime is calculated using the gross hourly rate (typical payroll practice)
Output impact: If you convert monthly salary to an hourly rate using the wrong assumptions/divisor, overtime pay will be scaled up or down even if the overtime hours are correct.
Inputs checklist (quick)
How the calculation works
DocketMath’s overtime calculator for Brazil (BR) typically follows a clear sequence:
- identify eligible overtime hours,
- apply the appropriate overtime premium(s), and
- compute overtime pay totals.
DocketMath applies the Brazil rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.
Step 1: Determine the “standard” hours for the pay period
First, define normal time for the pay period. Common ways to do this:
- A weekly standard (e.g., 44 hours/week), or
- An 8-hour day structure that totals the required weekly hours
Then compute what portion of actual hours exceeds that baseline.
Output impact:
- Higher baseline → fewer overtime hours → lower overtime pay
- Lower baseline → more overtime hours → higher overtime pay
Step 2: Classify overtime hours into categories (premium may vary)
Next, separate overtime hours by category because premium treatment can differ—especially for:
- Regular overtime (typical weekdays)
- Sunday/holiday overtime (overtime occurring on Sundays/public holidays)
- Night-related overlap (only if your payroll/rules treat those hours with special handling)
| Category | What you’re looking for | Why it matters |
|---|---|---|
| Regular overtime | Hours above baseline on standard weekdays | Usually uses the baseline overtime premium (often 50%) |
| Sunday/holiday overtime | Overtime on Sundays or public holidays | May use a different premium per your applicable rule set |
| Night-related overlap | Overtime hours that fall in “night” periods | May change how amounts are computed if your system/policy does so |
Output impact: Mixing categories can cause DocketMath to apply the wrong premium to some hours, leading to an incorrect total.
Step 3: Convert your rate to an hourly amount (if needed)
If you input a monthly wage, DocketMath may require an hourly conversion based on your configured approach.
Output impact: An incorrect hourly conversion scales overtime pay incorrectly across all overtime hours.
Step 4: Apply the overtime premium to overtime hours
At its core, the math is:
- Overtime pay = overtime hours × hourly rate × overtime premium multiplier
Examples:
- 50% premium → 1.5× multiplier
- 100% premium → 2.0× multiplier
Output impact:
- If you change only the premium multiplier, the overtime hours remain constant—so you can quickly see sensitivity of totals.
- If your premium differs by day type, use separate category handling so totals align with payroll expectations.
Step 5: Apply hours bank logic (if applicable)
If you have a hours bank, overtime pay can be reduced or deferred:
- Some overtime hours may be offset with time off
- Only remaining balance (if any) after settlement may become payable as overtime
Output impact: Even with correct overtime hours, the overtime pay portion can be much lower due to compensation and settlement timing.
Pitfall: Overestimating overtime pay by assuming every overtime hour becomes overtime cash value when an hours bank converts it to compensated time.
Common pitfalls
- missing a required input
- using a stale rate or rule
- ignoring calendar or holiday adjustments
- skipping documentation of assumptions
Capture the source for each input so another team member can verify the same result quickly.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
1) Counting overtime against the wrong baseline
If your “normal” schedule is entered incorrectly, the calculator may classify too many or too few hours as overtime.
Common causes:
- Using a generic 8 hours/day baseline when your schedule differs
- Not aligning to your actual weekly hours plan or schedule adjustments
2) Not separating Sunday/holiday overtime
Premium treatment often changes on Sundays and public holidays. If you combine everything into one bucket, the premium rate may be wrong.
Quick checklist:
3) Ignoring night-work overlap complexity
In Brazil, night work can trigger an additional allowance (adicional noturno). If your payroll also treats those hours as overtime in a certain way, you need consistent modeling.
Practical approach:
- Use consistent category modeling across your inputs.
- If your payroll system calculates night allowance separately, avoid double-counting by ensuring DocketMath premium rules reflect only overtime, while night allowance is handled elsewhere.
4) Mixing pay period boundaries
Overtime categorization depends on the time window. Mistakes in pay period boundaries can cause:
- Hours to be assigned to the wrong month
- Premium rates to be applied under the wrong period settlement
Tip: Use exact pay period dates and verify shifts that cross into the next period.
5) Hours bank settlement timing
Even when overtime hours and premiums are correct, overtime pay can differ due to when the hours bank is settled.
Typical symptoms:
- DocketMath estimate doesn’t match payroll because payroll applied settlement in a different period
Sources and references
Sources are provided for context on the Brazilian labor framework (not as DocketMath configuration instructions):
- CLT – Consolidação das Leis do Trabalho (Brazil)
- Concepts related to working hours and overtime are covered in CLT provisions that address working time rules and overtime concepts.
- Brazilian constitutional and statutory framework (general working time rules)
- Baseline limits on working time inform how overtime is defined, while overtime premium rates are often influenced or modified by agreements.
- **Collective bargaining agreements (
Next steps
After you run the Overtime calculation, capture the inputs and output in the matter record. You can start directly in DocketMath: Open the calculator.
If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.
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
