Skip to main content
See what this connector supports ↓

​
Introduction

EBP Comptabilité is accounting software for small and medium-sized businesses in France, covering bookkeeping, VAT returns, bank reconciliation and financial statements. The Chift connector reaches it through a local agent installed on the same server or computer. The online version, EBP Comptabilité en ligne, is not supported.

​
Activate EBP Comptabilité

​
Partner keys

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

Activate EBP Comptabilité in your Chift account

One click in Connectors, then create connections straight away.

​
Connector settings

No connector-specific settings.

​
Test EBP Comptabilité

​
Vendor fees

Software editor (you)

No fees.

End user

An EBP Offre de Services subscription: EBP requires it for software connected through its command-line module (Module SDK). Most local EBP customers do not have one, so it is an extra cost for them.
EBP sells the Offre de Services on quote, directly or through its resellers: see EBP’s article on the Module SDK.

​
Connect EBP Comptabilité

EBP Comptabilité 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:
  • EBP Comptabilité ELITE, version 24.8 or later, installed on their own server or computer (local subscription, not the online version), activated, with EBP’s command-line module (Module SDK) active on the license
  • an active EBP Offre de Services subscription, which EBP requires for SDK solutions such as this connector (see Vendor fees)
  • a Windows admin account on that machine, to install the local agent next to EBP Comptabilité
  • the full path of the company’s .ebp file
  • an EBP user created for the connection, with its password (recommended), so that writes do not clash with someone working in EBP under the same user
To connect, they:
  1. Name the connection, then download the local agent installer, or have it emailed to whoever installs it.
  2. Run the installer on the EBP Comptabilité server.
  3. In the local agent’s configuration window (Cockpit), enter the path of the company’s .ebp file, the EBP user and its password, and the SQL Server login if Windows authentication is not used.
  4. Check that both connection lines in Cockpit, EBP Accounting database and EBP Accounting application, pass.

​
Rate limits

No rate limit documented by EBP. Creates and updates go through EBP’s own import, run by the local agent one at a time per connection (one EBP company): about 8 to 10 writes per minute. The first write after a long pause can take up to about a minute. Reads are not slowed down by writes. In a burst of more than about 15 writes on the same company, the last ones get ERROR_GATEWAY_TIMEOUT (504). They may still be done in EBP: check there before sending them again.

​
Limitations & specificities

Not supported: each connection covers one EBP company, the one of its .ebp file. Other companies on the same server need a connection each.
  • Only client accounts (41…) and supplier accounts (40…) are returned, as in EBP’s own lists. Employees, social bodies and the State are only in the chart of accounts.
  • A client or supplier cannot be renamed.
  • is_company cannot be set on create: EBP creates a natural person.
  • An update cannot remove the contact’s last name or the address’s country.
  • On read, the address has no separate number or box: its lines are all in street. The same goes for the folder’s address.
  • Clients and suppliers without a general account of their own cannot be updated: those synchronized from EBP Gestion Commerciale and never posted, and those on a collective or auxiliary account.
  • language, currency, internal_notes and active are not written.
  • external_reference is not stored. On read, it holds the client’s or supplier’s EBP code. On create, it gives the account number when no account_number is sent.
  • Account numbers: letters and digits only, not ending with 0 (EBP drops trailing zeros), 15 characters at most. A client’s starts with 41, a supplier’s with 40, and both are longer than 3 characters. Without one, the connector builds a free number from the name.
  • Clients and suppliers created through Chift get a general account of their own, never an auxiliary account.
  • In a company that keeps auxiliary accounts, entries post a client or supplier to its auxiliary account, under its collective account. A client or supplier with an auxiliary account in a company that keeps none is refused.
  • Entries are created not validated, and posted is ignored: the accountant validates them in EBP.
  • The entry number has 20 characters at most, and is unique per journal and accounting year.
  • Inactive journals (blocked = true in GET journals) cannot receive entries.
  • Account numbers are sent as EBP stores them, without trailing zeros: 706000 is 706.
  • Lines on an employee account are refused: EBP Comptabilité has no employees.
  • VAT codes are checked but not stored: EBP takes VAT from the accounts. In tax_info, vat_account (or reversed_vat_account for a reverse-charge code) must be the tax_code itself, and tax_amount the code’s rate of its line, within 0.02.
  • start_date and end_date are not stored.
  • The PDF is attached to one line: the first client or supplier line, else the first line. A request is at most 4 MB, so a PDF of about 3 MB at most.
  • In a treasury journal that EBP balances at the end of each period, EBP books the bank or cash line itself, as one total per month. That line is returned as sent, without an id, and cannot carry analytic accounts or the PDF.
  • Clients and suppliers without an account number, or whose account is not in the chart of accounts yet, need force_general_account.
  • Invoices are the entries of sales and purchase journals that have a client or supplier line. Their id is the EBP entry number.
  • Lines are read back from the entry: one line per income or expense account line, with quantity 1. When the VAT of each line cannot be worked out from the VAT accounts’ rates, the lines have no tax and the VAT comes as lines of its own.
  • paid: the invoice is fully lettered in EBP, or every due date is settled. draft: simulated entries only. Entries not yet validated are posted.
  • A payment only lettered with the invoice has dedicated_amount 0.
  • Refused on create: withholding_tax, nl_payment_terms_split, status draft, and the force_financial_period query parameter.
  • Not stored on create: start_date, end_date, delivery_date, payment_term_id, payment_communication, shipping_country.
  • One due date only.
  • An invoice has no description of its own: each VAT line is labeled TVA - followed by the descriptions of its lines (200 characters at most).
  • A reverse-charge line has no tax_amount. The VAT due and deducted are booked at the code’s rate, the deducted VAT on the company’s only active deductible VAT account (44566…) of that rate.
  • An exempt tax code (export, intra-EU supply…) only works on an account set as exempt under that operation in EBP.
  • Without invoice_number, the journal must number its entries itself. The number has 20 characters at most and is unique per journal and accounting year.
  • Currencies, analytics, the PDF size and partners without an account follow the journal entry rules.
