HR / HCM integrations
Connect governed workforce records with HR operations.
Explore how approved time, attendance and exception records can support HR/HCM workflows while ownership, permissions and receiving-system decisions remain clear.
Specific HR/HCM connections depend on deployment and approval.
What happens to your HR data?
Illustrative fields
TEMVERIS governed record
Approved- Approved hoursTravels
- Approval stateTravels
- Exception reason (classified)Travels
- Record versionTravels
- Reviewer notes (free text)Never public
Your HR / HCM system
System of record- Employee master recordStays in HR
- Job & organizationStays in HR
- Leave balancesStays in HR
- Employment statusStays in HR
- Employee link keyNever public
Approved time context travels one way. HR/HCM keeps its master data and makes its own decisions.
Each system keeps
its decision authority.
Approved attendance never becomes HR master data by default. One-way, non-overwriting handoffs are the starting point.
Governed workforce record
Approved time, attendance, exceptions and their history.
Employee master
Identity, job, organization, leave and employment status.
Pay processing
Calculation, deductions and payment.
Review authority
Configured approval for assigned teams.
From approved work to
reviewed HR handoff.
Capture → Review → Approve → Map → Deliver → Reconcile. Reconciliation is confirmed by the HR system, not assumed.
Capture
Approved source event
Review
Context and exceptions
Approve
Configured authority
Map
Approved mapping version
Deliver
Idempotent batch
Reconcile
HR/HCM confirms
Evaluate suitable HR
workflows without
assuming a live connection.
Examples are illustrative; no HR functions are invented or implied.
Attendance context
Approved attendance as context for HR review — not a disciplinary finding.
Exception follow-up
Classified exceptions routed to the right HR owner.
Leave-adjacent coordination
Context alongside leave processes; balances stay owned by HR.
Record evidence
Versioned history when HR needs to understand a decision.
Integration methods
vary by deployment.
No named HRIS is listed until it appears in a signed, supported-connector registry.
Core HRIS
Employee master and organization structure.
HCM suites
HR, talent and workforce modules.
Absence & leave
Leave processes and balances.
Workforce management
Scheduling and time-related HR workflows.
Know what travels and
what remains authoritative.
| FIELD | AUTHORITY | RULE |
|---|---|---|
| record_version | TEMVERIS | Immutable revision for corrections |
| event_period | TEMVERIS | Local period with time zone |
| approval_state | TEMVERIS | Not conflated with downstream status |
| exception_reason | TEMVERIS | Classified only — no sensitive free text |
| employment_scope | HR / HCM | Employer-approved purpose only |
| mapping_version | Integration owner | Environment-scoped schema control |
| target_ack_state | HR / HCM integration | Transport result — not "applied" |
| target_apply_state | HR / HCM | Only if the target supplies evidence |
Illustrative data dictionary; exact fields require approved purpose and market mapping.
An unresolved identity
must never create
a confirmed match.
Employee link keys are pseudonymous and never appear in public pages or analytics.
Sent is not received.
Received is not applied.
Each state is shown independently. “Applied” appears only when the HR system supplies that evidence.
Corrections preserve what changed and why.
Supersession, late changes, duplicate protection and rollback — never a silent rewrite.
- 1
VERSION 1
Approved and delivered
- 2
LATE CHANGE
Correction requested with reason
- 3
VERSION 2
Supersedes v1 — lineage kept
- 4
DUPLICATE CHECK
Batch ID blocks a second apply
- 5
REPLAY
Off by default; audited when enabled
Permissions follow purpose and least privilege.
Purpose limitation
Each role sees only what its purpose needs.
Least privilege
Integration admins see health — not HR records.
Encryption
Confirmed by the security owner per deployment.
Audit
Every mapping change and delivery is referenced.
Implementation begins
with verified readiness.
A reading aid only — nothing is saved.
Accountability without invasive monitoring.
HR receives governed records — never surveillance data.
Included
Governed- Approved time and attendance
- Schedules
- Approvals and exceptions
- Record history
Excluded
Never- Screenshots or screen recording
- Keystroke capture
- Continuous behavioral surveillance
- Unverified compliance badges
Frequently
asked questions
about HR/HCM
integrations.
Discuss your deployment requirements.
Bring your HR system owner and approval model. There's no test connection on this website.