# Hyfecta standard attendance CSV — version 1

Use one file for one employing company. Select that company in Hyfecta before importing. All example records are fictional and are not payroll instructions.

## Files

- `attendance-template.csv`: blank input template; retain the header and add your records.
- `attendance-sample-india.csv`: 15 fictional shifts for three employees in Gujarat, 14–18 September 2026.
- `attendance-sample-uk.csv`: 10 fictional shifts for two employees in London over the same dates.

## Fields to complete

All five columns are required. Column order may change, but names must stay the same. Extra columns are rejected so that data is never silently discarded.

| Column | Meaning and format | India example | Validation |
|---|---|---|---|
| employee_code | Stable employee identifier from the selected company’s Employee directory. Treat this as text, including leading zeroes. | IN-P001 | Must match an existing employee code exactly. Do not use names as identifiers. |
| clock_in | Start of the attendance period, including date, seconds and UTC offset. | 2026-09-14T09:00:00+05:30 | Full timestamp required; ambiguous local times are not accepted. |
| clock_out | End of the attendance period in the same timestamp format. | 2026-09-14T19:00:00+05:30 | Must be after clock-in; duration must be a whole number of minutes and no more than 24 hours. |
| break_minutes | Total breaks within the attendance period, as whole minutes. Enter 0 when there were no breaks. | 60 | Non-negative integer no larger than the attendance period. Blank does not mean zero. |
| source | Source of the record, such as export batch, device or manually checked register. | Office clock export Sep-2026 | Non-empty text, maximum 60 characters. Quote values containing commas. |

Timestamp pattern: `YYYY-MM-DDTHH:MM:SS±HH:MM`. India examples use `+05:30`. London examples for September use `+01:00`; do not reuse that offset throughout the year. Use the offset valid at the time of the shift. `Z` is accepted for UTC. Hyfecta assigns the work date from the start timestamp in the selected company’s country timezone: Asia/Kolkata for India and Europe/London for the UK.

## Employee setup for the fictional examples

Create these codes in the corresponding sample company’s Employee directory before trying the sample CSV. Names below are deliberately fictional role labels. These files do not create employees or set salary details.

| Company | Code | Suggested sample name |
|---|---|---|
| India | IN-P001 | Sample India preparer |
| India | IN-R001 | Sample India reviewer |
| India | IN-M001 | Sample India manager |
| UK | UK-MKT001 | Sample UK marketing employee |
| UK | UK-OPS001 | Sample UK operations employee |

## Calculated by Hyfecta — do not add these CSV columns

| Output | Calculation or source |
|---|---|
| Work date | Local date on which the attendance period starts. |
| Presence | Elapsed minutes between clock-out and clock-in. |
| Available time | Presence less break minutes. |
| Actual task time | Employee-linked task records across jobs on that date; not inferred from attendance. |
| Booked task time | Booked minutes from those task records. |
| Unexplained attendance gap | Presence minus breaks minus actual task minutes. This is a prompt to review internal work, training, outside-premises work or missing data—not a judgement of misconduct. |

Leave approval, paid days, overtime entitlement, quality, salary and productive hours are not supplied through this attendance file. They belong to their own workflows. An absent employee is not represented by a fabricated zero-duration shift. Missing attendance is not automatically an absence or unpaid leave.

## Import procedure

1. Select the employing company and save its country in **Settings › Company** (Company profile).
2. Add employee codes in **People Management › People & costs**. Use the same code consistently.
3. Download the blank template. Fill it in using a text editor, spreadsheet or export tool. Keep employee codes and timestamp columns as text; export as CSV UTF-8.
4. Choose the CSV under **People Management › People & costs → Import clock-in/out CSV**, then select **Review import**.
5. Check employee names, work dates, presence, breaks and any existing records that will be replaced. Previewing makes no attendance changes.
6. Select **Apply reviewed attendance records**. If records changed after the preview, review a fresh preview before applying.

Files are limited to 200 rows and 60 KB. Keep one shift summary per employee per local start date. Duplicate employee/date rows in one file are rejected. The same employee/date already in Hyfecta appears as a replacement in the preview. The complete batch saves together, and retrying the same submission does not duplicate it.

Overnight attendance belongs to its start date. The current version is for daily attendance summaries, not raw badge scans or multiple split-shift events. For split shifts, supply the full attendance window and include all gaps outside attendance in the break total, after reviewing the result. Do not sum separate shift durations and mislabel them as continuous presence. Where that representation is unsuitable, retain the original export for a future event-level connector.

## Sample controls

| File | Shifts | Employees | Presence hours | Break hours | Available hours |
|---|---:|---:|---:|---:|---:|
| India sample | 15 | 3 | 137.5 | 12.5 | 125 |
| UK sample | 10 | 2 | 82.5 | 7.5 | 75 |

These are attendance totals only. No task hours, billable hours, leave balances or payroll values can be deduced from them. Import sample files only into a sample company.