Entries and invoices in another currency:
  • EBP’s multi-currency feature (option Multi-devises) must be switched on in the company, and the currency must be in its list of currencies.
  • The amount is converted at the company’s latest rate on or before the entry date, not at the currency_exchange_rate sent, unless force_currency_exchange = true. The rate sent is used when the company has none. With neither, the entry is refused.
  • The rounding cent goes on the largest line, so that line’s rate is slightly off the one given. The lines on VAT accounts (445…) come first.
  • A journal kept in a currency of its own only takes entries in that currency.
  • Analytic accounts are the last level of each plan. The levels above them (for example regions grouping products) are not listed and cannot be created.
  • Endpoints without a plan use EBP’s main plan (the plan ticked Principal). Without one, they are refused.
  • On create, the code gives every level of the plan joined with . (for example AUTRES.CHIFT), under an existing parent. Each level has 13 characters at most: uppercase letters, digits, - and _. The name has 50 characters at most.
  • Analytic accounts are created active (active = false is refused). In an inactive plan, EBP creates them inactive. An update can only change the name.
  • debit, credit and balance cover every year, with no date filter. currency is always empty.
  • On entries, a line can go to several plans and several analytic accounts per plan. Each percentage becomes an amount in euros, the rounding cent on the largest share.
  • Refused on entries: an inactive plan or analytic account, an analytic account whose code another account of the plan shares, and an analytic distribution on an account that does not take analytics in EBP (usually client, supplier, VAT and bank accounts).
  • An account with an analytic grid in EBP can also get the grid’s other plans, returned with the entry.
  • Headings (root accounts such as 4, 40, 445) are not listed.
  • The account type is deduced from the account number (French chart classes). other_expense is accounts 66 and 67 only. tax_information is always empty.
  • EBP Comptabilité has no VAT codes of its own: the VAT codes returned are the company’s VAT accounts (445…), and their id is the account number. EBP’s exempt operations follow, as codes at 0 % with no account.
  • Reverse-charge VAT codes (reversed = true, accounts 4452…) only give their payable_account.
  • VAT code scope is unknown for “Assujetti établi hors de France”. country is never set.
Only files stored in EBP are returned. Links (URL, OneDrive) are not.
  • The folder’s main_currency is always EUR.
  • Reads only need the EBP database. Creates and updates need EBP Comptabilité installed on the machine of the local agent: they are done by EBP’s own import.
  • Writes fail while someone works in the company with the EBP user of the connection: EBP allows one session per user and company. Give the connection its own EBP user.
  • Writes are done one at a time per connection: see Rate limits.
  • The first read after the company’s database has been idle can take tens of seconds, since EBP’s databases close when unused. A large company can time out on it.
  • Companies with the “complete with zeros” account format: creates work in EBP but cannot be read back.

​
Coverage