ERP connectors & synchronization
Why
Connectors feed the accounting software or ERP of a group, an accounting firm, or a partner from Tauraco's SYSCOHADA data, without rewriting the accounts, according to mappings declared by the company. The catalog states honestly what is native, what requires setup, and what is not supported.
How, in the application
Read the catalog. “Connectors” classifies each target with a maturity badge: Available, Beta, Setup required, or Not supported; a tooltip explains its meaning.
| Maturity | Targets | What is provided |
|---|---|---|
| Available | CSV and XLSX files; generic REST API; SFTP drop | Configured files; JSON delivery over https; SFTP drop with a mandatory server fingerprint (ports 22 or 2222). |
| Beta | Odoo 17, 18, and 19 | Partners and invoices sent as drafts; no reading from Odoo in this version. |
| Setup required | Sage 100, EBP, QuickBooks Online, Pennylane | Files in the expected format; not a native integration: the import template is configured in the target software. |
| Not supported | SAP, Microsoft Dynamics 365, Oracle Fusion Cloud ERP, Oracle PeopleSoft, Oracle NetSuite, Cegid, Xero, Sage X3, Sage cloud APIs | Descriptive sheet only; no connection possible. |
Configure a connection. “New connection” records the destination and its credentials. “Test the connection” is required before any synchronization and after each change; its message is deliberately generic.
Declare mappings. Mappings link Tauraco codes to those of the remote software: accounts, taxes, currencies, journals, and third parties. The engine never reclassifies an account and keeps SYSCOHADA numbering. A different remote currency causes the document to be rejected, unless the “Convert amounts at the ERP fixed rate” box is checked: conversion is then accepted only for a fixed parity (UEMOA or CEMAC CFA franc, Comorian franc, euro), declared in the document sent.
Synchronize and check. A dry run checks everything without sending anything. “Sync history” shows each run: “Partial” if documents are rejected, “Failed” in the event of a transport error; documents already sent count as ignored duplicates, and a reconciliation compares Tauraco and remote totals. Each rejection carries a reason, without stopping the batch: Required field missing, Account without mapping, Tax without mapping, Currency conversion not allowed, Unreadable date, Invalid amount, Unknown partner, Duplicate, Rejected by the remote software, or Invalid value.
Safeguards
- Mapping tables must be validated by an OHADA chartered accountant before the first live delivery.
- A connection's secrets are encrypted and never displayed again. If the destination changes, they must be re-entered.
- Internal or non-public destinations are refused, both when they are saved and at each run.
- Connectors have been validated on simulated environments, not on a publisher's real installation: start with a dry run on your own software.
- Managing connections is reserved for the company's owner and ERP administrator, as well as for platform administration.