ERP Connector Overview
ERP Connector is an on-premise application that fiscalizes invoices straight from your ERP or Odoo cash register. It signs them either with the SDC (Sales Data Controller) on your own network, or in the cloud through FiscoBridge Cloud POS — you choose which when you set it up.
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 and reads your ERP over your LAN. It then signs through the SDC in your office or, if you prefer, through FiscoBridge Cloud POS.
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, MYOB AccountRight desktop, Odoo Accounting, Sage 300, Odoo Point of Sale |
How invoices are signed | Cloud signing with your uploaded certificate | Your own SDC and secure element, or FiscoBridge Cloud POS |
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, Sage 300 and an MYOB AccountRight company file kept on your own computer 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, MYOB AccountRight desktop, 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 signs the invoice. The invoice goes to the signing option you chose — the SDC on your network, which signs it with your secure element, or FiscoBridge Cloud POS, which signs it in the cloud.
It writes the result back. Where the ERP allows it, 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 |
MYOB AccountRight | Not attached — saved on the connector's machine instead | A |
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.
MYOB AccountRight cannot take file attachments through its API, so the receipt PDF for those invoices is kept in %LOCALAPPDATA%\ErpConnector\journals on the connector's machine, in one folder per integration and month. The verification link in the invoice Comment lets anyone open the receipt from MYOB itself. See Setting up the connector for how MYOB is connected.
Two ways to sign: SDC or Cloud POS
Every invoice and Odoo POS receipt the connector handles is signed the same way — one choice, made once on the Fiscalization tab, covers all integrations and the cash register.
Local fiscal device (SDC) | FiscoBridge Cloud POS | |
|---|---|---|
Where signing happens | The SDC application on your network, with your secure element (smart card) | In the FiscoBridge cloud |
Internet needed | No — it keeps signing while the internet is down | Yes — a constant connection |
Hardware | A smart card reader and card, with the SDC running on this machine or another on your network | None — no card, no reader, no SDC |
Licences | An SDC Pro licence, plus the connector's activation key | An active Cloud POS subscription and API key, plus the connector's activation key |
Best when | Internet is unreliable, or you already run an SDC on site | The internet is always on, or the smart card and reader sit on a remote server you cannot rely on or reach |
Choose Cloud POS when the site has a constant internet connection and you would rather not run a smart card reader and SDC at all. Choose the SDC when the site must keep trading through internet outages.
Switching is safe at any time. An invoice is signed by whichever option was selected when it was processed, and an invoice that has already been signed is never signed again by the other option — a retry reuses the fiscal result it already has.
Invoices signed through Cloud POS count towards your Cloud POS plan's monthly invoice limit. When the limit is reached, signing stops until you upgrade; there is no overage billing.
What you need before you start
The connector always needs its own activation key, plus whatever your chosen signing option needs. The connector reads your ERP and feeds the signer — it does not sign anything itself.
Licence | What it covers | Where it comes from |
|---|---|---|
ERP Connector activation key | The connector on one machine — needed whichever way you sign | Issued by your FiscoBridge partner |
SDC Pro licence | The SDC that signs each invoice — only if you sign with the SDC | Applied in the SDC itself — see Applying a License |
Cloud POS subscription and API key | Signing in the cloud — only if you sign with Cloud POS | Your FiscoBridge account — see Custom integration for how to create the API key |
If you sign with the SDC, it must be on a Pro licence — a Lite licence is not enough. The SDC's License tab shows which one you have. 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.
For the SDC: the SDC installed on site, with a working secure element.
For Cloud POS: a constant internet connection from that machine. No SDC, smart card or reader is needed.
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. MYOB AccountRight needs MYOB's own API add-on running on the same computer as the connector.
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 signer as training documents, so you can run the whole flow — polling, tax mapping, write-back — without issuing real fiscal invoices and without entering payment details. With the SDC, test against a sandbox smart card. 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