Inbound View

Section 1 — The basics

Why this view matters. Inbound integrations automate a job that used to be manual and error-prone: bringing employee details, master data and pay elements from your source systems (HCM/HRIS) into HR Blizz. Because your payroll results depend entirely on these inputs being correct, this view gives you full transparency – you can see each file arrive, check its validation results per record, and decide whether to import it, hold it, or turn it away. Data can arrive in several formats (XML, JSON, CSV, text, fixed-length) from a range of source systems. Operational inbound carries everyday payroll data; Statutory inbound carries mandatory data such as tax cards and per-employee tax rates issued by the authorities.

What “Inbound” means. Inbound is data coming into HR Blizz from an external system, to be validated and then imported into masterdata. The Inbound view brings monitoring, triggering, uploading, diagnosing and actioning into one place. You’re looking at transmission history – a continuous, paginated list, newest first – not a payroll cycle.

Three ideas to know first

• Integration configuration – transmissions are grouped by their configuration (for example, “Jira Time”). Each config is its own group with a header. The config name is clickable and opens its Status Log.
• Appearing – a configuration only shows here if it’s actually configured on the legal entity. Where it sits (Operational or Statutory) is set by the configuration itself.
• Parser mapping group – when several items in the same group are waiting to be persisted, they persist oldest-first, so chronological order is preserved.

Section 2 – Finding the view and reading the screen

1. Open the Inbound view

• In the sidebar, open Integrations, then choose Operational or Statutory.
• On the domain page, select the Inbound tab.

2. Read the configuration header

• Live / Down – a green or red health signal, tested automatically on a schedule. Health shows even when no file has arrived yet; when a config is Down, an Info icon appears and opens the Status Log filtered to that configuration.
• Run – manually triggers an inbound retrieval for that configuration; the action is written to the Status Log as “Run initiated by [user]”.
• Automation status – shows the automation in effect: Auto Persist, Manual Persist, or Scheduled. (Configuring automations from within PAC is coming with a later announcement.)

3. Understand the columns

• File Name – name of the received or uploaded file.
• Update time – the time column in the Inbound view.
• Process ID – system-generated identifier for the transmission.
• Source – where the file came from: INT (automatic via integration) or PAC Upload (manual).
• Status & Quality – current status (see Section 3) with quality indicators.
• Actions (3-dot menu) – status-aware actions for that item (see Section 4).

4. Refresh the view

• Use Refresh Status to update item statuses and any open drawer’s log snippets without reloading the page.
• Refresh does not change config health – health runs on its own scheduled cadence.
• You get UI feedback (a spinner and/or toast) while it runs.

Section 3 – Statuses and what they mean

The status controls which actions are available on an item.

Section 4 – Acting on an item

The 3-dot menu (fixed order)

The per-item menu always contains the same options in the same order, and only the actions valid for the current status are enabled:

1. Persist
2. Reject
3. Postpone

——————-

1. Download interface file
2. Download Import file
3. Download Log file

What’s enabled at each status

Persisting into masterdata

Persisting imports validated items into HR Blizz masterdata. Items are always persisted in bulk, in chronological order. There are two ways:

• Bulk actions on selected items – select one or more items with the checkboxes to reveal bulk buttons in the config header: Reject (N) and Postpone (N).
• Persist All Pending – takes every item on Ready to persist, across all parser mapping groups, and imports them in chronological order. To keep specific items out of the run, Postpone them first – postponed items are skipped and can be resumed later.

Reject, Postpone & Resume

These give you control over correctness and timing for items awaiting a decision.

• All three write audit / Status Log entries recording who, when and what.
• Persist a postponed item only after Resume, for audit clarity.
• As an alternative to Re-trigger (below), you can have the source system resend corrected data from your HCM.

Re-trigger (same file)

Re-trigger reprocesses the same stored file after a fix – with no need to ask the sender to resend or rename anything.

