ubique24 connectors, a public API, and Merge for the rest
Ubique should be the system of record for employment, not a second place to type things. New hires flow in from your HRIS or ATS, payroll journals flow out to your accounting system, and your identity provider decides who can log in.
All connectors are included in every plan. Set-up takes minutes for most; your account manager helps with HRIS mappings.
By category
Native connectors built and maintained by Ubique. Each one says what it syncs and in which direction.
HRIS Two-way
Starters, leavers, salary changes, job titles and managers sync from your HRIS. Ubique writes back employment status, payslip availability and leave balances.
Finance Ubique → Finance
Payroll journals by entity, cost centre and account; contractor invoices and payment runs; Ubique invoices. Mapped to your chart of accounts once, then pushed after each run.
Identity and SSO Login and provisioning
Single sign-on with SAML 2.0 or OIDC. SCIM provisioning creates and deactivates Ubique users when you add or remove them from your directory. MFA remains mandatory in Ubique regardless of your IdP policy.
Communication Notifications
Approval requests, compliance updates and onboarding reminders where your managers already are. Approve a leave request from the message without opening the dashboard.
ATS ATS → Ubique
When a candidate reaches "offer accepted", Ubique creates the hire with name, role, salary, country and start date, and shows the full employer cost before you send the contract.
Automation and work management Events
Every Ubique event (hire created, contract signed, payroll approved, leave requested) can trigger a workflow elsewhere, with no code.
Everything in the dashboard is in the API
REST, JSON, OAuth 2.0 client credentials, with scoped API keys per integration. Webhooks for every event, signed so you can verify them. Rate limits that a 2,000-employee customer does not hit.
- People: create and update employees and contractors, read employment status and cost
- Contracts: generate, send for signature, retrieve signed PDFs
- Payroll: read runs, line items and journals; submit variables and expenses
- Leave: read balances, create and approve requests
- Documents: upload to and read from the vault, with the same permissions as the UI
- Webhooks: hire.created, contract.signed, payroll.approved, leave.requested and 30 others
Generic connectors via Merge
If your HRIS, ATS or accounting system is not in the list above, Ubique connects through Merge's unified API. This covers well over a hundred further tools. Field mapping is slightly less rich than a native connector, and we will tell you which fields are affected.
Sandbox
Every account gets a sandbox with test countries and test employees. Build and test your integration there before pointing it at production.
Who builds integrations with it
Finance teams pulling payroll into a data warehouse, IT teams automating equipment orders on hire.created, and People teams syncing a custom HRIS. Typical build time for a one-way sync is a day or two.
Integration questions
Which system should be the source of truth?
For most customers, the HRIS holds the person and Ubique holds the employment: contract, payroll, compliance. New hires are created in the HRIS or the ATS and flow into Ubique. Changes to pay are made in Ubique, because Ubique validates them against local law, and written back. We help you set the direction field by field.
Do connectors cost extra?
No. Every connector, the API and Merge are included in all plans. Merge itself may need its own agreement for very high volumes; your account manager will tell you if that applies.
Can we use the API to build our own reports?
Yes, and many finance teams do while the custom report builder is on the roadmap. The payroll and people endpoints return everything the CSV exports contain, with pagination and filters.
Connect Ubique to the tools you already run
Tell us your HRIS, ATS and accounting system. We show you the sync on the call.