Integrator for EBP
Integrating the EBP API into your system
We wire EBP into your job-site app, e-commerce or billing stack: the document created in the product lands in EBP. First call: cloud or desktop. Not the same project.
- Senior product team
- business connectors in production
- from scoping to monitoring
Why work with an EBP integrator and why wire it into your platform?
EBP is a French management publisher for SMEs and micro-businesses: accounting, commercial management, payroll, and construction. You integrate it so your platform pushes quotes, invoices, customers and ledger entries into EBP with no double entry and no Monday CSV. EBP stays the commercial and accounting system of record; your product stays the field tool. The channel depends on the line: REST API for SaaS, SDK for Open Line desktop. Settling SaaS or desktop on the first call decides the project.
What EBP changes in your platform
The job closes, the invoice is born in EBP
The field app closes the job and creates the sales document in EBP Construction SaaS. Stock, VAT and dunning stay EBP's, with no retyping.
E-commerce pushes order and payment
Customers, items and orders flow down into Sales SaaS from your storefront. Payments carry their reference; no Monday CSV export.
Credit note or journal that reverses in Hubbix
Payroll, till, return or e-commerce inject a balanced journal-entry. The accountant stops the homemade FEC import and the parallel spreadsheet.
A portal reads balances from the same system
The customer sees their SaleDocument records and the third-party balance in your portal, without an EBP seat for everyone. EBP stays the source.
What it changes in your product
Engineering in service of a measurable outcome: invoice from the job site, clean Hubbix entries, SaaS or desktop settled.
Teams keep EBP, the field keeps the product
EBP remains the commercial and accounting source of truth. Your application remains the job-site or storefront tool. Nobody switches apps to invoice.
SaaS or desktop settled before the quote
Online EBP and desktop EBP are not the same project or timeline. We settle it in scoping so the quote holds.
Entries hold their balance from the product
Journals, accounts and VAT are signed off with your accountant before the first entry. You avoid rejections at close.
The customer journey does not break under volume
Flows are paced and large imports run asynchronously. A bulk customer push does not block same-day invoicing.
How we connect EBP to your system
Scoping
Where EBP enters your product: job site, storefront, portal, Hubbix. SaaS or Open Line, API product, developer subscription, volumes: without that, the estimate means nothing.
Mapping
Matching customers, items, documents and the Hubbix chart of accounts. Idempotence by document reference. This decides whether the product invoice posts correctly.
Development and testing
A connector wired into your business events. OAuth Authorization Code, atomic refresh rotation, 1 req/s queue, Import/Export jobs. Staging on EBP preprod.
Monitoring
Alert 7 days before refresh expiry, daily counter, import job tracking. You see an incident before it breaks billing or close.
What EBP brings to your platform
- Create quotes and invoices from the field
- Sales and Construction SaaS: sales documents created from your job-site or storefront app, without opening EBP on every job.
- Push ledger entries into Hubbix Accounting
- Balanced journal-entries from payroll, till or the product. Hubbix stays the micro-business firm's software, not desktop accounting.
- Feed Hubbix Sales from the front
- Customers, items and sales documents synced with your e-commerce or portal. One system for the customer journey.
- Bulk import without breaking the journey
- Async Import/Export jobs for volume. The 1 req/s quota holds while the product keeps invoicing.
The vocabulary of an EBP integration
- SaaS and Open Line
- Two worlds. The REST API does not work on desktop applications. Open Line integrates through the SDK (EBP.Invoicing.Application.exe), not through HTTP.
- Authorization Code
- The only documented OAuth flow. A daemon with no initial EBP login is outside the current contract. After that the refresh automates, provided you refresh at least once every 30 days.
- Single-use refresh
- Each refresh invalidates the previous one. Two workers in parallel break one of them. A lock per folder, persistence of the latest token, an alert before day 30.
- Early Adopters
- Current cap: 1 request per second and 10,000 per day. EBP says the limit may change later. We size against it, we do not bet on an increase.
- Hubbix
- Cloud TPE line (accounting and sales), distinct from historic Sales SaaS. Pagination, fields and headers (DomainId vs tenantid) diverge.
- Import job
- An async process followed by a status. That is the volume channel. One POST per record exhausts the quota before the file ends.
The real constraints of an EBP integration
SaaS and desktop do not mix
Most of the historic EBP estate is still Open Line. An EBP API page that ignores the SDK lies to the prospect. First scoping filter: are you on EBP SaaS or Hubbix?
No machine-to-machine
OAuth Authorization Code only. The init is manual (EBP login page, not customisable). The refresh lasts 30 days, single use: miss it and the connector stops.
The Early Adopters cap is low
1 call per second and 10,000 per day, pages of 100. A naive import dies. We go through the async Import API, and we count every status poll in the budget.
The subscription goes through EBP
Portal signup, product subscription, email validation, primary and secondary keys. Client ID and secret arrive by email, not through instant self-service. That delay belongs in the plan.
EBP or Sage, and what it implies
The choice follows whichever software already runs in your platform, rarely the technology. Both are product families, not a single API.
| Criterion | EBPThis page | SageMost common in SMEs |
|---|---|---|
| What the name covers | SaaS REST and Open Line desktop, two worlds | 100, Business Cloud, Active, X3, distinct channels |
| Cloud channel | REST v1 gescom / batiment / Hubbix | Active REST, X3 GraphQL, local business objects |
| Cloud authentication | Authorization Code, no M2M | OAuth 2.0 on Active and Business Cloud |
| Documented quota | 1 req/s and 10,000/day Early Adopters | Varies by line, to be read on the contract |
| Desktop estate | Command-line SDK, direct SQL discouraged | Windows business objects, agent on Partner Cloud |
| Integration effort | Medium, mostly the quota and the refresh | Medium to high, mostly the 100 line |
| The right case | SME already on EBP SaaS or Hubbix, business or e-commerce flow | SME already on Sage, needing a durable connector |
We claim no EBP partnership and no reseller status: we build on the documented REST APIs of the developer portal, and we work with your EBP partner on Open Line desktop.
What we measure on an EBP project
The other accounting tools we integrate
If EBP is not the core of your billing / job-site journey, these options are worth discussing during scoping.
EBPIntegrating the EBP API into your systemThis page
SageThe most common in SMEs. Several lines, from on-prem to a cloud API, to be scoped before the quote.
PennylaneA modern web API and collaboration with the firm, simpler to plug in than a historic ERP.
CegidLoop on the firm's side, XRP on the ERP side: access often runs through the accountant.We combine EBP with
The stack around EBP when we wire it into a job-site app or an e-commerce site.
EBP integration: your questions
We wire it into your product touchpoints: job site, storefront, portal, Hubbix. First qualify the line: SaaS (Sales, Construction, Hubbix) or Open Line desktop. On SaaS: developer portal signup, EBP validation, Authorization Code, encrypted refresh and a queue at 1 request per second. Volume goes through async Import/Export. The real difficulty is not the REST call; it is the mapping and respecting the quota.
To roll out EBP, train teams and sell licences, a reseller makes sense. To wire EBP into a custom platform, what counts is connector experience, rigour on the chart of accounts and command of the real quota. We claim no EBP partnership and no reseller status: we build on the documented REST APIs, with your EBP partner on desktop if needed.
It depends on the line, the number of flows and the volume to backfill. A sales document pushed from a site app costs far less than an e-commerce chain plus Hubbix journal plus customer portal. Two things weigh as much as the engineering: the time EBP takes to validate the API subscription, and the state of your masters (duplicate customers, VAT, journals). We scope the perimeter up front and give a firm estimate.
Yes, on Sales SaaS: customers, items, sales documents and transfers. The connector respects 1 req/s, deduplicates on a business key, and runs backfills through the Import API. On an Open Line desktop estate the channel changes (SDK, often an agent next to the workstation), so it is no longer the same quote. In both cases stock and VAT stay EBP's: we do not invent a second sales ledger.
The public table of contents of the developer portal, as read in August 2026, does not document a webhook resource. We therefore design polling bounded by the cap (1 req/s, pages of 100), with an overlap window to catch documents that changed. If EBP opens an event channel on your subscription, we add it; we do not promise it in the initial quote.
An EBP integration project?
Let's talk. 30 minutes to scope where EBP enters your platform (job site, storefront, Hubbix) and settle SaaS or desktop.
Discuss my EBP project