ERP Connector Overview
ERP Connector is an on-premise application that fiscalizes invoices straight from your ERP or Odoo cash register, using the Smart Device Client on your own network.
Cloud integrations vs. the on-premise connector
Both do the same job, and both are fully supported — they differ in where the software runs. Cloud integrations run on FiscoBridge servers: you authorize Xero or MYOB once and there is nothing to install or maintain. ERP Connector runs on your machine, reads your ERP over your LAN, and signs through the SDC in your office.
Cloud integrations | ERP Connector | |
|---|---|---|
Where it runs | FiscoBridge servers | A Windows PC or server on your network |
Systems | Xero, MYOB, Zoho Books, QuickBooks, Odoo Accounting, Cloudbeds | MYOB EXO, Odoo Accounting, Sage 300, Odoo Point of Sale |
Fiscal device | Cloud signing with your uploaded certificate | Your own SDC and secure element |
To set up | Authorize the connection, nothing to install | Install and keep a machine running |
Licensing | Integration plan on your account | One activation key per machine |
Which one you use is decided by your ERP, not by preference. Choose ERP Connector when your ERP runs inside your own network and is not reachable from the internet — MYOB EXO and Sage 300 typically are. If your system is on the list of cloud integrations, use that: it is quicker to set up and there is nothing to keep running.
What it connects
ERP invoices — polled. MYOB EXO, Odoo Accounting and Sage 300. The connector asks each ERP for newly posted invoices on an interval you choose.
Odoo Point of Sale — pushed. The connector opens a small endpoint on your network that the Odoo POS cash register calls as each order is paid, and answers with the fiscal result while the cashier waits.
How it works
It watches your ERP. On your chosen interval the connector asks the ERP for sales invoices posted (or paid) since it last looked.
It maps the tax codes. Each line's ERP tax code is translated to the fiscal tax label your SDC expects, using a mapping you configure once per integration.
It fiscalizes through your SDC. The invoice goes to the Smart Device Client on your network, which signs it with your secure element.
It writes the result back. A fiscal receipt PDF is attached to the invoice, and a note carrying the fiscal number and verification URL is added to it.
You watch the results. The Fiscalized invoices tab lists every invoice the connector has handled, what succeeded, what failed and why — and lets you retry anything that needs it.
Because the connector polls rather than waiting for a push, an ERP invoice is normally fiscalized within a few minutes of being posted — not instantly. Odoo POS orders are different: they are fiscalized on the spot, as part of closing the order.
What gets written back to each system
System | Fiscal receipt PDF | Fiscal note |
|---|---|---|
MYOB EXO | Attached to the debtor transaction | History note on the debtor |
Odoo Accounting | Attached to the invoice | Message in the invoice chatter |
Sage 300 | Added to the invoice's attachments | Written into the invoice comment |
If fiscalization fails for good, the connector writes a failure note back the same way, so the reason is visible to whoever works in the ERP.
What you need before you start
Two FiscoBridge licences are involved, and fiscalization needs both. The connector does not replace the SDC — it feeds it, so the SDC must be licensed in its own right.
Licence | What it covers | Where it comes from |
|---|---|---|
SDC Pro licence | The Smart Device Client that signs each invoice | Applied in the SDC itself — see Applying a License |
ERP Connector activation key | The connector on one machine | Issued by your FiscoBridge partner |
ERP Connector requires the SDC to be on a Pro licence — a Lite licence is not enough. The SDC's License tab shows which one you have.
Neither licence works without the other: an unlicensed SDC will not fiscalize against a production card, and an unlicensed connector will not send it anything.
You also need:
A Windows PC or server on the same network as your ERP, left running.
The Smart Device Client installed on site, with a working secure element.
Your ERP's API access, licensed from your ERP vendor. MYOB EXO, for example, sells its API as a paid annual add-on — the connector cannot read invoices without it.
One activation key covers one machine. If you run the connector on two servers, you need two keys.
Testing before you go live
Every integration has a Training mode switch, and Odoo POS has its own. With it on, documents are sent to the SDC as training documents, so you can run the whole flow — polling, tax mapping, PDF write-back — against a sandbox smart card without issuing real fiscal invoices and without entering payment details. Fiscalizing real invoices requires a paid plan and an activated licence.
Next steps
Setting up the connector — install it, point it at your SDC, connect your ERP and map your tax codes
Running the connector — day-to-day monitoring, retries and troubleshooting
Activating a connector — enter your key, or activate a machine with no internet access