SRI Ecuador — Electronic Invoicing (electronic receipts)
Overview
Section titled “Overview”The SRI nodes connect your workflows with Ecuador’s electronic invoicing (electronic receipts from the Servicio de Rentas Internas). Floogos builds the XML, computes the access key (49 digits), signs it and runs the reception and authorization flow with the SRI.
| Node | What it does |
|---|---|
SRI: Issue invoice (sriEmitirFactura) | Issues an invoice (01) → authorization |
SRI: Credit/debit note (sriEmitirNota) | Issues CN (04) or DN (05) referencing the original |
SRI: Query authorization (sriConsultarAutorizacion) | Status of a document by its access key |
SRI: RIDE / QR (sriRIDE) | Generates the printable representation with QR |
Credential
Section titled “Credential”The nodes use an SRI credential. Create it under Credentials → Add → Ecuador SRI with:
| Field | Description |
|---|---|
| Certificate (.p12) | Your digital certificate, base64. |
| Certificate password | The .p12 password. |
| RUC and Legal name | Issuer data (13-digit RUC). |
| Environment | Test or Production. |
| Establishment and Emission point | The codes (e.g. 001 / 001). |
| Required to keep accounting | YES / NO. |
The full flow
Section titled “The full flow”-
Prepare the document as JSON (buyer, items with
precioUnitarioandcodigoPorcentajeIva). -
Issue with Issue invoice. Floogos builds the XML, computes the access key, signs, sends to reception and queries authorization.
-
If it was left IN PROCESSING, reconcile it with Query authorization.
-
Generate the RIDE with RIDE / QR to deliver/print the document.
Issuing an invoice
Section titled “Issuing an invoice”Node: SRI: Issue invoice. Example:
{ "comprador": { "tipoIdentificacion": "04", "identificacion": "1791234567001", "razonSocial": "Cliente SA" }, "items": [ { "codigo": "P1", "descripcion": "Product", "cantidad": 2, "precioUnitario": 50, "codigoPorcentajeIva": 4 } ]}codigoPorcentajeIva: 4 = 15%, 0 = 0%, 7 = exempt, 6 = not subject. precioUnitario is without VAT. The sequential is auto-numbered if not provided. Buyer tipoIdentificacion: 04 RUC, 05 ID card, 06 passport, 07 final consumer.
Credit and debit notes
Section titled “Credit and debit notes”Credit/debit note issues a CN (04) or DN (05) that references the modified document (docModificado):
{ "tipo": "04", "motivo": "Merchandise return", "docModificado": { "tipo": "01", "numero": "001-001-000000001", "fecha": "2026-07-20" }, "comprador": { "tipoIdentificacion": "04", "identificacion": "1791234567001" }, "items": [ { "descripcion": "Product", "cantidad": 1, "precioUnitario": 100, "codigoPorcentajeIva": 4 } ]}The debit note (05) uses motivos (reason + value) instead of items.
Querying authorization
Section titled “Querying authorization”Query authorization queries a document by its access key and returns whether it is AUTHORIZED, NOT AUTHORIZED or IN PROCESSING, updating the status in the database. Useful when issuance was left in processing.
RIDE (representation with QR)
Section titled “RIDE (representation with QR)”RIDE / QR generates the printable representation of the electronic document in HTML (exportable to PDF), with the authorization number, the access key and the QR that contains it.
Error handling
Section titled “Error handling”| Situation | Retryable | What to do |
|---|---|---|
| RETURNED (reception) | No | The SRI returned the document with error messages. Fix the XML. |
| NOT AUTHORIZED | No | The SRI did not authorize; check the messages. |
| Expired certificate | No | Renew the .p12 and update the credential. |
| Network / Timeout | Yes | Transient issue; retried automatically. |
See also
Section titled “See also”- Retry queue (DLQ) — how failed executions are retried.
- HTTP node — for services not covered by these nodes.