On this page0

Section 1 — How items get here and how the list is organised

Why this view matters. Outbound integrations carry the results of payroll back out to the parties that need them – and this view lets you see and control every submission end to end. Operational outbound sends files such as bank files to banks, so employees get paid. Statutory outbound sends calculated payroll results to tax authorities, pension funds and similar bodies. Even where a third party runs your payroll, you’ll use this view to reconcile and review the outputs before they go – catching anomalies like a duplicated pay element or an unapplied tax-card update – and to confirm each file was actually accepted.

How items appear. Outbound items aren’t created on this screen. After a payroll is approved, the Send to integration action pushes the file here and starts whatever automation applies to that integration:

Scheduled – the item arrives queued for a future submission time.
Auto-trigger – submission begins automatically.
Ready to Submit – no automation is configured, so it waits for a manual push.

How the list is organised. The Outbound view is a continuous list (not tied to a single run or cycle):

Newest first, based on the time an item appeared on the view (some items, like Scheduled ones, don’t have a submission date yet).
Paginated, with a configurable page size.
Grouped by integration, each with its own header.
Version grouping – when the same report for the same period is submitted more than once (e.g. rejected, then resubmitted after a correction), those versions collect into a single expandable line item instead of separate rows. Expand it to see every version, newest on top.

Outbound list grouped by integration; expandable version group

Payroll run – “Send to integration” on a report row

Section 2 – Reading the screen

1. The integration group header

Integration configuration name – clicking it opens the Setup for that config (Status Log tab by default).
Live / Down indicator – whether the integration is currently up.
Automation state – whether the scheduler and auto-run are on or off.
Run – triggers manual submission of the selected items in that group.
Search and Filter – standard controls for the group.
Selecting rows shows a selection summary and enables Submit (N) for that group only.

Group header with Live/Down, automation, Run

2. Understand the columns

Column	What it represents	Click behaviour
Filename	Name of the outbound file (plain text)	Clicking the row (not an action) downloads the file
Period	The reporting period the data covers – not when the file was generated	Opens the detail drawer
Due Date	Submission deadline (statutory: set by the authority; operational: by business policy). A dash if none	If dashboard context exists, opens the Dashboard focused on this item
Actor	The user who performed the action	–
Submission Date	Timestamp of the most relevant event for the current state (Scheduled = future send time; Ready to Submit = no date yet)	–
Process ID	Internal identifier; present once a process has started (Success / Partial Success / Failed)	Cross-references logs, drawer, dashboard
Encrypted / Signed	Security applied to the file – encrypted, signed, or both	Opens the detail drawer
Submission Status	Current lifecycle state (see Section 3)	Opens the detail drawer
Actions (3-dot)	Operations available for that row	Opens the row’s action menu

3. Refresh the view

The header includes a Refresh Status control that updates row statuses and any open drawer data.
The page doesn’t reload; you get a spinner or short message while it refreshes.

Refresh Status control

Section 3 – Statuses and row actions

Status	Meaning
Ready to Submit	File created; the integration has no automation set – it needs a manual push
Scheduled	Configured to submit on a schedule; will send automatically at its time
Failed	Not successful, or the recipient returned a comparable outcome (rejected, denied, not accepted, failed validation)
Partial Success	Accepted with warnings, or partially accepted (some items accepted, some rejected)
Success	Accepted with no errors/warnings, or delivered where the recipient provides no feedback by design
Excluded	Deliberately held back so it isn’t sent – e.g. to keep control over an error found after approval, or to keep an item out of a bulk action

Row actions (3-dot menu) – options depend on the item’s status:

Action	What it does	Available when status is
Submit	Pushes the submission for that item	Ready to Submit, Scheduled
Download Outbound file	Downloads the prepared outbound file	All statuses
Download Response file	Downloads the recipient’s response	Failed, Partial Success, Success
Log file	Downloads the log for the item	Failed, Partial Success, Success
Exclude	Holds the item back so it isn’t sent	Ready to Submit, Scheduled
Enable for Submission	Reverses Exclude so the item can be submitted	Ready to Submit

3-dot menu on a Ready-to-Submit row

Section 4 – Submitting

Submit a single file

Confirm the integration header shows Live.
Select the item – or use the row’s 3-dot menu – and choose Submit.
Watch it move to Success, Partial Success, or Failed.

