How to Mark, Bulk-Mark and Import Attendance in CrmLeaf
All editions. Core feature - no add-on required.
Availability: All editions. Core feature - no add-on required.
Overview
Employees normally record their own attendance by clocking in and out, but managers need to fill gaps: a missed punch, a day recorded from a paper register, or a team whose attendance was tracked elsewhere. CrmLeaf lets a manager mark attendance for an employee, bulk-mark attendance for many employees at once, and import attendance from a CSV file or a calendar. Attendance reports can then be exported per member per month.
How It Works
You review the attendance data, correct or add what is missing, then export the month for verification or payroll.
Review attendance → Mark or bulk-mark → Import CSV or calendar → Verify against shifts → Export the report
- Marking attendance creates or corrects the record for one employee on one date.
- Bulk-marking applies attendance to many employees at once, which suits a whole team on a normal working day.
- CSV import loads attendance from a file; calendar import loads it against dates.
- Records carry the same context as a self-recorded punch, including the linked shift and the late, half-day and work-from flags.
- Attendance reports export per member per month, and attendance feeds Payroll where that add-on module is enabled.
Who Can Use This Feature?
Administrator
- Mark attendance for an individual employee and date.
- Bulk-mark attendance for many employees.
- Import attendance from a CSV file or from a calendar.
- Export attendance reports per member per month.
This functionality is available only to Administrators, or to a role your Administrator has given attendance management access. Employees record their own attendance by clocking in and out.
Prerequisites
- Employee records exist for everyone whose attendance you will mark.
- Shift schedules or a default shift are in place, so records are evaluated against the correct hours.
- Company holidays and weekly offs are configured, so you do not mark attendance on non-working days by mistake.
- For an import, the source data is prepared with one row per employee and date.
For Administrators
Step 1: Review the attendance data
What to do: Use Filter to select the period and the employees, and identify the gaps: days with no record, days with a missing clock-out, and unexpected late flags.
What to verify: You have a definite list of the days that need correction before you change anything.
Step 2: Mark attendance for one employee
What to do: Select the employee and the date, then record the attendance for that day, including whether it is a half day and whether the person worked from office or home. Select Save.
What to verify: The day now shows a record with the correct shift and flags.
Step 3: Bulk-mark attendance for a team
What to do: Select the employees and the date or period, set the attendance to apply, and confirm. Use bulk-marking where a whole group had the same normal working day.
What to verify: Every selected employee has a record for the period, and nobody was marked on a holiday or weekly off.
Step 4: Import attendance
What to do: Select Import and choose the CSV or calendar import. Prepare the file to match the expected columns, then upload it. Correct any rows the import rejects and repeat.
What to verify: The imported days appear in Attendance for the right employees and dates. Spot-check several rows against the source data.
Step 5: Export the month
What to do: Select Export to produce the attendance report per member for the month. Use it to verify the period before you close it, and before a payroll run.
What to verify: Each member's total working days for the month matches your expectation, allowing for approved leave and non-working days.
Expected Result
The corrected and imported attendance records appear in Attendance for the right employees and dates, with the linked shift and flags, and the monthly attendance report exports per member.
Service Organisation Context
Consultants who spend the day at a client site are the people most likely to miss a punch, so a delivery-heavy month usually leaves gaps for a manager to close. Correcting them keeps the presence record consistent with the shift and leave data that the Resource Utilization views read where that add-on is enabled. Keep the distinction in mind: attendance says who was working, while billable and non-billable hours per person, project and period come from the Time Log Report, not from here. The same marking and import routes serve site crews, production teams and any group whose hours were captured elsewhere.
Important Notes
- Menu names and their position can differ between product editions and can be customised for your account, so your sidebar may not match these paths exactly. Use Search or your Quick Access items if you cannot find a screen.
- Marking attendance on someone's behalf overrides what the employee did or did not record. Keep your own note of why a record was changed.
- Import a small test batch first and check the result before importing a full month.
- Correct attendance before running payroll where the Payroll add-on module is enabled, because payroll works from this data.
- Marked and imported records are still evaluated against the employee's shift. Fix the roster first if the shift is wrong.
Common Scenarios
Example: a forgotten clock-out. An employee clocked in but never clocked out. Mark the attendance for that employee and date so the day is complete, then check the monthly export before payroll.
Example: moving from a paper register. Enter the month's register into the expected CSV layout and import it, then bulk-mark any remaining normal working days. Export the month and compare the totals with the register before you rely on it.
Example: an offsite day for a whole team. Bulk-mark the team for that date rather than editing each record, and set the work-from flag appropriately.
Troubleshooting
| Issue | Possible Cause | Resolution |
|---|---|---|
| You cannot mark attendance for an employee. | Your role does not have attendance management access. | Ask an Administrator to grant the access. |
| Marked days show a late flag. | The record is compared with the employee's assigned shift. | Check the shift schedule for that date and correct the roster if it is wrong. |
| Import rows are rejected. | A mandatory value is missing, or the employee or date cannot be matched. | Correct the rows and re-import. Confirm the employee exists and the date format matches. |
| Bulk-marking created records on a holiday. | The selected period included a company holiday or weekly off. | Review the holiday configuration and remove the incorrect records. |
| The monthly total is lower than expected. | Days are missing, or approved leave covers them. | Filter the month for days with no record and check the leave for the same period. |
Frequently Asked Questions
Can I correct an attendance record after the day has passed?
Yes. An Administrator can mark or correct attendance for a past date.
What is the difference between marking and importing?
Marking is done in the application for one employee or a selected group. Importing loads attendance in bulk from a CSV file or a calendar.
Can I export attendance for one employee only?
Yes. Attendance reports export per member per month.
Does marked attendance count for payroll?
Attendance feeds payroll where the Payroll add-on module is enabled, so correct the data before the payroll run.
Related Articles
Our support team answers on business days. Reference ATT-03 so we can jump straight in.