KeyPay connector for construction payroll
KeyPay is a payroll platform used to manage employee pay runs, timesheets, leave, and employment agreements. Demiton integrates with KeyPay to retrieve payroll records and reconcile labour costs against field data from Assignar, and to support workforce lifecycle workflows.
Authentication: API key
System type: KEYPAY
API reference: KeyPay API
See your KeyPay payroll data in Claude — book a 30-minute call.
Supported resources
Section titled “Supported resources”| Resource | FETCH | PUSH |
|---|---|---|
employees | ✓ Yes | ✓ Yes |
payruns | ✓ Yes | — No |
timesheets | ✓ Yes | ✓ Yes |
leaverequests | ✓ Yes | ✓ Yes |
locations | ✓ Yes | — No |
paycategories | ✓ Yes | — No |
leavecategories | ✓ Yes | — No |
deductioncategories | ✓ Yes | — No |
payschedules | ✓ Yes | — No |
payrateschedules | ✓ Yes | — No |
employmentagreements | ✓ Yes | — No |
qualifications | ✓ Yes | — No |
Business | ✓ Yes | — No |
Pagination is handled automatically (100 records per page). All resources are scoped to your KeyPay business ID.
Registers this connector fills
KeyPay keeps 12 registers current in Civil Memory , with 8 mapped to source fields. Each name is the record you ask for, not the system it came from - ask for it in Studio or from your own AI client.
| Register | What it holds | Fields from KeyPay |
|---|---|---|
Leave category listleave_category_list | Leave types defined in your payroll and operational systems. | 27 of 33 |
Pay categoriespay_categories | Pay category definitions, with rates and award mappings. | 20 of 24 |
Legal entitieslegal_entities | The operating companies in your group: the root every worker, project and cost code belongs to. | 13 of 20 |
Payroll runpayroll_run | Completed pay runs with gross and net totals. | 7 of 16 |
Project listproject_list | Active and completed projects from your operational and ERP systems. | 5 of 18 |
Employee contact detailemployee_contact_detail | Employee contact and emergency-contact details from payroll. Readable only by roles permitted to see personal information. | 4 of 13 |
Leave balanceleave_balance | Current leave balances per employee and leave category. | 2 of 9 |
Timesheet entrytimesheet_entry | Timesheet submissions, with hours by date and pay category. | 1 of 12 |
Employee listemployee_list | Employees registered in your payroll system. | Fills all of 21 |
Leave requestleave_request | Leave requests and their approval status. | Fills all of 14 |
Project detailsproject_details | Details of active and completed projects from your operational and ERP systems. | Fills all of 11 |
User listuser_list | Users in your identity directory and operational systems. | Fills all of 13 |
The full field list, requiredness and an example record for any register are on its published contract. Where more than one system fills a register, the register is the same shape either way.
Integration model
Section titled “Integration model”Records are retrieved and normalised into PayrollRecord business objects with fields: employee, period, hours, gross cost. Worker identities are resolved across systems using a stable employee ID as the cross-system join key.
Labour reconciliation
Section titled “Labour reconciliation”The primary use case is reconciling payroll totals against field system data:
- Hours recorded in Assignar are compared against payroll hours
- Discrepancies are surfaced as variance records for review
- Simulation is not on by default; it is enabled per run, and production writes are queued for admin approval
Workforce mirroring
Section titled “Workforce mirroring”Demiton supports KeyPay→Assignar employee mirroring as part of workforce lifecycle workflows. When an employee is added or updated in KeyPay, the record can be propagated to Assignar - maintaining a consistent worker identity across payroll and field systems without manual data entry. Mirroring runs through the Workflow Runtime; simulation is not enabled by default. It is enabled per run, and production writes are queued for admin approval.
Connection setup
Section titled “Connection setup”Required values:
- API Key - a KeyPay API key with access to your business
- Business ID - the KeyPay business the connector is scoped to
Security
Section titled “Security”Access type: Read and governed write
Demiton reads the full range of payroll entities from KeyPay. Write operations - creating or updating employee records, timesheets, and leave requests - occur only through governed workforce lifecycle workflows with explicit approval gates: simulation is not on by default, it is enabled per run, and production writes are queued for admin approval.
Permissions required: KeyPay API key with access to your business. Use a dedicated API user for Demiton. Grant the minimum access needed - for reconciliation-only workflows, read access to employees, pay runs, and timesheets is sufficient.
Data sensitivity: Payroll data is the most sensitive data domain in Demiton. Access is restricted to payroll administrators and executives by default. Project Managers see aggregated labour cost totals for their projects but never individual pay records or rates. See the Security Overview for the full payroll domain access model.
Next steps
Section titled “Next steps”- Connecting a System - step-by-step wizard for setting up the connector
- Assignar - the reconciliation partner: Assignar hours vs KeyPay payroll hours
- Business Central - full cost stack when ERP, field ops, and payroll are all connected
- Connect your operation - talk to us about scoping a Connected deployment
Frequently asked questions
- What does the Demiton KeyPay connector do?
- The Demiton KeyPay connector reads payroll records (pay runs, timesheets, leave requests, employees, pay schedules, employment agreements) and reconciles labour costs against field data from Assignar. It also supports workforce mirroring - when an employee is updated in KeyPay, the record propagates to Assignar, keeping worker identity consistent across payroll and field systems.
- Who can see payroll data in Demiton?
- Payroll data is the most sensitive domain in Demiton. By default, access is restricted to payroll administrators and executives. Project Managers see aggregated labour cost totals for their projects but never individual pay records or rates. Access is enforced by Demiton's role-based access model, which maps to Entra ID group memberships.
- What tier is required for the KeyPay connector?
- The KeyPay connector requires the Connected tier (AU$50,000/year). It uses an API key scoped to your KeyPay business. A dedicated API user is recommended. For reconciliation-only workflows, read access to employees, pay runs, and timesheets is sufficient.
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.