Spirit TSMS — Time Stamp Management Solution
Connect employee time-recording terminals to SAP HCM automatically — collect, map, and validate every clock event from any terminal brand, and deliver complete attendance data into SAP HR Time Management without manual effort.
Request a Demo →
What is Spirit TSMS?
Organizations running SAP HCM depend on accurate attendance data for payroll, scheduling, and compliance. But that data is physically captured by hardware terminals from different manufacturers — each producing files in its own proprietary format. Without a dedicated integration layer, collecting, translating, and validating that data before every payroll run falls on IT and HR teams. Spirit TSMS eliminates that burden entirely: it connects to your time-recording terminals, applies configurable mapping rules per terminal brand, validates every record against SAP HR master data, and delivers attendance records into SAP using the standard IDoc interface — running silently as a Windows Service around the clock.
Built for any organization running SAP HCM
Any organization running SAP HCM with positive time recording and physical time-recording terminals benefits from TSMS — regardless of sector or employee count. Used across manufacturing, wholesale distribution, retail, consumer goods, pharmaceutical, engineering & construction, professional services, and automotive organizations.
The problem with manual time & attendance integration
Bridging the gap between time-recording hardware and SAP HR manually creates errors, delays, and payroll risk every pay cycle.
- Your time-recording terminals have no built-in connection to SAP HR — meaning every clock-in and clock-out must be manually exported, reformatted, and uploaded into SAP before each payroll run.
- Different terminal manufacturers produce attendance files in completely different formats — and SAP HR only accepts data in its own strict structure. Bridging that gap without a dedicated integration means custom development, fragile scripts, or error-prone manual re-entry.
- There is no reliable way to know which attendance records reached SAP, which failed validation, and which need to be resubmitted — leaving HR and payroll teams to investigate discrepancies manually every pay period.
- Building a custom integration between time-recording terminals and SAP HR means months of development effort, ongoing maintenance, and the constant risk of breaking when SAP or terminal firmware is updated.
- When terminal records fail SAP validation — because an employee number is incorrect, a cost assignment has changed, or an event type is unmapped — there is no automated way to capture, review, and reprocess those records without restarting the upload.
- Managing attendance data from multiple sites and terminal brands as separate manual processes creates reconciliation gaps and compliance risks — particularly in multi-location organizations where payroll accuracy depends on complete data from every site.
Spirit TSMS takes care of the entire journey — from collecting raw terminal files at each site to delivering validated, structured attendance records directly into SAP HR — so your HR and payroll teams never have to touch it.
Key Features
Supports Multiple Terminal Brands
Works with Suprema, ZKTeco, Handpunch, and other terminal types simultaneously — no hardware replacement or vendor lock-in required.
Configurable Field Mapping Per Terminal
Each terminal's proprietary file format is mapped field-by-field to SAP's time event structure, including date and time format conversion and event code translation — configured once and applied automatically.
SAP HCM Standard IDoc Integration
Delivers attendance records to SAP HR using the standard HRCC1UPTEVEN01 IDoc interface — no custom ABAP development required on the SAP side.
Pre-Submission Validation Against SAP Master Data
Every record is validated against live SAP HR master data for employee existence, valid event types, absence reasons, and cost assignments before posting — preventing rejected records from reaching payroll.
Time Event Type Translation
Maps terminal button codes to SAP time event types based on each employee's assigned group — supporting scenarios such as overtime entry, shift differentials, and visitor access.
Automated Error Capture and Reprocessing
Failed records are captured with full details, categorized by failure phase (mapping, validation, or posting), and can be reprocessed automatically on a schedule without restarting the integration.
Real-Time Monitoring and Trace Console
The built-in admin console provides a live trace log, error log, and SAP connection status — giving IT and HR teams full visibility into what is being processed and what requires attention.
Multi-Site Terminal Support
Handles multiple terminal sources across different locations simultaneously, making it suitable for organizations with distributed sites or multiple access-control zones under a single SAP HR system.
Business Outcomes
No hardware changes, no manual exports
TSMS connects to the terminals you already have and collects attendance files automatically — no changes to existing hardware or manual file handling workflows.
Payroll runs on complete, validated data every cycle
Attendance records flow from terminals into SAP HR automatically before each payroll run, eliminating missed entries and last-minute corrections.
One integration handles every terminal brand
Whether you have Suprema on one floor and ZKTeco on another, TSMS normalizes everything into SAP's format through a single, centrally managed system.
Failed records are caught and reprocessed automatically
Every validation failure is logged with its cause and can be retried on a configured schedule — so no attendance record is permanently lost.
No custom ABAP or ongoing SAP maintenance required
The standard IDoc interface means nothing bespoke to build or maintain in SAP — reducing both implementation cost and long-term IT support burden.
How it connects to SAP
Spirit TSMS registers with the SAP Gateway as a dedicated RFC server, making it a native participant in SAP's integration framework. SAP triggers attendance data collection by sending a standard IDoc request; TSMS collects, maps, validates, and posts the records back to SAP — all without manual intervention or custom ABAP. The bidirectional IDoc communication ensures TSMS always works with current SAP master data and SAP always receives complete, accurate attendance records.
- SAP products required
- SAP ERP (ECC 6.0 or S/4HANA) with HCM and Time Management (PT) activated
- SAP modules integrated
- Human Capital Management (HCM) — Time Management (PT)
- Middleware
- TSMS is the middleware — installs as a Windows Service, no third-party middleware required
- Deployment model
- On-premises Windows Service + desktop admin console
- Offline capability
- Partial — terminal files queue automatically if SAP is temporarily unavailable, and submission resumes once connectivity is restored
- Availability
- Egypt
- Language support
- Arabic and English
Frequently Asked Questions
Which time-recording terminal brands does TSMS support?+
TSMS works with Suprema, ZKTeco, Handpunch, and other terminal types simultaneously — so there's no need to replace existing hardware or standardize on a single vendor.
Do we need custom ABAP development in SAP to use TSMS?+
No — TSMS delivers attendance records using SAP's standard HRCC1UPTEVEN01 IDoc interface, so no custom ABAP development is required on the SAP side.
What happens if an attendance record fails validation?+
Failed records are automatically captured with full details, categorized by failure phase (mapping, validation, or posting), and can be reprocessed automatically on a schedule — no manual restart of the integration required.
Can TSMS handle multiple office or factory locations at once?+
Yes — TSMS supports multiple terminal sources across different locations simultaneously, making it suitable for organizations with distributed sites or multiple access-control zones under a single SAP HR system.
What happens if SAP is temporarily unavailable?+
Terminal files continue to be collected and queued locally, and submission to SAP resumes automatically once the connection is restored — no data is lost during downtime.
Does TSMS require replacing our existing time-recording hardware?+
No — TSMS connects to the terminals you already have through configurable field mapping, so there's no hardware replacement or vendor lock-in required.
How does TSMS keep up with changes to SAP HR master data?+
SAP sends time event group master data to TSMS via a standard IDoc (HRCC1DNTEVGR01), keeping the mapping engine automatically current without manual updates.
Which industries commonly use Spirit TSMS?+
Any organization running SAP HCM with physical time-recording terminals benefits, regardless of sector — common users span manufacturing, wholesale distribution, retail, consumer goods, pharmaceutical, engineering & construction, professional services, and automotive.
Bring Spirit TSMS into your SAP HR landscape.
Book a free working session with a Spirit SAP expert. We'll map your goals to a concrete next step — no slide decks, no obligation.