Running the Connector

Once the connector is set up it needs very little attention: leave it running, and check the Fiscalized invoices tab when something looks wrong. This page explains what you see there, how retries work, and what to do about the errors you are most likely to meet.

Day to day

Leave ERP Connector running on its machine. Closing the window only hides it to the notification area; polling continues. The tray tooltip shows how many invoices need attention, so a glance at the notification area tells you whether anything is stuck.

Switch on Start on login so the connector comes back by itself after a restart or a power cut. Nothing is lost while it is stopped — invoices posted in the meantime are picked up on the next poll, as long as they fall inside the poll window.

What happens to each invoice

The connector polls each Active integration and queues any invoice it has not seen before.
Queued invoices are processed in batches, oldest first — up to ten per cycle.
The tax codes are translated to fiscal labels, and the invoice is sent to be signed — by the SDC or by Cloud POS, whichever you chose on the Fiscalization tab.
The fiscal receipt PDF is attached back onto the invoice in the ERP. MYOB AccountRight cannot take attachments, so its PDF is saved in %LOCALAPPDATA%\ErpConnector\journals instead.
A note carrying the fiscal number and verification URL is written onto the invoice.
The invoice is marked Completed.

Between cycles the connector waits for the shortest poll interval among your active integrations.

The Fiscalized invoices tab

Every invoice the connector has handled is listed here, newest first, with the integration it came from, the ERP invoice number, date, amount, the fiscal number once issued, and the error if there is one.

Status	Meaning
Pending	Queued, or waiting for a condition to clear. It will be tried again on the next cycle.
Processing	In flight right now.
Completed	Fiscalized, PDF attached and note written. Nothing left to do.
Failed	Given up after repeated attempts. Fix the cause, then press Retry.

Tick Failures only to hide everything that worked. A red banner appears above the list whenever anything is failed, so you do not have to go looking.

Retry re-queues a failed invoice. Use it after you have fixed whatever caused the failure — the mapping, the credentials, the SDC — not as a way of trying the same broken thing again.

Retries and what they protect

An invoice is attempted up to five times before it is marked Failed. Once it fails for good, the connector writes a failure note back onto the invoice in the ERP, so the reason is visible to whoever works there.
A not-ready signer does not burn an attempt. If the SDC answers but its secure element is unavailable, or Cloud POS answers that it is busy, rate limiting or not ready, the invoice stays Pending with the reason shown, and waits. The backlog clears by itself once the signer is ready again.
A signer that cannot be reached does burn attempts. If nothing answers at all — the SDC application is stopped, or the machine has lost its internet connection while you sign with Cloud POS — each cycle counts as a failed attempt. After five, the invoice is marked Failed. Restore the connection, then press Retry on the failed invoices.
A rejected invoice fails at once. If Cloud POS rejects the API key, the invoice limit of your plan has been reached, or the invoice fails validation, the invoice goes straight to Failed with Cloud POS's reason. Fix the cause, then Retry.
An invoice is never fiscalized twice. If the signer issued a fiscal number but a later step failed — the PDF was rejected, for instance — a retry reuses the fiscal result the connector already stored instead of signing the invoice again.

Errors you are likely to see

