HRIS & Payroll Integration
Connect your payroll platform to obligation-first salary routing
Integration Modes
Post-Payroll (File Ingestion)
Payroll runs normally through your existing system. tPay365 ingests the BACS or CSV output, applies obligation logic, and routes funds to vaults and the employee's clean paycheck.
Best for: Systems that already export BACS Standard 18 or CSV payroll files
Pre-Payroll (API)
tPay365 provides deduction instructions before payroll is finalised. Your system applies them at source, meaning employees receive their clean paycheck directly from payroll — no post-processing step.
Best for: Modern HRIS platforms with pre-payroll hook capability
Continuous Sync (Webhook)
Real-time employee lifecycle events (new hire, termination, pay change, role change) sync to tPay365 automatically via webhooks. Combined with Mode A or B for full integration.
Best for: Enterprise platforms with event-driven architecture
Data Requirements
| Field | Mode A | Mode B | Mode C |
|---|---|---|---|
| employee_id | |||
| employee_email | |||
| employment_status | |||
| gross_pay | — | ||
| net_pay | — | — | |
| deductions_breakdown | — | ||
| pay_period | — | ||
| pay_date | — |
Double-Deduction Prevention
tPay365's delta engine detects statutory deductions already applied by your payroll system (tax, NI, pension, student loan) and excludes them from obligation routing. This prevents any deduction from being applied twice.
Upstream Deductions
- Income Tax
- National Insurance
- Pension
- Student Loan
Delta Engine
Compares upstream deductions against obligation list. Excludes anything already applied.
tPay365 Additions
- Vault Allocations
- Safety Buffer
- Clean Paycheck
Supported Platforms
| Platform | Integration | Status |
|---|---|---|
| BACS Standard 18 | File-based | Supported |
| CSV Export | File-based | Supported |
| API Webhook | API | Supported |
| Workday | Direct | Target 2026 |
| ADP | Direct | Target 2026 |
| Xero Payroll | Direct | Target 2026 |
| Sage HR | Direct | Target 2027 |
| Merge.dev | Middleware | Target 2026 |
Sample Integration Sequence
Employer connects HRIS
The employer authorises the connection between their HRIS or payroll platform and tPay365 via OAuth or API key.
tPay365 syncs employee roster
Employee records are synced from the HRIS. PII is encrypted and stored in the vault; Server A receives only hashed references.
vIBANs provisioned (inactive)
Virtual IBANs are created for each employee via the banking partner API but remain inactive until the employee activates their account.
Employees activate accounts
Each employee receives an invite, sets up their obligation profile, and activates their vIBAN. The activation gate engine validates readiness.
Payroll routes through tPay365
On each pay run, salary is routed through tPay365. Obligations are ring-fenced into vaults, and the clean paycheck is released to the employee.