8. Punch Types & Log Types
8.0 Punch Types from CAMS
The CAMS Gateway supports the following punch types in the Type field:
| CAMS Punch Type | Description | Treated as Attendance? |
|---|---|---|
CheckIn |
Standard clock-in | Yes (creates IN log) |
CheckOut |
Standard clock-out | Yes (creates OUT log) |
BreakOut |
Employee goes on break | Configurable |
BreakIn |
Employee returns from break | Configurable |
OverTimeIn |
Overtime start | Configurable |
OverTimeOut |
Overtime end | Configurable |
MealIn |
Meal period start | No (filtered separately) |
MealOut |
Meal period end | No (filtered separately) |
8.1 Special Handling for MealIn / MealOut
A key feature added in v1.0.0 is separate handling for MealIn and MealOut punch types. These punches are captured and stored but do not affect normal attendance marking. This prevents meal breaks from being mis-classified as clock-outs and inflating absent or short-hour records.
The fixture for this field is included in the release and no manual configuration is needed.
8.2 Log Type Mapping
FrappeHR's Employee Checkin uses log_type values of IN and OUT. The mapping from CAMS punch types is:
| CAMS Type | FrappeHR log_type |
|---|---|
| CheckIn, BreakIn, OverTimeIn | IN |
| CheckOut, BreakOut, OverTimeOut | OUT |
| MealIn, MealOut | Handled separately |
8.3 Input Types
The CAMS payload also includes InputType indicating the biometric method used:
FingerprintFacePalmCardPassword
This data is available in the raw payload received by the app, though FrappeHR's standard Employee Checkin doctype does not have a dedicated field for it by default.