🔥 DOC TO SHARE WITH PROSPECTS:Google Doc versionPDF version:Fichier non disponible

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

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

This integration only works for FRANCE and this section describes the prerequisites for using the connector.

2.1 Technical Prerequisites

The integration is compatible with the majority of the Sage 100 ecosystem.

Supported Versions ✅	Partially supported 🏗️	Not supported versions ❌
• Sage 100 Comptabilité (v6 et +) • Sage 100c • Sage 100c Comptabilité • Sage 100 i7 • Sage 100 Cloud • Sage 100 Entreprise • Sage 100 Suite comptable et financière	• Sage 100 Sage Partner Cloud (SPC, hosted on Sage Cloud/Azure) → Beta for: business documents, purchase journal export, bank journal export & payment files (not tested yet) → ⚠️ Prerequisite: iO execution agent must be installed inside the SPC environment	• Other products outside Sage 100 suite • Sage 100 Gestion commerciale • Sage 100 Paie • Sage 100 Online, Sage Hébergé (private Sage cloud hosted) • Sage 100 Essential Comptabilité 7.00 cloud / Sage Online (not yet available)

How to check your version

Open Sage 100
Click " ? " then " A propos de… "

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: IO Manager Service Installation. This service is unique per customer, and setup is part of the IO Manager project onboarding. See Appendix for detailed set up prerequisites

3. General Information

This section describes the global infrastructure that supports data exchange.

2.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 (CS Tech & PKM), 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.

2.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.
In Agicap, the connection will synchronize only if there is some new data or updates to synchronize.

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

Name	Status	Flow Type	Description	Limitations
Auto invoice reconciliation via bank journal export	🔵 In Beta			Some clients are live with this Beta, be it with invoices imported to the ERP Agicap Purchase Journal or invoices exported from the ERP via Business documents
PA emission	🟠 Planned	Agicap → ERP		SFTP for now
PA reception	🔵 In Beta	Agicap → ERP
Import only Expected transactions in Agicap	🟢 Available	ERP → Agicap	Feed TRY with expected transactions	OpenAPI connection: This type of connection is destined to be depreciated
Export AP purchase orders from Agicap	🔴 Not available	Agicap → ERP	Use case for PDP to be precised (for French ERPs)
Export Debt from Agicap	🔴 Not available	Agicap → ERP
Export intragroup financing from Agicap	🔴 Not available	Agicap → ERP
Export Bank Statements from Agicap to ERP	🟢 Available	Agicap → ERP	Automatise the sync of the chart of accounts and third parties account between the ERP and Agicap	Statements are exported to a folder on Client server but not directly in Sage
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)
Export follow-ups from Agicap AR	🔴 Not available	Agicap → ERP
Export Financial Investments from Agicap	🔴 Not available	Agicap → ERP
Import Payment Files in Agicap	🔵 In Beta	ERP → Agicap	Leverage Agicap banking connectivity to automatize the payment process and provide a better security	Currently not available if the client is on Sage SPC
Import client base & contacts in Agicap	🟠 Planned	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 (incl. PDFs)	🟢 Available	Agicap → ERP	Leverage Agicap SIM OCR to digitalise the provider invoices and create them in the purchase journal with the associated PDF	The entries can be exported only in one code journal per entity
Export Bank Journal TRY to ERP	🟢 Available	Agicap → ERP	Leverage Agicap reconciliation and bank journal module to automatise the bank journal creation + auto reconciliation of AR/AP invoices	Not working if the “centralisation en fin de mois” is activated on Sage 100 FR in the “journal de trésorerie” setting (one monthly bank journal entry produced each end of month)
Export AP invoices from Agicap	🔴 Not available	Agicap → ERP	Use case for PDP to be precised (for French ERPs)
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
Export forecasts from Agicap	🔴 Not available	Agicap → ERP
Import Chart of Accounts / Third Party Codes in Agicap	🟢 Available	ERP → Agicap	The import is only for TRY. To retrieve the data also in AP, an AFT is necesserary.
Export Spend Bank Journal from Agicap	🔵 In Beta	Agicap → ERP	Automatise the creation of bank journal entries in the ERP for the transactions made with the spend module in Agicap	1 client live

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?