• It re-runs the validation pipeline on the same payload.
• The download time updates to reflect the re-triggered ingestion time.
• A Status Log entry is written for the action.

Section 5 – Manual Upload

When automation isn’t available, bring a file in through PAC.

1. Open the modal

• Click Manual Upload (the “+” in a circle) to open Initiate Manual Upload.
• Close it via the X, the Cancel button, or by clicking the background.

2. Complete the fields

• File selection – browse or drag/drop.
• File Name – shown but non-editable; derived from the selected file.
• Integration System (dropdown) – required.
• Initiating Actor – displayed, read-only (the current user).
• Supported files: CSV, XLSX, XML Maximum size: 25 MB.

3. Submit

• Click Initiate Manual Upload. The system shows an uploading / processing state and creates a new item with Source = PAC Upload.
• The item starts on Validating by default (or Queued if the pipeline uses queue-first semantics), then follows the normal status flow.

Section 6 – Diagnosing (the Status Log and the drawer)

The Status Log

The Status Log is the diagnostic heart of the Inbound view and the main tool for the Support Department. It’s where you confirm polling activity (including when nothing was retrieved) and investigate failures, per configuration.

How to reach it:

• Click an integration configuration name in the Inbound list – the Status Log opens with that config pre-selected.
• Click the Info icon on a Down configuration – the Status Log opens filtered to that config.
• Use the Edit Integration Config / View Status Log link from an expanded Current Status panel when configuration is missing.

What each entry shows – one execution record per row:

• Entries are listed in time order and can be filtered by configuration.
• A file count of 0 means a successful poll with nothing to retrieve.

The Transmission Details drawer

Opening an item opens a drawer that lets you diagnose and act without leaving the view. Close it via the X (top-right) or the Close button; each sub-view offers Back to Details.

Sub-views:

• Details (default).
• Current Status – expands for relevant statuses (e.g. Failed, Ready to persist) with actionable detail: what happened, plus error codes/messages. If the issue is missing configuration, an Edit Integration Config / View Status Log link is shown.
• Process Summary cards – three clickable cards: Processed (opens the employee list), Errors (clickable when > 0), Warnings (clickable when > 0).
• Error List – a banner summary plus a record-level table. A “Go to Status Log” action appears when the error indicates missing configuration.
• Warning List – a banner summary plus a record-level table. Warnings are non-blocking – review them before you persist, but they don’t by themselves prevent import.
• Interface File Viewer – inspect the staged payload: a file summary plus employee rows, with working Search/Filter and Download. Clicking an employee opens a nested Employee drawer.
• AI Generated Summary (being switched on progressively) – a plain-language summary of validation outcomes, delivered as part of the AI validation capability. You’ll see an entry point that opens it once the capability is available.

Common workflows

Import today’s inbound data

1. Open Integrations – Operational (or Statutory) – Inbound.
2. Find the configuration group and confirm the header shows Live.
3. Click Refresh Status so statuses are current (optional).
4. Review items on Ready to persist; open the drawer to check Errors / Warnings.
5. Choose Persist All Pending, or hold some back first.
6. If persisting, watch statuses move Importing – Imported.

Hold an item, then release it

1. On a Ready-to-persist item, choose Postpone (status becomes Postponed).
2. When ready, Resume it (back to Ready to persist).
3. Persist as normal.

Support: nothing is showing up for a configuration

1. Check the header health. If Down, click the Info icon.
2. In the Status Log (filtered to that config), review the latest poll / trigger entries.
3. Check the file count: 0 means polling worked but nothing arrived; an error code means a connectivity or configuration problem.
4. Fix the configuration.
5. Return to the Inbound view and use Run to retry.

Support: an item failed after ingestion

1. Open the item drawer and expand Current Status to read the error detail.
2. If configuration is missing, use the Edit Integration Config / View Status Log link.
3. Check the Error List and download the log if you need full detail.
4. Fix the configuration.
5. Use Re-trigger Process on the same file – no resend or rename needed.

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