Home · Data & ERP · TOTVS

Data & ERP · TOTVS

Protheus, Datasul or RM: the statutory files go out — but do they go out right?

TOTVS is the most common ERP in Brazil's mid-market, and its statutory tax filings depend on a sensitive mechanism: tax configuration rules, product master data with tax codes maintained by hand, and legislation updates that demand constant adjustment. With a lean tax team, obligations get filed on time — without anyone being able to check everything. Azets robots extract data from your TOTVS and cross-check XML × SPED × ERP across 100% of records, before anything is filed. We do not implement or replace ERP.

Who it's for

Typical symptoms of TOTVS-based tax reporting

  • Tax configuration as a blind spot — one misconfigured rule replicates the error across thousands of invoices before anyone notices.
  • Master data maintained by hand — outdated tax codes contaminate the invoice, the books and the tax computation.
  • A lean tax team — you can file on time or check carefully; both at once is not an option.
  • Recurring amended filings and credits left on the table — PIS/COFINS credits underused because of conservative or plainly wrong classification.

How it works

Five steps from TOTVS data to validated filings

Validation is built from your data and your tax rules — not from off-the-shelf software that ignores how your TOTVS was configured.

01 · EXTRACTION

Your TOTVS data

We work with what the system already produces: generated SPED files, authorized XML invoices, reports and table extractions. No IT project on your side — and no direct system access required, if you prefer.

02 · RULES

Your tax premises

Tax specialists register your business rules: product and partner master data, tax codes, operation types — as they should be, not as they are.

03 · ROBOTS

Tailor-made automation

We build the robots from your data and rules — checks that would take weeks resolved in minutes, following the standards with absolute rigor.

04 · CROSS-CHECK

XML × SPED × TOTVS

Automated electronic cross-checking across 100% of records: documents, revenue across SPED files, credits and debits item by item.

05 · REVIEW

People validate what matters

Flagged exceptions go to your team and our specialists for review before filing — with the root cause identified for correction at the source.

What the cross-check finds

Errors no sampling approach catches in a TOTVS environment

  • Errors replicated by tax configuration — one wrong rule multiplied across thousands of identical operations.
  • Discrepancies between authorized XML and the statutory books — every invoice checked, not samples.
  • Tax classification errors inherited from master data — misclassification that means overpaid tax or assessment risk.
  • Unused PIS/COFINS credits — the natural bridge to tax credit recovery.
  • Revenue mismatches across EFD, ECF and other files — the exact cross-check Brazilian electronic auditing runs, run before it.
  • Taxes declared but not paid — before they become notices.
Your TOTVS stays exactly as it is. Azets does not implement, configure or replace ERP systems — it validates the filings they generate and returns a map of what to fix at the source. After the project, recurring cross-checks keep the operation continuously validated.

Frequently asked questions

Straight answers

Do you implement or configure TOTVS?

No. Azets is the tax validation layer on top of the data your TOTVS produces. When our cross-checking pinpoints the root cause — a misconfigured tax rule, outdated master data — your team or your TOTVS partner fixes it at the source, with an exact map of what to change. We do not implement or replace ERP systems.

Does it work with Protheus, Datasul and RM?

Yes, with all three product lines — and from any available data source: generated SPED files, authorized XML invoices, reports and extractions. No required table formats and no IT project on your side.

Our bookkeeping is outsourced. Does this still make sense?

Yes — that is precisely where the risk usually lives. When an external accounting firm receives the files and files them, nobody checks 100% of the records against the XML invoices and the ERP. Azets provides an independent validation layer: you keep your accountant and gain evidence of what is going out right and wrong.

Which Brazilian filings are in scope?

EFD ICMS/IPI, EFD Contribuições, ECD, ECF, DCTFWeb, EFD-Reinf and the validations that precede the filing of any Brazilian statutory tax obligation. Scope is defined around your processes and deadlines.

How many inconsistencies leave your TOTVS every month?

Book a diagnostic: we process your files under a non-disclosure agreement and return a report with the inconsistencies found and a map of what can be automated.