Integrations & Automation

Connecting

Integrations → Accounting → Connect. You are redirected to the provider to authorise access. Only the scopes needed to read your chart of accounts and post journals are requested.

Syncing accounts

After connecting, sync the chart of accounts so the GL mapping screen offers real account names rather than free text.

Pushing a journal

Generate the journal from a finalised run and push it. The system records the resulting journal reference so you can trace payroll to the ledger.

Disconnecting

Disconnect at any time; tokens are deleted server-side. Tokens are never readable by application users — only the connection status and organisation name are visible in the interface.

Email

Transactional email is used for invitations, payslip notifications, approvals and system alerts. Bounces and unsubscribes are tracked, and suppressed addresses are flagged so you know why an employee is not receiving mail.

WhatsApp

Payslip links, leave decisions and reminders can be delivered by WhatsApp. Employees must have a valid mobile number captured in international format.

SMS

Bulk SMS delivery is available for employees without smartphones or data. Messages carry a secure link rather than the document itself.

Choosing channels

Set default delivery channels per company, and override per employee where needed.

Automated runs

For stable, salaried workforces you can schedule a run to be created and calculated automatically on a set day each period. The run is created in draft — it is never finalised without a human — so you still review before employees are paid.

Reminders

Automatic reminders for cut-off dates, unfinalised runs, EMP201 due dates and expiring contracts.

Automatic distribution

Once a run is finalised, payslips can be generated and delivered automatically on the pay date.

Safeguards

Automation respects approval workflows. If approval is required, the scheduled run stops at the approval step.

When to use it

Use the API when you need payroll data inside another system — a BI tool, an internal HR platform, or a custom employee app.

Authentication

API access uses scoped keys issued per company. Keys are shown once at creation; store them in your own secret manager. Requests are made over HTTPS with the key in the Authorization header.

Typical endpoints

Employees, payroll runs, payslips, leave balances and reports. Reads are the common case; writes are limited to clearly scoped operations such as creating employees or submitting timesheet lines.

Webhooks

Subscribe to events such as run finalised, payslip generated and leave approved, so your systems react instead of polling.

Good practice

Never embed an API key in a browser or mobile app. Call the API from your own server.