Your PaySpace Data, Analysed Automatically
Appsentia connects to PaySpace using your API credentials. A nightly sync imports new employees and leave transactions, and risk scores are recalculated after it.
PaySpace integration is available on the Professional and Enterprise plans. It cannot be connected during the free trial.
How the Integration Works
You enter your PaySpace API credentials once in Appsentia. No custom development or spreadsheet exports are needed after that.
Enter Your PaySpace API Credentials
In Appsentia Settings, enter your PaySpace API client ID and client secret, choose the staging or production environment, and choose whether to sync employees, leave transactions or both. The client secret is encrypted with AES-256-GCM before it is stored.
Standard Fields Are Mapped for You
Appsentia reads the standard PaySpace fields: employee number, name, department, start and termination dates, leave type, and leave start and end dates. Leave types such as Sick Leave are recognised as sick leave. Pay cycles and paydays are not read from PaySpace; you set them in your company settings in Appsentia.
Run the Initial Full Sync
Start the first full sync from Settings. Appsentia pulls all employees and all historical leave applications from your PaySpace environment. The time it takes depends on the size of your data. Each sync is recorded in a sync log you can review.
Nightly Sync Runs Automatically
Every night, Appsentia syncs your PaySpace data. New employees are added, new leave transactions are imported and updated records are reconciled. Your dashboard shows the previous day's data in the morning.
Risk Scores and Alerts Update After the Sync
After the sync, every employee's risk score is recalculated. An alert appears on the dashboard when an employee moves into the high risk band, rises by 20 points or more, or moves from low to medium. High-risk alerts are also emailed to your company contact email address.
Security First
Your PaySpace API credentials give access to employee and payroll data. This is how Appsentia handles them.
AES-256-GCM Encryption
Credentials are encrypted using AES-256-GCM before any database write. The encryption key is not stored alongside the credential. Plain-text credentials are never written to logs, responses, or database records.
Minimal Credential Exposure
Your PaySpace API credentials are decrypted only at the moment of an active sync operation, held in memory for the duration of the request, and released immediately afterwards. There is no persistent decrypted credential state.
Audit and Sync Logs
Connecting, changing, deleting and manually syncing an integration are recorded in the audit log with the user and time. Every sync, including the nightly sync, is recorded in a sync log your admin users can review.
What the PaySpace Integration Gives You
Without the integration, someone has to export and upload leave data. With it, the data is updated every night.
Leave data updated nightly
No month-end data requests to payroll. Every morning, your leave data includes the previous day's PaySpace activity: new employees, new leave transactions and updated records.
Accurate employee headcount for billing
Appsentia's billing is based on active employee count. The PaySpace sync updates this count as employees join or leave, so you do not maintain it by hand.
Payday pattern detection
Set your pay cycles (monthly, fortnightly or weekly) and paydays once in company settings in Appsentia. Payroll data is not read from PaySpace. Appsentia then flags sick leave on or after payday in the leave it syncs.
Historical backfill for pattern analysis
The initial full sync imports historical leave data, not just current records. This means pattern analysis starts with meaningful history from day one, rather than requiring months of data accumulation before the analytics become actionable.
Not on PaySpace?
Appsentia supports CSV and Excel upload for any leave export format, with an intelligent column-mapping wizard that handles inconsistently formatted files. A manual upload takes five to ten minutes. Most South African HRIS systems can export leave data in a format Appsentia can ingest on the first attempt.