Goal
Weekly paycheck split into regular and overtime pay at an adjustable threshold and multiplier.
Overtime Pay
Weekly paycheck split into regular and overtime pay at an adjustable threshold and multiplier.
Key facts
- What it does
- Weekly paycheck split into regular and overtime pay at an adjustable threshold and multiplier.
- Formula
regularHrs = min(hours, threshold); otHrs = max(0, hours - threshold); total = regularHrs x rate + otHrs x rate x multiplier.- You enter
- Hours worked · Hourly rate · Overtime threshold · Overtime multiplier
- Worked example
- Regular pay 800.00; overtime pay 150.00; total pay 950.00.
A clearer path to an answer
From your question to a useful result
This page keeps the calculation transparent: define the goal, enter the matching values, inspect the method, and decide what the result means in your situation.
Inputs
Hours worked · Hourly rate · Overtime threshold · Overtime multiplier
Method
regularHrs = min(hours, threshold); otHrs = max(0, hours - threshold); total = regularHrs x rate + otHrs x rate x multiplier.
Next step
Calculate, review the assumptions below, then compare a related tool when the decision needs more context.
Overtime Pay
Weekly paycheck split into regular and overtime pay at an adjustable threshold and multiplier.
Open the Overtime Pay pageMore business tools
Download PDFDownload Word (.doc)
Result
Enter your values above and choose Calculate to see the result here.
Calculation map
Follow the path from input to answer
01
Inputs (4)
- Hours worked Ready
- Hourly rate Ready
- Overtime threshold Ready
- Overtime multiplier Ready
02
Formula
regularHrs = min(hours, threshold); otHrs = max(0, hours - threshold); total = regularHrs x rate + otHrs x rate x multiplier.
Bounded, transparent calculation
03
Result
- Calculate to preview the result.
Recent runs
Your recent runs stay in this browser session only.
Formula, assumptions, and example
Formula: regularHrs = min(hours, threshold); otHrs = max(0, hours - threshold); total = regularHrs x rate + otHrs x rate x multiplier.
Hours up to the threshold earn the base rate; hours beyond it earn the rate times the multiplier. With 45 h at 20 and 40/1.5 defaults, regular pay is 800 and overtime is 150.
- US-style weekly overtime default (40 h at 1.5x); adjust both to match local rules.
- Single base rate with no taxes, deductions, shift differentials, or daily-overtime rules.
Worked example: Regular pay 800.00; overtime pay 150.00; total pay 950.00.
Displayed input contract
- Hours worked · minimum 0 · maximum 10000
- Hourly rate · minimum 0 · maximum 1000000
- Overtime threshold · minimum 0 · maximum 168
- Overtime multiplier · minimum 1 · maximum 100
The displayed limits are checked before the handler runs. Model-specific domain checks may also reject impossible or non-finite inputs.
Methodology: This calculator follows the WorldCalculate input, formula, precision, and boundary policy. Read the official methodology.
Calculator usage statistics
Usage of this calculator and related tools
This section counts anonymous successful Calculate submissions, not unique visitors. Counts and top tools appear only when trusted aggregate data is available; country analysis is shown only under the same condition and reporting threshold.
Total successful calculations
Top tools
Country analysis
Most-used tools
Where usage is reported
Answer-first guide
How to use the Overtime Pay for a real question
Weekly paycheck split into regular and overtime pay at an adjustable threshold and multiplier. Start with one clearly defined goal, enter values in the units shown, and keep the result attached to the assumptions below.
What this answers
This tool is useful when your question includes overtime, time and a half, paycheck. It returns the outputs declared in the calculator contract rather than a live quote, approval, diagnosis, or professional sign-off.
What you enter
Hours worked · Hourly rate · Overtime threshold · Overtime multiplier. Keep the same time period, unit system, and currency wherever the form requires comparable values.
How to check it
Run the worked example first, compare its output with the page's example, then change one input at a time. This makes an unexpected result easier to trace to a unit, boundary, or assumption.
Three checks before you rely on the answer
- Match the question. Confirm that the result means the quantity you need, not a similar-sounding percentage, balance, rate, or estimate.
- Match the inputs. Use the requested units and period, and read each hint before replacing the example values with your own.
- Read the boundary. Review the assumptions and limits. US-style weekly overtime default (40 h at 1.5x); adjust both to match local rules.
Need a wider view? Browse Business Calculators or compare the related tools below. The WorldCalculate methodology explains how formulas, examples, limits, and revisions are reviewed.
How to use the Overtime Pay
- Enter Hours worked (hours).
- Enter Hourly rate.
- Enter Overtime threshold — US weekly standard is 40. (hours).
- Enter Overtime multiplier — US standard is 1.5 (time-and-a-half).
- Choose Calculate and read the result panel.
- Use Download PDF or Download Word to save a result sheet.
Formula
regularHrs = min(hours, threshold); otHrs = max(0, hours - threshold); total = regularHrs x rate + otHrs x rate x multiplier.
Hours up to the threshold earn the base rate; hours beyond it earn the rate times the multiplier. With 45 h at 20 and 40/1.5 defaults, regular pay is 800 and overtime is 150.
Worked example
Regular pay 800.00; overtime pay 150.00; total pay 950.00.
Assumptions and limits
- US-style weekly overtime default (40 h at 1.5x); adjust both to match local rules.
- Single base rate with no taxes, deductions, shift differentials, or daily-overtime rules.
Context and background
How business measures fit together
Business tools separate revenue, cost, margin, markup, cash, time, and return so a planning decision can be checked one layer at a time.
Management accounting and operating analysis use ratios and thresholds to make business performance easier to compare. The right denominator and period are part of the answer, not a hidden detail.
Research and review
How this guide was researched
Researched by Hassan ALRowaie, Founder and editorial researcher at WorldCalculate.
This guide follows the live calculator's declared inputs, formula, worked example, assumptions, validation boundaries, and source-backed methodology. The review date describes editorial review of the calculator explanation; it is not a promise that external facts or rates remain current.
Overtime Pay separates a bounded number of worked hours into regular and overtime portions, then applies one base hourly rate and one overtime multiplier. Its fields are hours, rate, threshold, and multiplier. The handler requires hours to be finite from 0 through 10,000, rate from 0 through 1,000,000, threshold from 0 through 168 hours, and multiplier from 1 through 100. The default is a US-style weekly example of 40 hours at 1.5 times the base rate, but both the threshold and multiplier are adjustable. The page calculates regularHours as min(hours, threshold), overtimeHours as max(0, hours - threshold), regular pay as regularHours x rate, overtime pay as overtimeHours x rate x multiplier, and total pay as the sum. It returns total first, regular second, and overtime third, each formatted as currency. This is a transparent estimate, not a payroll record or legal determination; it excludes taxes, deductions, shift differentials, daily overtime, multiple rates, salary rules, and weighted regular-rate calculations.
What this calculator answers
The page answers a specific wage-arithmetic question: given one number of hours, one base hourly rate, one threshold, and one multiplier, how much pay belongs to the regular portion, how much belongs to the overtime portion, and what is their total? It does not inspect a timecard, identify a workweek, classify a worker, or determine which legal rule applies. The calculation begins only after you have selected the hours and rules you intend to model.
The output order is part of the contract. The first result is Total pay, the second is Regular pay, and the third is Overtime pay. All three are currency results, so they should be interpreted in the same currency as the rate. The rate field has no separate currency selector, which means the page cannot convert dollars to another currency or combine rates from different currencies. Keep the currency label outside the four numeric fields when sharing the estimate.
A total can be arithmetically correct while still being the wrong paycheck estimate if the threshold, multiplier, hours, or included rate was chosen incorrectly. The tool is most useful when the inputs are documented first and the result is then checked against the applicable agreement, payroll policy, or jurisdictional rule. Its simplicity is a feature for a single-rate scenario, but it is also the reason that complex payroll questions must stop at this model's boundary.
- The page splits one hours value into regular and overtime hours.
- It applies one rate and one multiplier, then adds the two pay portions.
- Results are ordered total, regular, overtime and formatted as currency.
- The estimate does not decide which wage rule applies.
The four fields and their units
The hours field is the total number of hours to model. It accepts a finite numeric value from 0 through 10,000, measured in hours. Because the catalog uses an any step, a decimal such as 42.5 is allowed; the handler does not require whole hours. The value should represent the period selected for the threshold. A weekly threshold paired with a monthly hours total would produce a number, but not a coherent weekly estimate.
The rate field is the single base hourly rate. It accepts a finite number from 0 through 1,000,000. The page does not attach a currency code, so use one currency consistently for rate and all pay interpretations. A zero rate is valid and produces zero regular pay, zero overtime pay, and zero total. The field is not a salary field and should not be used to hide an annual salary conversion or a blended hourly rate that requires a separate method.
The threshold field is the point at which hours stop being regular under the selected scenario. It accepts a finite number from 0 through 168 hours. The default is 40, matching the page's US-style weekly example. The multiplier field is the factor applied to the base rate for overtime hours. It accepts a finite number from 1 through 100, and the default is 1.5. Both fields are deliberately editable so a user can model a different stated rule, but editing them does not make the result legally authoritative.
- hours: finite 0 to 10,000 hours.
- rate: finite 0 to 1,000,000 in one consistent currency per hour.
- threshold: finite 0 to 168 hours.
- multiplier: finite 1 to 100; default 1.5.
The default weekly scenario
The default inputs are 45 hours, a rate of 20, a threshold of 40 hours, and a multiplier of 1.5. Read as a scenario, that means the first 40 hours earn 20 per hour and the remaining 5 hours earn 30 per hour because 20 x 1.5 = 30. The result is a weekly-style estimate under the selected assumptions, not a statement that every worker or every week is governed by those assumptions.
The threshold and multiplier are separate controls because they play different roles. The threshold decides how many hours are placed in each portion. The multiplier changes the rate applied only to the overtime portion. Raising the multiplier without changing the threshold increases overtime pay but does not move any hours between regular and overtime. Lowering the threshold can increase overtime hours while leaving the base rate and multiplier unchanged.
The default is useful as a recognizable worked example, but a user should replace it when the task concerns a different period or rule. Some arrangements use a different threshold, a different premium, or a different definition of hours worked. The calculator allows numerical scenarios within its bounds; it does not verify that a selected scenario is the correct interpretation of a contract, statute, collective agreement, or employer policy.
- Default scenario: 45 hours at rate 20, with a 40-hour threshold and 1.5 multiplier.
- The first 40 hours use the base rate and the last 5 use 1.5 times the base rate.
- Changing the threshold changes the split; changing the multiplier changes overtime rate.
- The default is a US-style weekly illustration, not universal payroll law.
How regular and overtime hours are split
The handler defines regularHours as min(hours, threshold). This means regular hours cannot exceed either the total hours entered or the threshold. It defines overtimeHours as max(0, hours - threshold). This prevents a value below the threshold from creating negative overtime hours. The two portions together equal the entered hours when hours and threshold are valid: regularHours + overtimeHours = hours.
For 45 hours and a threshold of 40, regularHours is min(45, 40) = 40 and overtimeHours is max(0, 45 - 40) = 5. For 32 hours and the same threshold, regularHours is min(32, 40) = 32 and overtimeHours is max(0, 32 - 40) = 0. At exactly 40 hours, regularHours is 40 and overtimeHours is 0. The max operation is what keeps the under-threshold cases sensible without a separate branch.
The model has one threshold and one overtime band. It does not create separate daily, weekend, holiday, double-time, or tiered bands. It also does not round hours before splitting them. If 40.25 hours is entered with a threshold of 40, the overtime portion is 0.25 hours. Whether a real payroll system rounds or records time in another increment is outside this handler and should be applied only when the governing rule is known.
- regularHours = min(hours, threshold).
- overtimeHours = max(0, hours - threshold).
- Valid regular and overtime portions add back to total hours.
- One threshold does not model multiple premium bands or daily rules.
The pay formulas
After splitting the hours, the handler calculates regularPay = regularHours x rate. Overtime pay is overtimePay = overtimeHours x rate x multiplier. The total is totalPay = regularPay + overtimePay. The multiplier applies to the entire base rate for each overtime hour in this model. A multiplier of 1.5 therefore makes the overtime hourly amount 150 percent of the base rate, while a multiplier of 2 makes it twice the base rate.
With a rate of 20, a 1.5 multiplier produces an overtime rate of 20 x 1.5 = 30. If the overtime portion is 5 hours, overtime pay is 5 x 30 = 150. The regular portion at 40 hours is 40 x 20 = 800. Adding 800 and 150 gives 950 total. Writing the two portions separately is valuable because it shows whether a disagreement comes from the hours split, the base rate, the premium factor, or the addition.
The formulas do not subtract anything. There is no tax, benefit, retirement, insurance, garnishment, fee, or other deduction field. The total is gross modeled pay for the two portions under the entered assumptions. Do not rename it take-home pay or net pay. If an external process needs a net amount, it requires additional inputs and rules that this page intentionally does not collect.
- regularPay = regularHours x rate.
- overtimePay = overtimeHours x rate x multiplier.
- totalPay = regularPay + overtimePay.
- The outputs are gross modeled portions, not take-home pay.
Worked calculation: the default example
Enter hours = 45, rate = 20, threshold = 40, and multiplier = 1.5. First calculate the split: regularHours = min(45, 40) = 40, and overtimeHours = max(0, 45 - 40) = 5. The five overtime hours are not added to the regular portion; they are kept separate so the premium factor can be applied only where the formula specifies it.
Next calculate each pay amount. Regular pay is 40 x 20 = 800. Overtime pay is 5 x 20 x 1.5 = 150. The total is 800 + 150 = 950. The page's example describes these values as Regular pay 800.00, overtime pay 150.00, and total pay 950.00. The actual result list places total pay first, so a reader should follow the result labels rather than assume the visual order of the arithmetic lines.
The implied average across all 45 hours would be 950 / 45, about 21.11 per hour, but that average is not an output and should not be confused with the base rate. It is merely a way to check the total's scale. The model's meaningful components remain 800 regular and 150 overtime. If a real payroll record includes other premiums or exclusions, this two-part calculation cannot be used as a complete reconciliation.
- Regular hours: min(45, 40) = 40.
- Overtime hours: max(0, 45 - 40) = 5.
- Regular pay: 40 x 20 = 800; overtime pay: 5 x 20 x 1.5 = 150.
- Total pay: 800 + 150 = 950, displayed as currency with two decimal places.
Worked scenarios below and at the threshold
Suppose hours = 32, rate = 20, threshold = 40, and multiplier = 1.5. Regular hours are min(32, 40) = 32 and overtime hours are max(0, 32 - 40) = 0. Regular pay is 32 x 20 = 640, overtime pay is 0 x 20 x 1.5 = 0, and total pay is 640. The multiplier is still valid, but it has no effect because there are no overtime hours.
At exactly the threshold, hours = 40 with the same other inputs gives 40 regular hours, zero overtime hours, 800 regular pay, zero overtime pay, and 800 total. This boundary is useful for testing because increasing hours from 40 to 40.01 creates only 0.01 overtime hours under the calculator's decimal-friendly contract. A payroll system may have a time-rounding policy, but this handler uses the numeric value supplied.
If hours = 0, every derived amount is zero for any valid rate, threshold, and multiplier. If rate = 0, the hour split still occurs, but all pay outputs are zero. These are valid inputs rather than parser errors. They can represent a scenario for testing, an unpaid period, or a placeholder, but the calculator cannot determine which interpretation is true from zeros alone.
- Below threshold, every entered hour is regular and overtime pay is zero.
- At the threshold, overtime hours are exactly zero.
- Decimal hours are not rounded by the handler before calculation.
- Zero hours or a zero rate produces zero pay without an error.
Worked adjustable-rule scenario
Consider 50 hours at a rate of 24, with a threshold of 35 and a multiplier of 2. The split is regularHours = min(50, 35) = 35 and overtimeHours = max(0, 50 - 35) = 15. Regular pay is 35 x 24 = 840. Overtime pay is 15 x 24 x 2 = 720. Total modeled pay is 840 + 720 = 1,560.
This example shows why the threshold cannot be treated as a label only. If the same 50 hours used a threshold of 40, regular pay would be 40 x 24 = 960 and overtime hours would be 10, producing 10 x 24 x 2 = 480 overtime pay and a total of 1,440. Moving five hours from overtime to regular lowers the modeled total because the multiplier is higher than one. If only the multiplier changed from 2 to 1.5 while the 35-hour threshold stayed fixed, overtime pay would become 15 x 24 x 1.5 = 540 and total would be 1,380.
The calculations are scenario comparisons, not advice about which rule to choose. A user can use them to see the arithmetic effect of a stated threshold or premium, then compare the scenario with the actual rule. The page does not know whether the threshold is weekly, daily, contractual, or otherwise defined, so the period and rule source must be documented outside the fields.
- At 50 hours, rate 24, threshold 35, multiplier 2: regular pay 840 and overtime pay 720.
- Total for that scenario is 1,560.
- Changing the threshold moves hours between the two pay rates.
- Changing the multiplier changes overtime pay without changing the hour split.
Validation and input handling
The handler's bounded guard requires each field to arrive as a JavaScript number. It rejects a value that is not of numeric type, is NaN, is positive or negative infinity, or lies outside that field's inclusive bounds. The catalog describes these controls as number fields, but the runtime contract still matters for integrations: a numeric-looking text value must be converted by the surrounding form layer before it reaches the handler. The handler itself does not evaluate text expressions or strip currency symbols.
The exact bounds are hours 0 to 10,000, rate 0 to 1,000,000, threshold 0 to 168, and multiplier 1 to 100. A negative hours value, negative rate, negative threshold, or multiplier below 1 is rejected. A threshold above 168 or a multiplier above 100 is rejected even if a caller believes that a larger scenario would be useful. These limits keep the page's intended model finite and prevent an out-of-contract input from being treated as an ordinary payroll case.
The bounded helper normalizes negative zero to zero. After validation, the formulas are applied directly; there is no hidden rounding of hours, threshold, rate, or multiplier. A valid decimal remains a decimal in the calculation. Passing validation means that the values fit the page's numerical shape. It does not validate a timecard, prove an employment classification, confirm a currency, or establish that the selected threshold and multiplier are legally applicable.
- Inputs must arrive as finite JavaScript numbers, not expressions or formatted text.
- Each field has its own inclusive numeric bounds.
- Negative zero is normalized to zero.
- Validation checks shape and range, not payroll records or legal applicability.
Currency output and numerical display
Each result is emitted with currency format. The result helper's default precision is 2, so total pay, regular pay, and overtime pay are intended to display with two decimal places, such as 950.00. The handler returns the total first, followed by the two components. The page does not add a currency code or exchange-rate conversion; the user must know which currency the hourly rate represents and keep all interpretation in that same currency.
The arithmetic is performed as ordinary JavaScript numeric multiplication and addition. The internal values can contain more precision than the two-decimal display, especially when fractional hours, a fractional rate, or a decimal multiplier is entered. Display rounding should happen at presentation, not be mistaken for a change to the formula. If a payroll system rounds each line item separately, rounds hours, or applies a currency-specific rule, its result can differ by a small amount from this page's direct calculation.
The output helper rejects a numeric result that is not finite. Under the documented bounds, the products are finite in normal JavaScript number arithmetic, but the guard keeps a non-finite result from being displayed if the implementation or inputs change. For an audit, retain the four inputs, the three labeled outputs, the displayed precision, and the rule period. Do not compare unlabeled rounded figures as though they were interchangeable payroll records.
- All three results use currency format with the helper's default precision 2.
- Output order is total pay, regular pay, overtime pay.
- The page does not select a currency or apply exchange rates.
- Display rounding and external payroll line-rounding policies can differ.
Threshold, multiplier, and boundary cases
A threshold of zero is valid. With hours = 10, rate = 20, threshold = 0, and multiplier = 1.5, regular hours are min(10, 0) = 0 and overtime hours are max(0, 10 - 0) = 10. Regular pay is zero, overtime pay is 10 x 20 x 1.5 = 300, and total is 300. This is a mathematical scenario in which every hour is beyond the threshold; it is not a default and not evidence that a real rule uses zero.
A multiplier of 1 is also valid. It makes overtime hours pay at the same numeric rate as regular hours, so the total becomes hours x rate even though the result remains separated into regular and overtime portions. A multiplier between 1 and 100 is accepted as a decimal, allowing a scenario such as 1.25. A multiplier below 1 is rejected because the contract defines overtime as no less than the base-rate factor.
The maximum threshold is 168 hours, the number of hours in a seven-day period. Hours can be greater than 168 up to the separate maximum of 10,000, so a scenario may place all hours above a selected threshold into overtime. Those large bounds are computational boundaries, not a statement about a normal work schedule. The model still has one threshold and one rate even at the extremes.
- Threshold zero assigns all positive hours to overtime.
- Multiplier one keeps the overtime rate equal to the base rate.
- Threshold is capped at 168; hours have a separate cap of 10,000.
- Boundary values describe arithmetic scenarios, not recommended schedules.
Practical uses for scenario planning
The calculator can help a worker or manager check the arithmetic of a simple single-rate estimate before comparing it with a timecard or a payroll statement. Enter the hours for the defined period, the base rate, the stated threshold, and the stated multiplier. The separate outputs make it possible to ask whether the discrepancy is in regular hours, overtime hours, the base rate, or the premium factor rather than treating the total as an unexplained amount.
It can also compare scenarios. Hold hours and rate constant while changing the threshold to see how the regular/overtime split changes. Hold the split constant while changing the multiplier to isolate the effect of the premium. Run an under-threshold case, an exact-threshold case, and a modest overtime case as sanity checks. These comparisons are most informative when the period and definitions are written beside each result.
For teaching, the page makes the min and max functions concrete: min caps regular hours at the threshold, and max prevents negative overtime hours. For a personal estimate, it can show gross modeled pay before deductions. For a review, it can provide a reproducible baseline that a qualified payroll or legal reviewer can replace with a fuller calculation when more factors apply.
- Check a simple single-rate estimate against a defined timecard period.
- Compare threshold and multiplier scenarios independently.
- Use boundary cases to test a spreadsheet or integration.
- Treat the result as a gross arithmetic baseline for further review.
What the model does not include
There are no fields for taxes or payroll deductions, so the page cannot compute net pay or take-home pay. It does not include retirement contributions, insurance premiums, garnishments, benefits, fees, reimbursements, or other adjustments. The result is the sum of the two modeled gross portions only. Applying a tax percentage after the fact would be a separate estimate and would not make the page's output a payroll calculation.
There is also no field for shift differential, holiday premium, weekend premium, double time, hazard pay, bonus, commission, tip credit, multiple job rate, or changing rate. The formula applies one rate to regular hours and that same rate multiplied by one multiplier to overtime hours. If different hours earn different rates or premiums, adding them into one blended rate can hide the distinction and may not match a required regular-rate method.
The page does not model daily overtime, consecutive-day rules, special employee categories, exemptions, salary thresholds, jurisdictional definitions, collective bargaining terms, or employer-specific rounding. It does not decide whether hours qualify as hours worked. Those omissions are deliberate: the tool is a four-number model for one threshold, not a jurisdiction-aware payroll engine. Use a fuller method when any omitted rule can change the result.
- No taxes, deductions, benefits, garnishments, or net-pay calculation.
- No shift differentials, multiple rates, bonuses, or separate premium bands.
- No daily overtime, exemption, salary, contract, or jurisdictional determination.
- A single blended rate cannot stand in for a required weighted regular-rate calculation.
Interpretation and legal limits
The narrowest defensible interpretation is: under the entered values, one threshold, one base rate, and one multiplier, the page calculates these three gross currency amounts. It does not say that the worker is entitled to the result, that the employer owes it, or that the inputs satisfy a statute. The default is a familiar US-style weekly example, but changing the controls only creates a numerical scenario; it does not select the governing law for a person or workplace.
A legal overtime question can depend on facts absent here, including the work period, worker status, exemptions, included compensation, regular-rate treatment, state or local requirements, agreement language, and timekeeping rules. Even the meaning of hours worked may require a factual determination. Because the page collects none of those facts, it cannot make a legal determination or resolve a wage dispute.
Use the result to explain arithmetic, identify which assumptions drive a difference, or prepare a question for payroll or a qualified adviser. Do not present it as an official wage statement, compliance certificate, or legal opinion. If a consequential decision depends on the number, verify the time record, rate components, threshold, multiplier, rounding, deductions, and applicable policy outside this page.
- The result is an assumption-bound gross-pay estimate.
- The default does not establish a universal overtime entitlement.
- The calculator cannot determine worker status, applicable law, or legal liability.
- Use payroll records and qualified review for consequential or disputed amounts.
A reproducible reporting checklist
Start a report by naming the period and currency, then record hours, rate, threshold, and multiplier exactly as entered. State whether the hours are a weekly total or another scenario and identify the rule source that supplied the threshold and premium assumption. The four fields alone do not preserve this context, so adding it in the surrounding record prevents a weekly estimate from being reused as a daily or monthly conclusion.
Show the split before the money: regularHours = min(hours, threshold) and overtimeHours = max(0, hours - threshold). Then show regular pay, overtime pay, and total in the same order as the page outputs. For the default example, write 40 regular hours, 5 overtime hours, 800 regular pay, 150 overtime pay, and 950 total. Preserve two-decimal display values while noting that the handler performs direct numeric arithmetic before presentation.
Finish with exclusions. Say whether taxes, deductions, multiple rates, shift premiums, daily rules, salary treatment, rounding, or legal classification were reviewed elsewhere. If any omitted factor applies, label the result as a partial scenario rather than a final paycheck. This reporting habit makes the page useful as a transparent calculation without allowing its short formula to impersonate a full payroll or legal analysis.
- Record period, currency, hours, rate, threshold, and multiplier.
- Show regular and overtime hours before showing pay.
- List total first, regular second, and overtime third with two-decimal display.
- State omitted payroll factors and legal review requirements.
The calculator's deliberate boundary
This page is intentionally a one-rate, one-threshold, one-multiplier model. That boundary makes every output traceable: the threshold determines the split, the rate prices regular hours, the multiplier prices overtime hours, and addition produces the total. It also makes the result easy to test with zero, under-threshold, exact-threshold, fractional-hour, and overtime cases. A smaller contract is preferable to a hidden collection of assumptions that a user cannot inspect.
The same boundary means that a realistic wage calculation may require another method. When compensation changes during the period, when different work types have different rates, when premiums affect the base used for overtime, or when multiple legal thresholds overlap, do not force the facts into one rate and one multiplier just to obtain a number. The page cannot recover information that its fields never collected.
Use the tool for the calculation it names and no larger one. Retain the inputs, formulas, output labels, currency, period, and assumptions. Verify orders of work, payroll policy, and applicable rules through the appropriate authority. The result is useful when it remains an honest estimate; it becomes misleading when its clean arithmetic is presented as a complete payroll record or legal answer.
- One rate and one threshold keep the arithmetic auditable.
- Complex compensation should not be compressed into a misleading blended input.
- The page cannot infer facts or rules absent from its four fields.
- Use it only for the stated estimate and preserve its assumptions.
Frequently asked questions
What is the Overtime Pay?
Weekly paycheck split into regular and overtime pay at an adjustable threshold and multiplier.
What is the formula for the Overtime Pay?
regularHrs = min(hours, threshold); otHrs = max(0, hours - threshold); total = regularHrs x rate + otHrs x rate x multiplier. Hours up to the threshold earn the base rate; hours beyond it earn the rate times the multiplier. With 45 h at 20 and 40/1.5 defaults, regular pay is 800 and overtime is 150.
What do I need to use this calculator?
Enter Hours worked, Hourly rate, Overtime threshold, Overtime multiplier, then choose Calculate.
What are the limits of this calculator?
US-style weekly overtime default (40 h at 1.5x); adjust both to match local rules. Single base rate with no taxes, deductions, shift differentials, or daily-overtime rules.
Methodology
This calculator is part of the WorldCalculate library. Its formula, example, assumptions, input bounds, and output formatting follow the official methodology.
Use this calculator as part of a bigger plan
These WorldCalculate collections connect this tool with related questions while keeping each calculation separate and transparent.