- Home
- Localization
- Brazil Taxation
- SAP e-invoicing and SPED
From J1BECD to DRC: twenty years of SAP e-invoicing and e-reporting in Brazil
Brazil asks companies to clear every invoice with the tax authority before the goods leave, and then to rebuild each month and each year as digital files. This page tells how SAP answered, from the first SAP ERP reports to GRC NF-e, TDF and DRC; what SAP still leaves to each company; and where partner solutions fill the gap.
- NF-e
- SPED
- GRC NF-e
- TDF
- ACR
- SAP DRC
One sale, five digital trails
A factory in São Paulo sells goods to a customer in another state. That one sale shows up in:
- SecondsNF-e: the electronic invoice, authorized by the state tax authority before the truck leaves.
- MonthlyEFD ICMS/IPI: the state VAT (ICMS) and federal excise (IPI) books of the plant.
- MonthlyEFD Contribuições: PIS and COFINS, the federal contributions on revenue.
- YearlyECD: the accounting books, from journal entries to financial statements.
- YearlyECF: the corporate income tax return (IRPJ and CSLL).
The first trail is e-invoicing. The other four are SPED files: e-reporting.
The basics
Two different jobs: e-invoicing and e-reporting
Many countries are meeting e-invoicing only now. Brazil has run both jobs at national scale since 2008, and each job asks something different from SAP.
E-invoicing
One document at a time, before the goods move
Every nota fiscal is an XML file signed with the company’s digital certificate and sent to SEFAZ, the tax authority of the state, which authorizes it in seconds. A printed summary, the DANFE, travels with the goods. The same model covers freight (CT-e), cargo manifests (MDF-e), retail sales (NFC-e) and, through the cities, services (NFS-e).
In SAP: sales and purchasing create the nota fiscal; GRC NF-e, and now DRC, carries it to SEFAZ and back.
E-reporting (SPED)
Many documents, once a month or once a year
SPED, the Public Digital Bookkeeping System, replaced paper books with text files. The company validates each file in the government’s own program, the PVA, signs it and sends it. Each file rebuilds a period: the documents, plus the tax calculations, adjustments and balances that follow from them.
In SAP: J1BECD and J_1BEFD in SAP ERP, then TDF, then DRC statutory reporting.
- Apr 2006The NF-e pilot starts with 19 companies.
- Jan 2007Decree 6,022 creates SPED.
- Apr 2008NF-e becomes mandatory, first for fuel and cigarettes.
- 22 billionNF-e authorized by July 2019.
Sources: Serpro (2019)Baguete (2007)
History
Twenty years in seven chapters
Pick a chapter. Each one shows what Brazil asked for, what SAP shipped in answer, and what SAP still left to its customers.
Before 2006
Paper notas and printed tax books
Before NF-e, SAP already kept the nota fiscal as a document of its own, and that made everything that came later easier.
Brazil asked for
Companies printed notas fiscais on pre-numbered paper forms and kept paper tax books, such as the ICMS and IPI calculation registers (models 9 and 8). States also asked for periodic magnetic files under the Sintegra agreement.
SAP answered with
SAP’s Brazil localization kept the nota fiscal as its own document, separate from the billing document, with its own header, item and tax tables, plus reports for the legal books. When the NF-e came, the data the government wanted was already in one place.
Left to the customer
Print layouts for the nota fiscal forms, and the differences each state added to its books.
SAP objects
J_1BNFDOCJ_1BNFLINJ_1BNFSTXJ1B1N
Consultant’s note. A fossil worth knowing: Customizing for the EFD ICMS/IPI still asks for the special accounts of the old model 8 and model 9 books, even if you never print them.
2006–2011
NF-e arrives, SAP answers with GRC NF-e
SAP’s first answer to e-invoicing was a separate system that talked to the tax authorities on behalf of the ERP.
Brazil asked for
The NF-e pilot started in April 2006 with 19 companies. From 1 April 2008 the NF-e became mandatory sector by sector, starting with fuel and cigarettes. Each state runs web services that authorize, cancel and correct documents, with contingency modes for when they are down.
SAP answered with
SAP built SAP Nota Fiscal Eletrônica (SAP NFE), release 1.0 and then 10.0, widely called GRC NF-e because it shipped under SAP’s governance, risk and compliance portfolio. It ran on its own SAP NetWeaver system, with SAP PI (later PO) for messaging: it signed the XML, sent it to SEFAZ, collected the answers and exchanged XML with customers and carriers. SAP ERP kept creating the nota fiscal and followed each status in the NF-e monitor.
Left to the customer
A second landscape to run and upgrade: the GRC system, PI, digital certificates and B2B mail. Inbound checks of suppliers’ XML against purchase orders were set up company by company.
SAP objects
J1BNFEJ_1BNFE_ACTIVE/XNFE/SAP PI / PO
Consultant’s note. GRC objects live in the /XNFE/ namespace. That helps when you map old GRC settings to DRC: /XNFE/CNPJ_MAINTAIN, for example, corresponds to views V_T001Z_N and J_1BBRANCV.
Sources: Serpro (2019)Baguete (2007)SAP blog: SAP NFE 10.0 (2011)DFSpro: GRC to DRC
2008–2013
SPED reaches SAP ERP: J1BECD, J_1BEFD and the empty BAdIs
SAP wrote the new files from standard data and handed customers empty hooks for everything else.
Brazil asked for
Decree 6,022 created SPED in January 2007. ECD, the digital accounting books, started with calendar year 2008 for the largest taxpayers, and EFD ICMS/IPI, the monthly state and excise tax books, in January 2009 for the companies the states picked first. Each file is a text layout of blocks and records, checked in the government’s PVA program before it is sent.
SAP answered with
SAP delivered two reports in SAP ERP: the electronic accounting file for the ECD (transaction J1BECD) and the electronic fiscal file for the EFD ICMS/IPI (transaction J_1BEFD). They read the general ledger and the notas fiscais and wrote every record SAP could fill from standard data. For the rest, SAP shipped BAdIs with methods per record, left empty for each customer to implement.
Left to the customer
This is the empty-BAdI era. Adjustments, CIAP, inventory rules and every record that depends on the business became custom ABAP inside BAdI implementations, written project by project and fragile whenever a layout changed.
SAP objects
J1BECDJ_1BECD_MAINBADI_J_1BECDJ_1BEFDJ_1BEFD_MAINBADI_J_1BEFDNote 1234056
Consultant’s note. Two documented tricks: the OK-code NOBADI runs J_1BEFD_MAIN without your BAdI implementations, so you see what SAP standard writes; and SAP Note 1234056 holds the content files with the record defaults and BAdI methods.
Sources: SAP Help: SPED EFD-ICMS/IPISAP Help: Customizing for SPED ECDSerpro (2019)
2012–2016
More files, one repository: TDF on SAP HANA
SAP moved tax reporting onto one repository on SAP HANA, built beside the ERP.
Brazil asked for
The list kept growing: EFD Contribuições for PIS and COFINS, the ECF for corporate income tax (replacing the old DIPJ return), and, announced in these years, eSocial for payroll and Bloco K for production and stock control. Layouts changed several times a year.
SAP answered with
In March 2014 SAP announced the Tax Declaration Framework for Brazil (TDF), co-developed in Brazil with customers and tax software partners, among them Thomson Reuters and Systax. TDF keeps a Central Tax Repository on SAP HANA, organized close to the SPED layouts, and generates the files from it. SAP ERP could run on other databases, so TDF often sat beside ECC on a HANA-based system kept in sync by SLT or SAP Data Services. Consultants call this the TDF sidecar.
Left to the customer
Data SAP does not have, or that must look different in the file without changing the SAP document, goes into complement tables and shadow tables instead of BAdI code. Partners could certify their own apps on top of TDF.
SAP objects
/TMF/Central Tax RepositorySLTJ_1BNF_ADD_DATANote 2248350
Consultant’s note. SAP Note 2248350 lists which SPED records TDF covers for ECD, ECF, EFD ICMS/IPI and EFD Contribuições. It changes whenever coverage changes, so read the latest version before promising a record to the tax team.
Sources: Portal ERP (April 2014)SAP blog (March 2014)sapbr.com (2016)SAP Community: note 2248350
2016–2021
SAP S/4HANA: TDF moves inside, ACR appears
On SAP S/4HANA, TDF runs inside the ERP, and SAP added a second option for the SPED files.
Brazil asked for
eSocial and EFD-Reinf (withholdings on services) started in 2018 and are sent as event messages, not as one file. The complete Bloco K started in 2019 for beverage, tobacco and vehicle makers with yearly revenue of R$ 300 million or more.
SAP answered with
SAP S/4HANA always runs on SAP HANA, so TDF can run in the same system with no replication. TDF added a Messaging Framework for eSocial and EFD-Reinf, a Tax Obligation Monitor that keeps each run with its proof of delivery and, later, a Layout Builder. In parallel, SAP S/4HANA for advanced compliance reporting (ACR) gained a Brazil option that generates the SPED files in the Run Statutory Reports app.
Left to the customer
Shadow tables became the normal way to fix a file: block 0 through master data maintenance, the other blocks through shadow tables, then a rectifying run.
SAP objects
LOG_TMF_INT_1/TMF/EFD/TMF/ECD/TMF/ECF/TMF/PCO/TMF/REINF/TMF/TOM02/TMF/BF_SPED
Consultant’s note. On premise, the ACR Brazil objects use the same /TMF/ namespace as TDF, which is why the two often behave alike. The Brazil option is documented from SAP S/4HANA 1809 FPS02, with business function /TMF/BF_SPED.
Sources: DFSpro: SAP TDFDFSpro: SAP ACRSAP blog: ACR Brazil and EFD-Reinf (2021)Ajuste SINIEF 25/2016
2020–2025
DRC and the cloud: GRC NF-e retires
The connection to the tax authorities moved to SAP’s cloud, and the old GRC product was retired.
Brazil asked for
More documents went electronic, such as NF3e for electricity and NFCom for telecom, and a national NFS-e standard for services appeared beside each city’s own. SEFAZ technical notes kept changing the XML.
SAP answered with
In September 2021 SAP put SAP Document Compliance and ACR under one name: SAP Document and Reporting Compliance (DRC). For Brazil, SAP cloud services on SAP BTP took over the connection: the outbound invoicing option for NF-e, CT-e, MDF-e and some NFS-e, and the inbound option for suppliers’ NF-e and CT-e. In April 2023 SAP announced the end of mainstream maintenance of SAP NFE for 31 December 2025.
Left to the customer
There is no migration tool. GRC settings are recreated in DRC, custom GRC processes become eDocument processes, and old XML files are best kept in an external archive, since uploading them counts as documents in the licence.
SAP objects
NFE_MNG_CERTEDOC_COCKPITEDOC_BR_DISTDFE_RETRIEVENote 2671909Note 2776753
Consultant’s note. Switching inbound from GRC to DRC: deactivate the old application, write down the last NSU processed and start DRC at NSU + 1. Two applications querying the same CNPJ can be rejected for misuse.
Sources: SAP blog (April 2023)DFSpro: GRC to DRCOur SAP DRC guide
2026 →
Tax reform: CBS and IBS in every document
The tax reform changes every document again, and every SAP and partner tool has to follow.
Brazil asked for
From 2026 the NF-e carries the new CBS and IBS of the consumption tax reform next to the current taxes: PIS and COFINS end in 2027, ICMS and ISS in 2033. During the transition an NF-e without the CBS and IBS group is not rejected, but the obligation to report them stays. Alphanumeric CNPJs start being issued in July 2026.
SAP answered with
SAP delivers the reform as SAP Notes for the nota fiscal, the tax calculation and DRC, and keeps a troubleshooting guide in KBA 3642384. SAP NFE, out of mainstream maintenance, does not receive these legal changes. TDF is still maintained: support package 20 shipped in 2025.
Left to the customer
CBS and IBS bring new calculations and new credit rules. Every partner engine, every custom adjustment and every BAdI from the old days has to be reviewed again.
SAP objects
KBA 3642384J_1BNFDOCJ_1BNFLINCBSIBS
Consultant’s note. Test the reform with three things on the same note level: the nota fiscal fields, the tax calculation and the DRC outbound option. KBA 3642384 covers SAP ERP 6.0, SAP S/4HANA and DRC outbound NF-e.
Sources: Our tax reform pageKBA 3642384Machado Meyer (2026)SAP blog: TDF SP20
The pattern
SAP never shipped the whole file. The way to fill the gap changed three times.
No SAP release has filled every record of every SPED file for every company. What changed over the years is the tool SAP hands you for the part it leaves open.
SAP ERP · from 2008
1. Write code
BAdIs with a method per record. Your ABAP fills or changes each record while the report writes the file.
BADI_J_1BECDBADI_J_1BEFD
Plus: anything is possible. Minus: every new layout can break custom code, and the logic lives with whoever wrote it.
TDF · from 2014
2. Store data
Complement tables hold what SAP does not have. Shadow tables override what the file must show without changing the SAP document. BRF+ rules check data as it is entered.
Shadow tablesCPL tablesBRF+
Plus: corrections are data, with a trail. Minus: someone has to load and own those tables every period.
ACR, now DRC · SAP S/4HANA
3. Model the report
Report definitions built on SAP HANA calculation views that can be extended, with each run reviewed in the Run Statutory Reports app before the file goes out.
Run Statutory ReportsHDI calculation views
Plus: extensions follow SAP’s model. Minus: needs SAP S/4HANA and modelling skills most tax teams do not have.
Partners add a fourth path: their own product does the calculations, inside or beside SAP. See the partners.
Where SAP stops
Analytic records and synthetic records
A useful way to read any SPED file: some records only show what was already posted in SAP; others are the result of calculations and decisions. SAP is strong at the first kind. The second kind changes from company to company, and that is where projects spend their time.
- AnalyticShows what was posted, line by line: documents, items, entries, balances. If the nota fiscal or the journal entry is right, the record is right.
- MixedStarts from SAP data but needs a rule or a choice on top: a valuation, a regime, a classification.
- SyntheticCalculated from many documents plus rules SAP cannot know by itself: state adjustment codes, tax benefits, special regimes, credit coefficients, production structures.
Monthly, one file per establishment. State VAT (ICMS) and federal excise (IPI).
4 analytic · 3 mixed · 3 syntheticOpening and master data
The establishment, every business partner in the period (0150), every item with its NCM code (0200), units and description changes (0205).
Watch out
The same material with a different NCM in two plants is a classic cause of conflicting item records.
Who usually does the thinking
SAP standard, fed by clean master data.
Where SAP reads it: Business partner and material master; business place (J_1BBRANCH).
Service tax (Federal District only)
Books and calculation of ISS, used only by taxpayers in the Federal District, where the same government collects both ICMS and ISS.
Watch out
Irrelevant for most companies, essential for those in Brasília.
Who usually does the thinking
Tax team of the Federal District establishment.
Where SAP reads it: Service notas fiscais.
Goods documents
Every nota fiscal of goods: header (C100), items (C170), the summary per tax situation, CFOP and rate (C190) and adjustments tied to a document (C197).
Watch out
C197 adjustment codes come from each state’s table and are often set by the tax team, not by sales or purchasing.
Who usually does the thinking
SAP standard, once tax determination is right.
Where SAP reads it: Nota fiscal tables J_1BNFDOC, J_1BNFLIN and J_1BNFSTX.
Transport and communication documents
Freight documents (CT-e) and communication services subject to ICMS (D100, D190 and others).
Watch out
Freight bought by the company must be booked as a document of its own, not hidden in a purchase price.
Who usually does the thinking
SAP standard, with freight processes set up for it.
Where SAP reads it: Nota fiscal tables for CT-e; freight documents from logistics or TM.
ICMS and IPI calculation (apuração)
The month’s debits and credits, adjustments (E111 and the records below it), amounts to pay (E116), ICMS-ST and DIFAL per destination state (E200, E300) and IPI (E500).
Watch out
Adjustment codes come from each state’s table, tax benefits and special regimes change the result, and E116 has to match the tax actually paid.
Who usually does the thinking
The tax team, through configuration, manual adjustments or a partner engine.
Where SAP reads it: Tax lines of the notas fiscais plus adjustment entries; TDF and DRC add their own tables for adjustments.
CIAP: ICMS credit on fixed assets
ICMS paid on fixed assets is credited in 48 monthly installments, scaled each month by the share of taxable exits in total exits.
Watch out
The monthly coefficient, asset transfers and sales before the 48 months end need rules that asset accounting does not apply by itself.
Who usually does the thinking
Tax team, with an asset-based solution or a partner tool.
Where SAP reads it: Asset master (FI-AA) and the acquisition nota fiscal.
Inventory
Stock on a reference date, item by item and valued, including goods held by third parties or for them. Required at least for 31 December, usually in the February file.
Watch out
The total (H005) must equal the sum of the items (H010), and the value must tie to the stock accounts on the same date.
Who usually does the thinking
Controlling and tax, together.
Where SAP reads it: Stock and valuation from MM and the Material Ledger.
Production and stock control
Stock balances (K200), production and consumption (K230, K235), outsourced production (K250, K255), corrections (K280) and joint production (from K290).
Watch out
It follows how production really runs: orders open at month end, co-products, scrap, rework and outsourced steps.
Who usually does the thinking
Production, controlling and tax, with a lot of project design.
Where SAP reads it: Production and process orders, bills of materials and goods movements.
Other information
A checklist record (1010) and records by situation: exports (1100), value added per municipality (1400) used to share ICMS with cities, card payments received (1600) and more.
Watch out
Each state decides which of these records it wants, and some need data no SAP module keeps.
Who usually does the thinking
Tax team, with SAP data where it exists.
Where SAP reads it: Export documents, notas fiscais by municipality, payment data.
Control and totals
The number of lines per record and per block. Written with the file.
Watch out
Only breaks when someone edits the text file by hand.
Who usually does the thinking
Generated.
Where SAP reads it: Generated from the other blocks.
Monthly, one file per company. PIS and COFINS on revenue.
5 analytic · 1 mixed · 2 syntheticOpening and master data
Company, establishments, partners, items and the accounts used.
Watch out
The PIS and COFINS regime chosen for the year (cumulative or not) shapes the rest of the file.
Who usually does the thinking
SAP standard plus a yearly choice by the tax team.
Where SAP reads it: Master data and company settings.
Service documents
Service notas fiscais issued and received, with PIS and COFINS per item.
Watch out
Service notas come from each city’s system, so some arrive in SAP late or incomplete.
Who usually does the thinking
SAP standard.
Where SAP reads it: Service notas fiscais in the nota fiscal tables.
Goods documents
The same notas fiscais as in the EFD ICMS/IPI, seen from PIS and COFINS: tax situation (CST), base and rate per item.
Watch out
A CST set wrong in tax determination flows into every record.
Who usually does the thinking
SAP standard.
Where SAP reads it: J_1BNFDOC, J_1BNFLIN and J_1BNFSTX.
Transport and communication
Freight and communication documents with their PIS and COFINS.
Watch out
Freight on purchases can give credits; freight on transfers between your own plants usually does not.
Who usually does the thinking
SAP standard.
Where SAP reads it: CT-e and service notas fiscais.
Other operations
Revenues and credits that come without a nota fiscal: other operations (F100), credits on fixed assets (F120, F130) and withholdings (F600), among others.
Watch out
Someone has to decide which ledger postings belong here and with which tax situation.
Who usually does the thinking
Tax team with FI support.
Where SAP reads it: G/L postings and asset accounting.
PIS and COFINS calculation
Credits (M100, M500), contributions due (M200, M600) and revenues with no contribution (M400, M800), with their adjustments.
Watch out
Non-cumulative credits depend on what counts as an input for this business, a question courts and the Receita Federal still argue about.
Who usually does the thinking
The tax team, often with a partner engine.
Where SAP reads it: Built from blocks A, C, D and F plus credit rules.
Credit control and complements
Credits carried from earlier periods and how they were used (1100, 1500), legal proceedings and other complements.
Watch out
It carries history: a mistake in one month follows the file for years.
Who usually does the thinking
Tax team.
Where SAP reads it: Previous files and the tax team’s controls.
Control and totals
Line counts per record and block.
Watch out
Generated with the file.
Who usually does the thinking
Generated.
Where SAP reads it: Generated.
Yearly, one file per company. The accounting books.
3 analytic · 1 mixed · 1 syntheticOpening
Company, period, book type and the people who sign.
Watch out
The persons responsible and their qualifications are Customizing in SAP, kept up to date by someone.
Who usually does the thinking
SAP standard.
Where SAP reads it: Company code settings and ECD Customizing.
Entries and balances
Chart of accounts (I050) mapped to the government’s referential chart (I051), cost centers (I100), periodic balances (I155) and every journal entry (I200, I250).
Watch out
The referential mapping is a design decision made once, and the ECF reuses it.
Who usually does the thinking
SAP standard plus the mapping by FI and tax.
Where SAP reads it: Journal entries (ACDOCA; BKPF and BSEG in SAP ERP), G/L accounts and cost centers.
Financial statements
Balance sheet (J100) and income statement (J150), plus other statements and notes where required.
Watch out
The financial statement version must reproduce the statements the company publishes.
Who usually does the thinking
FI.
Where SAP reads it: Financial statement version.
Consolidation
Consolidated statements for groups that must report them: entities, eliminations and consolidated balances.
Watch out
Consolidation often lives outside the ledger, so the data has to come back in.
Who usually does the thinking
Group reporting team.
Where SAP reads it: Consolidation solution or group reporting.
Control and totals
Line counts per record and block.
Watch out
Generated with the file.
Who usually does the thinking
Generated.
Where SAP reads it: Generated.
Yearly, one file per company. Corporate income tax (IRPJ and CSLL).
3 analytic · 3 mixed · 3 syntheticOpening and parameters
Who the company is and how it is taxed: the parameters switch whole blocks on or off.
Watch out
One wrong parameter asks for blocks that do not apply, or hides ones that do.
Who usually does the thinking
Tax team.
Where SAP reads it: Entered for the file.
Data recovered from the ECD and the last ECF
Imported by the government program from the ECD and from last year’s ECF, not generated by your system.
Watch out
A wrong ECD comes back here, so fix the ECD first.
Who usually does the thinking
The PVA program.
Where SAP reads it: The ECD already sent.
Chart of accounts and balances
Accounts and cost centers with their referential mapping (J), and balances (K).
Watch out
Should match the ECD exactly.
Who usually does the thinking
SAP standard.
Where SAP reads it: Same as the ECD.
Statements by tax regime
Balance sheet and income statement for real profit (L), presumed profit (P), arbitrated profit (T) or exempt entities (U).
Watch out
Only the block of the company’s regime applies.
Who usually does the thinking
FI and tax.
Where SAP reads it: Ledger balances mapped to the referential chart.
e-LALUR and e-LACS
The bridge from accounting profit to taxable profit: additions, exclusions and loss carry-forwards for IRPJ and CSLL.
Watch out
Each addition and exclusion is a tax decision, many with their own control accounts carried over the years.
Who usually does the thinking
Tax team, often with a partner tool.
Where SAP reads it: Tax team’s calculation; few companies derive it fully from SAP.
IRPJ and CSLL calculation
Tax bases, rates, the 10% surcharge on IRPJ, incentives and the monthly estimates paid during the year.
Watch out
Has to tie to what was paid and offset during the year.
Who usually does the thinking
Tax team.
Where SAP reads it: Block M plus payments.
Country-by-country report
For multinational groups above the threshold, the group’s figures country by country.
Watch out
Data comes from the whole group, not from the Brazilian ledger.
Who usually does the thinking
Group tax.
Where SAP reads it: Group data.
Economic and general information
Exports, imports, operations abroad, related parties, partners and other data the Receita Federal cross-checks.
Watch out
Many lines need data spread across SD, MM, FI and treasury.
Who usually does the thinking
Tax team with help from every module.
Where SAP reads it: Spread across modules.
Control and totals
Line counts per record and block.
Watch out
Generated with the file.
Who usually does the thinking
Generated.
Where SAP reads it: Generated.
Our reading for teaching purposes, not an SAP classification. Which records SAP actually fills depends on the product and release: SAP Note 2248350 lists TDF’s coverage. Careful with one word: the EFD layout calls record C190 a “registro analítico”, meaning the summary of one document by tax situation (CST), CFOP and rate.
What SAP delivers well
- The nota fiscal with its taxes, once tax determination is configured.
- The signed XML, its authorization and its status history.
- The document-level records of each SPED file, and the accounting books for the ECD.
- A run history: parameters, logs and, in TDF and DRC, a monitor for proofs of delivery.
What stays with the company
- Each state’s adjustment codes, tax benefits and special regimes, across 27 federative units.
- CIAP coefficients, Bloco K mapping and the e-LALUR decisions.
- Returns outside SPED: state returns that still exist, and service tax returns in up to 5,570 municipalities.
- Validating in the PVA, reconciling with what was paid, and answering for the file: SAP calculates, the company signs.
Why every project is different
Same SAP release, different company, different files
Two companies on the same SAP release can face very different work. Switch on what applies to a company and see what it adds to the synthetic layer. The meter counts drivers, not hours: it is only an illustration.
Industry solutions make it sharper
SAP’s industry solutions bring their own documents and billing, and Brazil often has a document or a rule for that industry too.
SAP for Utilities · FI-CA
Electricity and water
Billing runs in contract accounts receivable and payable (FI-CA), and electricity bills have their own electronic document, the NF3e. Consultancies note that TDF’s EFD ICMS/IPI does not support FI-CA, so utilities lean on partners or custom builds.
DFSpro: SPED EFD in SAPSAP for Oil and Gas
Fuels
Fuel ICMS has been charged once, per litre, since 2023, and fuel items carry ANP product codes in the NF-e. Fuel was also the first sector forced onto the NF-e, in 2008.
Baguete (2007)Telecom billing
Telecommunications
Telecom services moved to their own electronic document, the NFCom, with very high volumes coming from billing systems that often sit outside SAP.
SAP for Retail · POS
Retail
Consumer sales use the NFC-e at the till, usually issued by the point-of-sale system, which leaves millions of small documents to bring into the books and the SPED files.
PP-PI · process industries
Food, beverages and chemicals
Bloco K must describe production in the tax authority’s terms: co-products, by-products, process losses and outsourced steps. Beverages and tobacco were the first sectors required to keep the complete Bloco K, from 2019.
Ajuste SINIEF 25/2016
Ecosystem
Partners: who fills the synthetic layer
Because SAP covers the legal document layer and leaves the company-specific calculations open, Brazil has a large market of tax software built to sit on top of SAP or beside it. Three set-ups are common:
- Inside SAPAn add-on in the SAP system, reading SAP tables and keeping its own.
- Beside SAPA separate platform, often in the cloud, that receives SAP data through an integration and calculates and files there.
- On top of TDFAn app built on TDF that reads its Central Tax Repository instead of keeping a copy of the data.
Source: GESIF (Synchro partner)
Thomson Reuters
Beside SAPONESOURCE (formerly Mastersaf) · Tax One
Thomson Reuters bought Brazil’s Mastersaf in May 2011. ONESOURCE Tax One is a cloud platform for tax books, calculations (ICMS, ICMS-ST, DIFAL, IPI, PIS, COFINS, ISS and withholdings), reconciliation and obligations, with a module for CBS, IBS and the selective tax. Thomson Reuters says it connects to SAP ECC and SAP S/4HANA through its own integration layer without changing SAP tables. It was also among the partners named in SAP’s 2014 TDF co-innovation.
Gap it covers: The synthetic layer, plus state obligations and service tax in more than 600 municipalities.
Sovos
Beside SAPTaxweb (2020) and Fit Sistemas (2021)
Sovos built its Brazil business by acquisition: Taxweb in 2020 for tax determination, and Fit Sistemas in 2021 for cloud SPED reporting and e-invoicing APIs covering NF-e, CT-e, NFC-e and other documents.
Gap it covers: Tax determination, SPED reporting and e-invoicing as cloud services.
Synchro
On top of TDFSynchro4TDF and Expert Fiscal
A Brazilian tax software company founded in 1991. In 2017 it launched SYN4TDF with SAP, a solution running inside SAP on top of TDF, later certified with SAP S/4HANA. It also offers a tax calculation engine integrated with SAP.
Gap it covers: Calculations, PVA-style validations and delivery of obligations, using TDF’s repository.
NTT DATA Business Solutions
For SAP and cloudGUEPARDO Tax and GUEPARDO e-Invoicing
An SAP partner’s suite for Brazil: GUEPARDO Tax for tax analysis, calculation and accessory obligations, and GUEPARDO e-Invoicing for issuing, receiving and recording fiscal documents.
Gap it covers: Calculations, obligations and fiscal documents, sold together with implementation services.
E-invoicing specialists
Beside or inside SAPFor example EDICOM, Qive and Megawork
When SAP NFE left mainstream maintenance, several vendors offered alternatives to DRC for issuing and receiving NF-e, from global e-invoicing networks to Brazilian inbound platforms and SAP add-ons.
Gap it covers: Issuing and receiving electronic documents. Compare coverage (NF-e, CT-e, NFS-e), support and how fast each follows SEFAZ and city changes.
Not a complete list and not a recommendation. Facts come from each vendor’s public pages and press coverage; check scope, certification and the tax reform roadmap before choosing. More partners, graded by topic, in SAP third-party solution partners.
Compared
SAP DRC elsewhere versus SAP DRC in Brazil
Same product name, different shape. If you know DRC from Italy, Mexico or a Peppol rollout, these are the differences that surprise people in Brazil. More on the product itself in our SAP DRC guide.
| Topic | Most DRC countries | Brazil | Verdict |
|---|---|---|---|
| Model | A mix: networks such as Peppol, and clearance models such as Italy’s SDI or Mexico’s CFDI. | Clearance before shipping: SEFAZ authorizes each NF-e before the goods move, and the DANFE travels with them. | Different |
| Which documents | Mostly invoices and credit notes; delivery notes in some countries. | Every movement of goods: sales, returns, transfers between your own plants, consignment, goods sent for processing, plus freight (CT-e) and cargo manifests (MDF-e). | Different |
| Source document in SAP | The eDocument, created from the billing document or the FI document. | Outbound: the nota fiscal, created by SD and MM. Inbound: the eDocument. | Different |
| Where you work | The eDocument Cockpit or the Manage Electronic Documents app. | The NF-e monitor (J1BNFE) for outbound; the eDocument Cockpit for inbound. | Different |
| Connection | SAP Integration Suite packages or the DRC cloud edition, depending on the country. | Brazil’s own SAP cloud services on SAP BTP, the outbound and inbound invoicing options, with SAP running the SEFAZ connection. | Different |
| Who you talk to | Usually one national authority or network. | The SEFAZ of each state for goods, and city halls for services, while the national NFS-e grows. | Different |
| Signature | Depends on the country; many network flows need none. | Every XML is signed with the company’s ICP-Brasil digital certificate. | Different |
| Format changes | Standards such as UBL, or national XML schemas. | XML schemas changed through frequent technical notes agreed by the federal and state tax authorities. | Different |
| Statutory reports | Run Statutory Reports with country report definitions. | Run Statutory Reports for the SPED files (DRC Brazil, grown out of ACR), or TDF. | Same idea |
| Licence metric | Documents in the cloud edition; company code and country objects in SAP S/4HANA. | The Brazil invoicing options are billed by number of documents. | Same idea |
| Age of the mandate | Many mandates are recent or still phasing in. | Mandatory since 2008: most SAP customers are migrating a mature process, not starting one. | Different |
| Next big change | In the EU, ViDA brings digital reporting for trade between member states from 2030. | CBS and IBS fields in every NF-e from 2026, with the full switch by 2033. | Different |
For consultants
Twelve things FI/CO consultants should know
The SPED files read FI, CO, MM and PP data, so the finance team ends up owning more of them than expected.
- 01FI
The ECD is the friendliest SPED file
It is mostly analytic: entries, balances and statements straight from the ledger. Spend the design time on the referential chart mapping (I051), because the ECF reuses it.
Our chart of accounts page - 02FI
Reconcile E116 with what was paid
The amounts to pay in the EFD (E116) must match the payment guides. Reconcile them with the tax payable accounts before the file goes out.
DFSpro: SPED EFD in SAP - 03CO and inventory
Bloco H is a valuation question
H005 must equal the sum of the H010 items, and the inventory value should tie to the stock accounts on the same date. With the Material Ledger, agree upfront which value goes into the file.
DFSpro: SPED EFD in SAP - 04CO and inventory
Bloco K follows your production design
Orders open at month end, co-products, scrap and outsourced steps all show up in Bloco K. A consumption record (K235) without its production record (K230) is a common error.
DFSpro: SPED EFD in SAP - 05FI
Fix the source, not the file
Correct the document or the master data in SAP and run the file again. Editing the text file breaks the trail between SAP and what the Receita Federal received.
DFSpro: SAP TDF - 06Projects
One material, one NCM
A material with different NCM codes in two plants produces conflicting item records (0200). Lock the NCM at material level early.
DFSpro: SAP TDF - 07FI
Test without your code: NOBADI
In SAP ERP, the OK-code NOBADI runs J_1BEFD_MAIN without the implemented BAdI methods. Compare both runs to see exactly what your custom code changes.
SAP Help: SPED EFD-ICMS/IPI - 08Projects
J1BECD lives in a deprecated package
In SAP S/4HANA the ECD program J_1BECD_MAIN sits in package J1BA_DEPRECATED, “Localization Brazil – Deprecated Objects”. Plan the ECD in TDF or DRC statutory reporting instead of carrying the old report forward.
ERPLingo: J1BECD - 09Projects
Rectify the TDF way
In TDF, correct block 0 through /TMF/EDIT_SPED_MD and the other blocks through shadow tables, run a Rectified file, send it, and upload the proof of delivery to the Tax Obligation Monitor.
DFSpro: SAP TDF - 10Projects
Open the ticket on the right component
DRC Brazil statutory reporting is FI-LOC-FI-BR-ACR; TDF is FIN-TMF-BR. A ticket on the wrong component gets rerouted, which costs time near a deadline.
KBA 2924049 - 11FI
SAP does not validate the file
Neither the SAP ERP reports nor TDF check the content of the file. The government’s PVA program does, so plan time to run it before every deadline.
SAP Help: SPED EFD-ICMS/IPI - 12Projects
Keep the evidence
For each period keep the run parameters, the log, the validated file and the proof of delivery. Auditors ask for the trail, not only the file.
DFSpro: SAP TDF
Suggestions
Where are you today? What to look at next
Pick the landscape closest to yours. These are the points we would review first; every company still needs its own assessment.
SAP ERP with GRC NF-e and the old SPED reports
- GRC NF-e left mainstream maintenance on 31 December 2025 and does not receive legal changes such as the tax reform. Plan the move to the DRC outbound and inbound options, or to a partner.
- List every custom BAdI implementation in the SPED reports: each one is a requirement the next solution has to cover.
- Decide where the SPED files will run after SAP ERP: TDF, DRC statutory reporting in SAP S/4HANA, or a partner.
- SAP ERP 6.0 mainstream maintenance ends in 2027. Align the tax roadmap with the SAP S/4HANA move instead of migrating twice.
SAP ERP with TDF running beside it
- Check the TDF support package against the current layouts, and SAP Note 2248350 for the records TDF covers.
- On SAP S/4HANA, TDF can run in the same system, so the sidecar and its replication can be retired in the move.
- Put the shadow and complement table loads in the migration plan: they hold decisions, not just data.
- Compare TDF with DRC statutory reporting before carrying TDF forward by default.
SAP S/4HANA with TDF
- Compare TDF with DRC statutory reporting file by file; SAP has published a blog on choosing between them.
- Bring the nota fiscal, the tax calculation and DRC to the tax reform notes together, using KBA 3642384 as the guide.
- Keep partner tools for the synthetic layer if they work; replace only what DRC really covers for your company.
- Review the shadow tables in use: some may point to master data that could be fixed at the source.
A new SAP S/4HANA project in Brazil
- Put e-invoicing (the DRC options) and the SPED files in scope from the design phase, not after go-live.
- Design for the reform from day one: CBS and IBS in tax determination, the nota fiscal and the reports.
- Map the synthetic layer early (apuração, Bloco K, CIAP, e-LALUR) and name an owner for each part: SAP standard, a partner or the tax team.
- Plan parallel runs and the PVA validation cycle before the first legal deadline after go-live.
SAP S/4HANA Cloud Public Edition
- Customization is limited to what the cloud releases, so the partner question comes earlier than on premise.
- Electronic documents and the Run Statutory Reports app are the standard path; check SAP’s Brazil scope for your release.
- Ask partners early how they connect to Public Edition, where only released APIs are allowed.
- Keep the synthetic-layer owners from the start: the tax team will still own the decisions.
Myths
Five things people believe about SAP and Brazilian compliance
Myth
SAP DRC covers every Brazilian obligation.FactDRC covers electronic documents and the main SPED files. State returns outside SPED, municipal service tax returns and the company-specific calculations stay with the company or a partner.
Myth
If SAP generated the file, SAP is responsible for it.FactSAP calculates and formats. The company validates, signs, sends and answers for the file.
Myth
An authorized NF-e proves the tax was right.FactSEFAZ checks the XML against its schema and a list of validation rules, not your tax decisions. A wrong rate can be authorized and still be wrong.
Myth
TDF validates the SPED file.FactTDF generates the file and tracks it in a monitor. The government’s PVA program is what validates it.
Myth
The ECD is the hardest SPED file.FactUsually the opposite: the ECD comes straight from the ledger. The EFD ICMS/IPI and the ECF carry most of the synthetic work.
Vocabulary
Eight words you will hear on day one
- SEFAZ
- The finance department of each state. It authorizes NF-e and collects ICMS.
- NF-e and DANFE
- The electronic invoice for goods (an XML file) and the printed summary that travels with the goods.
- SPED
- The Public Digital Bookkeeping System: the family of digital files that replaced paper books.
- PVA
- The government’s program that validates, signs and sends each SPED file.
- Apuração
- The period’s tax calculation: debits, minus credits, plus or minus adjustments.
- CNPJ and IE
- The federal company number, one per establishment, and the state taxpayer registration.
- Shadow table
- In TDF, a table that changes or adds data for the file without changing the SAP document.
- NSU
- The sequence number SEFAZ uses to hand out the documents addressed to a company.
Related pages
References
SAP Notes and knowledge base articles need an SAP for Me login. Consultancy and vendor pages are marked as such: treat their claims as a starting point. Checked in November 2026.
- SPED EFD-ICMS/IPI report (J_1BEFD_MAIN)SAP Help
- Customizing for SPED EFD-ICMS/IPI (BADI_J_1BEFD)SAP Help
- Customizing for SPED ECD (BADI_J_1BECD)SAP Help
- SAP GRC NFE 1.0: introduction and best practicesSAP Community
- SAP NFE 10.0: what it is all aboutSAP blog, September 2011
- Fiscal solutions for Brazil: SAP TDF powered by HANASAP blog, March 2014
- Coverage of SPED records by TDF (SAP Note 2248350)SAP Community
- SAP TDF SP17: what is newSAP blog
- SAP TDF SP20: what is newSAP blog, 2025
- TDF or DRC statutory reporting: which should I use?SAP blog
- ACR Brazil option: where to start with EFD-ReinfSAP blog, January 2021
- ACR Brazil option on premise: extending with HDI calculation viewsSAP blog
- SAP NFE: end of mainstream maintenanceSAP blog, April 2023
- KBA 2924049: EFD ICMS IPI in DRC Brazil and TDFSAP knowledge base
- KBA 3642384: Brazil tax reform troubleshooting guideSAP knowledge base
- Transaction J1BECD (package J1BA_DEPRECATED)ERPLingo
- Transaction J_1BEFDSAP Datasheet
- NF-e and Serpro: the history of digital governmentSerpro, 2019
- NF-e: a new status quo for the fuel marketBaguete, November 2007
- Ajuste SINIEF 25/2016 (Bloco K schedule)Normas Legais
- Ajuste SINIEF 25/2022 (Bloco K schedule)Inventti
- Ato Técnico Conjunto RFB/CGIBS 1/2026Machado Meyer, 2026
- SAP announces its tax management solution (TDF)Portal ERP, April 2014
- SAP TDF: where to startsapbr.com, June 2016
- SAP TDF and complementary solutions (vendor partner)GESIF, 2021
- SAP TDF in Brazil (consultancy)DFSpro
- SPED Fiscal in SAP (consultancy)DFSpro
- GRC NF-e to DRC migration (consultancy)DFSpro
- SAP ACR and SPED in SAP S/4HANA (consultancy)DFSpro
- SAP DRC country factsTJC Group
- Thomson Reuters acquires Brazil’s MastersafAccounting Today, May 2011
- ONESOURCE Tax One (vendor)Thomson Reuters
- Sovos acquires Taxweb (vendor)Sovos, 2020
- Sovos acquires Fit Sistemas (vendor)Sovos, March 2021
- About Synchro (vendor)Synchro
- Synchro launches a tax solution on TDF with SAPPortal ERP, June 2017
- GUEPARDO (vendor)NTT DATA Business Solutions
- End of SAP GRC support in Brazil (vendor)EDICOM, 2024
- Discontinuation of GRC in SAP (vendor)Qive
- SAP GRC NFe will be discontinued (vendor)Megawork, 2025