Home · Data & ERP · SAP
Data & ERP · SAP
SAP runs your Brazilian operation. Who validates the tax filings it generates?
Brazil has one of the most complex digital tax-reporting systems in the world (SPED) — and SAP subsidiaries feel it every month. Between material master data, tax configuration and the local fiscal add-on, every link in the chain can introduce discrepancies: the authorized XML invoice says one thing, the ledger another, the statutory file a third. Azets robots extract data from your SAP and cross-check everything — XML × SPED × ERP, across 100% of records — before anything is filed with the tax authorities. Without touching your system: we do not implement or replace ERP.
Who it's for
Typical symptoms of SAP-based tax reporting in Brazil
- The local team exports from SAP and "fixes" files in spreadsheets — every month, before filing. The obligation goes out, but it goes out by hand.
- A fiscal add-on sitting between SAP and the tax authorities — TDF, Mastersaf, Synchro, ONESOURCE or similar: every integration is a point where numbers can diverge.
- Master data as the Achilles' heel — outdated NCM codes, origin and tax classifications contaminate everything, from the invoice to the statutory file.
- Recurring amended filings and credits left on the table — Brazilian PIS/COFINS credits underused because of conservative or plainly wrong classification.
How it works
Five steps from SAP data to validated filings
Validation is built from your data and your tax rules — not from off-the-shelf software that ignores how your SAP was configured.
Your SAP data
We work with what SAP 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.
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.
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.
XML × SPED × SAP
Automated electronic cross-checking across 100% of records: documents, revenue across SPED files, credits and debits item by item.
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 an SAP environment
- Discrepancies between authorized XML, bookkeeping and ledger — the classic issue of ERP + fiscal add-on landscapes.
- Tax classification errors inherited from master data — misclassification that means overpaid tax or assessment risk.
- Invoices missing from the statutory books — XML × SPED × ERP cross-check on every single document.
- 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.
Frequently asked questions
Straight answers
Do you implement or configure SAP?
No. Azets is the tax validation layer on top of the data your SAP and its fiscal add-on produce. When our cross-checking pinpoints the root cause of an error — a master data record, a configuration — your team or your SAP partner fixes it at the source, with an exact map of what to change. We do not implement or replace ERP systems.
Do you need access to our SAP system?
Not necessarily. We work with what SAP already produces: generated SPED files, authorized XML invoices, reports and table extractions. If direct access is more practical for your team, that works too. Either way, under a non-disclosure agreement.
Does it work with ECC and S/4HANA?
Yes — and with whichever fiscal add-on sits in between (TDF, Mastersaf, Synchro, ONESOURCE or similar). Our robots work from any available data source, with no required table formats. S/4HANA migration projects are actually an excellent moment to clean up master data and validate the legacy.
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 SAP 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.