🔥 DOC TO SHARE WITH PROSPECTS:Google Doc version: GDOCPDF 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
SAP Business One (SAP B1) is an enterprise resource planning software for small and mid-sized businesses. This integration allows you to synchronize SAP B1 data with Agicap, supporting multi-entity setups and bi-directional data flows.
This section describes the prerequisites for using the connector.
2.1 Technical Prerequisites
| Prerequisite | Notes |
SAP B1 Version | Version 10 and subsequent versions | / |
SAP B1 Deployment Type | All deployment types supported: On Premise, Private Cloud, Public Cloud | Public/Private Cloud integrations require collaboration of the client's SAP System Integrator |
SAP B1 Database | SQL or HANA | / |
SAP B1 Service Layer | Must be active | Almost always active by default; if unsure, ask your System Integrator to verify or activate it |
SAP B1 User | One SAP B1 user with one of these license types: SAP Business One Indirect Access User, or SAP Business One Professional User | / |
Permission to access Database Tables | Access required to standard tables, plus CTG1 and OBOE | On-Premise: check |
IP Address Whitelisting | For Public/Private Cloud connections, whitelist Agicap's IP: | / |
2.2 Deployment Organization
The installation of this connector is a collaborative process that requires:
Your teams: For validation of access and selection of accounts to synchronize.
Your SAP System Integrator: For Service Layer activation, IP whitelisting (Cloud setups), and table access permissions.
Agicap technical team: For the connector setup and flow testing.
3. General Information
This SAP B1 connector is an in-house Agicap integration (no third-party integration provider). It uses SAP B1's native Service Layer API to exchange data securely between SAP B1 and Agicap.
3.1 Synchronization Frequency
Business Documents: once per day
Chart of Accounts: once per day (same as Business Documents)
Bank Journal Export: once per hour
Purchase Journal Export: once per hour
3.2 Integration Cost
No additional cost for clients.
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 |
Import Suppliers in Agicap | 🟠 Planned | ERP → Agicap |
|
|
Import POs & DN | 🔵 In Beta |
|
|
|
Import SAP Projects | 🟢 Available |
|
|
|
Import Analytical Plans | 🟢 Available |
|
|
|
PA Emission (France only) | 🟠 Planned |
|
|
|
PA Reception (France only) | 🔵 In Beta |
|
|
|
Auto reconcile invoices in ERP via Bank Journal export | 🔵 In Beta |
|
|
|
Import Business Docs in Agicap (incl. for AP) | 🟢 Available | ERP → Agicap | Feed TRY with expected transactions, AR with invoices to be paid and to follow-up on + the PDF |
|
Export intragroup financing 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 |
|
Import beneficiaries in Agicap | 🟠 Planned | 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 follow-ups from Agicap AR | 🔴 Not available | Agicap → ERP |
|
|
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 |
|
Import client base & contacts in Agicap | 🔵 In Beta | ERP → Agicap | Feed Agicap AR module with clients data from the ERP to avoid manual updates in Agicap |
|
Export Debt from Agicap | 🔴 Not available | Agicap → ERP |
|
|
Export Financial Investments from Agicap | 🔴 Not available | Agicap → ERP |
|
|
Export AP purchase orders from Agicap | 🔵 In Beta | Agicap → ERP | Use case for PDP to be precised (for French ERPs) |
|
Export Bank Journal from Agicap TRY to ERP | 🔵 In Beta | Agicap → ERP | Leverage Agicap reconciliation and bank journal module to automatise the bank journal creation + auto reconciliation of AR/AP invoices |
|
Import Chart of Accounts / Third Party Codes in Agicap | 🟢 Available | ERP → Agicap |
|
|
Export Purchase Journal from Agicap to ERP | 🔵 In Beta | Agicap → ERP | Leverage Agicap SIM OCR to digitalise the provider invoices and create them in the purchase journal with the associated PDF |
|
Export AP invoices from Agicap | 🔵 In Beta | Agicap → ERP | Use case for PDP to be precised (for French ERPs) |
|
Export forecasts from Agicap | 🔴 Not available | Agicap → ERP |
|
|
Export Bank Statements from Agicap to ERP | 🟡 In Beta with limitations | Agicap → ERP | Automatise the sync of the chart of accounts and third parties account between the ERP and Agicap | Only cfomb120 and camt053 - for other formats ask @Matthieu.landeche |
Note: For BETA features, an additional deployment timeframe may be required depending on the complexity of your environment.
7. Frequently Asked Questions
7. Frequently Asked Questions
🔌 On-premise agent (Agicap ERP Connector / agicapd ) — network, security & service info
🔌 On-premise agent (Agicap ERP Connector / agicapd ) — network, security & service info
What it is. For on-premise connections the client installs a small agent — the Agicap ERP Connector service ( agicapd , OS service name agicap-erp-connector ) — on a server next to the ERP. It opens an outbound-only tunnel to Agicap: no inbound port to expose and no inbound IP to whitelist on the client side.
Network. 100% outbound from the client over TCP 7000 , TLS 1.2+ , to host agicapd-server-1.agicap.com . ⚠️ This is different from 34.78.232.170 , which is Agicap's egress IP for cloud connectors reaching SaaS ERPs — it is not used by the on-premise agent.
Authentication. Fingerprint-based (generated at install, verified on each connection); TLS 1.2 minimum; no mutual TLS.
SAP credentials. Never stored in the connector or its database — stored encrypted by Agicap's Foundation service and withdrawn on demand at collect/push time.
Auto-update. None today — updating the agent is a manual re-run of the install script.
Collection cadence (SAP B1 defaults, currently hard-coded). Initial import window = last 3 months of business documents; sync every 12 h . Push: Bank Journals = manual button only; Purchase Journals & Bank Statements = every 12 h or manual button.
Full reference (security & network due-diligence): agicapd on-premise agent — security & network FAQ — di-business-on-premise-connectors-app.
Need help or more information?
Contact your Agicap support.
6. Technical Appendices
Need help or more information?
Contact your Agicap support.