Daily and Weekly Hours Pay Ledger

How to use Daily and Weekly Hours Pay Ledger

Enter a repeating seven-date anchor, explicit hour limits and rate multipliers. Separate daily premium hours first, allocate remaining hours chronologically to the weekly regular pool, then compare day and week half-up cent rounding.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Enter a repeating seven-date anchor, explicit hour limits and rate multipliers. Separate daily premium hours first, allocate remaining hours chronologically to the weekly regular pool, then compare day and week half-up cent rounding.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–200 unique dates in strict chronological order, Gregorian years 1900–9999. Daily hours are 0–24, optional daily limit 0–24 and optional weekly regular limit 0–168. Exact decimal strings allow six places. Base rate is 0–1,000,000 and multipliers 1–10.
• A null threshold disables that bucket. Daily premium hours do not enter the weekly regular-hour pool. Missing dates mean no entered hours, and incomplete weeks cannot establish complete payroll. Week start/end dates must remain in the supported calendar.
• An original user-policy scenario only. No statutory thresholds, exemption, minimum wage, weighted regular rate, holiday premium, tax, time-zone/DST shift conversion, employer import or legal/payroll compliance conclusion.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.