Use this guide when a backup cannot be created, unlocked, validated, or restored. Paydae validates a restore point before changing workspace data; a failed validation should not be treated as a partial restore.

What this means

The restore flow can report an invalid password, corrupted or unsupported format, missing required file, empty destination, database/integrity failure, licence incompatibility, an unavailable destination, or a pending maintenance/safety-backup step. Automatic backup settings have separate states such as Needs password, Unavailable, Not writable, and Not due.

Common causes and fixes

Wrong password or mismatch

enter the password used for that .paydaebak file rather than the device’s protected password if they differ. A forgotten password cannot be recovered.

Corrupted, incomplete, or unsupported file

copy the original file again, verify its extension and size, and retry Unlock and review. Do not edit the archive.

Database or integrity failure

preserve the displayed reason and select another verified restore point if available. Create a fresh manual backup from a healthy workspace before further changes.

Destination missing/not writable

choose a local folder you control, check space and permissions, and retry.

Not compatible or licence incompatible

use the installation/version indicated by the validation result and activate its licence separately.

Protected backup password required

configure one in Backup settings, then resume the prepared replacement. Choose a writable Safety backup destination. This safety point is created and verified as part of the replacement operation.

Owner, recovery, or licence prerequisite

use the action offered on the prepared restore screen, then return to the same operation. A prepared restore can be cancelled before confirmation if Cancel prepared restore is offered.

Existing-workspace replacement blocked

keep the app open and follow the maintenance or safety-backup message. Do not assume replacement occurred until the completed state is shown.

Interrupted operation or recovery required

reopen Paydae, review the pending operation, and use Reconnect to restore or Recover operation when shown. See Recover an interrupted restore.

Automatic backup failed

check the folder, protected smart password, selected execution mode, and last automation run. Use Create backup now while repairing the schedule.

How to investigate safely

  1. Record the failure

    Record the selected file path, validation status, compatibility result, and exact reason shown in the UI.

  2. Review the selected backup

    Reopen Restore Workspace and stop at the prepared review if validation succeeds. Confirm the workspace name, backup time, contents, and mode before continuing.

  3. Check replacement prerequisites

    For an existing workspace, check that a protected smart password and safety backup destination are available. After confirmation, review the operation’s safety-backup result before treating replacement as complete.

  4. Verify the outcome

    After a completed restore, sign in again and verify workspace records, settings, organisation context, and retained safety point.

What not to do

Do not delete the only restore point, type a password into a support ticket, merge files manually, or claim that a failed validation restored data. Do not use a backup as a licence or account transfer mechanism.

Still stuck

Share the exact status, error code/message, app version, file size, and whether the flow was empty-install or existing-workspace replacement. Remove payroll values and passwords from diagnostics unless your approved support process specifically requests a controlled evidence package.

Bureau and single-organisation notes

Restore errors apply to the whole local workspace. In a Bureau workspace, verify client data after recovery and do not mix points from different workspace copies.