Setting Up the Connector

This page takes a fresh machine to a working connector: install it, point it at your fiscal device, connect your ERP, map your tax codes, and — if you use the Odoo cash register — switch on the Odoo POS endpoint.

Work through it in order. Each step depends on the one before it.

Before you start

  • A Windows PC or server that stays on, on the same network as your ERP and your SDC.

  • The SDC running on a Pro licence, with its secure element ready. A Lite licence is not enough — check the SDC's License tab, and see Applying a License if you need to apply or upgrade one.

  • ERP API access licensed and reachable from that machine.

  • An ERP Connector activation key from the Client Portal, one per machine. This is a separate licence from the SDC's, and you need both.

1. Install ERP Connector

  1. Run the ERP Connector installer (Installer.msi) on the machine that will host the connector.

  2. Accept the licence agreement and install. The app is installed to C:\Program Files\ERP Connector and a desktop shortcut is created.

  3. Launch ERP Connector from the desktop shortcut.

The installer also adds a Windows Firewall rule named ERP Connector - Odoo POS, allowing TCP port 8890 from the local subnet. That rule only matters if you use Odoo Point of Sale; it is harmless otherwise.

The connector keeps its database, licence and logs in %LOCALAPPDATA%\ErpConnector, so it runs correctly from a read-only install folder.

Keep it running. Closing the window hides the app to the notification area — it keeps polling. Use the tray icon's Exit to actually stop it. Only one copy runs at a time; launching it again brings the running window to the front. Switch on Start on login in the top-right of the window so the connector comes back after a restart.

2. Point it at your fiscal device

Every integration and the Odoo POS endpoint share one SDC address.

  1. Open the Fiscal device tab.

  2. Enter the SDC URL. If the SDC runs on the same machine, that is http://localhost:8888.

  3. Click Test, then Save.

The pill in the window header shows the live state, re-checked every 30 seconds:

Pill

Meaning

Ready

The SDC answered and the secure element is ready.

Not ready

The SDC answered, but the secure element is not ready — check the smart card.

Not reachable

Nothing answered at that address. Check the SDC is running, and the address and port.

Nothing is fiscalized while the device is not ready, so fix this before moving on.

3. Connect your ERP

Open the ERP integrations tab and click Add integration. You can add as many as the site needs — one per company file or per ERP.

Step 1 — name it and pick the system. Give the integration a name you will recognize in the invoice list (EXO Live, Odoo Fiji), then choose the ERP.

Step 2 — enter the connection details.

Field

EXO

Odoo Accounting

Sage 300

API URL

http://exo-server:8080

http://odoo-server:8069

http://sage-server/Sage300WebApi

Database

—

Odoo database name

—

Username

EXO API user

Odoo user

Sage 300 user

Password / API key

EXO password

Odoo API key

Sage 300 password

EXO token

Required

—

—

Developer key

Required

—

—

Company ID

Required

Required — Discover lists them

Required

Click Test connection before creating. A successful test reports how many tax codes the ERP returned — that number is also your first sign that the credentials reach the right company.

For Odoo, click Discover once the URL, database, username and API key are filled in. The connector lists the companies in that database and fills the Company ID for you.

Click Create. The integration is created with sensible fiscalization defaults, and switched off — nothing is polled yet.

4. Set the fiscalization options

Select the new integration. The Fiscalization card holds the settings that decide what gets fiscalized and when.

Setting

What it does

Trigger

On posted fiscalizes every posted invoice. On paid waits until the invoice is settled.

Poll every

How long to wait between checks, 10–3600 seconds. 60 seconds suits most sites.

Payment type

The payment type sent to the SDC for these invoices.

Spare reference

Optional ERP field name used to carry an extra reference. Leave it blank unless support asks for it.

Training mode

Sends documents to the SDC as training documents. Use it while you test.

Active

Starts polling this integration.

Click Save. Do not tick Active until your tax mapping is done — see the next step.

Sage 300 and "On paid": Sage 300 does not report payment state on an invoice batch, so a Sage 300 integration fiscalizes every posted invoice whatever this is set to. Leave it on On posted to avoid surprises.

Odoo Accounting picks up posted customer invoices only. Credit notes are not fiscalized.

The first poll after you switch an integration on looks back 24 hours. Invoices posted before that window are not picked up, so switch the integration on before, not after, the invoices you want fiscalized.

5. Map your tax codes

The SDC will not accept an invoice line without a fiscal tax label, so every tax code your invoices use has to be mapped once.

  1. Open the Tax mapping tab and choose the integration.

  2. Click Reload. The connector pulls the live tax codes from that ERP and shows their code, name and rate.

  3. Type the fiscal label your SDC is configured with — A, B, C and so on — beside each code you actually invoice with.

  4. Click Save.

Map every code you use. An invoice carrying an unmapped tax code is never sent to the SDC; it lands in Fiscalized invoices as failed, with a message naming the codes it could not translate. Add the mapping, then retry the invoice.

Where the tax codes come from: EXO returns its tax rate table, Odoo returns its sales taxes, and Sage 300 derives them from recent invoice batches — so a brand-new Sage 300 company may return nothing until it has posted invoices.

Once the mapping is saved, go back to ERP integrations, tick Active and Save. Polling starts immediately.

6. Odoo Point of Sale (optional)

Skip this unless you run the Odoo Point of Sale cash register. It is independent of any ERP integration and has its own settings.

  1. Open the Odoo POS tab and turn the switch on.

  2. Copy the connector address shown in step 1 of that tab — http://<this-machine>:8890/api/v1/pos/fiscalize.

  3. In Odoo, open Point of Sale → Configuration → Settings and paste the address into FiscoBridge SDC URL.

  4. Tick Training mode while you test, so receipts are sent as training documents.

  5. Click Save.

The pill on that tab reads Listening once the endpoint is up. If it reads Not running, something else already holds the port — pick another one under Advanced and save again.

Changing the port: the installer opens 8890 only. If you move the endpoint to another port, add a Windows Firewall rule for it yourself, or the tills will not reach the connector.

Every POS order is fiscalized through the same SDC address you set in step 2, and only while the licence on this machine is valid.

7. Activate the licence

Nothing is fiscalized until the machine is licensed. Follow Activating a connector, then check Fiscalized invoices to see the first results arrive.

Editing an integration later

Select it on the ERP integrations tab:

  • Edit reopens the connection details. Secret fields are deliberately shown blank — leave one blank to keep its stored value, or type a new value to replace it. Credentials are encrypted on disk.

  • Test connection re-checks the saved connection at any time.

  • Delete removes the integration.

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.