Installing collaborative Isacompta on a workstation or a network of firms requires mastering several parameters that are not always included in public documentation. The success of the installation depends less on the download procedure itself than on the preparation beforehand, particularly the creation of user accounts and network configuration.
This article measures the gaps between the prerequisites documented by Agiris and the actual blocking points encountered during deployment, to identify where errors are concentrated.
Recommended read : Free Alternatives for Streaming Movies and Series in 2021
MyISA Portal and Account Management: The Lock That the Installer Does Not Mention
Since 2024, Agiris requires centralized authentication via the MyISA portal for collaborative Isacompta. User creation, workstation assignment, connection tracking: everything is managed in this space even before launching the installer. A firm that downloads the installation file without having previously created and activated accounts in MyISA finds itself blocked at the synchronization stage.
This administrative prerequisite changes the logical order of installation. The classic reflex (download, execute, configure) no longer works. First, it is necessary to verify that each collaborator has an active ISA Group account, then assign the corresponding licenses in the portal, and only then proceed to launch the installer.
Read also : Effective Solutions to Unlock a Lock: Tips and Practical Advice
A collaborative Isacompta installation guide details this sequence with screens from the MyISA portal, allowing for verification of each license assignment before touching the server workstation.
Technical Prerequisites for Isacompta: Checklist Table Before Installation
Version notes 25.10 and 25.20 list prerequisites that the majority of competing guides summarize as “check your Windows version.” The reality is more granular.
| Checkpoint | Documented Requirement | Consequence if Absent |
|---|---|---|
| Operating System | Windows 10 or higher (64 bits) | Installation impossible or instability |
| TLS 1.2 | Enabled at the Windows level | Collaborative synchronization fails (error “unable to connect to the server”) |
| MyISA Account | Created and licenses assigned before installation | Blockage at post-installation authentication |
| Administrator Rights | Windows session with admin rights for the installer | Installation interrupted or files partially copied |
| Network Connection | Access to Agiris servers (ports not blocked by the firewall) | Update and synchronization impossible |
The most underestimated point remains TLS 1.2 enabled at the Windows level. On older workstations or enterprise configurations locked by a group policy, this protocol may be disabled. The installation then completes without visible errors, but collaborative synchronization fails afterward.
Check TLS 1.2 on a Windows Workstation
Verification is done through the Windows registry or through the Internet options in the control panel (Advanced tab, Security section). If the TLS 1.2 box is not checked, it needs to be enabled and the workstation restarted before launching the Isacompta installation.
This manipulation takes a few minutes, but it avoids hours of troubleshooting afterward. The synchronization error messages do not explicitly mention TLS, making the problem difficult to identify without knowing this prerequisite.
Electronic Invoicing and Initial Configuration of Collaborative Isacompta
Order No. 2021-1190 and its implementing decrees gradually make electronic invoicing mandatory in France. New installations of collaborative Isacompta must integrate this constraint from the initial configuration wizard, not after several months of use.
Agiris publishes specific preparation guides that cover three parameters to configure immediately:
- Activation of GED (electronic document management) to archive invoices in the format required by dematerialization platforms
- Choice of export formats compatible with future PDPs (partner dematerialization platforms) or the PPF (public invoicing portal)
- Configuration of sales journals to ensure that each entry generated complies with the mandatory mentions of electronic invoices
Configuring dematerialization at installation avoids a complete overhaul of the journals a few months later. Firms that postpone this configuration find themselves reclassifying hundreds of entries to make them compliant.
GED and Sales Journals: Two Related Settings
The GED in collaborative Isacompta is not limited to storing PDFs. It structures the link between the supporting document and the accounting entry. If the GED is activated after several weeks of data entry, previous entries are not automatically linked to the documents, creating a gap in traceability.
The configuration of sales journals, on the other hand, determines the format of data exported to dematerialization platforms. A poorly configured journal produces files rejected by the platform, without an explicit error message on the Isacompta side.
Installation of the Server and Mobile Workstations for Isacompta: Sequence and Common Blockages
The Agiris documentation for version 25.20 clearly distinguishes two phases: the installation of the server, and then that of the mobile workstations. Production is blocked during the server update, which requires notifying all users and choosing a time slot outside of intensive data entry periods.
On the server, the installer updates the database and synchronization components. If a remote workstation attempts to connect during this phase, the database may end up in an inconsistent state. Once the server is operational, each mobile workstation must be updated individually.
Common Errors on Mobile Workstations
The most frequent scenario: a collaborator launches Isacompta on their laptop without having executed the local update. The software detects a version mismatch with the server and refuses the connection. The solution is simple (run the mobile installer), but the error message displayed does not clearly indicate this.
Another blockage occurs when the mobile workstation does not have access to Agiris servers at the time of the update, for example on a hotel network or a filtered public Wi-Fi. The mobile installation requires unrestricted network access to the synchronization servers.
All of these constraints (MyISA accounts, TLS 1.2, dematerialization, server/mobile sequence) form a technical pathway where each conditional step affects the next. Skipping or postponing any of these settings results in malfunctions that only appear in use, sometimes several weeks after installation.