# Connect the ERP you already use.

> 25+ ERPs; Odoo, Holded, Tango, SOS Contador and EternumPRO via live API. ERP without a connector? Upload the journal in Excel or use the API.

Updated: 2026-10-02 · Author: Santiago Viglione (Fibady) · https://www.fibady.com/en/integrations

Fibady connects to 25+ ERPs, with a live API for [Odoo](/integrations/odoo), [Holded](/integrations/holded), [Tango](/integrations/tango), [SOS Contador](/integrations/sos-contador) and [EternumPRO](/integrations/eternumpro), and turns their entries into consolidated reporting. If your ERP has no connector, you export the journal to Excel, upload it and Fibady adapts it: you map the columns once and the format is reused on later loads. For in-house systems there is the API, and if you want a native connector for your ERP, we build it for a one-off fee with a fixed quote.

## Four ways to connect

Fibady connects through a connector to 25+ ERPs, through an Excel export of the journal, through the API or with a connector built to order.

| Mode | ERPs | How it works | Time to first report |
|---|---|---|---|
| Connector | 25+ ERPs, with a live API for Odoo, Holded, Tango, SOS Contador and EternumPRO | You authorise the connection; entries and accounts sync on their own (daily, weekly or monthly) | Minutes to load; 1–4 h of mapping |
| Excel journal | Any ERP without a connector | You export the journal to Excel; Fibady adapts it to its format and remembers the column mapping next time | Same day |
| API | In-house systems | Your team sends the entries to Fibady through the API | Depends on your build |
| Connector on request | Any ERP with an API | We build the connector for your system; then it works like Odoo | Fixed quote · 4–8 weeks |

## What if your ERP is SAP or a customised version?

We connect it all the same. We have a team that specialises in API connectors and builds the connector for your ERP as it is. It is the usual case with SAP, where every installation is a world of its own, and with versions of ERPs we already connect that carry their own developments. We analyse your setup, agree a fixed one-off quote and, while it is being built, you start with the journal in CSV.

## If you need something we don't have, let's talk

Our vision is to sit between the data and the decision: to be the tool that helps decision-makers decide better, with complete information. If what you need fits that vision, we can build it with you. Tell us in the [demo](/demo).

## Frequently asked questions

### What if my ERP is not on the list?

You export the journal to Excel, upload it and Fibady adapts it: you map the columns the first time and the format is reused. For in-house systems you can use the API. If you want a native connector, we build it for a one-off fee with a fixed quote, in 4–8 weeks.

### Does Fibady write anything to my ERP?

No. Every connection is read-only. We never create or modify entries.

### Can I consolidate entities running different ERPs?

Yes. Each entity connects its own way (connector, Excel journal or API) and the group consolidates in Fibady.

### How much does the integration cost?

Nothing beyond the subscription: $200 per entity per month, all included. Only the connector on request is quoted separately, as a one-off fee.

Book a demo: https://www.fibady.com/en/demo