On a a Monday morning, the general secretary of a rural municipality opens his workstation for the first time with Berger Levrault. The goal for the day: to enter the first mandates of the budgetary exercise. However, without a correct configuration of rights and synchronization with the HRIS, each operation risks generating duplicates or declaration errors. The first connection to Berger Levrault software is not just an administrative formality; it is the technical foundation for everything that follows.
HRIS Synchronization and Access Rights: The Real Starting Point
Most connection guides start with “enter your username.” This misses the point. Before even typing a password, user rights must be correctly synchronized with the municipality’s HRIS. Without this step, agents end up with incomplete profiles or overly broad access.
Specifically, an agent in charge of accounting who inherits a “view-only” profile because synchronization has failed will not be able to enter mandates. Conversely, an overly permissive profile exposes sensitive data. This situation is often encountered in small municipalities where one person manages both payroll and accounting.
To avoid these situations, it is recommended to validate the correspondence between the job descriptions in the HRIS and the rights profiles in Berger Levrault before sending the usernames to users. A comprehensive guide on using Berger Levrault software details this relationship between rights and initial access.
Berger Levrault Connection in SaaS Mode or Local Installation
The procedure for the first connection directly depends on the hosting mode chosen by the municipality. Feedback varies on this point: some municipalities still operate with a local installation on a dedicated server, while more and more organizations are transitioning to externalized SaaS hosting.
Local Installation: What Changes at Connection
With an on-site installation, access is generally via a thick client or an internal web interface. The initial configuration involves setting up the SQL server, creating the database, and opening network ports. The IT department (or the service provider) must also configure backups and maintenance for updates.
The classic pitfall: forgetting to check the SQL version compatible with the deployed software version. An incompatibility generates silent connection errors, where the login screen appears but validation spins in vain.
SaaS Hosting: VPN, SSO, and Monitoring
In SaaS mode, the municipality accesses the software via a browser. The initial configuration is different:
- Setting up a secure VPN access if required by the publisher, with certificates to install on each workstation
- Configuring SSO (single sign-on) to avoid multiple usernames across different Berger Levrault modules
- Ensuring that monitoring and backups are properly managed by the publisher, and not left to the municipality’s responsibility
The SaaS mode simplifies maintenance but shifts the responsibility to the publisher. It is essential to contractually ensure that data remains accessible in case of a change in service provider.
Client Space Configuration and User Management
Once the connection is established, the next step is to configure the Berger Levrault client space so that each agent has the appropriate modules. In a small municipality, the general secretary often combines financial management, human resources, and civil status. His profile must reflect this versatility without granting access to system administration functions.
Profiles are structured into three levels:
- Administrator: manages user accounts, updates, and global software settings
- Business Manager: accesses budget management, payroll, or invoicing modules according to their responsibilities
- Consultation: views data without the ability to modify it, useful for elected officials or auditors
Each profile must be documented in an internal sheet to facilitate handover in case of agent changes. Municipalities that neglect this step end up with orphaned accounts and access that cannot be reassigned.
Password and Activation of the Berger Levrault Account
The account activation follows a standard process but with enhanced security requirements. The new user receives an activation email sent from an address like [email protected]. This message contains a time-limited link to set their personal password.
The password must contain at least twelve characters, including four distinct types: uppercase letters, lowercase letters, numbers, and special characters. This is not a recommendation; it is a technical constraint. A password that does not meet these criteria will be systematically rejected by the system.
Two common errors slow down this step. The first: the activation email lands in the spam folder, especially when the municipality’s mail server applies strict filters. The second: the agent lets the activation link expire and must contact support to restart the process.
Opening the Budgetary Exercise After Configuration
In small municipalities, the first connection directly conditions the opening of the budgetary exercise and the entry of the first mandates. Daily accounting management (titles, mandates, invoice tracking, exchanges with the treasury) is carried out entirely within the software. A delay in configuration postpones the entire accounting chain.
Before launching the first exercise, it is essential to verify that the accounting nomenclatures are up to date, that the links with the invoicing module are functioning, and that exports to the treasury are configured in the correct format. A test send to the accounting position allows for validating the entire chain without engaging real data.
Configuring management software like Berger Levrault cannot be improvised on the day invoices pile up. Municipalities that anticipate the synchronization of rights, choose their hosting mode knowingly, and document user profiles gain several weeks on the effective production rollout.