Isacompta, published by Agiris (Isagri group), is an accounting management software designed for accounting firms and agricultural operations. Its installation relies on a precise sequence where each step conditions the next, from downloading on the client space to configuring the billing and file management modules.
Network and server prerequisites before installing Isacompta
Before launching any executable, the preparation of the server workstation determines the success of the entire chain. The official documentation from the ISA Group specifies that production is blocked during the update: all users must be logged out and notified in advance.
Related reading : Step-by-Step Guide to Effectively Contest a Fine for Not Using Turn Signals
For a detailed guide covering each action, you can refer to the installation procedure for Isacompta on Home Educ, which complements the points discussed here.
System compatibility remains a frequent point of friction. Isacompta operates on Windows, but not all editions are supported. Windows Server versions must correspond to specific editions, or there may be issues when assigning user rights or during network synchronization.
See also : Discover how to rent an apartment without a tax notice: complete guide and practical tips
- Ensure that the necessary ports for synchronization between workstations are open on the server’s firewall, including exceptions for third-party software (antivirus, corporate VPN).
- Make sure that the Windows account used for installation has full administrator rights, not just standard user rights.
- Plan a complete backup of the existing database before any intervention, even for a minor version upgrade.
An often-overlooked point: the data import and export options are not active by default in Isacompta. A specific validation step in the initial setup must be completed before any transfer of accounting files. Skipping this step locks access to certain modules without an explicit error message.
Isacompta version upgrade: server and mobile workstation installation sequence
Upgrading to a new version follows a strict order. According to the official documentation for upgrading from version 24.20/25.10 to 25.20, the installation is broken down into three phases: preparation, server installation, and then deployment on mobile workstations.
The server installation always precedes that of the client workstations. Launching the installer on a mobile workstation before the server is updated causes version conflicts in the shared database. The software does not always report this inconsistency immediately, complicating diagnosis.
Post-installation configuration
Once the server is operational, the initial configuration requires manually validating the activation of the billing, quote management, and client file tracking modules. Each module is activated separately in the administration interface.
Connecting mobile workstations to the server requires entering the exact network address and testing synchronization before opening any accounting files. A silent failure at this stage can corrupt shared files during simultaneous access.
Migrating a client portfolio from Cegid or Sage to Isacompta
The migration from a competing software like Cegid or Sage represents the most risky moment of the deployment. The structure of the chart of accounts differs between each publisher, and a simple copy-paste of files does not work.
The procedure begins with exporting data from the original software. Cegid and Sage offer export formats (CSV, FEC, sometimes proprietary formats), but mapping accounts to the Isacompta chart of accounts requires checking line by line for atypical accounts.
Specifics of subcontracting invoicing in the construction industry
Construction companies managing subcontracting face an additional challenge during migration. Self-assessment of VAT in subcontracting requires specific accounting treatment: VAT does not appear on the subcontractor’s invoice but must be declared by the client.
During the transfer to Isacompta, entries related to self-assessment must be recoded according to the software’s conventions. The deductible and collected VAT accounts used in Sage or Cegid do not necessarily correspond to the accounts set by default in Isacompta. A manual adjustment of the chart of accounts is required before import.
- First, export a closed and complete fiscal year from the old software, then ensure that the total balances match to the cent after importing into Isacompta.
- Process subcontracting invoices with self-assessment separately: identify each relevant entry and confirm its attachment to the correct VAT account in the new framework.
- Test the migration on a pilot file before switching the entire portfolio, targeting a construction client with subcontracting operations to validate the accounting treatment.
Agiris support and resources to resolve installation issues
The Isagri client space provides access to installation files, release notes, and deployment documentation. Version 25.20.009, referenced in the Swiss client space, illustrates the regular update pace of the software.
When a blockage occurs during installation, Agiris technical support is the main recourse. The most common errors (closed network port, insufficient rights, conflict with antivirus) are generally resolved by checking system prerequisites rather than a complete reinstallation.
Firms deploying Isacompta in a multi-user environment benefit from documenting their network configuration (open ports, server access paths, service accounts) in an internal file. This document prevents starting from scratch during each version upgrade or workstation change.
The success of an Isacompta installation depends less on the technical complexity of the software than on the rigor of the preparation beforehand. A properly configured server, verified network rights, and a tested migration on a pilot file are enough to avoid most incidents reported by users.