Every invoice in Brazil's economy runs on SOAP 1.2 — and we mapped it all
Every invoice in Brazil's economy runs on SOAP 1.2. We mapped it all
A complete Postman collection for Brazil's SEFAZ electronic invoice web services: NF-e, NFC-e, CT-e, and MDF-e. It packages the SOAP 1.2 envelopes, mTLS e-CNPJ setup, and production-tested DFe distribution endpoints that normally require digging through manuals and authorizer portals. The repo includes conventions for XMLDSig-signed requests and highlights quirks like CT-e's cUFAutor requirement and MDF-e's GZip+base64 payload.
Integrating with SEFAZ requires digging through manuals (MOC NF-e/NFC-e 4.00, CT-e 4.00, MDF-e 3.00b, NT 2015.002) and authorizer portals to discover the URL, SOAP envelope, and quirks of each service.
- pjmlp
It isn't that bad, at least XML is machine friendly, supports schema validation, and does comments, contrary to its replacements that had to rediscover why such features matter.
As for performance, that was also rediscovered why none of them are great, thus gRPC rediscovering CORBA, COM and Sun RPC.
- adontz
Similar in Georgia
https://eservices.rs.ge/app/Downloads
XML/SOAP based protocol was created with modern at the time .Net technologies, but nobody really cared about interoperability, so it screams "old .Net" now.
- mhl47
When we rolled out an ERP in our Brazil subsidiary the whole internal consulting team immediately agreed to leave our brains untouched by this complexity and hire a local consultant team as help. And the local consultant team in turn immediately suggested useing a middleware provider.
- bluegatty
seems like a great idea, as long as it's well maintained etc
- Muromec
This sounds similar to Ukrainian cash registers. Every retail operation goes through a cash register API on the tax agency side (because who would not love to keep some cash off the books, right), but there it is RESP+JSON and a cottage industry of services running it for you. It would not even be that hard is it wasn't sneaking the whole PKI into it.