Paydae Desktop treats a software update and a statutory-pack update as different operations. Workspace Settings → Statutory Packs exposes pack checks and installation for review; desktop binary download and licence eligibility are handled through the separate customer portal.

What this means

For a statutory pack, open Statutory Packs. “Check for updates” can return “No eligible statutory pack updates were found”, “Some pack data is unavailable”, or “No available pack releases”. An installed pack can show “Activation blocked” even after it was installed for review.

Common causes

  • The update feed cannot be reached because the computer is offline, the network timed out, or the service returned an error.
  • The licence, product edition, release channel, current app version, or installation is not eligible for the release.
  • No release covers the selected effective date or jurisdiction.
  • The package is incompatible, unsigned, or fails verification.
  • A pack was installed for review but the current user lacks workspace pack-management permission, or the server’s candidate validation found a blocker.
  • Another workspace user changed the policy revision after the page loaded, so the default change no longer matches the revision you reviewed.
  • The workspace has an immutable release conflict: the same pack identifier and version already exists with different signed content.
  • A desktop application update is being looked for in Statutory Packs; that screen manages statutory packs, not the application download.

How to fix it

  1. On Statutory Packs, use “Retry” when the screen shows a pack-data error, then select “Check for updates”.
  2. Read the result and the “Available packs and updates” table. Confirm the pack identifier, version, source, signature status, and compatibility.
  3. If an eligible update is listed, select “Install for review”. Installation downloads and verifies the package but does not activate it.
  4. Check “Installed statutory packs” and “Default for new payroll.” Before selecting “Set as default,” inspect the covered statutory range, exact hashes, candidate validation, preserved open preparations, and unfinished-run counts. This is a workspace change, not an organisation activation.
  5. If the policy revision changed, refresh the page, confirm the current default, and review the impact again before retrying. Do not reuse a stale confirmation.
  6. If the same identifier/version has a different signed hash, the app rejects the incoming release and leaves the installed pack unchanged. Ask the release owner for corrected signed content with a distinct version.
  7. If the desktop binary itself needs updating, use the customer portal’s download/update-eligibility process for the licence and installation. Do not treat a statutory-pack version as an application version.
  8. When no network is available, use “Import pack for review” only with a signed pack JSON/file obtained through the approved distribution path. Importing never changes the workspace default.

What to check before continuing

The applicable workspace default should show its authority, effective range, contract, calculator, signature, policy revision, and dependency hashes. An installed candidate should show its version, integrity/hash, and either an enabled “Set as default” action or the server validation/permission reason it is blocked. Confirm the statutory date is covered before creating a new preparation. Existing preparations keep their pinned pack.

How to prevent it

Keep the licensed desktop installation and workspace pack inventory current for new preparations’ statutory effective dates. The operational close-by deadline does not select a pack. Check the workspace default after a change and retain the policy revision, update history entry, and package/dependency hashes.

Still stuck

Record the app version, pack identifier/version, effective date, release channel, exact message, and update-history status. Do not activate an unverified or incompatible package. Share only the diagnostics needed by support; local payroll records are not automatically sent to the vendor.

Related guidePayroll preparation unavailableRelated guideStatutory output blockedRelated guideSupport cannot see my payroll data