Skip to main content
See what this connector supports ↓

​
Introduction

Sage 50 France, formerly known as Ciel Comptabilité, is a desktop accounting application for small businesses in France, covering bookkeeping, quotes and invoicing, and bank reconciliation. It runs on a local server, and the Chift connector reaches it through a local agent installed on that server.

​
Activate Sage 50 FR

​
Partner keys

No partner keys and no approval: the connector is ready to use.

Activate Sage 50 FR in your Chift account

One click in Connectors, then create connections straight away.

​
Connector settings

No connector-specific settings.

​
Test Sage 50 FR

​
Vendor fees

No vendor fees, for you or your end users.

​
Connect Sage 50 FR

Sage 50 FR setup guide for end users

The full step-by-step, with screenshots.

Local agent guide

Installing and running the local agent.
Before they start, your end users need:
  • Sage 50 version 5.5 or later
  • admin access to the server where Sage 50 is installed, with the server permanently accessible over the internet
  • a Windows user on the server whose session stays logged on, since the local agent runs under that user
  • their Sage 50 username, and password if that user has one
  • .NET Framework 4.8 installed on the server
To connect, they:
  • authorize COM access in Sage 50 (File > Options > Utilities > Miscellaneous > COM Access Authorisation)
  • retrieve the data path to their Sage 50 folder (File > Options > Information)
  • name the connection and enter the Sage 50 data file path, username, and password
  • download and install the local agent on the server running Sage 50, or send it to whoever hosts it

​
Rate limits

No rate limit documented by Sage.

​
Limitations & specificities

Only invoices whose first line uses a client account or a supplier account are returned: 411 for clients, 400 or 401 for suppliers. Invoices booked to other accounts are not listed.
One connection covers one Sage 50 data file. To connect several files, create one connection per file.
Requests fail with a 504 error when the local agent has not checked in for 35 minutes, for example when:
  • the server is off or offline
  • with agent 6.3 and later, the agent’s Windows session is logged off

​
Coverage