1. Document Objectives

This document aims to detail the technical and functional operation of our connector. It defines the scope of action (what is covered or not) and lists the prerequisites necessary for its implementation.

Important Note: Our teams are available if you need any clarifications or further information.

How to use this document? We recommend reviewing this document with all knowledgeable persons (CIO, CFO, Chief Accountant, IT Manager), which objective is to:

Verify if the proposed flows match your business needs.
Confirm that your technical environment meets the installation prerequisites.

⚠️ Deployment Methodology:Our approach is intended to be pragmatic. If, after analysis, the prerequisites appear to be validated, we will favor the installation of the native connector.However, if for a technical reason or a specific configuration, the connector could not be activated , we will switch without problem to an alternative method via SFTP to ensure the continuity of your project.

2. Prerequisites and Deployment

2.1 Technical Prerequisites

This integration only works for FRANCE.

Overview of Sage FRP 1000 Integration

Sage FRP 1000 is business accounting software provided by Sage. This integration allows you to synchronize Sage FRP 1000 data with Agicap, supporting multi-entity and multi-currency environments, pre-matching payments, and advanced automation.

Supported Sage FRP 1000 Versions

Supported Versions ✅	Not supported versions ❌
Sage FRP 1000 v8 and above , whatever the naming (v8, v9R2, version 11 2025 R2, and later releases)	Sage FRP 1000 versions below v8

ℹ️ Sage has changed its version naming over time (v8, v9R2, then "11 2025 R2"). There is no upper version limit. Any version from v8 onwards is in scope. Version support is independent from the server prerequisites below (Windows Server 2016+, .NET 4.7.2+, SQL Server 2016+ for business documents).

Connecting Sage FRP 1000 with Agicap

⚠️ This integration requires a software installation on the Sage server which will be handled by the Agicap technical team but requires IT/Integrator/Server Admin involvment.

Your setup Prerequisites

Windows Server 2016 or higher / Windows 8 or higher
.NET framework 4.7.2 (or higher) installed on the SQL server
Administrator access to the server hosting the Sage databases
Name of the SQL server and Sage databases
(Optional) SQL user for Agicap with read-only access
You must generate an API key ( Settings link ); the Agicap tech team will guide you to perform it
The synchronization of business documents is supported starting from SQL Server 2016
Antivirus: exclude the folders C:\Program Files (x86)\Les Editions CoMPAGNoNS and C:\ProgramData\Les Editions CoMPAGNoNS (recommended), or at least ProjectLauncherFx.exe, ProjectLauncherNet.exe, serviceutlis.exe and updater.exe. Otherwise the antivirus can block the service or its updates.
The iO service account needs read and write access to these two folders, and the right to run msiexec.exe, which is used for service updates.
Startup type: the iO service ("iO Main Local Service") must be set to Automatic startup in Windows services. Otherwise it does not restart after a server reboot, and the flows stop without any error (e.g. bank statements no longer dropped).

2.2 Deployment Organization & set up prerequisites

The installation of this connector is a collaborative process that requires the intervention of three stakeholders:

Your teams: For validation of access and selection of accounts to synchronize.
Your Managed Service Provider: For opening server access and installing the technical component.
Your Company's Technical Team: For configuration, flow testing, and commissioning.

To operate, it requires the installation of a liaison agent on your Sage server (the iO Manager service ). This service is unique per customer, and its setup is part of the project onboarding. The setup prerequisites are listed in section 2.1 above; the database access needed by each flow is described in section 6.

⚠️ The connection meeting requires the presence of a person with administrator access to Agicap and a person with access to the ERP (Sage FRP 1000 server and databases).

3. General Information

This section describes the global infrastructure that supports data exchange.

Domain / IP	Port	Direction	Comments
.iomanager.app	443	Out	Outbound communication with iO for accounting and journaling features
iO Manager service IP: 20.19.239.7	443	In	Incoming communication with iO for business calls. Only useful for SaaS ERPs
papi.lestudio.app	443	Out	Flowwa API gateway (PAPI)
sb-papi-prod-00000001-iO.servicebus.windows.net and sb-papi-prod-00000001-iO-02.servicebus.windows.net	443	Out	Azure Service Bus, secure link between iO and the local service

3.1 Flowwa

