Version history

A future version of CheckBiz360 will offer an automatic version history that will allow you to consult every revision a document has had over time, who made each change and when, directly from the back office. Managers will be able to access previous versions and employees will always see the current version in their app.

How to manage document updates in the current version

Although the automatic version history is not available yet, it is perfectly possible to keep documentation up to date in CheckBiz360 by following a simple, consistent manual flow.

Archive the previous version

When an existing document becomes obsolete —because of a contractual amendment, a corrected payslip or a procedure update— the first step is to archive the previous document so that it stops being visible to employees without deleting it permanently. Archiving is logical: the document stops appearing in the active view, but managers with back office access can consult it if necessary.

To archive a document:

1. Sign in to the back office and find the document you want to withdraw.
2. Open the document detail.
3. Select the Archive option. The document will move to archived status and will stop being visible to employees.

Upload the new version as a new document

Once the previous document has been archived, create a new document with the updated file. You can reuse the same title and category to keep the document archive consistent, and assign the same recipients.

If the document required reading confirmation, enable it again on the new document so that employees acknowledge receipt of the updated version.

Recommended naming convention

To make historical consultation easier while the automatic history is not available, including a date or version reference in the document title is recommended. For example:

• Employment contract — May 2025 update
• March 2025 payslip (corrected)
• Health and safety protocol — v2

This makes it possible to identify at a glance, both in the back office and in the archive, which document corresponds to which moment, and avoids confusion when there are several versions of the same document type for the same employee.

Common use cases

Amended contract

When an employment contract is amended —because of a pay rise, a change of grade or a change to working hours— archive the previous contract and upload the new one as a separate document. Assign the same employee and category to maintain the traceability of the file.

Payslip with a correction

If an error is detected in a payslip already published, archive the incorrect payslip and upload the corrected version as a new document. If necessary, send a notification to the employee so they are aware of the correction and confirm receipt of the rectified document.

Renewed certificate

Employer or sick-leave certificates have a defined validity. When an updated certificate is issued, archive the previous one and upload the new one with the issue date reflected in the title.