NFS-e · National standard · Issued at scale
Every invoice, authorized.
Upload the sheet, review what the validator found, confirm. Each valid row becomes an NFS-e signed with your certificate and authorized by the national system. A row you send twice never becomes two invoices.
Rio de Janeiro on the national standard today. Fortaleza in homologation.
The Nota Carioca became legacy. Whoever issued dozens of invoices a month by hand kept the same volume and got a new portal, a new layout and a new list of rejection codes. The deadline stayed where it was.
A spreadsheet goes through validation first: client, service code, municipal code, amounts. You see every finding per row and confirm. Only then does a valid row become an invoice, and the file you resend does not duplicate what was already confirmed.
The invoice number is reserved under a database lock before anything is queued. Every API call carries an idempotency key. Before any retry, the product asks the government whether the invoice already exists. When it cannot know, it does not resend.
The XML is signed with your A1 certificate and kept for six years next to the DANFSe in the official layout. Every status change is an append-only event with a chained hash: nothing is edited, everything is explained.
The issuer’s city code decides where the invoice goes and which local rules apply. Rio de Janeiro goes through the national system, with the three-digit municipal code the server demands. Fortaleza runs its own system, with signed batches and asynchronous answers, and the product speaks that too.
Sefin Nacional · national DPS layout · RSA-SHA256 signature · mTLS with your own A1.
In restricted production. First invoice authorized and cancelled on 13 Oct 2026.
ISS Fortaleza · GINFES RPS batch v04 · signed as a whole document · IBS/CBS required.
In homologation.
A new provider implements three verbs — issue, find existing, cancel — plus one line in the registry. Nothing else changes.
On demand.
The A1 file is wrapped in an envelope encrypted with a master key the database never sees. The password exists only in memory, during the upload request. The certificate is unwrapped only to open the TLS session with the government, and is never written to a log, a bucket or a disk beyond that.
A recurrence issues the invoice on the day you set, with the amount and the service you froze. An authorized invoice is immutable: changing it means cancelling with a signed event and issuing a new one, and both stay in the trail.
Email leaves through Quathos Mailer. Sign-in moves to Quathos Account, the single login of every Quathos product. The next step is Quathos CLM: an approved measurement becomes an invoice without retyping. That one is on the roadmap, not in the code yet, and we say it as it is.
Send us a sample. We map the columns, run it through the sandbox and show you every finding before a single invoice is issued.