Statutory packs
Understand installed statutory rule packs and workspace defaults in Paydae Desktop.
When to use it8 sections
A statutory pack is a signed, versioned rule and output definition set that Paydae can use for a compatible statutory date. Workspace Settings → Statutory Packs manages the desktop workspace inventory and date-scoped default for new payroll preparations. It works before you select an organisation. Compliance provides Statutory Rules and detached Tax Preview. A signed pack supplies calculation rules; it does not register an employer, file a return, or settle a liability.
When to use it
Use this guide when checking a pack update, importing a pack for review, or confirming which workspace default a new payroll preparation will capture.
Pack lifecycle
Use the exact lifecycle controls shown in the screen:
- Check for updates looks for an available pack update.
- Install for review or Import pack for review verifies and stores a release without changing the workspace default.
- Default for new payroll identifies the signed, compatible release selected for the displayed date range.
- Retained for existing payroll means an older release remains available to execute work that already captured it.
- A workspace administrator can set a default for an effective range or roll the policy back to an earlier revision. Both actions require current workspace permission and server validation.
The screen shows the policy revision and activation impact before a default changes. Existing preparations and payroll history keep their captured pack and dependency hashes when a workspace default is updated or rolled back. A newly created organisation inherits the workspace default automatically; it does not need a separate pack activation.
Every supported preparation captures its exact workspace policy entry, signed pack dependencies, and required employer facts before calculation. Signed RC5 packs use their assessed-rate profile when the current preparation provides the required evidence; RC6 uses its industrial-rate profile. A preparation without a complete current binding cannot be resumed or recalculated. Create a new preparation under the applicable workspace default; never attach current organisation facts or a newer pack to an incomplete record.
Before you begin
- Choose the Effective date you want to inspect. Organisation selection is not required to manage workspace packs.
- Have the pack source and version information available if you are importing for review.
- Ensure a user with workspace pack-management permission handles default changes; installation alone never changes payroll defaults.
Steps
- Open Statutory Packs
Open Statutory Packs.
- Record the current default
Record the current Default for new payroll identity, version, policy revision, effective range, compatibility, and hash/signature evidence shown by the app.
- Check for updates
Select Check for updates when you want Paydae to look for an available pack.
- Install for review
Select Install for review or Import pack for review to inspect a supplied release. Confirm its signed identity and server validation status.
- Review activation impact
Before choosing Set as default, check that the release covers the requested date range and review the impact counts for preserved open preparations and unfinished runs.
- Confirm the exact release
Confirm the workspace and exact release hashes. The app checks the policy revision again when saving. If another user changed it, refresh the policy and review the impact again.
- Verify persisted history
Use the persisted history and policy revisions to confirm the result. Existing work continues to use its captured release.
What to check
Check signed status, compatibility, effective coverage, version, all dependency hashes, and the recorded workspace policy revision. An installed pack may be available for review while remaining ineligible as a default. If an import uses the same identifier and version as an installed pack but has a different signed hash, the app rejects it and keeps the installed release. Obtain a corrected release with a distinct signed version; the conflicting content is never installed over the original.
Important compliance boundary
Pack metadata and activation state are product evidence, not legal approval. A compliance owner must review whether the selected pack and resulting output meet the organisation’s obligations and official-channel requirements.
Common problems
Set as default is unavailable
confirm the effective range, candidate compatibility/signature, and the user’s workspace pack-management permission. Read the server validation blockers shown beside the release.
Update is installed for review
this is the intended lifecycle separation; review the release before changing the workspace default.
Policy revision changed
refresh the workspace policy, verify the current default, then run the impact review again before saving.
The same version has a different hash
the import is rejected and the installed release remains unchanged. Contact the release owner for a corrected signed release with a distinct version.
Pack hash/signature is not shown
use the displayed status and update history; do not invent a reference.
A new organisation has no pack
refresh workspace policy. New organisations inherit a workspace default automatically; there is no per-organisation activation step.
RC5 assessed-rate evidence is required
provide the explicit NSSA classification, assessed rate, and assessment reference required by the selected pack profile before capture. Do not substitute current organisation values or RC6’s industrial-rate catalogue.
A preparation has no complete policy binding
the current contract cannot safely resume or recalculate it. Create a replacement preparation under the applicable workspace default; historical outputs remain tied to their recorded calculation evidence.
Bureau and single-organisation notes
The pack inventory and default policy are shared by the desktop workspace. Bureau users do not activate a separate release for each client. Organisation classifications, exemptions, and employer evidence remain organisation-specific inputs when preparing or calculating payroll.