NETTCOM

ACCOUNTING · TAX · NFS-E + ASAAS

NFS-e issued via city API and collection synced to Asaas — no manual typing.

manual NFS-e typing after rollout

100%

collection synced to Asaas on issue

2% / 5%

ISS parameterized by service type

See solution →

Problema

The firm issued NFS-e on the city portal by hand and then re-entered the collection in Asaas. Double typing, ISS rate errors by service type and collection out of sync with the issued invoice.

Solução

Odoo calls the city NFS-e API with A1 digital certificate, parameterizes ISS by service type (2% or 5%) and syncs collection in Asaas in the same issuance flow — one entry, invoice and collection ready.

Resultado

Zero manual NFS-e typing, 100% of collection synced to Asaas on issuance and ISS parameterized by service type without rework. The firm's billing started closing daily, not at month end.

“The invoice left the city portal and the collection was forgotten in another system. Today one entry solves both ends.”

— Managing Partner · Nettcom Accounting

Stack

Odoo · NFS-e (city API) · Asaas · A1 digital certificate

Implementation time

First workflow live in 19 days

Frequently asked questions

Are these numbers guaranteed?

No. Every operation is unique. The case studies show results observed in specific contexts. What we guarantee is methodology, follow-up and continuous adjustments.

Why are some cases anonymous?

We respect the confidentiality of clients who prefer not to disclose their identity. Anonymous cases are based on patterns observed across multiple operations in the same segment.

Does it work for my segment?

Mágica Suite already runs in telecom, healthcare, finance, real estate, education, industry and retail. Book a diagnosis — we probably already have a similar stack running.