Message	What to do
This invoice has lines whose tax code is not mapped to a fiscal label…	Open Tax mapping, choose that integration, Reload, map the codes named in the message, Save, then retry the invoice.
The fiscalization engine is not ready.	The SDC or Cloud POS answered but cannot sign yet. Check the pill on the Fiscalization tab: for the SDC, its application and smart card; for Cloud POS, your subscription. The invoice stays Pending and resumes on its own.
Fisco PosApi rejected the API key. Check the API key on the Fiscalization tab.	The Client ID or secret is wrong, or was revoked. Re-enter them on the Fiscalization tab, save, then retry the invoice.
Cloud signing is selected but no Fisco PosApi API key is configured.	Cloud POS is chosen but no Client ID or secret is saved. Add them on the Fiscalization tab.
The Fisco PosApi invoice limit for this plan has been reached.	Your Cloud POS plan's monthly invoice limit is used up. Signing resumes once you upgrade; retry the failed invoices afterwards.
Fisco PosApi is rate limiting this connector or is unavailable	Temporary. The invoice stays Pending and is retried; nothing to do.
Fisco PosApi rejected the invoice: … followed by field names	The invoice has a value Cloud POS cannot accept. Correct it in the ERP, then retry.
MYOB … is a credit, not an invoice	Credits are not fiscalized for MYOB AccountRight. Handle the refund manually.
MYOB invoice … does not reconcile	The invoice's lines do not add up to its total. Correct the invoice in MYOB, then retry.
MYOB tax code … is not in the company file's tax code list	Check the tax code on that invoice in MYOB, then retry.
MYOB returned … for … or a connection error from MYOB	The MYOB API add-on is probably not running. Start it — see Connect MYOB AccountRight — and retry.
Fiscalization is paused: the ERP Connector licence is …	The machine is not licensed. See Activating a connector.
Fiscal number … was issued, but the journal PDF was not attached	The invoice is fiscally done, but the ERP refused the attachment. Fix the cause in the ERP — permissions, or attachment size limits — and retry to complete the write-back.
Authentication or connection errors from the ERP	Open ERP integrations, select it and use Test connection. Credentials, tokens and API modules expire.

Full detail for every ERP and SDC call is in the log, at %LOCALAPPDATA%\ErpConnector\logs\erpconnector-<date>.log. A new file is written each day and the last 14 are kept — send these to support when you raise a ticket.

Nothing is being picked up

Check, in this order:

Licence tab reads Licensed. Polling is paused entirely while it does not.
The integration is ticked Active and saved.
The header pill reads SDC connected or Cloud POS connected, matching your choice on the Fiscalization tab.
The invoice is inside the poll window — the first poll after activating an integration looks back 24 hours only. For MYOB AccountRight, only invoices created or changed after activation are picked up.
The invoice matches the trigger. On On paid, an unsettled invoice is not picked up yet.
For Odoo, the document is a posted customer invoice. Credit notes are not fiscalized.
For MYOB AccountRight, AccountRight and the API add-on are running on the connector's computer.

Odoo Point of Sale

POS orders do not go through the queue above — the till calls the connector and waits for the answer, so a receipt is fiscalized within the sale itself.

Recent POS fiscalizations on the Odoo POS tab lists one row per attempt, with the order reference, transaction type, cashier, total, fiscal number and any error. If the same order is sent again, the connector replays the fiscal result it already has rather than fiscalizing it twice.

When the till reports an error, the message tells you where the problem is:

What the till reports	Cause
Licence message	The connector's licence is not valid. Activate it.
The endpoint is switched off	The Odoo POS switch is off, or was turned off without saving.
The signer could not be reached, or is not ready	Same problem as for ERP invoices — check the pill and test on the Fiscalization tab. With Cloud POS, also check the connector machine's internet connection.
A field-level validation error	Odoo sent an order the connector could not read. Send the log entry to support.
Nothing at all — the till cannot reach the connector	Network or firewall. Confirm the address on the Odoo POS tab, and that the port is open if you changed it from 8890.

Switching between SDC and Cloud POS

You can change the choice on the Fiscalization tab whenever you like — click the other card, fill in its details if needed, Save, then Test.

New invoices are signed by whichever option is selected when they are processed.
An invoice that was already signed keeps the option that signed it. If a later step failed and you retry after switching, the connector reuses the stored fiscal result rather than signing again with the other option, so no invoice is ever fiscalized twice.
The choice covers every integration and the Odoo POS endpoint together; you cannot sign one integration with the SDC and another with Cloud POS.

Training mode and the retry rules above apply the same way to both options.

Training mode

Training mode sends documents as training documents rather than live fiscal invoices, whichever signing option you use. It is set per ERP integration on the ERP integrations tab, and separately for the cash register on the Odoo POS tab — turning one off does not turn the other off.

Turn it off on every integration before you go live, and confirm on the next invoice that a live fiscal number comes back.

Setting up the connector — installation, ERP connection and tax mapping
Activating a connector — licence statuses and what happens without one