Ad-hoc Pay Run Warning and Mandatory Delivery Format

Ad-hoc Pay Run Warning and Mandatory Delivery Format

Overview

When posting a Salary Packaging pay run for a period that has no existing regular pay run, Catch-e now warns you upfront that the pay run will be ad-hoc, and requires you to explicitly choose an Email or PDF delivery format before you can proceed. This closes a gap where ad-hoc pay run report batches could previously get stuck unsent, with no warning that anything unusual was happening.

When the Ad-hoc Warning Appears

  • You select Go on the Salary Packaging Pay Run screen for a client, pay cycle and period combination that has no existing regular pay run for that period — this is what makes the resulting pay run ad-hoc.

  • A pay run for a period/pay cycle that already has a regular pay run is unaffected and behaves exactly as before.

How It Works

  1. On the Salary Packaging Pay Run screen, select the client, pay cycle and period, then select Go.

  2. If the selected period will produce an ad-hoc pay run, a warning appears immediately — before any records load — telling you the period will create an ad-hoc pay run.

  3. Choose to cancel the warning: no records load, nothing is created, and Go remains available to try again.

  4. Choose to proceed: records load as normal, but the delivery format field is left blank rather than defaulted.

  5. Select Invoice without choosing a format, and you're blocked with a message asking you to choose Email or PDF first.

  6. Choose a format, then select Invoice and Post as usual.

  7. If Email was chosen, the existing pay run report review pop-up still appears — listing the pending items with Send and Cancel, and letting you edit an item before it goes out — the same as it does for a regular pay run.

  8. Once the ad-hoc pay run posts successfully, its status advances from Open to Pending, matching how a regular pay run behaves.

Expected Behaviour

Ad-hoc Warning Shown at Go

  • The warning appears before any records load, stating that the period will create an ad-hoc pay run.

  • No pay run record exists yet at this point.

Declining the Warning

  • No records load.

  • Go remains usable.

  • Nothing is created.

Delivery Format Is Blank and Mandatory

  • The Email/PDF field starts blank for an ad-hoc pay run instead of defaulting to the client's configured default.

  • Selecting Invoice without choosing a format is blocked, with a message asking you to choose Email or PDF first.

Regular Pay Runs Are Unaffected

  • No ad-hoc warning appears.

  • The delivery format still defaults as before.

  • Behaviour is unchanged from prior releases.

Ad-hoc Pay Run Status After Posting

  • A successfully posted ad-hoc pay run's status advances from Open to Pending, the same as a regular pay run.

  • If posting fails, the pay run stays at Open so it can be retried.

  • Only the pay run that is actually posted advances — an earlier abandoned attempt for the same client/period is not incorrectly advanced.

Review Pop-up Is Unchanged

  • The existing pay run report review pop-up — listing pending items, Send and Cancel, and per-item editing — still appears for Email delivery, including for ad-hoc pay runs.

  • Closing the pop-up window cancels the batch, the same as before.

  • Edits made to an item's subject or body before sending are preserved through to the sent email.

Known Limitation — Cancelling After Posting

Cancelling the review pop-up leaves the invoice posted and the ad-hoc pay run finalised, but no report sent — with no on-screen indication that the client didn't receive their report. This is an existing limitation carried over from before this change, not something introduced by it, and it's tracked separately by an internal monitoring report rather than fixed here.