Bulk submit

Select items within a group, or use Select all to select every eligible item for that configuration across all pages.
A confirmation appears before anything is sent, telling you how many items are selected. Proceed or reject.

Bulk selection bar with Submit (N)

Eligibility rules

Eligible for Submit: Ready to Submit and Scheduled.
Not eligible: Excluded, Failed, Partial Success, Success.
If a selection includes an ineligible item, Submit (N) is disabled until only eligible items remain.
For bulk submission, the eligible-to-select items are those on Ready to Submit. Scheduled items are excluded from bulk – submit them individually.

Working with Scheduled items

You can:

Exclude the item so it isn’t submitted (only a Payroll Practitioner or Payroll Admin can change a Scheduled item to Excluded).
Run it individually – submit the single Scheduled item now, ahead of its schedule.

You cannot:

Include Scheduled items in bulk actions.
Reverse a Scheduled item back to Scheduled once it’s been Excluded – exclusion is one-way.

Scheduled item: run individually / exclude

Section 5 – Handling corrections and resends

If the recipient didn’t receive a file, or a payroll change is required, unlock the payroll before the pay date (unlock is allowed up to one day before).
Make the necessary payroll change, then Approve and Lock again.
Regenerate the affected report – a new version is created and shows the Send to integration option again.
Send it. The system only sends files that haven’t already been transmitted, so previously sent files aren’t resent – no duplicates.
Verify the newly generated version is the one transmitted.

Section 6 – The Transmission Details drawer

Clicking a row (or its status) opens a drawer with three internal views; move between them and back with Back to Details. Close via the X (top-right) or Close.

Current Status view – the present state: current submission status, the Encrypted/Signed value, the time the status was last updated, and a text description.
Metadata view – supporting details: the integration configuration (system), period and due date, actor and submission date, Process ID, and traffic direction (Outbound).
Delivery Status view – the final known details, including the recipient’s response and an AI-interpreted summary. Because it adapts to the actual response, the layout varies but typically includes general status and submission details, blocks for warnings and errors, a breakdown of individual errors/warnings, a table of employees / pay elements, and a summary table.

Note

Anything that needs data the item doesn’t have yet is shown disabled, labelled “Not available yet.”

Drawer: Current Status / Metadata / Delivery Status

Cautionary notes

Don’t transmit until all payroll changes and validations are complete.
Once a file is sent, avoid further changes unless you intend to unlock – update – regenerate – resend.
Mind the unlock cutoff: unlock is allowed only up to one day before the pay date.
Excluding a Scheduled item is one-way – it can’t go back to Scheduled.
Confirm whether a report has already been sent before using bulk transmission, even though the system prevents duplicate sends.

Tips for efficiency

Validate reports right after generation so issues are caught before lock.
Use version grouping to track changes and confirm you’re sending the latest file.
Use bulk Submit when several Ready-to-Submit items are waiting.
If a report must be resent, regenerate only the affected version instead of reprocessing everything.
Refresh Status updates rows and any open drawer without reloading the page.

Quick reference for Support

If a user asks-	Answer
Why can’t I submit this item?	Submit works only for Ready to Submit and Scheduled. Excluded, Failed, Partial Success and Success aren’t eligible.
Why is Submit (N) greyed out?	The selection includes at least one ineligible item – deselect it, leaving only eligible items.
Why wasn’t a Scheduled item picked up by Select all?	By design – Scheduled items are excluded from bulk. Submit them individually.
Can I put an Excluded item back to Scheduled?	No. If it was Scheduled before being Excluded, that can’t be reversed.
Who can exclude a Scheduled item?	Only a Payroll Practitioner or a Payroll Admin.
Why does the Period not match when the file was generated?	Period reflects the period the data covers, not when the file was produced. A correction in a later period still shows under the original period.
Where do I find the response or logs?	The row’s 3-dot menu (Download Response file, Log file) for Failed / Partial Success / Success items; the Delivery Status view in the drawer shows the interpreted summary.
The list looks out of date.	Use Refresh Status in the header – it updates rows and any open drawer without reloading.

Screenshots reflect the Outbound view at time of writing. If the UI has changed since, verify the current screen before following a step exactly.

Was this page helpful?

Outbound View