# Hubsoft integration with BCore – SipPulse

> Hubsoft, an ERP for internet service providers (ISPs), integrates with SipPulse's BCore to bill fixed-line telephony.

Fonte: https://hubsoft.io/en/integrations/bcore-sippulse/

![Logo BCore – SipPulse](/_astro/parceiro-bcore-sippulse-recortado-mv13cr3v_eV02l.webp) 

[STFC](/en/integrations/category/stfc/) 

# Hubsoft integration with BCore – SipPulse

Hubsoft, an ERP for internet service providers (ISPs), integrates with SipPulse's BCore to bill fixed-line telephony. Hubsoft retrieves each customer's monthly usage from BCore and turns the amount into an invoice or charge, without entering accounts one by one.

BCore is SipPulse's telephony billing BSS. Through Hubsoft, the ISP imports each customer's monthly billed amount from BCore and generates the charge, without registering numbers or plans.

[ Request a Demo ](/en/request-a-demo/) [Partner website](https://sippulse.com/bss/) 

## About BCore – SipPulse

BCore is SipPulse's BSS (Business Support System), developed by a telecommunications software company based in Florianópolis (SC). It is a billing solution for STFC and SCM operators and VoIP providers: it imports call records from the softswitch, applies customized plans, tiered billing and usage allowances, and maintains a numbering inventory. It can run on the ISP's infrastructure or in SipPulse's cloud.

## What the integration does

The integration is only for billing. BCore calculates usage, and Hubsoft handles the charges:

* **Monthly billing lookup:** the ISP selects the month, year, and billing status, and Hubsoft retrieves the amounts from BCore through the API.
* **Cost per customer:** Hubsoft displays the cost of each number before generating the charge.
* **Invoice or charge:** the amount becomes an invoice for the customer or a charge for the next monthly bill, according to the selected type.
* **Status filter:** the lookup can return billed charges (the default), charges awaiting billing, or paid charges.
* **Identification without number registration:** the customer is identified by the customer code or by a contract entered in their service.
* **Telephony invoice:** a parameter in the customer's service provides the phone number for issuing the telephony service invoice.

## What you need

* A contract with SipPulse for BCore and the API access details (production URL, username, and password), provided by the platform.
* The customer's code or contract must be the same in both systems.

## How to activate

1. In Hubsoft, go to Settings > Integrations > STFC and click Add.
2. Enter the description, API URL, username, and password.
3. If the customer is identified by contract, enter the contract under the service's STFC Details.
4. To bill, go to Actions > Process/Bill, select the charge type, month, year, and status, and load the processing.
5. Review the costs per number and generate the invoices or charges.

The step-by-step guide with screenshots is on the [BCore page in the Hubsoft wiki](https://wiki.hubsoft.com.br/pt-br/modulos/configuracao/integracao/stfc/bcore).

## Limitations

* The integration does not register numbers or plans in BCore. It only retrieves billing data.
* Hubsoft imports the amounts stored in BCore. If an amount is incorrect, it must be corrected on the platform.

## Frequently asked questions

### Do I need to register phone numbers in Hubsoft?

No. BCore identifies the customer by code or contract. The numbers remain only on the platform.

### The customer's telephony amount is incorrect. What should I do?

Hubsoft imports what is billed in BCore. Check the usage with SipPulse, correct it on the platform, and process it again.

### Can I charge for telephony together with the internet monthly bill?

Yes. During processing, select the charge type that goes to the next monthly bill instead of generating a separate invoice.

Reviewed on 10/10/2026.

## Similar integrations

* ![Logo Flux Tecnologia](/_astro/parceiro-flux-tecnologia-recortado-mv13d401_1i93Dr.webp)  
### [Flux Tecnologia](/en/integrations/flux-tecnologia/)  
STFC
* ![Logo Interede](/_astro/parceiro-interede-recortado-mv13d9cq_umPHY.webp)  
### [Interede](/en/integrations/interede/)  
STFC
* ![Logo SAPER X](/_astro/parceiro-saper-x-recortado-mv13dkqn_1PrRDl.webp)  
### [SAPER X](/en/integrations/saper-x/)  
STFC
* ![Logo SipPulse](/_astro/parceiro-sippulse-recortado-mv13dnb0_wqkIA.webp)  
### [SipPulse](/en/integrations/sippulse/)  
STFC
* ![Logo Summit Networks](/_astro/parceiro-summit-networks-recortado-mv13dotq_dGePp.webp)  
### [Summit Networks](/en/integrations/summit-networks/)  
STFC

![Illuminated fiber optic cables converging into a connection hub](/_astro/site-cta04_TkBg7.webp) 

## Want to use this integration with your internet service provider (ISP)?

[ Request a Demo ](/en/request-a-demo/)