When your people start the day at a depot, a customer site or their own home, attendance stops being a register at the door. Drivers, delivery crews, warehouse teams and field sales staff all present the same difficulty: you need a record you can trust, and the people generating it are rarely where you are.
This post covers how to build an attendance and payroll routine for a logistics or field team with roughly 20 to 100 employees on your payroll, what to record, how to deal with weak networks, and how to turn it all into pay without month-end arguments.
Figures here reflect the rules as we understand them at the time of writing. Verify against the current rules and notifications before relying on them.
What you actually need to know about a field day
Before choosing a tool, decide what the record has to answer. For most teams it comes down to four questions.
- Did this person start work, and when?
- Where were they when they started?
- Did they finish, and how long did they work?
- Is there anything unusual that a supervisor should look at?
You do not need to track every minute of the day. A start and an end, with a location and an optional photo, covers most disputes. More than that tends to create resentment and data nobody reads.
Punching from a phone
In Saralix, employees punch in and out from a web or mobile app. Three optional controls decide how strict the record is.
Location. The punch can capture GPS. Each branch has an office location, and the system compares the punch against it with a radius, allowing for the accuracy the phone reports. You choose what happens when a punch falls outside: nothing, flag it for HR, or block it. Work from home can be exempt, and any one of your offices counts as a valid location. Check-in and check-out locations are kept separately, and HR and the manager see a map icon in the Today view with the distance from the office and a map link.
Office network. You can also list the IPv4 or IPv6 addresses and ranges of your office network, and apply the same off, flag or block choice. For a depot or warehouse that is useful. For a driver on the road, leave it off or flag only.
Selfie. Under attendance policies, a selfie at each punch can be off, optional or required. On a phone, check-in opens the front camera while the location is found. Selfies are kept for a period you set, between 30 and 365 days with 90 by default, and a daily job deletes them afterwards. If the camera is blocked or missing, the employee is told how to fix it and can skip unless a selfie is required.
These checks reduce buddy punching. They do not make it impossible, so treat the flags as prompts for a conversation, not proof. Be open with staff about what you collect and for how long, and keep the policy in writing. The product also includes DPDP-related tools: employees can download their data, and HR can handle erasure requests, which keep only what labour and tax law require.
When there is no signal
Roads, basements and warehouses with poor coverage are normal. If a punch fails, people fill the gap later from memory, and the record is only as good as that memory.
The installable app deals with this by saving a check-in or check-out on the phone and sending it when the connection returns, with the time it was made. HR sees it flagged as, for example, punched offline at 09:02 and sent at 10:15. There are limits: an offline punch cannot be older than 12 hours, cannot be in the future, cannot land before the check-in or after a later check-out, and skips the office network check. The location check still applies.
The app can be installed on Android, iPhone or desktop. Its shell opens on a weak connection, but payslips, salaries and personal details are never stored by it.
Rosters for depots and warehouses
Warehouse and depot staff usually work shifts. A shift roster planned day by day tells the system what counts as late or early, which days are weekly offs, and which days are unpaid. Supervisors plan their own team, and a night shift that ends after midnight is counted against the day it started. Employees see their next two weeks in self-service.
For field staff who work whenever the route requires, a roster may be too rigid. In that case, set a standard shift and use attendance corrections and manager approval for exceptions. The Today view lists exceptions first, so a supervisor looks at the odd cases instead of every row.
Overtime and working on offs
Long routes and peak seasons generate overtime, and they also generate work on weekly offs and holidays. Two mechanisms apply.
- Overtime is recorded in attendance. In the payroll review you see it per employee, edit hours to what was approved and save. It is paid at twice the ordinary hourly rate, worked out from monthly gross over 26 days and 8 hours by default, and the divisors are configurable. More than 50 hours in a month is flagged. Overtime is taxable and counts as ESI wages but not PF wages.
- Comp off is claimed by the employee from self-service for a weekly off or holiday they worked. A full shift earns a day and half a shift earns half a day, checked against their shift, the holiday calendar and attendance. The manager or HR approves, and unused comp off lapses on its expiry date.
Decide which one you use for which group and write it down. Mixing the two for the same person invites disputes.
As we understand it, overtime and working-hour limits are set by the factory, shops and establishments or transport laws that apply to you, and by state rules. The Labour Codes were reported as in force from 21 November 2025, with transition details settling. Check what applies to your drivers and warehouse staff before fixing your policy.
Trip expenses and advances
Field teams spend money: fuel, tolls, parking, food, a replacement tyre. Handling this on loose receipts creates delay and doubt.
Claims. A policy per category sets a limit per claim, day, month, trip or night, or a rate per kilometre for fuel. GST can be captured, and a receipt is required above a threshold you set. Employees submit from self-service with receipts as PDF, PNG, JPG or WebP up to 10 MB. Future dates, dates before joining and duplicates with the same category, date and amount are blocked. The manager approves, then finance where the policy needs it, and nobody approves their own claim. Approved claims join the next payroll and add to net pay and the bank file, but not to gross, PF, ESI or TDS.
That tax treatment rests on the claims being actual business expenses backed by bills. A flat allowance with no bills belongs in the salary structure instead. If in doubt, ask your advisor.
Advances. Drivers and crew often need money before payday. A loan or advance record sets the amount and instalments, with optional interest on the reducing balance. Each instalment is deducted when payroll is calculated. Whatever is owed when someone leaves comes off their full and final settlement. Employees can request advances from self-service, within company limits you set as a share of monthly gross.
Minimum wages and salary templates
Drivers, loaders and helpers are often in scheduled employments with state minimum wages by skill category. Set a category per employee, let payroll flag anyone below the limit, and use the Minimum wage check report to see the shortfall. Create named salary templates for each group so that a helper and a branch manager do not share one structure by accident. We do not quote minimum wage figures, since they change and differ by state, so check your state notification. See our note on minimum wages for payroll teams.
A monthly rhythm
- Daily: staff punch in and out. Supervisors scan the Today view for flagged punches and missing check-outs.
- Weekly: approve attendance corrections and comp off requests, and plan next week’s roster.
- During the month: claims with receipts go to the manager and finance. Advance requests are approved and paid out.
- Cut-off: clear pending corrections, because payroll approval is blocked while they are open, and check the minimum wage report.
- Payroll days: run the seven-step wizard, edit overtime to approved hours, review exceptions against last month, and have a second person approve and lock. Publish payslips, then export the bank file.
- After payroll: pay PF and ESI by the 15th of the next month, TDS by the 7th, and Professional Tax by the state’s date. Record each challan.
For the month-end detail, see the payroll month-end close checklist.
Statutory notes
As we understand it, PF is 12% from the employee and 12% from the employer on PF wages (basic plus dearness allowance), with a Rs 15,000 ceiling until 16 September 2026 and contribution on higher wages by agreement. ESI is 0.75% from the employee and 3.25% from the employer on gross wages for employees earning up to Rs 21,000 a month. The Government’s press release of 16 Sep 2026 (PIB release ID 2310973) raises the wage ceiling for mandatory EPFO coverage to Rs 25,000 from 17 September 2026. EPFO’s implementing circular is awaited, so check current EPFO circulars and confirm how your payroll is configured. Professional Tax is a state levy and Saralix has tables for seven states, with LWF for Gujarat and Maharashtra. Other states show a payslip warning. Verify all of this against current rules.
Limits to know
- Saralix does not run payroll for contractors, gig delivery partners or drivers supplied by a vehicle owner. It covers your own employees.
- It does not track vehicles, routes or trip sheets.
- Per-trip or per-kilometre pay is not computed automatically. Add such amounts as one-time earnings in review.
- Offline punches skip the network check.
Pricing
A field or logistics team of 11 to 100 employees pays Rs 99 per employee per month plus GST on the Business plan, applied to all employees once above 10. A team of up to 10 with one admin can use the free plan, and above 100 is Enterprise by contract. See pricing, look at the attendance and leave features, or book a demo to see the punch flow on a phone.