Agicap collaborates with Flowwa and its platform IO Manager to integrate with on-premise ERPs such as Sage 100, Sage FRP 1000, and EBP (not the cloud ones). This partnership enables seamless data exchanges between our clients’ ERP systems and Agicap, supporting both business data imports (e.g., invoices, credit notes, sales orders) and the export of banking files from Agicap to the ERP.

All connections, configurations, and data flows are set up and maintained in close collaboration between Agicap’s technical teams, our clients, and Flowwa as the integration provider.

What is Flowwa? It is a data integration platform (iPaaS) specialized in interconnecting SaaS software and ERPs.
Security: Flowwa ensures the secure transport of data without permanently storing your accounting data on its servers, thus guaranteeing optimal confidentiality.

3.2 Synchronization Frequency

Data collected through IO Manager is sent to Agicap’s APIs in real time just after each data retrieval by the ‘IO Manager Agent’:
- Open API : For expected cash transactions in Treasury module (synched in Agicap only during a whole hour or hour and a half - e.g., 08:00 or 08:30 or 10:00 or 10:30…)
- Public API : For business documents in Accounts Receivable module

Import/export flows are secured: Flowwa does not store or visualize client data, it only handles transmission through the IO Manager platform.
For each integration, an identifiable connection is created in Agicap (as a cash-flow integration or as a business integration, depending on the use case explained below).
In Agicap, the connection will synchronize only if there is some new data or updates to synchronize.
Synchronization times and frequency are configured during implementation: the connector can synchronize as many times per day as needed.

3.3 Multi-Entity and Multi-Currency Support

The connector supports multi-entity and multi-currency setups.
Agicap creates one account per entity (company) and per currency in the Treasury module.
Example: Company ALPHA (EUR), Company ALPHA (USD), Company BETA (EUR), Company BETA (USD).

3.4 Data and Synchronization Customizations

Customizations can be applied to adapt the labels, dates or amounts of the imported data. Feasibility is studied by the Agicap technical team.
The synchronized data can be filtered according to specific rules. Feasibility is studied by the Agicap technical team.

3.5 Pre-Matching (Pré-lettrage) Support

Pre-matching is supported: the amount shown in Agicap is only the remaining unpaid amount, not the total invoice amount.
Transactions pre-matched in Sage FRP 1000 appear in Agicap with their open (unpaid) balance only.

4. Flows & Use Cases

Here are the functionalities available via the connector. Some flows are marked as "Beta", meaning they are in gradual deployment or final testing phase.

For more technical details on additional settings and limitation per use cases, go in appendix

Note: For BETA features, an additional deployment timeframe may be required depending on the complexity of your environment.

⚠️ It is not possible to feed the Accounts Payable Agicap module with a Sage FRP 1000 connection.

5. Frequently Asked Questions (FAQ)

Can there be multiple synchronizations per day?

Yes, synchronization times and frequencies are configurable during implementation; multiple daily syncs are possible.

What happens if a client only wants certain accounts or journals?

During implementation, the tech team can set filters for included/excluded accounts and filtered journals.

Where can I see the status of synchronizations?

The last synchronization date is displayed next to the connection name in Banks & Integrations. Detailed logs and traceability information can be requested from Agicap Support.

Are partial payments taken into account in Treasury?

An operation entered in Treasury impacted by a partial payment will be displayed directly with its remaining amount.

How are pdfs synced to Sage?

The file is uploaded by Flowwa in a temporary folder. The file path is updated in Sage. Sage's objets metiers move the file to a media directory and creates the link.

6. Technical Appendices

6.1 Database Access per Flow

Flow	Access to the Sage FRP 1000 database
Imports (business documents, expected transactions, chart of accounts)	Read-only SQL access.
Payment files	The only flow that writes into the database, either through a module signed by Flowwa (DSM, installed by your integrator) or through a PowerShell script.
Bank journal export	The write method is being finalized. The related prerequisites will be shared with you before the setup.

6.2 API & Security

Data is sent to Agicap through REST APIs over HTTPS (TLS encryption).
Flowwa only handles the transmission of data and does not permanently store your accounting data.
For import flows, a SQL user with read-only access can be created for Agicap (optional, see 2.1).

Need help or more information?

Contact your Agicap support.

Sage FRP1000