SalesTOSLet’s talk
ERP & Accounting · ERPNextAvailable

Connect employee identity and attendance events.

Working ERPNext workflows cover employee synchronisation and configured employee check-in exchange. That verified workforce scope does not establish a ready-made accounting, stock or payroll connector.

Discuss This Integration View Data Scope
ERPNext Scope map · supported and assessed paths
ERPNextConfigured service
01
Employee recordsERPNext → SalesTOS
02
Reporting managerERPNext → SalesTOS
03
IN / OUT eventsSalesTOS → ERPNext
SalesTOSTeam identity and mapping

Record ownership and direction are defined below. No universal two-way sync is implied.

The operational need

Why connect these systems?

Employee identifiers must match before attendance can be exchanged.

Reporting relationships should reflect an agreed employee master.

A failed check-in transfer needs a traceable status rather than a silent gap.

Direction, ownership, prerequisites

What data can be exchanged?

Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.

ERPNext data scope
Record or objectDirectionSystem of recordPurposeAvailability / prerequisites
Employee recordsERPNext → SalesTOSERPNextTeam identity and mappingAvailable: configured employee sync
Reporting managerERPNext → SalesTOSERPNextReporting relationship mappingAvailable: matched employee identifiers
IN / OUT eventsSalesTOS → ERPNextSalesTOS for captured eventEmployee Checkin exchangeAvailable: configured attendance workflow
Check-in historyERPNext → SalesTOSERPNextConfigured attendance reviewAvailable within supported history workflow
Invoices or payrollScope to assessERPNextPotential future data contextNot part of verified employee/check-in scope
Connection design

How the connection works

The adapter uses authorised Frappe API access. Employees are mapped before attendance events are queued. Supported event processing records job state and uses idempotency keys. Confirm the enabled workflow and ERPNext HR configuration in a test environment.

Illustrative working scenario

From system context to a useful next action.

A mapped employee records an IN event in SalesTOS. The configured job sends the check-in to ERPNext and records the result. HR applies its shift and attendance rules in ERPNext.

What happens to writeback?

A check-in is not a payroll calculation, approved paid day or financial posting. Those decisions remain with the configured HR process.

Before implementation

Setup requirements

  1. ERPNext/Frappe versions and enabled HR configuration
  2. Authorised API access and Employee Checkin permissions
  3. Employee identifiers and reporting-manager mapping
  4. Shift rules, event timestamps and a pilot employee group

Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.

Operating the agreed scope

Reliability & access

The attendance workflow has job/error history, idempotency and audit records. Retry policy differs between reads and writes. Failed employee matches require correction before resubmission; these controls should not be extrapolated to unimplemented ERPNext objects.

A clearer scope starts here

Questions, answered.

ERPNext integration

Does this calculate salary?

No. The verified scope exchanges employee and check-in records, not payroll.

Why must employees be mapped first?

The destination needs a valid employee identifier to attach a check-in to the right person.

Does an IN event equal attendance approval?

No. Shift rules and HR processing determine the attendance outcome.

Are ERPNext invoices supported too?

Not by the verified workforce workflow described here. Financial objects need separate assessment.

What should we prepare for a ERPNext discussion?

ERPNext/Frappe versions and enabled HR configuration; Authorised API access and Employee Checkin permissions; Employee identifiers and reporting-manager mapping; Shift rules, event timestamps and a pilot employee group. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.

How is ERPNext integration scope confirmed?

Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. A check-in is not a payroll calculation, approved paid day or financial posting. Those decisions remain with the configured HR process.

Explore the adjacent workflow

Related integrations

View all integrations →

Your systems. A defined scope.

Discuss ERPNext with SalesTOS.

Bring your business workflow and current setup. We’ll use them to assess the right data scope.

Discuss This Integration