The problem it solves: Integrations quietly do one of the most important jobs in payroll: they carry employee data, master data and pay elements from your HCM into HR Blizz, and they carry the results back out to banks and authorities. It’s automation replacing a manual, error-prone task – and payroll is only ever as good as the data feeding it. Yet that flow used to be a black box. The old integration screen mixed unrelated things together – payroll period selections, outbound files, interface files – in one place that was hard to read. You couldn’t easily tell whether a file had arrived, whether it had passed validation, or whether an outbound submission had actually been accepted. Answering that often meant raising a ticket and waiting for someone with system access to read a log, sometimes after a deadline had already slipped.
What we built: A redesigned Integration view in the Payroll Admin Console that gives you control, visibility, accountability and history over every feed. It’s organised into two domains that behave identically – Operational (your everyday feeds) and Statutory (mandatory reporting) – and each has an Inbound tab (data coming in) and an Outbound tab (files going out). One table layout, one set of actions, one detail drawer across all four, so once you learn one you know them all. Every transmission shows a plain-language status, every integration shows a Live/Down health signal, and a diagnostic Status Log plus an AI-interpreted detail drawer let you see exactly what happened.
This is a control-and-visibility layer over the integrations you already run. The connections, parsers and compliance logic are unchanged – what’s new is that you can finally see every exchange and act on it yourself.
What this means for your team
Visibility
One screen for every feed, in and out, operational and statutory, each with a clear status and a Live/Down health signal.
Control
Decide what enters payroll and what leaves it: persist, reject, hold, retry, submit, or deliberately exclude a file so it isn’t sent.
Accountability
Diagnose without a ticket. The Status Log records every poll, trigger and validation; the drawer gives an AI-interpreted read of each response.
History
Every run, submit, persist, reject and re-trigger is logged, and corrections group as versions instead of scattering across the list.
No accidental sends
Clear eligibility rules and a confirmation before any bulk submission.
What flows through each domain
| Domain | Inbound (coming in) | Outbound (going out) |
|---|---|---|
| Operational | Employee details, master data and pay elements from your HCM/HRIS | Bank files sent to banks to pay employees |
| Statutory | Tax cards and per-employee tax rates from the authorities | Calculated payroll results sent to tax authorities, pension funds and similar |
How it works – Inbound: data comes in, you decide what to import
It arrives
Via a scheduled poll, an auto-trigger, or a manual upload – and appears in the Inbound table under its integration.
It validates itself
Moving Queued → Validating, then landing on Ready to persist (or Failed).
You review, then persist
Check errors and warnings per record in the drawer, then import into masterdata. Hold something back with Postpone if you need to make a retrospective change first, or turn it away with Reject.
If it failed, fix and retry
Read the reason in the Status Log, correct the setup, and Re-trigger the same file (or simply have the source system resend) – no black box.
How it works – Outbound: payroll is approved, files go out under control
It’s created by the run
After Approve & Lock, Send to integration pushes the file here, arriving Scheduled, auto-submitting, or Ready to Submit.
You submit – or let it go
Push a single item, submit a selection in bulk, or let a scheduled item send itself.
You see the outcome
Success, Partial Success or Failed, with the recipient’s response and an AI-interpreted summary in the drawer.
Corrections stay tidy
Resubmissions group under one expandable line; hold items with Exclude; regenerate a bank file after a master-data fix without reopening the run.
Statuses at a glance
| Domain | Statuses |
|---|---|
| Inbound | Queued Validating Failed Ready to persist Postponed Rejected Importing Imported |
| Outbound | Ready to Submit Scheduled Failed Partial Success Success Excluded |
Important to know before activation
Items appear only once a file exists. Failures before a file is produced – a bad request, a wrong SFTP path, an expired certificate – don’t create a row; they surface through the Live/Down health signal and the Status Log.
Some actions are role-gated. Only a Payroll Practitioner or Payroll Admin can exclude a scheduled outbound item, and that exclusion is one-way.
A few things arrive progressively. Configuring integration automations from within PAC, and the AI-generated summary in the drawer, are being switched on in stages and announced as they land.
Audience at a glance
| Role | Primary action |
|---|---|
| Payroll Admin / Practitioner | Review inbound data and persist it; submit and monitor outbound files; hold, retry and diagnose. |
| Managed-services / Fully-managed clients | Reconcile inputs, review results and get internal/finance sign-off – catching anomalies (a duplicated pay element, an unapplied tax card) before submission. |
| Support | Use the Status Log and detail drawer to resolve cases without system access. |
| Finance / Compliance | Rely on a complete, versioned, audit-ready record of every submission. |