Last sync date will be mentioned next to connection name in tab Bank & Integration sync status and logs and traceability information can be accessed only by 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

Setup Prerequisites

Before proceeding with the configuration of the Sage 100 connection, please verify and validate the following items:

Operating System: Windows Server 2016 (or higher) or Windows 8 (or higher).
Database Management: SQL Server Management Studio (SSMS) must be installed on the Sage 100 server.
Framework: .NET Framework version 4.7.2 (or higher) must be installed on the SQL Server.
SQL Server Version: Minimum version 2016 (version 13.X).
Sage Components: The "Sage 100 Objets Métiers" (Business Objects) service must be installed in your Sage 100 environment.
Permissions: Data writer access is required for journal entry use cases.

Notes on iO Service Access

The connector implementation involves installing a Windows service that reads from and writes to Sage 100 databases. You must ensure that this service has sufficient permissions on the folders and databases it needs to access.

If the iO service is not run under the Local System Account, a dedicated Windows account must be created with read/write permissions on the relevant Sage 100 SQL databases.

This account must be configured:

As a SQL Server login.
On all SQL instances likely to be used by plugins relying on Sage 100.

If the server hosting the iO service is different from the SQL server:

The service account must be a Domain Account .
It must have the appropriate authorizations on the remote SQL instance

Data Collection & Filtering

The IO Manager service routinely queries the client’s ERP for new or updated data.
The frequency and schedule for these queries can be configured per project in IO Manager.
Filters can be applied to restrict data collection by journals or general accounts directly in IO Manager.
A specific fiscal year retrieval can be set up directly in IO Manager.

General information on data flows, security, data fields

Data Synchronization Flow

1️⃣ A scheduled task starts the Sage connector service.

2️⃣ The service queries the Sage database for all unreconciled accounting entries closed Customer and Vendor Invoices.

3️⃣ The service calls the Agicap API to create, delete, or update entries as needed.

Data and synchronization customizations

Agicap customization can be applied in order to adapt labels, dates or amounts of the data imported (the feasibility has to be studied by the Agicap technical team).

The data synchronized can be filter out regarding specific rules (the feasibility has to be studied by the Agicap technical team).

API & Security

REST API over HTTPS (TLS encryption)
Rate limiting: 100 requests/min/user; above this, a HTTP 429 error is returned; infrastructure can support 500k+ requests from over 150 users in a few hours
Authentication: token from Agicap interface; used in API authorization (not in header)
No SQL/code injection risk: only JSON input; objects are strictly formatted
Databases tables used: F_ECRITUREC, F_COMPTET, F_COMPTEG, F_JOURNAUX

Multi-Entity and Multi-Currency Support

Supports multi-entity and multi-currency setups. Agicap creates one account per entity (company) per currency in Treasury module.

Example:

Company ALPHA (EUR), Company ALPHA (USD)
Company BETA (EUR), Company BETA (USD)

Data Fields & Date Handling

Sage 100 Date Logic

Billing Date

Combination: JM_date (month/year) + EC_jour (day)
Example:**F_ECRITUREC_JM_Date = 2023-11-01F_ECRITUREC_EC_Jour = 8**→ BillingDate: 2023-11-08

Payment Date

If reconciled: use EC_Echeance field
If reconciled and EC_Echeance is empty: fallback to Billing Date (JM_date + EC_jour)
If unreconciled: use Billing Date

Details per use cases

Export Banks Files to Sage 100

This connector allows customers to use Agicap as a datasource for exporting bank files into their ERP.

💡

Automatic export of bank files collected in Agicap to a designated folder on your Sage 100 server.
Files will NOT be automatically imported into Sage 100; manual import is required.
Any bank file available via Agicap’s public API is eligible.

The customer still needs to manually import the exported file into their ERP. This connector can only transfer the file to a designated folder on the customer’s server but does not trigger the import process in the ERP.

Import Chart of account (TRY, AR)

Additional settings
- IO
  - ⚠️ you need to fill the source on the “business documents / Engagés” tab
  - Check the “active” case on “Supplier Accounts” and “General Accounts”

Sage FR 100