How to run Overtime in DocketMath for Brazil

Step-by-step

Run this scenario in DocketMath using the Overtime calculator.

Running overtime in DocketMath for Brazil (BR) is mainly about: (1) using the Overtime calculator, and (2) entering Brazil-relevant inputs (dates, schedule baseline, and overtime quantities) so jurisdiction-aware rules can compute the payable results.

1) Open the Overtime calculator

1. Go to the primary CTA: /tools/overtime
2. Confirm you’re viewing the Overtime calculator.
3. Set Jurisdiction to Brazil (BR).

2) Enter the core schedule inputs (these drive the result)

In the Overtime calculator, you’ll typically provide inputs that represent:

• what your normal schedule is, and
• how much time you want to treat as overtime (the incremental portion).

Use these as your baseline:

• Work date(s): Use the actual calendar dates overtime occurred.
• Normal hours / schedule reference: Provide the schedule baseline the tool should compare against (for example, the “normal” day/shift the tool expects).
• Overtime hours: Enter the overtime quantity for each date (or per entry, if the interface supports multiple rows).

If overtime happens on multiple days: add separate entries with their own date. This matters because the tool may classify overtime differently depending on patterns like weekends/holidays or other date-based category rules.

3) Add overtime characteristics that change the output

In Brazil, overtime often varies based on the type/category of overtime and the details of when it occurs. In DocketMath, that usually shows up as selectors, multipliers, or additional fields.

Enter the overtime characteristics available in the tool, for example:

• Overtime type (e.g., weekday vs. weekend-like categories, or other category selectors provided in the interface)
• Start/end times (if the tool requests time window details) or overtime duration
• Shift context (if there’s an input about how the overtime relates to normal schedule boundaries)

As you update these fields, watch the outputs change:

• More overtime hours should generally increase the overtime base.
• Changing the overtime category can change the payable amount even with the same hours.
• Splitting entries by date can change classification and totals.

4) Choose the pay rate inputs DocketMath needs

Overtime calculations rely on a pay rate base. In DocketMath’s Overtime tool, you’ll typically provide either:

• an Hourly rate (direct entry), or
• a Monthly salary plus conversion rules (if the tool supports that input mode)

Enter the rate format that matches your payroll conventions.

If you use monthly salary, the tool will convert it into an hourly figure using the tool’s configured assumptions for Brazil (BR). If you switch between hourly vs. monthly inputs:

• confirm the tool recalculates any derived hourly rate, and
• only then trust the overtime totals.

5) Review category totals and the grand total

After you finish the inputs, DocketMath will produce outputs such as:

• Overtime hours by category
• Overtime pay by category
• Grand total overtime amount

Use the breakdown for sanity-checking. For example, if you expected “8 hours weekday overtime” but the tool distributes hours across multiple categories, revisit in this order:

• the dates you selected,
• the overtime hours entered,
• the overtime type/category selector,
• any time window or shift boundary inputs.

6) Export or capture the scenario for auditability

If the tool offers export/download or copy options, save the results for the specific scenario you modeled.

A practical approach:

• Keep separate scenarios for single-day vs. multi-day runs
• Keep separate scenarios for weekday vs. weekend overtime
• Keep separate scenarios for different pay rates (e.g., after a rate change)

This reduces confusion later when you reconcile or compare scenarios.

7) Use jurisdiction-aware rules intentionally

Because you set Jurisdiction = Brazil (BR), the Overtime calculator applies Brazil-specific logic. Treat the jurisdiction setting as a rules switch, not just a label.

After switching to Brazil (BR), re-check:

• whether the expected overtime categories appear,
• whether totals are being calculated by category,
• whether any salary-to-hourly assumptions change.

A reliable workflow:

1. Run a single known day with known overtime hours.
2. Verify the category classification and total.
3. Then expand to the full date range, keeping entries split by date when categories differ.

Common pitfalls

Brazil overtime modeling is detail-sensitive. These are the most common issues that lead to incorrect outputs when using overtime calculators (including DocketMath):

• If overtime spans multiple dates, consolidating everything into one line can misclassify categories.
• Entering an hourly rate that doesn’t match your payroll method, or using monthly salary conversions inconsistently, can change the final overtime amount.
• Even if overtime hours are correct, changing the category (weekday vs. weekend-like classification or other tool-provided types) can materially affect pay.
• Ensure overtime hours represent the incremental overtime portion. The tool typically expects overtime-only quantities beyond normal schedule.
• If the tool asks for time windows or shift relations, incorrect start/end entries can move overtime into a different classification.
• A jurisdiction switch can alter derived assumptions and categories. Always verify the output summary right after setting Brazil (BR).
• The grand total can hide category mistakes. Review category hours and confirm they align with your expectations.

Quick self-check table

Try it

Use this quick “one-day validation” workflow to build confidence before running a full Brazil overtime scenario.

1. Open /tools/overtime
2. Set Jurisdiction = Brazil (BR).
3. Choose one known date where overtime occurred.
4. Enter:

   • Normal schedule baseline (or the schedule reference the tool requests)
   • Overtime hours (e.g., 2.5 hours)
   • Pay rate (hourly or monthly, matching your payroll approach)
   • Overtime type matching the classification shown/required by the tool
5. Review outputs:

   • the derived hourly rate (if you used monthly salary),
   • overtime hours by category,
   • category pay and the grand total.
6. Make one controlled change:

   • increase overtime hours from 2.5 → 3.0
7. Confirm:

   • the grand total increases according to the tool’s rate logic, and
   • the overtime doesn’t unexpectedly move into a different category (unless your change crosses a boundary or you changed the overtime type selection).

Once your one-day case behaves as expected, expand to your full date range—keeping entries split by date when categories differ.

If you’re ready to run your real scenario, start here:

• /tools/overtime

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