Ecuador: receipts are authorised by the SRI
In Ecuador, per the sources read, the tax authority, the SRI (Servicio de Rentas Internas), has issuers send electronic receipts (factura, nota de crédito, nota de débito, retención, guía de remisión) as signed XML for authorisation, each identified by a 49-digit clave de acceso. Below: how it works as vendor guides report it, where the sources are thin, and local checks of a RUC and a clave de acceso.
How it works (as vendor guides, press and the authority report)
| Step | What happens |
|---|---|
| Identify | The issuer has a 13-digit RUC: a cédula or company number plus an establishment number. |
| Issue a receipt | The issuer produces a receipt as signed XML in the SRI’s format, with a clave de acceso, using a certificate from an accredited provider (vendor guides; the technical sheet is unread). |
| Authorise | The XML goes to the SRI’s reception and authorisation web services; the receipt is valid once authorised, and the clave de acceso then serves as its authorisation number (vendor guides). |
| Deliver | The buyer gets the authorised XML and a printable representation (RIDE), per vendor guides. |
Where it is unsettled: the SRI resolutions were not read, so which taxpayers are bound and from when, the exceptions and the penalties are unconfirmed here; the structure above comes from open-source libraries and vendor guides (search excerpts), not from the SRI’s technical sheet. No penalty is stated because none was read. A summary, not tax advice.
Check a RUC or a clave de acceso
Tests the shape and the check digits (spaces, dots and hyphens are ignored). It does not look anything up, so it cannot say whether the RUC is registered, active, or belongs to the name on the receipt, or whether the SRI authorised a key.
The RUC rule (third digit 0 to 5: cédula, modulo 10 on nine digits; 6: public body, modulo 11 with weights 3,2,7,6,5,4,3,2; 9: private company, modulo 11 with weights 4,3,2,7,6,5,4,3,2) and the key rule (modulo 11, weights 2 to 7 from the right, 11 gives 0 and 10 gives 1) are the ones open-source libraries and vendor guides describe. They were not read from the SRI’s technical sheet. The sample RUC (1790010937001) is a widely published company number recalled from memory that fits the rule; it was not confirmed with the SRI.
What this checker does and does not cover
The main checker reads UBL, CII and Factur-X and applies EN 16931 and Peppol rules. It does not call the SRI’s services, cannot obtain or verify an authorisation, and has no SRI schema or codes. Treat the tests here as typo catches only.
Test a file before you send it
For a European or Peppol invoice, open the checker, drop your XML and read the findings, each with a rule ID and a fix (the rule reference). No account, nothing uploaded. No invoice yet? The e-invoice creator turns a form into UBL or CII XML and checks it. Other countries: all side by side Mexico Brazil Chile Colombia Peru Argentina Uruguay Paraguay.
Common questions
What is the clave de acceso?
A 49-digit number that identifies each electronic receipt: issue date, receipt type, the issuer’s RUC, environment (1 test, 2 production), series, sequence, an 8-digit numeric code, emission type and a modulo 11 check digit. Vendor guides say it doubles as the authorisation number once the SRI, the tax authority, authorises the receipt. This is a summary from vendor guides, not advice; confirm with the SRI or your accountant.
Who has to issue electronic receipts?
Vendor guides describe a mandate phased in by taxpayer group over several years, with most registered taxpayers now covered. The SRI resolutions were not read, so exceptions, dates and the rules for sales to consumers are unconfirmed here; check sri.gob.ec or ask your accountant.
What is a valid RUC?
Thirteen digits: a 10-digit cédula or company number, then an establishment number. The check digit follows from the earlier digits by a modulo 10 (people) or modulo 11 (companies and public bodies) rule. A matching digit does not mean the RUC is registered or active; the SRI’s public lookup answers that. The tests on this page catch typos only.
Can this checker validate an Ecuadorian invoice?
No. It does not read the SRI’s XML schema and cannot obtain or verify an authorisation. It does test a RUC and the check digit of a clave de acceso on this page, and a clean result is not an authorisation by the SRI.
Open the E-invoice Preflight checker to validate your own invoice file.
More countries
Australia Austria Belgium Brazil Bulgaria Croatia Cyprus Czech Republic Denmark Estonia Finland France Germany Greece Hungary Ireland Italy Latvia Lithuania Luxembourg Malta Netherlands Nigeria Norway Poland Portugal Romania Serbia Singapore Invoicenow Slovakia Slovenia Spain Switzerland Uk India Malaysia Saudi Arabia Sweden Turkey United Arab Emirates Peru Chile Colombia Uruguay Paraguay Vietnam