Timesheet Validator - Validation Rules

Business Logic:
On weekdays, employees are expected to work. If no time is entered and no remarks explain the absence, this indicates unapproved leave.

Example:
Date: Jan 15 (Mon) | C/D/H: All empty → Error

Business Logic:
Partial attendance must be explained with a valid leave type or have both start/end times filled.

Example:
Date: Jan 20 (Mon) | C: Empty, D: 18:00, Remarks: "Doctor appointment" → Error

Business Logic:
CL, ML, and PL are special paid leave types that don't require work hours. These are exempt from "leave without reason" rules.

Example:
Date: Jan 25 (Mon) | C/D: Empty, Remarks: "CL - Family emergency" → OK ✅

Business Logic:
If marking half-day leave (AM or PM), the employee should still work the other half and enter those hours in columns C/D.

Example:
Date: Feb 5 (Wed) | C/D: Empty, Remarks: "AL (AM)" → Error

Business Logic:
Full-day NPL or NPSL means no work should be recorded. If C/D are filled alongside a full-day NPL/NPSL remark (without an AM/PM marker), the entry is contradictory.

Half-day NPL(AM) or NPL(PM) is valid — the employee works the other half and enters times in C/D.

Example (error):
Date: Mar 4 (Tue) | C: 09:00, D: 18:00, Remarks: "NPL" → Full-day NPL but 9.0h recorded → Error

Example (valid):
Date: Mar 4 (Tue) | C: 13:00, D: 18:00, Remarks: "NPL (AM)" → Half-day NPL, afternoon worked → OK

Business Logic:
If time is entered (C & D), the working hours formula (E) should calculate a numeric value. "N/A" or errors indicate formula/data issues.

Example:
Date: Jan 12 (Mon) | C: 09:00, D: 18:00, E: "N/A", actual: 9.0h → Error

Business Logic:
The working hours in column E must match the calculated difference between end time and start time [(D-C) × 24].

Example:
Date: Jan 18 (Mon) | C: 09:00, D: 18:00, E: 8.5h, actual: 9.0h → Error

Business Logic:
Employees should work their expected hours unless on approved leave. Small discrepancies within tolerance (0.5h) are allowed for rounding.

Example:
Date: Feb 8 (Mon) | actual: 7.5h, expected: 9.0h → 7.5+0.5=8.0<9.0 → Error

Business Logic:
Overtime is only permitted when actual hours exceed expected hours + tolerance. Working exactly expected hours = no OT allowed.

Example:
Date: Jan 22 (Mon) | actual: 9.0h, expected: 9.0h, OT: 1.0h → Error

Business Logic - 1-hour buffer rule:
Employees must work >1 hour beyond expected hours before OT is counted.
• actual - expected ≤ 1h → No OT allowed
• actual - expected > 1h → OT = excess hours - 1

Example:
Date: Feb 3 (Wed) | actual: 11.0h, expected: 9.0h, OT(F): 2.0h, calcOT: 11-9-1=1.0h → Error

Business Logic:
Employees arriving later than scheduled start time + 15min tolerance are marked as late. Requires employee schedule data.

Example:
Date: Jan 10 (Mon) | Scheduled: 09:00, Actual: 09:25 → 09:25>09:15 → Error

⚠️ Status: Not started - requires employee schedule data

Business Logic:
Employees leaving earlier than scheduled end time - 15min tolerance are marked as early departure. Requires employee schedule data.

Example:
Date: Jan 15 (Mon) | Scheduled: 18:00, Actual: 17:30 → 17:30<17:45 → Error

⚠️ Status: Not started - requires employee schedule data

Business Logic:
When hours worked are significantly less than expected (beyond 0.5h tolerance), it suggests late arrival or early departure. This flags for manager review.

Example:
Date: Feb 12 (Fri) | actual: 7.0h, expected: 9.0h → Error (warning)

Business Logic:
5.5-day employees are expected to work Saturdays (typically 4 hours). Partial hours without valid leave explanation require justification.

Example:
Date: Jan 11 (Sat) | Type: 5.5-day, expected: 4.0h, actual: 2.5h, Remarks: "Personal matters" → Error

Business Logic - Saturday OT Rule:
• First 4 hours = regular working hours
• Hours beyond 4 = overtime
• OT only counted if worked >5.5 days that week
• Formula: Saturday OT = actualHours - 4

Example:
Date: Jan 18 (Sat) | Type: 5.5-day, actual: 6.0h, OT(F): 2.5h, calcOT: 6.0-4.0=2.0h → Error

Business Logic:
5.5-day staff Saturdays are working half-days. Any leave taken on a Saturday should specify AM or PM to clarify which half was taken. A warning is generated when a leave type is present but no half-day marker is found.

Example (warning):
Date: Jan 11 (Sat) | 5.5-day, Remarks: "SL" → Warning: "Jan 11 - Saturday SL should specify (AM) or (PM)"

Example (valid):
Date: Jan 11 (Sat) | 5.5-day, Remarks: "SL (AM)" → OK ✅

Leave types checked: AL, SL, CL, ML, PL, NPL, NPSL, COMPASSION

Business Logic - Rest day work rule:
• All hours worked on a rest day = OT (no "regular hours")
• C-D, E, and F must all match
• Applies to: Sunday, Public Holiday, AND Saturday for 5-day staff
• 5-day staff Saturday is treated as a rest day (same as Sun/PH)
• 5.5-day staff Saturday is handled separately by Rules 11 & 12

Example (Sun/PH):
Date: Jan 1 (Sun-PH) | C: 10:00, D: 15:00, E: 5.0h, F: 4.5h → Error

Example (5-day Saturday):
Date: Jan 11 (Sat) | 5-day staff | C: 10:00, D: 14:00, E: 4.0h, F: 3.5h → Error

Business Logic:
Sundays, public holidays, and Saturdays for 5-day staff are all rest days. No work = no error.
5-day staff Saturday is a rest day (same treatment as Sun/PH).

Example (Sun/PH):
Date: Jan 1 (Sun-New Year) | C/D: Empty → OK ✅ (no error)

Example (5-day Saturday):
Date: Jan 11 (Sat) | 5-day staff | C/D: Empty → OK ✅ (no error)

Business Logic:
Leave types shouldn't be marked on rest days (Sunday, Public Holiday, or Saturday for 5-day staff) since these are already non-working days. This is a WARNING to prevent accidental leave deduction.
Leave is NOT counted but a warning remark is generated.

Example (Sun/PH):
Date: Jan 1 (Sun-New Year) | Remarks: "AL" → Warning: "Jan 1 - AL marked on rest day (Sun/PH)"

Example (5-day Saturday):
Date: Jan 11 (Sat) | 5-day staff | Remarks: "SL" → Warning: "Jan 11 - SL marked on rest day (Sun/PH)"

7 different messages: One for each leave type (AL, SL, CL, ML, PL, NPL, COMPASSION)