ERPNext
AvailableConnect employee identity and attendance events.
Explore data & scopeAssess employee and attendance requirements for your HR system. SalesTOS has a specific ERPNext employee/check-in workflow; that does not establish general payroll connectors or salary processing.
Record ownership and direction are defined below. No universal two-way sync is implied.
Employee codes must remain consistent across team administration.
Reporting-manager changes need a defined master.
Raw check-ins are not the same as approved payroll attendance.
Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.
| Record or object | Direction | System of record | Purpose | Availability / prerequisites |
|---|---|---|---|---|
| Employee identities | HR system → SalesTOS | HR system | Team administration | Assessment; ERPNext has a verified scoped workflow |
| Reporting relationships | HR system → SalesTOS | Agreed employee master | Manager visibility | Assessment: role and manager mapping |
| Check-in events | SalesTOS → HR system | SalesTOS for captured event | Attendance input | ERPNext configured workflow available; others assessed |
| Approved attendance summaries | Scope to assess | HR approval process | Potential payroll input | Custom scope; raw location is not approval |
| Salary calculations | No supported exchange claimed | Payroll system | Payroll processing | Not part of verified SalesTOS integration |
Begin with the HR product and the record required: employee, check-in or approved summary. ERPNext is a specific implemented path. Other interfaces or file handoffs require mapping and acceptance criteria.
A field employee records check-ins. An agreed HR workflow reviews exceptions and shift rules before any payroll use. The HR team remains responsible for the approved attendance result.
No salary, deduction, statutory calculation or payroll posting is implied by attendance visibility.
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Permissions, correction history and event deduplication must match the selected system. ERPNext-specific job controls should not be advertised as universal payroll integration controls.
No verified salary-processing integration is established here.
No. Location and check-ins are evidence for an authorised attendance process.
Configured ERPNext employee and check-in workflows have implementation evidence.
The exact format, approval status and enabled export workflow require assessment.
HR/payroll product and enabled interfaces; Employee codes and manager mapping; Shift, timezone and approval rules; HR owner, test data and authorised access. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.
Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. No salary, deduction, statutory calculation or payroll posting is implied by attendance visibility.
No matching questions. Clear your search or discuss your requirements with us.
Connect employee identity and attendance events.
Explore data & scopeStart with an approved template and a reviewable import.
Explore data & scopeDefine one useful interface between your system and field work.
Explore data & scopeBring your business workflow and current setup. We’ll use them to assess the right data scope.