Overtime rule lens: Brazil

7 min read

Published April 15, 2026 • By DocketMath Team

The rule in plain language

Run this scenario in DocketMath using the Overtime calculator.

In Brazil, overtime (“hora extra”) is governed primarily by the Consolidação das Leis do Trabalho (CLT) and is commonly implemented through a mix of statute rules plus the employee’s contract and/or a collective bargaining agreement (CBA).

A practical “rule lens” for overtime calculations is:

  • Overtime is paid at a premium over the regular hourly rate.
  • Working time is limited, and hours worked beyond statutory limits can create both (a) higher pay obligations and (b) compliance/audit risk if the employer’s scheduling and time-recording practices are not consistent with the applicable rules.
  • The premium can depend on the type of hours and schedule, including how night work interacts with overtime.
  • Overtime pay generally must be supported by time records (for example, time controls/carteões de ponto) or a legally acceptable alternative mechanism.

Key CLT touchpoints (what you’ll see in calculations)

Use these as your “calculation anchors” when building an overtime model:

  • Overtime concept and premium framework (CLT): Hours beyond the employee’s standard work schedule are compensated at a higher rate.
  • Daily/weekly limits affecting working time: Brazilian labor rules impose constraints on maximum working time and overtime accumulation. These limits may affect how hours are characterized and the risk profile of the payroll treatment.
  • Working-time recording: Overtime is not just a number to multiply—your inputs should be traceable to working-time controls (or another lawful basis).

Note (important for modeling, not legal advice): Brazil’s overtime outcome depends heavily on what counts as “hours worked” (e.g., effective time at the employer’s disposal) and whether the schedule is compliant. In other words, your result in any calculator is only as good as your inputs for baseline hours, overtime hours, and whether any night component (adicional noturno) applies.

Night work is a frequent “multiplier trap”

A common error is to compute overtime on top of an hourly base that doesn’t reflect the night-hours interaction.

In practice, night work can change the effective hourly compensation components, so you should treat overtime + night-work as a separate modeling step rather than assuming the overtime premium always uses the same denominator/base as regular day hours.

Why it matters for calculations

When you run overtime scenarios in DocketMath, the biggest calculation errors typically come from:

  1. incorrectly defining the base, and/or
  2. missing schedule interactions (especially regular-vs-overtime splits and night-work components).

Small differences in the rule text can change the output materially. Using the correct jurisdiction and effective date ensures the calculation aligns with the authority that applies to your matter.

1) The baseline determines everything

Overtime premium is applied as a percentage/multiplier to an hourly base. If the baseline is wrong, the output shifts across the entire calculation.

In your model, you typically need to define:

  • Regular weekly hours (44 hours/week is common in Brazilian practice, but the employee’s schedule may differ)
  • Standard daily schedule (if fixed daily hours apply)
  • Overtime hours for the period you’re calculating (and whether they overlap with special regimes like night work)

2) Premium can change with context

Even if you think “overtime is X%,” real payroll modeling often has variations such as:

  • statutory premium rules as a baseline, and/or
  • additional premium requirements negotiated via CBA (where applicable) or reflected in the employment contract, and
  • interaction effects when overtime includes night hours.

So in DocketMath, you should represent (as applicable):

  • regular hours
  • overtime hours
  • a night component that changes how the effective base/amount should be computed

3) Caps affect whether hours are “overtime” in practice

If statutory working-time limits are exceeded, overtime may still be payable, but compliance risk increases and disputes can arise—particularly where working-time controls and scheduling evidence are incomplete.

For your calculator outputs, this means you should be able to answer:

  • “How much overtime premium pay is due under the premium rule?”
  • “Does this scenario exceed common working-time caps that could affect characterization and audit risk?”

4) Recordkeeping drives auditability

DocketMath can compute based on your inputs, but it cannot fix missing/incorrect time records. If the inputs come from unreliable or incomplete working-time data, the overtime pay computed will be unreliable too.

Use DocketMath to maintain a calculation trail you can reconcile against:

  • timecards / working-time controls,
  • payroll worksheets,
  • any wage supplements or rules required by a CBA.

Use the calculator

Use DocketMath’s overtime calculator for Brazil (BR) to model how overtime hours affect total compensation.

Inline link: /tools/overtime

Run the Overtime calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step-by-step inputs (Brazil lens)

When you set up the overtime calculator, think in terms of these input categories:

  1. **Regular hourly rate (R$ / hour)

    • This is the base your overtime premium multiplies.
    • If you only have monthly salary, derive an hourly rate using the employee’s standard work hours.
  2. Overtime hours

    • Enter the hours that exceed the employee’s regular schedule for the period you’re modeling.
    • Don’t enter “total hours worked” unless the tool is explicitly designed for that input structure.
  3. **Overtime premium setting (statutory / negotiated)

    • Choose the premium configuration that matches the rule you’re modeling (statutory baseline or a CBA/contract rate, as relevant).
  4. **Night work interaction (if overtime overlaps night hours)

    • If overtime includes night hours, configure the night-work logic so you’re not applying overtime premium using the wrong underlying hourly basis.

Example scenario (what to model)

A practical pattern you can adapt:

  • Regular schedule: 44 hours/week
  • Regular hourly rate: R$ 20.00/hour
  • Overtime worked: 6 hours in a week
  • Premium: configure in DocketMath based on the premium rate you are modeling

A simplified view of the logic you should expect conceptually:

  • Overtime pay = overtime hours × hourly rate × overtime premium multiplier
  • Total weekly pay (simplified) = regular pay for baseline hours + overtime pay

How output changes when you adjust inputs

Use this mini-table to sanity-check your model:

Input changeWhat it does to your result
Increase overtime hours by +2Overtime pay increases roughly linearly by the premium-applied hourly amount
Increase regular hourly rate by +R$ 5Overtime pay increases proportionally (base rises)
Increase overtime premium multiplierOvertime pay increases at the premium multiplier’s rate
Add night-work component (if applicable)Effective compensation can shift; re-check the hourly basis used for overtime

Pitfall: Don’t enter “total hours” and assume the calculator will automatically treat the extra time as overtime. Use a clear “regular vs overtime” split, or use DocketMath’s input fields exactly as intended.

Quick checklist before you run DocketMath

Once inputs are set, DocketMath outputs computed overtime premium and total compensation for your defined period, letting you run “what-if” comparisons (for example, 2 hours vs 6 hours overtime; different hourly bases; different premium multipliers).

Sources and references

Start with the primary authority for Brazil and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading