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

Microsoft Dynamics 365 Business Central is a cloud-based ERP solution for small and mid-sized businesses. This integration allows you to synchronize Business Central data with Agicap, supporting business document import and bi-directional data flows.

2.1 Access & Credentials Prerequisites

Deployment: Business Central Online (Cloud) only — On-Premise deployments are not supported through this connector.
User Role: The user must have Administrator permissions on the Business Central environment to authorize the integration.
Business Central extension: The Business Central extension required by the integration must be installed and up to date in your environment (see the Chift help page below).

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 Agicap Support on the Chift platform, using the credentials provided by your Business Central administrator.

2.3 Functional Prerequisites

Agicap API token: Chift connects to Agicap with an Agicap API token. A single token is enough for all your entities. It must be generated by an Agicap administrator: an organization administrator for the Public API (standard setup), or an administrator of the entity being connected for the Open API (older connections).
Tax key (VAT code): For the entries exported to Business Central, the tax key (TaxKey) set in Agicap must correspond to a VAT code that exists in your Business Central environment (see the FAQ for an example).
Matching keys for the bank journal export: For the bank journal export to also match (letter) the related invoices in Business Central, these invoices must first have been imported into Agicap with the right matching keys: the invoice number and the invoice due date (format dd/mm/yyyy). Please check this before the connection is set up.
Bank journal and expected transactions: If you export your bank journal through Chift, do not import your expected (forecast) transactions through Chift as well.
Purchase journal export: The Agicap Supplier Invoice Management (SIM) or Spend module must be enabled on the entity.

3. General Information

3.1 Chift

Agicap collaborates with Chift to integrate with a wide range of cloud and on-premise ERPs.

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 Agicap Support.
Security: Chift acts as a secure data-transport layer between your ERP 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.
A dedicated, identifiable connection is created for each integration.

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 Reception (France only)	🟡 Available with limitations			if other flow in addition of the purchase journal export are required like import purchase order or reception order in P2P an SFTP is required
PA Emission (France only)	🔴 Not available
Auto reconcile invoices in ERP via Bank Journal export	🔵 In Beta	Agicap → ERP	Leverage Agicap reconciliation and bank journal module to automatise the bank journal creation + auto reconciliation of AR/AP invoices	Jun 2026 : Auto-reconciliation only works when invoices were previously imported from the ERP into Agicap (via Business Documents). Invoices originating from Agicap (not imported from the ERP) will not be auto-reconciled.
Export forecasts from Agicap	🔴 Not available	Agicap → ERP
Export intragroup financing from Agicap	🔴 Not available	Agicap → ERP
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	Only header level info
Export bank journal without automatisation of reconciliation TRY to ERP	🔵 In Beta	Agicap → ERP	Leverage Agicap reconciliation and bank journal module to automatise the bank journal creation
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
Import Business Docs in Agicap	🔵 In Beta	ERP → Agicap	Feed TRY with expected transactions, AR with invoices to be paid and to follow-up on + the PDF
Export AP purchase orders 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 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 follow-ups from Agicap AR	🔴 Not available	Agicap → ERP
Export Financial Investments from Agicap	🔴 Not available	Agicap → ERP
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
Export Debt from Agicap	🔴 Not available	Agicap → ERP
Import Chart of Accounts / Third Party Codes in Agicap	🔵 In Beta	ERP → Agicap
Import Payment Files in Agicap	🔴 Not available	ERP → Agicap	Leverage Agicap banking connectivity to automatize the payment process and provide a better security

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

4.1 Business documents import: history

Initial import: invoices with an invoice date within the last 6 months . When the ERP allows Chift to retrieve only updated records, all older invoices that are still unpaid are imported as well.
Daily updates: in that case, invoices created or updated since the last synchronization are retrieved every day. Otherwise, Agicap re-reads every day a rolling window of invoices going back to 6 months before the activation date, capped at 12 months .

4.2 Pre-accounting export options (purchase journal / bank journal)

When the export flow is configured, the following options are set with you:

Journal: the purchase or bank journal of the entity in Business Central.
Suspense accounts: if an account used in Agicap has no match in your Business Central chart of accounts, the exported entry is recorded in these suspense accounts.
Synchronization time: expressed in UTC (e.g. 06:00 UTC = 07:00 in France in winter).
Start date: no entry dated before this date is exported.
Draft option: exports entries as drafts in the ERP for a final review. Not recommended: we advise reviewing entries in Agicap instead.
Invoices without attachment: choose whether they are included in the exported entries.
Entry label: purchase title, supplier name, or both (recommended).
Supporting documents: receipts and invoices from SIM or Spend can be attached to the exported entries. Accounts Receivable documents cannot be exported via Chift.
Export errors, if any, are visible directly in your Agicap account.

5. Frequently Asked Questions (FAQ)

Is Business Central On-Premise supported?

No. Only Business Central Online (Cloud) is supported through this connector.

What must be in place in Business Central before the connection?

A user with Administrator permissions, and the required Business Central extension installed and up to date in your environment.

Which tax key (TaxKey) should be entered in Agicap?

The tax key must identify a VAT code of your Business Central environment. You can use either the ID of the VAT code or its code without special characters (not case-sensitive). For example, for this VAT code in Business Central:

{
  "id": "1a2b3c4d-0000-0000-0000-000000000000",
  "code": "DRITTLAND / EUST",
  "label": "EK: Drittland Einfuhrumsatzsteuer",
  "rate": 100
}

the tax key in Agicap can be 1a2b3c4d-0000-0000-0000-000000000000 or DRITTLANDEUST (or drittlandeust ).

My invoices are not matched in Business Central after the bank journal export. Why?

The invoices must have been imported into Agicap with the expected matching keys (invoice number and invoice due date). Check that these keys are present on the imported invoices.

How far back are invoices imported?

Up to 6 months based on the invoice date at the first import (plus older unpaid invoices when the ERP supports it), then daily updates within a 6 to 12-month window.

Can I export my bank journal and import my expected transactions through Chift at the same time?

No. If the bank journal is exported through Chift, expected transactions must not be imported through Chift.

Can I trigger a synchronization manually?

No. Synchronization runs automatically once per day, at the time set during configuration (in UTC).

Who must generate the Agicap API token?

An Agicap administrator: an organization administrator for the Public API, or an administrator of the connected entity for the Open API. One token is enough for all entities.

The purchase journal export is not available. Why?

The Agicap Supplier Invoice Management (SIM) or Spend module must be enabled on the entity.

Where can I see export or import errors?

Errors are displayed directly in your Agicap account.

6. Technical Appendices

Chift capabilities used by the bank journal export

Synchronization of the chart of accounts and third parties: GET /chart-of-accounts , GET /clients , GET /suppliers
Creation of bank journal entries: POST /journal-entries
Automatic matching (lettering): POST /matching

Need help or more information?

Contact your Agicap support.

Business Central - Chift