Chile

In Chile, Floogos connects to the SII (Servicio de Impuestos Internos, the tax authority) through OpenFactura, Haulmer’s platform. Instead of building the XML and talking directly to the SII, the engine delegates that work to OpenFactura: it builds the document from the receiver’s data and the item detail, sends it to OpenFactura’s REST API, and OpenFactura takes care of stamping it and submitting it to the SII.

Integration model

• Via a platform, no in-house XML: Floogos does not generate or sign the tax XML itself; OpenFactura does that work and handles communication with the SII.
• API key authentication: each openfactura credential stores the API key (sent in the apikey header) and the environment (production or the test sandbox).
• Single document type (DTE): every Chilean electronic voucher is an Electronic Tax Document (DTE), differentiated by its dte_type_id.
• 19% VAT: Value Added Tax is calculated at 19% on taxable items; exempt documents (type 34 or 41) are marked separately.

Supported DTE types

Code	Document
33	Electronic Invoice
34	Tax-exempt Invoice
39	Electronic Receipt
41	Tax-exempt Receipt
52	Electronic Dispatch Guide
56	Electronic Debit Note
61	Electronic Credit Note

When a document becomes valid

A DTE is not valid just by being sent to OpenFactura: the document goes through stamping and submission to the SII, which assigns it a trackId for tracking. Only once the queried status shows the SII accepted it does the DTE have tax validity. If the submission fails or the SII rejects it, the data must be corrected and the document reissued.

Available nodes

Node	Description
OpenFacturaDTE	Issues the DTE (invoice, receipt, credit/debit note or dispatch guide) via OpenFactura
OpenFacturaConsulta	Queries a DTE’s status by its OpenFactura ID or the SII trackId
OpenFacturaPDF	Downloads the PDF or XML of an already issued DTE

Typical flow

1. OpenFacturaDTE — issues the document with the receiver’s data and item detail; returns the dte_id and, when applicable, the SII track_id.
2. OpenFacturaConsulta — the DTE’s status is queried (by dte_id or track_id) until the SII’s acceptance is confirmed.
3. OpenFacturaPDF — once accepted, the PDF or XML is downloaded to hand it to the customer or archive it.

Notes

• The openfactura credential type stores the API key and the environment (production or sandbox); it does not require its own digital certificate, since OpenFactura handles the signing.
• All three nodes share the same openfactura credential, so it only needs to be configured once per client.