How do users register with Digiposte?

Digiposte has several procedures that simplify the process for users. 

If your users have an e-mail address, the most effective way is by a Digiposte invitation e-mail. 

If they don't have an e-mail address, however, they can register through a generic URL of the type: "register.digiposte.fr/companyname." 

Finally, users who already have a Digiposte and would like to register can do so through their safe. 

This access can be configured before deployment.

What information do users need to register for digital payslips?

Depending on how they register, the information they will need to provide varies, for security reasons. 

If they register via an invitation e-mail sent to professional e-mail addresses, they will need a personal code (registration number or agent code / identifier). 

If they register via generic URL or via the employee safe, they will need a second code, called a security code. 

This code can be configured. These codes must only be provided once for digital payslip registration.

Can digitisation be imposed?

You cannot force your users to adopt digitisation. You must inform them of the transition to the digital payslips at least 30 days before they are issued.

This mandatory 30-day communication period leaves users the time to refuse, if they so wish. Furthermore, once the payslips have been digitised, users can cancel registration at any time. 

How can you ensure the digitisation project is a success?

There are many key steps to ensure the project succeeds. 

First of all, your digital transformation plan should be properly mapped out. 

Success is also proportional to how invested you are in the plan. Payslips don't digitise themselves. You must make an effort to clearly communicate about the plan. 

Finally, the language you use must make sense and reach out to your users. This means that the same arguments don't necessarily work with different groups of people, so you need to adapt and tailor what is said in the Digiposte standard kit. 

This is the role of the digicoach consultants.

What rate of digitisation should I expect?

The implementation of the 2017 Labour Law considerably increased the rate of digitisation of company payslips, and today companies are achieving a digitisation rate approaching 50%.

Many companies have higher rates. Remember that the rate off acceptance for you will depend on a variety of factors:

  • the profile of your users
  • your organisation's digital agility
  • your commitment to the project (it affects the teams, and the way it is communicated is essential); etc.

Even if the use of digital is constantly changing, remember that for some people, digitising payslips causes anxiety, both because of the type of document, which many feel is significant, and the way the user deals with the digital world in their private life.

All of these factors mean that digitisation rates vary widely from one company to another, ranging from 50% to over 90%. To help you, remember that Digicoach, which is a change support service, is available. 

How much time does it take to launch a digitisation project?

In general, it takes two to three months to launch a digitisation project. 

What are the steps in the digitisation project?

Digitisation projects have three phases: preparation, launch of the deployment and support.

Each phase makes the following step easier. For more detailed information, please get in touch with your dedicated contact (the distributor, for example) or check the business site.

https://business.digiposte.fr/

When should the digital payslips be deployed?

Is there a best time to digitise payslips?

The payslip digitisation project is part of your company’s digital transformation plan. It can even be one of the foundations, insofar as it represents an inclusive strategy, and the project involves all users regardless of their digital “agility”.

Beyond that, as the project affects users and their routines, payslip digitisation must be understood by all employees. So you should avoid launching the project during busy periods (e.g. peak periods), at the same time as another project that is more time-consuming (changes to complementary health insurance or pension contracts, for example), during crises (such as restructuring or redundancies), and so forth. 

Should there be a pilot programme before the deployment is generalised?

The purpose of a pilot programme is to test the technical and functional environment along with the communication procedures required. 

If the pilot programme involves representative targets, and if you give it enough time, meaning enough time to review all or part of the process for implementing the change, then yes, it could be a good idea. In the absence of these conditions, spare yourself the extra workload it involves, especially if you are assisted by a digicoach consultant who can share their experience with you.

How should users be informed of the digitisation?

They can be informed using any means necessary. But they must be informed at least 30 days prior to the first digitisation and you must have enough time to collect and process collaborators refusals. 

We recommend repeating the information using the different communication channels available both before and during deployment.

Have more questions? Submit a request