Hubsoft integration with Seidor / Orbit

Hubsoft, an ERP for internet service providers (ISPs), integrates with Orbit by Seidor for NFS-e issuance. The invoice leaves Hubsoft, Orbit transmits it to the city government, and notifies Hubsoft when the status changes or the PDF and XML are ready.

Orbit by Seidor is Seidor’s cloud platform. With Hubsoft, the provider issues and cancels NFS-e through Orbit, with a webhook registered by Hubsoft and the PDF and XML sent back.

Request a Demo Partner website

About Seidor / Orbit

Seidor offers services from leading cloud platforms and maintains its own platform, Orbit by Seidor. Orbit is a digital platform developed and managed by Seidor, with cloud applications and services that integrate business data and processes. These services include the issuance of tax documents, which Hubsoft uses for NFS-e.

What the integration does

Because each city government has its own NFS-e standard, Hubsoft sends the invoice to Orbit, and Orbit handles communication with the municipality. The integration uses Orbit’s API and provides:

NFS-e issuance from Hubsoft’s NFSe dashboard.
Invoice status inquiries.
NFS-e cancellation.
Invoice PDF and XML downloads.
Webhook registration and removal through the integration screen in Hubsoft.
Two types of notifications from Orbit: invoice status changes (authorized, rejected, canceled) and generated PDF or XML files, including the file address so Hubsoft can update the invoice.

Without the webhook, Hubsoft checks invoices in Orbit periodically, and updates may take longer when volume is high.

What you need

An active Seidor license and access to the Orbit portal.
Companies and branches registered in the Orbit portal.
The Branch ID, copied from the Orbit portal.
The integration username and password, as instructed by Seidor. They are usually the same as those for the web portal, but confirm with Seidor.
The CNPJ of the company that will issue the invoice.
RPS numbering control configured by the Seidor/Orbit team.
In Hubsoft, NFS-e services must be registered and plans must be configured with the NFS-e document type. Consult your accountant for tax information.

How to activate

In the Orbit portal, go to Settings > General > Branch, edit the company, and copy the Branch ID.
Ask the Seidor/Orbit team to configure the initial RPS number and inform them that Seidor controls the RPS. Usually, the reference is the last RPS issued by the city government.
In Hubsoft, go to Configuration > Integrations > NFSe, click Add, and enter the Branch ID, username, password, and CNPJ.
Go to Configuration > General > Company > Company, edit the company, and in the CONF. NFSE (ISS) tab, select the integration and fill in the tax and tax liability information.
In the NFSe integrations list, copy the callback URL and register it under Actions > Webhook.
Issue an invoice to validate communication.

The step-by-step guide with screenshots is on the Seidor/Orbit page in the Hubsoft wiki. Invoice issuance and tracking are covered on the NFSe page in the wiki.

Limitations

RPS numbering is controlled by Seidor, not Hubsoft. The initial number is configured by the Seidor/Orbit team at the provider’s request.
An invoice issued directly through the city government portal does not appear as authorized in Hubsoft. To track the invoice in Hubsoft, issue it through Hubsoft.

Frequently asked questions

Do I need to purchase Orbit separately?

Yes. The integration requires an active Seidor license, purchased directly from Seidor.

Who defines the integration username and password?

Seidor. They are usually the same as those for Orbit’s web portal, but Seidor may use different credentials for the integration. Request the information from its team.