Learn More

Validite System Architecture Diagram

Comprehensive overview of the Validite Time Attendance Payroll System architecture

Clock In/Out A

An Employee Clocks In/Out via

   - Validite Wall-mounted Clock

   - Validite Desktop solution (small companies)

   - Companies own Clocks


The Clock In/Out transaction is stored on the Branch LAN Server in a SQL Express Database


NB.The Branch LAN Server acts as a Web Server with all data being stored here

ie Employee data / Fingerprint Templates / Rfid Tag Numbers etc

Clock Icon

Fingerprint and RFID Clocks

Time-and-Attendance Icon

Branch LAN Server acts as a Web Server

Branch LAN Server B

Each Branch LAN Server acts as Self-Hosting Web Service with a SQL Express Database


The SQL Express Database stores all relevant data for Employees which is downloaded from or uploaded to the Validite Cloud-based Server Database


The Clock In/Out transaction is uploaded to the Validite Cloud-based Server via a batch run or via a timer based service

Validite Cloud-Based Server C

The Validite Cloud-Based server is the central point of our solution


All Setup data is Captured here and data is uploaded / downloaded to each individual Company's Branch LAN Server from here


Each Company has its own Cloud Database allowing for its own Backups / Restores


The Validite Cloud-Based Server allows data from different branches to be centrally controlled and distributed

Clock Icon

Validite Cloud-Based Server

Time-and-Attendance Icon

Time Attendance / Payroll

Time Attendance / Payroll D

Once all Employee Clock In/Out errors have been corrected, these times are rolled up into Normal Time and Over Time buckets


These Normal Time and Over Time buckets for each employee are then run through the payroll system resulting in an Employee Payslip


Employee Payslips can then be emailed to each employee