Skip to content

Fiscal Hub

The Fiscal Hub is the set of Floogos nodes that solves electronic invoicing across Latin America: issuing valid documents before each tax authority, querying them, voiding them and storing them in a normalized way — without your team having to fight XML, digital signatures, certificates or each country’s SOAP protocols.

Every LATAM country has its own fiscal reality, and they are all different:

  • Different authority: AFIP (Argentina), SAT (Mexico), SII (Chile), DIAN (Colombia), SUNAT (Peru), SRI (Ecuador), DGI (Uruguay), DNIT/SIFEN (Paraguay), Hacienda (Costa Rica), SAT/FEL (Guatemala), Ministry of Finance (El Salvador), DGII (Dominican Republic), DGI/SFEP (Panama), SIN/SIAT (Bolivia).
  • Different format: custom XML, UBL 2.1, CFDI 4.0, DTE JSON, e-CF… each with its own schema.
  • Different signature: XMLDSig, XAdES, JWS RS512, certifier seals.
  • Different protocol: SOAP with WS-Security or mTLS, REST with OAuth2 or session token.
  • Different tax: VAT, IGV, ITBIS, ITBMS, each with its own rates and rules.
  • Different certification model: direct submission to the authority, via a PAC (Mexico, Panama), or via an authorized certifier (Guatemala).

Integrating each country separately is a months-long project: understanding the regulation, generating the correct XML, handling certificates, signing, speaking the protocol, interpreting rejection codes and maintaining it when the authority changes the schema.

The Fiscal Hub encapsulates all that complexity into ready-to-use nodes. Your company gets:

  • One provider, many countries: invoice in 14 countries from the same platform, with the same working model.
  • Zero technical friction: you don’t have to implement digital signatures, XML generation or SOAP clients. The node does it for you.
  • Issue from any trigger: automate the invoice from an e-commerce order, a form, an ERP record or a scheduled task. Fiscal issuance is just another step in your workflow.
  • Normalized documents: store, query and export your documents with a common model (the unified hub nodes), regardless of the country of origin.
  • Integration with your stack: push documents into Bill.pt, Sage or Shopify with dedicated nodes.
  • Test and production: each connector distinguishes the test environment from production so you can validate before issuing for real.

In short: you turn electronic invoicing from an integration project into a step of your automation.

The Fiscal Hub has two layers:

  1. Per-country connectors — specific nodes that issue and query documents before each country’s authority (e.g. AfipCreateInvoice, the SAT/CFDI, SIFEN, DGI nodes, etc.). Each country has its own page in this section with its node details.
  2. Unified layer (Hub) — nodes to create, query, update and export normalized fiscal documents and push them into external systems (HubfiscalCreateDocument, HubfiscalGetDocuments, HubfiscalExportPdf, HubfiscalStoreBillpt, HubfiscalStoreSage, HubfiscalStoreShopify).
CountryAuthority / PlatformIntegration modelTax
🇦🇷 ArgentinaAFIP (via AFIP SDK)Direct (self-hosted SDK)VAT 21% / 10.5%
🇲🇽 MexicoSAT — CFDI 4.0Via PAC (Facturama / Finkok / SW)VAT 16%
🇨🇱 ChileSII (via OpenFactura)Via OpenFactura platformVAT 19%
🇨🇴 ColombiaDIAN (via Factus)Via Factus platformVAT 19%
🇵🇪 PeruSUNAT — CPEDirect (UBL 2.1 + WS-Security)IGV 18%
🇪🇨 EcuadorSRIDirect (reception → authorization)VAT 15%
🇺🇾 UruguayDGI — CFEDirect (daily report + CAE)VAT 22%
🇵🇾 ParaguayDNIT / SIFENDirect (XML + CDC + SOAP mTLS)VAT 10%
🇨🇷 Costa RicaHacienda (v4.4)Direct (REST + OAuth2)VAT 13%
🇬🇹 GuatemalaSAT — FELVia authorized certifierVAT 12%
🇸🇻 El SalvadorMinistry of FinanceDirect (DTE JSON + JWS)VAT 13%
🇩🇴 Dominican Rep.DGII — e-CFDirect (seed → token)ITBIS 18%
🇵🇦 PanamaDGI — SFEPVia PAC (CUFE + CAFE/QR)ITBMS 7%
🇧🇴 BoliviaSIN / SIATDirect (SOAP + GZIP)VAT 13%
🇧🇷 BrazilNF-e / NFS-eComing soon—
  • Explore your country’s page in the Countries section to see its nodes and how to configure them.
  • Check the Use cases for complete automation examples (invoicing from an e-commerce, bulk issuance, multi-country from an ERP, etc.).
  • Each node has its own reference page with configuration, credential, output and examples.