Georgia overtime calculator

Negative hours worked fail with invalid_input instead of printing a nonsense negative check.

What Georgia overtime means and how the forty-hour week splits

This calculator encodes that weekly identity and nothing else: regular_hours is the lesser of hours_worked and forty, overtime_hours is the excess above forty or zero when the week is shorter, regular_pay is hourly_rate times regular_hours, overtime_pay is hourly_rate times one-point-five times overtime_hours, and total_pay is the sum of those two money amounts rounded to two decimal places. Negative hours_worked cannot describe a schedule, so they are rejected rather than rendered as a refund. Example: an eighteen-dollar-and-fifty-cent rate with forty-eight hours in the week yields forty regular hours and eight overtime hours, so regular_pay is seven hundred forty dollars and overtime_pay is two hundred twenty-two dollars, for a total_pay of nine hundred sixty-two dollars.

Input contract, response shape, and error behaviour

POST a JSON body with two required finite numbers: hourly_rate, the non-negative base wage per hour, with aliases rate, wage, hourly, pay_rate, and hourly_wage; and hours_worked, the hours actually worked in one Georgia workweek, with aliases hours, weekly_hours, hrs, hours_week, and total_hours. hours_worked may be zero through one hundred sixty-eight, the hours in seven twenty-four-hour days; a figure above that ceiling cannot be a single week and is rejected. Each field may arrive as a JSON number or as a numeric string; non-finite values, missing fields, and empty strings fail with invalid_input naming the field. A negative hourly_rate is rejected the same way. On success the body includes the echoed hourly_rate rounded to two decimals; hours_worked as parsed; weekly_threshold always forty; overtime_multiplier always one point five; regular_hours and overtime_hours as the split; ot_hourly_rate as the time-and-a-half wage; regular_pay, overtime_pay, and total_pay as money fields; currency_decimals of two; method georgia_flsa_weekly; and jurisdiction Georgia. Example: hourly_rate of twenty with forty hours yields eight hundred dollars of regular_pay, zero overtime_pay, and a total_pay of eight hundred dollars because the week never crossed the FLSA threshold. Pair the gross figures with your own withholding table if you need net take-home; this endpoint computes regular plus overtime pay only and does not emit a tax line.

Where a Georgia overtime calculator earns its keep

Payroll clerks and bookkeepers in Georgia shops search for a Georgia overtime calculator when they already know the hourly rate and the hours on the timesheet but do not want to split the week by hand or to confuse Georgia with a daily-overtime state. Staffing firms and shift marketplaces live on hourly quotes; applying the forty-hour FLSA split on the Georgia landing gives the same premium a recruiter should expect without forcing them to remember whether Georgia uses eight-hour days. Failed validation does not consume balance. Keep the hourly rate and the hours non-negative, pin the rounded money fields in tests, and you get a reproducible Georgia overtime check for widgets, course modules, and edge workers without standing up a payroll engine of your own. Household budget apps can store the returned total_pay as a weekly inflow when a worker regularly clocks extra hours, then let the user layer rent and savings on a cadence that matches payday. Human-resources microsites and applicant-tracking add-ons can call the same pure module from the browser for a free preview and from the API when they persist a scenario, guaranteeing that the number a visitor saw on a landing page is the number stored after they save. Educators teaching the difference between weekly FLSA overtime and daily overtime can seed classroom examples that fail loudly on negative hours_worked instead of silently printing a minus sign a student might treat as a refund.