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

EBP is business accounting software provided by EBP Informatique. This integration allows you to synchronize EBP data with Agicap, supporting multi-entity and multi-currency environments, payment pre-reconciliation, and advanced automation.

This section describes the prerequisites for using the connector.

2.1 Technical Prerequisites

The integration is compatible with on-premise EBP installations, including EBP hosted on your integrator's server (often called "cloud"), provided server and SQL access can be granted. EBP's own SaaS cloud offering is not supported.

Supported ✅	Not supported ❌
• EBP Accounting (Compta) on-premise, Pro and PME ranges, from version 21.0 • EBP hosted on an integrator's server or VM, if server and SQL access can be granted	• EBP SaaS cloud offering • EBP versions below 21.0

The exact version is confirmed during the deployment phase with your EBP integrator and the Agicap technical team.

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 EBP server: IO Manager Service Installation. This service is unique per customer, and its setup is part of the project onboarding.

2.3 Setup Prerequisites

EBP environment

Windows regional settings: the Windows culture must be set to fr-FR before the EBP database is installed on the server.
SQL instance: all the EBP companies of one project must be hosted on the same SQL instance. If your companies are spread over several SQL instances, one project per instance is required.
Database model: one SQL database = one EBP company = one Agicap entity.
Auxiliary accounting: not required. Without auxiliary accounting, the connector reads general accounts instead of third-party accounts.
Before the connection: delete the demo (fictitious) data from your Agicap account, so that it is not mixed with the data synchronized from EBP.

iO service access

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.
Folder rights: 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).

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 (one SQL database = one EBP company = one Agicap entity).
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 EBP 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.

Name	Status	Flow Type	Description	Limitations
PA Emission (France only)	🔴 Not available
PA Reception (France only)	🔴 Not available
[DEPRECIATED] Import only Expected transactions in Agicap	🔴 Not available	ERP → Agicap	Feed TRY with expected transactions	DEPRECIATED: legacy OpenAPI flow, replaced by "Import Business Docs in Agicap" (Public API). Do not use for new connections. This page will be deleted once all connections are migrated.
Export Reconciliation in ERP via bank journal	🔴 Not available
Export forecasts from Agicap	🔴 Not available	Agicap → ERP
Import Business Docs in Agicap	🟢 Available	ERP → Agicap	Feed TRY with expected transactions, AR with invoices to be paid and to follow-up on + Credit notes	PublicAPI: retrieves only the purchase and sales journals 1. Only the lettered entries of the current fiscal year and of the last 6 months of the previous fiscal year that meet the above criteria are synchronized 2. Only AN from the 4 past fiscal years can be retrieved (the original documents from the current fiscal year + if linked to an AN up to 4 years) ⚠️ Not available if it’s EBP Cloud, unless it’s hosted on the integrator’s server (in which case it can be treated as on-premise).
Export AP invoices from Agicap	🔴 Not available	Agicap → ERP	Use case for PDP to be precised (for French ERPs)
Import client base & contacts in Agicap	🔴 Not available	ERP → Agicap	Feed Agicap AR module with clients data from the ERP to avoid manual updates in Agicap
Export Purchase Journal from Agicap to ERP	🔴 Not available	Agicap → ERP	Leverage Agicap SIM OCR to digitalise the provider invoices and create them in the purchase journal with the associated PDF
Export follow-ups from Agicap AR	🔴 Not available	Agicap → ERP
Import beneficiaries in Agicap	🔴 Not available	ERP → Agicap	Feed Agicap list of beneficiaries in the payment module to avoid having to create/update them manually. + security need: avoid mistakes or fraudulent changes in Agicap
Import Chart of Accounts / Third Party Codes in Agicap	🔴 Not available	ERP → Agicap
Export Spend Bank Journal from Agicap	🔴 Not available	Agicap → ERP	Automatise the creation of bank journal entries in the ERP for the transactions made with the spend module in Agicap
Export Bank Statements from Agicap to ERP	🔴 Not available	Agicap → ERP	Automatise the sync of the chart of accounts and third parties account between the ERP and Agicap
Export intragroup financing from Agicap	🔴 Not available	Agicap → ERP
Export Financial Investments from Agicap	🔴 Not available	Agicap → ERP
Import Payment Files in Agicap	🔴 Not available	ERP → Agicap	Leverage Agicap banking connectivity to automatize the payment process and provide a better security
Export Debt from Agicap	🔴 Not available	Agicap → ERP
Export Bank Journal without automatisation of reconciliation TRY to ERP	🔴 Not available	Agicap → ERP	Leverage Agicap reconciliation and bank journal module to automatise the bank journal creation + auto reconciliation of AR/AP invoices
Export AP purchase orders from Agicap	🔴 Not available	Agicap → ERP	Use case for PDP to be precised (for French ERPs)

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

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 expected transaction in Treasury impacted by a partial payment will be displayed directly with its remaining amount.

Need help or more information?

Contact your Agicap support.