Skip to content

Bolivia

In Bolivia, Floogos connects directly to the SIN (National Tax Service) through the SIAT (Invoicing System), with no mandatory intermediate provider: the engine itself builds the invoice XML, signs it with the issuer’s certificate, and speaks the SIN’s SOAP protocol, with the body compressed in GZIP.

  • Direct, no PAC: the flow goes straight to the SIAT’s SOAP services, depending on the mode (testing/pilot or production) and the certificate provided by the credential.
  • Daily CUFD: before issuing any invoice, you need to obtain the CUFD (Daily Unique Invoicing Code), valid for 24 hours, together with its control code. The CUIS (System Startup Unique Code) can also be obtained there if you don’t have one yet.
  • CUF per invoice: each invoice generates its own CUF (Unique Invoicing Code), computed from the issuer’s NIT, the issuance date, the day’s CUFD and other document data.
  • Digital signature: the invoice XML is signed with XMLDSig using the credential’s certificate (.p12) before sending it.
  • SOAP submission with GZIP: the signed XML is compressed and sent over SOAP to the SIN’s services, for reception and, optionally, status validation.
  • 13% included VAT: the Value Added Tax is included in each item’s unit price, not reported as a separate tax.

The SIN receiving the XML doesn’t close the process by itself. The issuance node can, in the same step, query the status validation (default behavior), and only then does the invoice become validated. If the SIN rejects it during reception or validation, it stays rejected and has no tax validity until it’s corrected and resent.

NodeDescription
SiatObtenerCufdGets the valid CUFD (24h) and its control code; optionally the CUIS
SiatEmitirFacturaGenerates the CUF, builds and signs the XML, and sends the sale invoice over SOAP/GZIP
SiatAnularCancels an invoice by its CUF with a reason code from the SIN catalog
SiatRepresentacionGenerates the printable representation (HTML/PDF) with the lookup QR
  1. SiatObtenerCufd — at the start of the day (or when the previous CUFD expires), the valid CUFD and its control code are obtained.
  2. SiatEmitirFactura — with that CUFD, each sale invoice is issued throughout the day.
  3. SiatAnular — if an already-issued invoice needs to be cancelled, it’s done by its CUF (also requires a valid CUFD).
  4. SiatRepresentacion — the HTML/PDF with the QR is generated to hand the customer their printed receipt.

Besides the direct connection, Floogos offers nodes for CUCU (docs.cucu.bo), an authorised provider that handles signing, CUIS/CUFD codes and submission to the SIN. It uses the cucu credential (sk_test_ API key for sandbox, sk_live_ for production).

  • Idempotency: every issue carries a key derived from the body, so a workflow retry does not duplicate the invoice.
  • 20 sectors with their own fields (rental, utilities, education, hospitals, export…), validated before calling the API.
  • Webhooks: the verification node checks the signature of CUCU events.
  • Sectors 3 and 9 are listed as sandbox-only in the CUCU documentation.
NodeDescription
cucuAdministrarSucursales, puntos de venta y certificado
cucuAnularAnular o revertir factura
cucuCatalogoCatálogos del SIAT
cucuConsultarConsultar facturas
cucuContingenciaContingencia (SIAT caído)
cucuCufdCUFD del punto de venta
cucuDocumentoDescargar o enviar documento
cucuEmisionMasivaEmisión masiva
cucuEmitirFacturaEmitir factura
cucuEmitirLoteEmitir facturas en lote
cucuNotaCreditoDebitoNota de crédito/débito
cucuValidarClienteValidar cliente (padrón / NIT)
cucuVerificarWebhookVerificar firma de webhook
cucuWebhooksGestionar webhooks

There are also nodes for factura.bo (api.factura.bo, by SimplifyIT S.R.L.), another authorised provider: it builds and signs the XML (electronic modality) or sends it with a control code (computerised modality) and talks to the SIN. It uses the facturabo credential (API key, environment, NIT and system code).

  • 12 sectors, each with its own endpoint and fields, validated before calling the API.
  • Idempotency with X-Idempotency-Key (30 days) so retries never duplicate invoices.
  • Credit/debit notes from the original invoice by giving only the returned lines.
  • Full contingency (event, package, validation) and webhooks with Standard Webhooks signatures.
  • BCB exchange rate and reports (RCV Sales Book and monthly backup) included.
  • Sandbox at apisandbox.factura.bo (pilot SIAT) and production at api.factura.bo; the key does not reveal the environment, the credential sets it.
NodeDescription
facturaBoAdministrarCuenta, sincronización y puntos de venta
facturaBoAnularAnular o revertir factura
facturaBoCatalogoCatálogos del SIAT
facturaBoConsultarConsultar facturas
facturaBoContingenciaContingencia (SIAT caído)
facturaBoDocumentoDescargar o enviar documento
facturaBoEmitirFacturaEmitir factura
facturaBoEmitirLoteEmitir facturas en lote
facturaBoNotaNota de crédito/débito
facturaBoReportesReportes contables
facturaBoTipoCambioTipo de cambio
facturaBoValidarNitValidar NIT
facturaBoVerificarWebhookVerificar firma de webhook
facturaBoWebhooksGestionar webhooks
  • The siat credential type stores the certificate (.p12 or private key + cert PEM), its password, the issuer’s NIT, the SIN token/apikey (or delegated token) and the environment (testing/pilot or production).
  • The Floogos engine validates that the certificate is not expired before attempting to sign and send a document.