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
Pennylane is a cloud-based accounting and financial management software. This integration allows you to synchronize Pennylane data with Agicap, supporting business document import and accounts receivable workflows.
2.1 Access & Credentials Prerequisites
Plan: A Pennylane plan Essential or above is required to activate the integration.
User Role: The user must have at least the gestionnaire role (Company settings > Team management).
For any questions regarding prerequisites and/or the method of collecting information, Chift has created a dedicated help page for each ERP.
2.2 Deployment Organization
The activation of this connector is straightforward: the connection is created and configured by the Agicap Support (CST) team on the Chift platform, using the credentials provided by your Pennylane administrator.
3. General Information
3.1 Chift
Agicap collaborates with Chift to integrate with cloud-based ERPs such as Pennylane.
What is Chift? Chift builds connectors to a variety of business softwares, all accessible through a single API. You can think of Chift as a "connector for business software." Agicap uses Chift as an integrator to establish connections with a wide range of ERPs that Chift already covers, instead of building an in-house connector for each one.
Purpose & how it works: The integration allows Agicap to securely (i) import key business documents from the client ERP into Agicap modules (Treasury, Accounts Receivable) and (ii) export accounting entries (purchase journal, bank journal) from Agicap into the client's ERP. Payment files and bank statements are not covered by Chift (see the Use Cases table).
Project setup: Each client integration requires a dedicated connection on the Chift platform. Connection creation and initial configuration are handled by the Agicap Support (CST) team.
Security: Chift acts as a secure data-transport layer between Pennylane and Agicap; data is exchanged through Chift's unified API.
See the complete Chift integrations list .
3.2 Synchronization Frequency
Data sync between Agicap and the ERP via Chift occurs once per day automatically.
Manual sync triggers are not available.
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 |
Auto reconcile invoices in the ERP via Bank Journal export | 🟡 In Beta with limitations | Agicap → ERP | Automatise the sync of the chart of accounts and third parties account between the ERP and Agicap | Jun 2026 : Auto-reconciliation only works when invoices were previously imported from the ERP into Agicap (via Business Documents). When invoices originate from Agicap and were not imported from the ERP, the reconciliation in Pennylane via Bank Journal export does not trigger. For now, when Chift cannot reconcile an exported entry, Agicap shows it like an export failure: the entry is marked as not imported, with the message "Chift cannot reconcile export". An evolution is planned to distinguish export failures from reconciliation failures. |
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 Import invoices in AR creates automatically clients with the couple counterparty name + counterparty ID → only these information are retrieved and no email address are added | |
Export Spend Bank Journal from Agicap | 🟢 Available | Agicap → ERP | Automatise the creation of bank journal entries in the ERP for the transactions made with the spend module in Agicap | |
Export intragroup financing from Agicap | 🔴 Not available | Agicap → ERP | ||
Export AP invoices from Agicap | 🔴 Not available | Agicap → ERP | Use case for PDP to be precised (for French ERPs) | |
Export forecasts from Agicap | 🔴 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 Payment Files in Agicap | ⚪ Standard SFTP | ERP → Agicap | Leverage Agicap banking connectivity to automatize the payment process and provide a better security | Link to standard SFTP process to apply: here |
Import Chart of Accounts / Third Party Codes in Agicap | 🟢 Available | ERP → Agicap | ⚠️ Pennylane has no generic third-party account: each supplier has its own account (e.g. 40100TOPSYS). On bank journal export, the counterpart account may not be filled automatically and may have to be set manually. | |
Export bank journal without automatisation of reconciliation TRY to ERP | 🟢 Available | Agicap → ERP | Leverage Agicap reconciliation and bank journal module to automatise the bank journal creation | Only the amount in the main currency is exported. The foreign currency amount is not sent (Pennylane accepts either the foreign currency amount or the exchange rate, not both). |
Export follow-ups from Agicap AR | 🔴 Not available | Agicap → ERP | ||
Export Financial Investments from Agicap | 🔴 Not available | Agicap → ERP | ||
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 Bank Statements from Agicap to ERP | ⚪ Standard SFTP | Agicap → ERP | Automatise the sync of the chart of accounts and third parties account between the ERP and Agicap | Link to standard SFTP process to apply: here |
Export Purchase Journal from Agicap to ERP | 🟢 Available | Agicap → ERP | Leverage Agicap SIM OCR to digitalise the provider invoices and create them in the purchase journal with the associated PDF | The sync uses the accounting module of Pennylane (not the invoicing module) For the import of the preaccounting in Pennylane : Prepaid Expenses/ Charges constatés d’avance do not import (27/02/2026) Exported entries cannot be modified one exported in Pennylane Analytical codes are exported only if the analytical plan is identical in Agicap and Pennylane. The analytical plan is not synced automatically. |
Import Business Docs in Agicap | 🟡 Available with limitations | ERP → Agicap | Feed TRY with expected transactions Feed AR with Business Documents (Invoices, Credit notes) | 1. ⚠️ Only purchase and sales journals are retrieved (no AN, bank journal, or OD). 2. ⚠️ A single invoice can't carry several expected dates → staged-payment invoices import as one date, so the TRY forecast timing might be wrong. 3. ⚠️ Only the total amount of partially paid invoices is retrieved (partial payments ignored) → outstanding amounts are overstated, so TRY expected amounts are inflated and the AR follow-up / DSO is inaccurate. 4. ⚠️ A document deleted or archived in Pennylane is only cancelled in Agicap if its invoice date falls inside the 12-month rolling sync window → older documents stay open in TRY and AR, so the cashflow forecast and the AR follow-up keep counting invoices that no longer exist in the ERP. Cancellation also happens at the next sync, not in real time. Workaround : ask support to delete these documents manually, the connector will not clean them up on its own. 5. ⚠️ PDF files are not imported. 6. ⚠️ Invoices received by email in Pennylane are processed overnight, validated by the client, then synced to Agicap the following night → up to 2 days of delay before they appear in TRY and AR. No manual resync is possible. 7. ⚠️ A document deleted and recreated in Pennylane gets a new ID → it is imported as a new document in Agicap, with no link to the previous one. |
Note: For BETA features, an additional deployment timeframe may be required depending on the complexity of your environment.
5. Frequently Asked Questions (FAQ)
6. Technical Appendices
Need help or more information?
Contact your Agicap support.