A build-to-order Frappe app that turns raw ERPNext attendance and check-in data into accurate timesheets and rule-based overtime slips (1.5x weekday, 2.0x holiday), then posts approved OT to payroll as Additional Salary. ECOSIRE builds, installs, and supports it for your v15/v16 site. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that turns raw ERPNext attendance and check-in data into accurate timesheets and rule-based overtime slips (1.5x weekday, 2.0x holiday), then posts approved OT to payroll as Additional Salary. ECOSIRE builds, installs, and supports it for your v15/v16 site.
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Factories and service firms running payroll on ERPNext keep hitting the same wall at month-end: attendance and Employee Checkin records capture when people clocked in and out, but nobody actually gets paid overtime from them automatically. ERPNext core has Timesheet and Additional Salary DocTypes, and the payroll engine will read salary components, but there is no native bridge that reads a day's check-in pairs, subtracts the standard shift, applies a weekday-vs-holiday multiplier, and produces an auditable OT figure. So teams fall back to spreadsheets — HR keys overtime hours by hand, supervisors argue over what counts as a holiday, and the numbers that hit the salary slip are impossible to trace back to the clock. On a 200-person factory floor that is both a payroll-accuracy risk and hours of avoidable admin every cycle.
Daily OT engine that rolls `Employee Checkin` pairs into worked hours and subtracts the assigned `Shift Type` window to isolate overtime
Configurable multiplier rules via a custom `Overtime Rule` DocType: 1.5x weekday, 2.0x holiday/rest-day, with your own thresholds and caps
Holiday and weekly-off resolution using the employee's ERPNext `Holiday List` and weekly-off to classify each OT hour
Automatic `Timesheet` generation from attendance with the correct `Activity Type`, billing/costing rate, and project link where required
Custom `Overtime Slip` DocType capturing source punches, computed hours, rate, and multiplier for a full audit trail
Frappe Workflow (Draft → Submitted → Approved/Rejected) with role-based transition permissions for supervisor and HR sign-off
We build a dedicated Frappe app (its own module, installed onto your bench) that closes that gap. A scheduler event and a hooks.py doc event on Employee Checkin/Attendance roll each employee's daily punches into worked hours, compare them against the assigned Shift Type and the standard working window, and split the excess into overtime buckets. A configurable rule engine — driven by a custom Overtime Rule DocType plus the ERPNext Holiday List and each employee's weekly-off — decides the multiplier: 1.5x for weekday overtime and 2.0x for work on holidays and rest days, with your own thresholds, rounding, and daily/weekly caps. Each computation is written to a custom Overtime Slip DocType and, where you want it, an auto-generated Timesheet with the right Activity Type and costing rate, so the same source data feeds both payroll and project costing.
Approvals and payroll posting are handled the ERPNext way. The Overtime Slip runs through a Frappe Workflow (Draft → Submitted → Approved/Rejected) with role-based permissions, and on approval a server script creates the matching Additional Salary record against the correct salary component and payroll period, so overtime flows into the next Salary Slip with no manual re-entry and a clean audit trail from clock-in to pay line. Client scripts surface a live OT preview on the form; whitelisted methods expose the calculations over the Frappe REST API so a kiosk, mobile app, or biometric integration can push check-ins and read back OT figures. Everything respects your role profiles, and the scheduler recalculation is idempotent so re-runs never double-count.
Because this is build-to-order, nothing is downloaded and dropped onto your production site blind. We start with a short scoping call to confirm your shift patterns, multiplier rules, holiday and rest-day logic, salary components, and which flows need timesheets versus OT-only. We then build the app against your exact ruleset, install and validate it on a staging copy of your ERPNext v15 or v16 site, run UAT with your HR and payroll teams on real attendance data, and only then cut over to production with a rollback plan in hand. Typical delivery is 2-4 weeks from confirmed scope, and you receive the full source and git repository so nothing is locked to us.
Runs monthly payroll on ERPNext for a large hourly workforce and needs overtime computed straight from the clock, not re-keyed from spreadsheets, with every pay line traceable back to check-in data.
Approves shift overtime for the floor and wants supervisor sign-off, holiday and rest-day rules, and OT cost visibility by department without chasing HR for numbers.
Bills client work from timesheets and pays technicians overtime; needs one source of attendance data to feed both project costing and the payroll `Additional Salary` line accurately.
Maintains the company's Frappe bench and wants a clean app with proper hooks, idempotent scheduler jobs, role permissions, and a git repo they can maintain and upgrade across v15/v16.
Achetez la licence sur ecosire.com et téléchargez le ZIP de l'application Overtime & Timesheet Automation for ERPNext depuis le tableau de bord de votre compte.
Extrayez le ZIP dans le dossier d'applications de votre banc ou exécutez « bench get-app » avec le chemin d'accès à l'application extraite.
Exécutez `bench --site SITE_NAME install-app APP_NAME` suivi de `bench migrate` pour installer Overtime & Timesheet Automation for ERPNext et appliquer son schéma.
Ouvrez les paramètres de licence ECOSIRE sur votre site et activez votre clé de licence. Nécessite les applications gratuites ecosire_connect et ecosire_license_client.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Overtime calculation | Auto 1.5x/2.0x from check-in data via rule engine | Possible but you design and build the whole engine | Fixed logic, often single flat multiplier | |
| Timesheet from attendance | Auto-generated with Activity Type and costing rate | Buildable at extra effort and cost | Rarely bundled with OT features | |
| Payroll posting | On-approval Additional Salary to correct component | You wire the workflow-to-payroll link yourself | May export values for manual entry | |
| Holiday & rest-day rules | Uses Holiday List + weekly-off, configurable caps | Depends on developer's implementation | Limited or hard-coded holiday handling | |
| Fit to your rules | Built to your exact shifts, thresholds, and caps | Fully custom but you carry full build risk | Configure within the vendor's fixed feature set | |
| Version support | Built and tested for your v15/v16 bench | Whatever you target and maintain | Vendor's supported versions, upgrade on their cycle | |
| Delivery & validation | 2-4 weeks, staging UAT + rollback plan | Timeline depends on your team's capacity | Instant install but no fit validation | |
| Ownership & support | Full source, git handover, post-go-live window | You own it and own all the maintenance | Vendor-locked, subscription support |
This is a build-to-order app, not an instant download. Typical delivery is 2-4 weeks from confirmed scope. After a short scoping call to lock your shift patterns, multiplier rules, and payroll components, we build against your exact requirements, validate on staging, run UAT, and then cut over to production.
A scheduler event and doc events on `Employee Checkin`/`Attendance` roll each day's punches into worked hours, subtract the assigned `Shift Type` window, and split the excess into OT buckets. A configurable `Overtime Rule` DocType applies 1.5x for weekday overtime and 2.0x for holidays and rest days, using the employee's `Holiday List` and weekly-off, with your own thresholds, rounding, and caps.
Yes. Each `Overtime Slip` runs through a Frappe Workflow with role-based approval. On approval, a server script posts an `Additional Salary` record to the correct salary component and payroll period, so the OT appears on the next Salary Slip with no manual re-entry and a clean audit trail from clock-in to pay line.
We build for Frappe/ERPNext v15 and v16. We confirm your exact bench version during scoping and build and test against a staging copy of your site so the app matches your environment.
Every engagement includes a post-go-live support window for defect fixes and configuration tweaks. Because you receive the full source and git repository, you can maintain it in-house, and we offer ongoing support or upgrade engagements for future ERPNext versions and rule changes on request.
Yes. The app exposes whitelisted methods over the Frappe REST API to push check-ins and read back OT figures, so biometric terminals, kiosks, or mobile apps can feed attendance and consume overtime data. Integration to a specific device is part of the scoped work.
Yes. Where you need it, the app auto-generates `Timesheet` records from attendance with the correct `Activity Type` and costing rate, so the same check-in data feeds both project costing and overtime pay. You decide during scoping which flows are OT-only and which also produce timesheets.
A build-to-order Frappe app that turns raw ERPNext attendance and check-in data into accurate timesheets and rule-based overtime slips (1.5x weekday, 2.0x holiday), then posts approved OT to payroll as Additional Salary. ECOSIRE builds, installs, and supports it for your v15/v16 site.