- Home
- Modules
- SAP DRC
SAP DRC: how your SAP system talks to the tax authority
SAP Document and Reporting Compliance (DRC) turns invoices, delivery notes and ledgers into the files governments ask for, one document at a time or one report per period, and keeps the proof of what was sent and what came back. This guide follows one invoice and one tax return through DRC, shows where each step lives in SAP, and collects the documented tricks that save hours in the eDocument Cockpit.
- SAP S/4HANA
- SAP S/4HANA Cloud
- SAP ERP
- Cloud edition on SAP BTP
- EDOC_COCKPIT
source: billing document- Created
- Mapped
- Sent
- Answer back
- In process
- Error
- Completed
What SAP DRC is
Two engines, one product
More and more tax authorities want to see transactions as they happen, not months later in a return. SAP’s product page describes this as the move from periodic reporting to continuous transaction controls. DRC answers it with two engines that live inside SAP S/4HANA (SAP ERP has the electronic documents engine only), so no data is copied to a separate tax tool. Only the connection to authorities and networks runs on SAP Business Technology Platform (SAP BTP).
- 1
Electronic documents
One per business document, close to real timeCreated from a single document, such as an invoice, a delivery or a withholding certificate, when it is posted. DRC turns it into the format the authority or the business partner expects, sends it and records every answer until the process ends.
Examples: Brazil’s NF-e, Peppol invoices, Peru’s electronic delivery notes.
EDOC_COCKPITF4306
- 2
Statutory reports
One per period: month, quarter or yearBuilt from many posted documents at once: VAT returns, EC sales lists, withholding tax reports and Brazil’s SPED files. The tax team reviews and approves them, then submits electronically where the country allows it, or downloads the file.
Examples: Brazil’s EFD ICMS IPI and ECD, EC sales lists, US Form 1099.
F1515 Run Statutory Reports
Quick test: which engine handles it?
Guess first, then open a card for the answer. Each answer links to the SAP documentation behind it.
An NF-e for one sale in BrazilBrazilShow the answer
Electronic documentEach NF-e goes to SEFAZ, the state tax authority, for authorization. In DRC, SAP runs the connection to SEFAZ’s web services from SAP BTP.
Source: SAP blog, April 2023The EFD ICMS IPI fileBrazilShow the answer
Statutory reportA monthly SPED file built from many postings and generated in the Run Statutory Reports app.
Source: SAP Help, EFD ICMS IPI ReportA Peppol invoice to a Belgian customerBelgiumShow the answer
Electronic documentPeppol invoices are electronic documents in DRC, and Belgium is one of the Peppol countries SAP lists.
Source: SAP Help, app and cockpit comparedThe ECD digital bookkeeping fileBrazilShow the answer
Statutory reportThe digital accounting books, built from the general ledger and generated in the Run Statutory Reports app.
Source: SAP Help, ECD ReportA withholding tax certificate for a supplierPeruShow the answer
Electronic documentEach certificate is created, approved by the authority and sent to the vendor.
Source: SAP Help, PeruThe EC Sales ListBelgiumShow the answer
Statutory reportA periodic list of sales to business customers in other EU countries, delivered as a statutory report.
Source: SAP Help, Belgium EC Sales ListAn electronic delivery note for a shipmentPeruShow the answer
Electronic documentCreated when the outbound delivery or goods issue is posted.
Source: SAP Help, PeruForm 1099-MISC for the yearUnited StatesShow the answer
Statutory reportA yearly withholding tax report built from supplier invoices and payments.
Source: SAP Help, 1099-MISC
Engine 1 · Electronic documents
Follow one invoice through DRC
The person who posts the invoice does nothing new. Everything below happens around their posting. Pick a step to see what happens, where you see it, and, in the Consultant view, what sits under the hood.
What happens · step 1 of 6
Post the business document
Someone posts a billing document in SD or a customer invoice in FI, exactly as before. If the company code is active for that kind of source document, DRC reacts to the posting.
Where you see it
Nothing new for the person posting. The eDocument appears in the eDocument Cockpit and in the Manage Electronic Documents app.
EDOC_COCKPITF4306
Under the hood
Source types are switched on per company code in view EDOCOMPANYACTIV, for example FI_INVOICE (accounting document), SD_INVOICE (billing document), OUTB_DELIV (outbound delivery) and GI_POSTING (goods issue). Business Transaction Events, assigned in FIBF, act as hooks after postings.
EDOCOMPANYACTIVFI_INVOICESD_INVOICEFIBF
Tables, Customizing views and BAdIs for this step are in the Consultant view.
Sources: SAP Help, Peru chapter (Activating Source Type Documents for Company Code); SAP PRESS (Technical Objects and BAdIs in SAP DRC, November 2025).
What happens · step 2 of 6
DRC creates the eDocument
DRC creates an eDocument linked to the source document. It has its own unique ID, a process and a status. If it was not created at posting time, for example because Customizing was missing, it can still be created later from the cockpit.
Where you see it
From the source document, Services for Object › Relationships shows the eDocument with its status; a double-click opens it in the cockpit.
EDOC_COCKPITEDOC_RELATION
Under the hood
The header is stored in table EDOCUMENT, with country-specific data in the tables listed in view EDOTYPEV. Billing and accounting document types are linked to eDocument types (TVFKEDOC, T003EDOC). Report EDOC_RELATION links eDocuments created before the relationship existed.
EDOCUMENTEDOTYPEVTVFKEDOCT003EDOC
Tables, Customizing views and BAdIs for this step are in the Consultant view.
Sources: SAP Help (eDocument Cockpit and Navigating from a Source Document to an eDocument, Peru chapter; Archiving Electronic Documents with EDOCUMENT); SAP PRESS (November 2025).
What happens · step 3 of 6
Map it to the legal format
The eDocument’s data is converted into the XML layout the authority defines. Codes that SAP does not store in the authority’s form are translated with value mappings; in SAP’s Peru example, units of measure are mapped to UNECE codes.
Where you see it
Most users never see this step. The files can be viewed or downloaded from the eDocument’s details in the app.
F4306
Under the hood
SAP Application Interface Framework (AIF) maps transactional data into the legally required XML. BC sets are uploaded with SCPR3 and activated with SCPR20; value mappings live in /AIF/VMAP and fix values in /AIF_CUST. BAdI EDOC_ADAPTOR, method SET_OUTPUT_DATA, changes the output without modifying SAP code.
AIFSCPR3SCPR20EDOC_ADAPTOR
Tables, Customizing views and BAdIs for this step are in the Consultant view.
Sources: SAP Help (Configurations for SAP Application Interface Framework, Peru chapter); SAP blog (September 2022); SAP PRESS (November 2025).
What happens · step 4 of 6
Send it
The file leaves through SAP BTP. Depending on the country scenario, the connection is an SAP integration package running in SAP Integration Suite or the DRC cloud edition. SAP supports one of the two per country and scenario, not both. Brazil’s NF-e is the exception: it has its own SAP cloud services.
Where you see it
Users press Submit in the cockpit or the app, or a background job sends the documents.
EDOC_BACKGROUND
Under the hood
Each eDocument type is linked to an interface type, and SOA services are assigned to the interfaces. The integration packages are published on the SAP Business Accelerator Hub (api.sap.com). BAdI EDOC_INTERFACE_CONNECTOR extends the interfacing logic.
EDOINTTYPEEDOC_INTERFACE_CONNECTOR
Tables, Customizing views and BAdIs for this step are in the Consultant view.
Sources: SAP Help, Peru chapter (Integrating With SAP Integration Suite; Processing eDocuments in the Background); SAP blog on cloud and on-premise (June 2023); SAP PRESS (November 2025).
What happens · step 5 of 6
The authority answers
The answer updates the eDocument: its process status moves on, the returned file is stored, and every step is written to the history. Incoming messages are kept with the eDocument.
Where you see it
History and files: in the cockpit under Goto › History; in the app on the Document Details page.
EDOC_COCKPITF4306
Under the hood
History goes to EDOCUMENTHISTORY, files to EDOCUMENTFILE and source files to EDOSRCFILE. Incoming messages use EDOMSGCONTROL, EDOMSGDATA, EDOMSGHISTORY and EDOMSGATTACHMENT. Inbound messages have their own handler, EDOC_MESSAGE_HANDLING.
EDOCUMENTHISTORYEDOCUMENTFILEEDOMSGDATA
Tables, Customizing views and BAdIs for this step are in the Consultant view.
Sources: SAP Help (Archiving Electronic Documents with EDOCUMENT; Authorization Objects, Peru chapter; app and cockpit compared).
What happens · step 6 of 6
Follow up
Documents that need a person show up as errors. Users resubmit, cancel or correct them. The app only lets you click the actions allowed in each scenario; the others are greyed out or hidden.
Where you see it
The eDocument Cockpit (all SAP S/4HANA releases) or the Manage Electronic Documents app (SAP S/4HANA 2021 and later), with its Error Analysis page.
EDOC_COCKPITF4306EDOC_COMPLETE
Under the hood
Process steps, actions and their parameters are defined in the Process Manager, view cluster EDOC_PROCMGR (SM34). For custom eDocument processes, the app also lets you define allowed actions by process status and a process status flow.
EDOC_PROCMGRSM34
Tables, Customizing views and BAdIs for this step are in the Consultant view.
Sources: SAP Help (app and cockpit compared; Use of Custom Electronic Document Processes); SAP PRESS (November 2025).
Statuses
Read an eDocument status like the tax team does
Every eDocument carries two layers of status. The process status is detailed and specific to each country process. Above it sits a simple eDocument status, In Process, Error or Completed, that tells you whether anyone has to act. Seen from the source document (Services for Object › Relationships), the same idea shows as three icons: completed, in process or action required. Pick a status to see what it means and what to do.
The process has not reached its end yet
The eDocument is somewhere between creation and the final answer. Its process status tells you which step it has reached, for example created but not yet submitted.
What to do
- Read the process status, not only the colour.
- If many documents wait at the same step, check whether a background job is scheduled for that action.
- In the app, filter by process status to count them without exporting to a spreadsheet.
Someone has to act
Something stopped the process. SAP lists the usual causes as data inconsistencies and technical or communication failures, which end in rejected exchanges. The document waits until a person fixes the cause and triggers the next action.
What to do
- Open the interface log and the application log of the document.
- In the app, use Error Analysis to group documents by error code and handle them together.
- Where Joule is enabled, ask it to explain the error in plain language.
The process is finished
The process has no step left to run. Completed documents are what the archiving program selects by default.
What to do
- Remember that Completed can also be set by hand with EDOC_COMPLETE.
- Plan archiving with archiving object EDOCUMENT once documents are no longer needed online.
- Archived eDocuments can still be displayed in the cockpit and the app.
The puzzle of the extra Completed
In the Manage Electronic Documents app, the Completed count can be higher than the sum of its process statuses. The difference is documents someone closed by hand with transaction EDOC_COMPLETE (Set eDocument Status to Completed). They count in the total but do not appear in the process status breakdown or the flow chart.
Two logs, two kinds of problem
Each eDocument has an interface log and an application log. In the cockpit they open in a pane beside the list once the details pane is switched on (see the tips); in the app they are on the Document Details page. The app also has an Error Analysis page that groups documents with errors by category and error code, so one fix can be applied to many documents.
SAP Help: app and cockpit comparedEngine 2 · Statutory reports
Follow one tax return through DRC
A statutory report is built once per period from many postings. DRC turns each obligation into reporting tasks with due dates, so the tax team works from a dashboard that shows what is completed, overdue or due soon. Pick a step.
What happens · step 1 of 7
Design the report
A report definition is the template of the output: its files, format and data mapping. A report category describes the obligation: its phases, its organizational units and whether submission is electronic or manual. Reporting activities are the steps users perform. SAP delivers standard reports for each supported country, and you can extend them.
Where you see it
Most users never open the design. Experts use the Define Statutory Reports app.
F2131
Under the hood
The app uses OData service SRF_REPORT_DEFINITION and SAPUI5 application SRF_REP_DEF_S1. Reports come in two types, Classic and Enhanced. An extension inherits all the functions of the standard report definition and adds your changes on top.
SRF_REPORT_DEFINITIONSRF_REP_DEF_S1
Technical objects for this step are in the Consultant view.
Sources: SAP Help (Run Statutory Reports; App Implementation: Define Statutory Reports; Usage of Run Statutory Reports; Extend Reports); SAP blogs on Define Statutory Reports (2021) and on extensibility (2022).
What happens · step 2 of 7
Set up the reporting entity
Each company that reports becomes a statutory reporting entity. You assign it organizational units, usually company codes, and the report categories it must file, then set each category’s periodicity and due date.
Where you see it
Customizing: Cross-Application Components › General Application Functions › Document and Reporting Compliance › Country/Region-Specific Settings › your country › Statutory Reporting › the report › General Settings › Setting Up Your Statutory Reporting.
Create Statutory Reporting EntitiesSet Periodicity of Report Category
Under the hood
When the content does not come through SAP Best Practices (then see SAP Note 3049113), sample settings come as BC sets activated with SCPR20: BCS_FIN_LOC_SRF_FISCAL_YEAR first, then HBCS_FIN_LOC_SRF for all countries or HBCS_FIN_LOC_SRF_XX for one country (XX is the ISO code). The bgRFC inbound destination SRF_REPORT_RUN must exist in SBGRFCCONF, and Adobe Document Services must be active for PDF output.
SCPR20HBCS_FIN_LOC_SRFSBGRFCCONFSRF_REPORT_RUN
Technical objects for this step are in the Consultant view.
Sources: SAP Help (Usage of Run Statutory Reports; Setting Up Your Statutory Reports; App Implementation: Run Statutory Reports).
What happens · step 3 of 7
Tasks appear on the dashboard
A background job creates and updates reporting tasks from the reporting entity settings. The dashboard shows what is completed, overdue or due soon. If you need tasks right away, Reporting Tasks › Update Reporting Tasks refreshes them for the reporting year you choose.
Where you see it
The dashboard of the Run Statutory Reports app.
F1515
Under the hood
Clean Up Reporting Tasks removes unwanted or inconsistent tasks, for example after wrong periodicity settings, together with their documents. Old tasks are archived with archiving object SRF_TASK. SAP’s knowledge base names the job SRF_TJD_CREATE_REPORTING_TASKS.
SRF_TASKSRF_TJD_CREATE_REPORTING_TASKS
Technical objects for this step are in the Consultant view.
Sources: SAP Help (Update Reporting Tasks; Run Statutory Reports; Statutory Reporting contents); KBA 3710409.
What happens · step 4 of 7
Generate the run
From the task, the user starts a run. It can run immediately or be scheduled, and a run in process can be cancelled. Supporting activities, such as Manage Tax Items for Legal Reporting or Tax Payable Posting, sit beside the generation step. Mass actions handle many reports in one go.
Where you see it
The Run Statutory Reports app.
F1515
Under the hood
The app relies on the bgRFC destination SRF_REPORT_RUN, the attachment service and output management for file and form generation.
SRF_REPORT_RUNOutput management
Technical objects for this step are in the Consultant view.
Sources: SAP Help (Run Statutory Reports; App Implementation: Run Statutory Reports).
What happens · step 5 of 7
Review and approve
The output can be previewed in a readable layout whatever its format: XML, XBRL, TXT or JSON. Users can adjust the generated data before submission; regenerating then refreshes the document and its associated documents. An approval workflow can make sure someone validates the report before it leaves.
Where you see it
In Run Statutory Reports: Preview, Manual Adjustment, Workflow for Approval, and Analyze Data, which drills down to the documents behind the report.
Analyze Data
Under the hood
Embedded analytics is not meant for mass data. SAP Note 2547776 explains why, and SAP recommends filters to keep response times down.
Note 2547776
Technical objects for this step are in the Consultant view.
Source: SAP Help (Run Statutory Reports).
What happens · step 6 of 7
Submit
Where the authority has a gateway, DRC submits electronically and updates the status as accepted or rejected. Otherwise the user downloads the file, or copies the values into the authority’s portal, and records the submission.
Where you see it
Submission statuses in Run Statutory Reports include Submitted to Authority, Submission Accepted by Authority and Submission Declined by Authority.
F1515
Under the hood
SAP Help describes electronic submission through the DRC cloud edition and keeps a list of the reports enabled for it. File compression is not available for reports submitted electronically.
Cloud edition
Technical objects for this step are in the Consultant view.
Sources: SAP Help (Run Statutory Reports; Integration for Submission of Reports); KBA 3675589.
What happens · step 7 of 7
Correct and clarify
After the declaration, some authorities accept a correction, an additional correction or a clarification. In the app you start a new phase on the same task. Each phase can be submitted once or several times, depending on the country.
Where you see it
Run Statutory Reports › start a new phase.
F1515
Under the hood
Phases are set in the report category. SAP Help illustrates them with a hypothetical country where corrections are allowed up to 25 days after the period ends and additional corrections up to one year after.
Report category
Technical objects for this step are in the Consultant view.
Sources: SAP Help (Correction, Additional Correction, and Clarification Phases); SAP blog on report categories (2021).
Classic or Enhanced
Statutory reports come in two types, Classic and Enhanced, and each has its own runtime screens in the Run Statutory Reports app. Check which type your report is before reading the documentation.
SAP Help: Usage of Run Statutory ReportsAd hoc reports
Some authorities ask for reports outside the normal calendar. Ad hoc reports are non-periodic, and their reporting tasks are not created automatically: users create them in the Run Statutory Reports app.
SAP Help: Ad Hoc ReportingWho sees which task
When organizational units are assigned to a reporting entity, users need authorization for those units to see the tasks, and to preview or download the documents of a run.
SAP Help: Usage of Run Statutory Reports
Brazil
Brazil: from GRC NF-e to DRC
Brazil authorizes every NF-e electronically at the state tax authority, SEFAZ. For years SAP customers did this through SAP NFE (GRC NF-e), an on-premise product on SAP NetWeaver. SAP planned its end for 31 December 2025 and points customers to two DRC cloud services on SAP BTP, in which SAP manages the connection to SEFAZ.
Two cloud services take over from SAP NFE
The successors are the outbound invoicing option for Brazil, for what you issue, and the inbound invoicing option for Brazil, for what you receive. Both are public cloud services on SAP BTP that work with SAP ERP and SAP S/4HANA.
- SAP planned the end of SAP NFE 10.0 for 31 December 2025 and asked customers to plan their migration (SAP blog, April 2023).
- SAP Help has migration guides on the inbound and outbound product pages, for customers coming from an on-premise solution.
- SAP Note 2671909 lists the notes required for the outbound nota fiscal; SAP Note 2776753 lists the notes for inbound NF-e.
- Both services are billed by number of documents.
- In December 2022, SAP noted that Brazil’s NF-e stays outside the DRC cloud edition, on its own cloud services.
Note 2671909Note 2776753
Sources: SAP blogs (April 2023, June 2022, June 2023); SAP service terms for the Brazil options (2022).
Outbound: NF-e, CT-e, MDF-e and NFS-e
Outbound documents start from the nota fiscal (tables J_1BNFDOC and J_1BNFLIN), which SD and MM processes create as before. They are followed in the NF-e/CT-e monitor, J1BNFE.
- Outbound CT-e since October 2021: authorization, cancellation, correction letter (carta de correção), gaps in CT-e numbering, SVC contingency and e-mails to business partners, with the same screens and tools as NF-e.
- Outbound MDF-e was delivered in 2022.
- NFS-e: in 2020 the cloud service covered São Paulo and Rio de Janeiro natively, other cities through partner enablement. SAP Help now lists new nota fiscal fields for the national NFS-e layout and the new São Paulo layout.
- An NF-e stuck In process and missing from the SEFAZ site, with report J_1BNFE_CF_STATUS_UPDATE ending in message J_1BNFE_CF 040, is covered by KBA 2941021.
- The company certificate for the cloud service is uploaded with NFE_MNG_CERT.
J1BNFEJ_1BNFE_CF_STATUS_UPDATEJ_1BNFE_ACTIVENFE_MNG_CERT
How the NF-e itself works: NF-e, Brazil’s electronic invoice.
Sources: KBAs 1641862, 2941021, 2479132 and 2400284; SAP blogs (October 2020, October 2021, December 2022); SAP Help, What’s New for Functional Localizations.
Inbound: suppliers’ NF-e and CT-e
Incoming NF-es and CT-es come from the cloud service into the eDocument Cockpit, where each is handled by its process, for example normal purchases. Posting them from DRC creates the nota fiscal.
- Receiver acknowledgment (manifestação do destinatário) has been available in the inbound service since July 2020.
- An NF-e missing from the cockpit can be entered by its access key with EDOC_BR_UPLOAD.
- The job EDOC_BR_DISTDFE_RETRIEVE brings XMLs from the cloud; EDOC_BR_PENDING_DOCU shows XMLs that failed because of configuration.
- When migrating, deactivate the old application and start the new one at the last NSU plus one; a brand-new go-live starts at NSU 0. Loading old XMLs into the cockpit counts against the document metric.
EDOC_COCKPITEDOC_BR_UPLOADEDOC_BR_DISTDFE_RETRIEVE
Sources: SAP blogs (July 2020, January 2021, implementation tips for the inbound option); KBA 3761940.
SPED files in Run Statutory Reports
DRC statutory reporting for Brazil, which grew out of advanced compliance reporting (ACR), generates SPED files in the Run Statutory Reports app of SAP S/4HANA. The older alternative is the Tax Declaration Framework (TDF); SAP’s knowledge base articles cover both.
- SAP Help’s Brazil chapter for SAP S/4HANA 2025 has report pages for ECD, ECF, EFD ICMS IPI, EFD Contribuições and EFD-Reinf. ECD, ECF and EFD ICMS IPI are generated in Run Statutory Reports, and EFD ICMS IPI is monthly.
- Opening an incident? DRC Brazil statutory reporting is component FI-LOC-FI-BR-ACR and TDF is FIN-TMF-BR; for EFD-Reinf, FI-LOC-FI-BR-REI and FIN-TMF-BR-ESO.
- SAP Note 3445225 enables the DRC cloud edition for EFD-Reinf.
F1515FI-LOC-FI-BR-ACRFIN-TMF-BR
Sources: SAP Help, Brazil chapter (ECD, ECF and EFD ICMS IPI reports); KBAs 2924049, 2922995 and 3777980.
CBS and IBS reach the nota fiscal
The consumption tax reform adds CBS and IBS to Brazil’s electronic documents. On the SAP side the changes arrive as SAP Notes for the nota fiscal and tax calculation, with a troubleshooting guide kept by SAP.
- KBA 3642384, Brazil Tax Reform Troubleshooting Guide, covers SAP ERP 6.0, SAP S/4HANA and DRC outbound NF-e (updated March 2026).
- New CBS and IBS fields exist in the nota fiscal tables J_1BNFDOC and J_1BNFLIN.
- New fields for the national NFS-e layout were added to J_1BNFDOC, J_1BNFLIN and J_1BNFSE_DOCREF.
- Under Ato Técnico Conjunto RFB/CGIBS nº 1 of 31 July 2026 (published 3 August 2026), NF-e, NFC-e, CT-e, CT-e OS, GTV-e, BP-e, NF3e and NFCom are not rejected during the transition when the CBS and IBS fields are missing. The obligation to report them remains.
KBA 3642384J_1BNFDOCJ_1BNFSE_DOCREF
Dates, XML layouts and the SAP Notes in order: Brazil’s tax reform and what changes in SAP.
Sources: KBAs 3642384 and 3784942; SAP Help, What’s New for Functional Localizations; Machado Meyer (August 2026); Sefin Rondônia (September 2026).
Versions
Where DRC runs: SAP ERP, SAP S/4HANA and the cloud
DRC is not the same product everywhere. Pick your system to see what you get.
SAP ERP 6.0
SAP ERP gets the electronic document framework only. Its statutory reports are SAP’s ABAP reports outside the DRC framework. The licence for SAP ERP is called SAP Document and Reporting Compliance, on-premise.
EDOC_COCKPIT
At a glance
- Yes:Electronic documents: yes, through the eDocument framework and the eDocument Cockpit.
- No:Statutory reporting framework: not in SAP ERP.
- No:Manage Electronic Documents app: not available; it starts with SAP S/4HANA 2021.
- Partly:Scope: SAP PRESS puts it at less than half of what SAP S/4HANA covers.
Sources: SAP PRESS (What is SAP DRC, October 2025); SAP blog on cloud and on-premise; SAP Help (app and cockpit compared).
SAP S/4HANA on-premise and Cloud Private Edition
Both engines with full access to Customizing and enhancements. This is where the eDocument Cockpit and the Manage Electronic Documents app live side by side.
EDOC_COCKPITF4306Run Statutory Reports
At a glance
- Yes:Electronic documents: yes; the app is available as of SAP S/4HANA 2021, the cockpit in all releases.
- Yes:Statutory reports: yes.
- Yes:Enhancements: Customizing, BAdIs and custom fields.
- Partly:Joule error explanation: in the app, rolling out country by country; SAP documents the Joule integration for Private Edition.
Sources: SAP PRESS (October 2025); SAP Help (Manage Electronic Documents; Electronic Document Error Handling with Joule).
SAP S/4HANA Cloud Public Edition
Nearly the same tasks as on-premise, with customization limited to what the cloud allows. Settings are configuration activities (SSCUIs), reached through the Manage Your Solution app. For countries SAP does not deliver, partners can build eDocument processes themselves with developer extensibility.
SSCUI 105518
At a glance
- Yes:Electronic documents: yes.
- Yes:Statutory reports: yes.
- Partly:Customization: limited to cloud configuration and released extensibility.
- Yes:Own countries: Manage eDocument Type, Manage eDocument Interface and Manage eDocument Process apps.
Sources: SAP PRESS (October 2025); SAP Learning (localization as a self-service); SAP blog (initial configuration); KBA 3047155 (an SSCUI in Manage Your Solution).
Central Finance
In a Central Finance system, only the statutory reporting framework is supported, with fewer compliance tasks than a full SAP S/4HANA system.
Run Statutory Reports
At a glance
- No:Electronic documents framework: not supported in Central Finance.
- Partly:Statutory reports: yes, with fewer tasks than SAP S/4HANA.
Source: SAP PRESS (What is SAP DRC, October 2025).
SAP Document and Reporting Compliance, cloud edition
A service on SAP BTP that connects business systems to authorities and networks; SAP released a new version in December 2022. It complements the DRC component inside SAP ERP or SAP S/4HANA and does not replace it: documents are still created and monitored in the business system. Brazil’s NF-e runs on its own SAP cloud services.
SAP BTP
At a glance
- Yes:Role: connectivity to authorities and networks.
- No:Creates documents? no; that stays in the business system.
- Partly:Integration choice: one option per country and scenario: cloud edition or SAP Integration Suite.
- Yes:Billing unit: documents, in blocks of 10,000 a year.
Sources: SAP blog on cloud and on-premise; SAP price list, checked October 2026.
| Topic | SAP ERP (ECC) | SAP S/4HANA |
|---|---|---|
| Electronic documents | eDocument framework and EDOC_COCKPIT | Same framework, plus the Manage Electronic Documents app (2021 and later) |
| Statutory reports | Not in DRC; SAP’s ABAP reports outside the framework | Statutory reporting framework (Run Statutory Reports) |
| Moving to SAP S/4HANA | Your starting point | SAP Help lists migration steps in the country chapters (Peru, for example: BC sets and SAP Notes) |
| Error help with Joule | No | In the app, where Joule is available (integration documented for Private Edition) |
How SAP counts DRC
SAP’s price list (checked October 2026) uses two different units. Prices are given on request.
- DocumentsCloud edition (and private cloud edition): blocks of 10,000 documents a year that run down as you use them. Electronic submissions of statutory reports count too.
- ObjectsDRC for SAP S/4HANA Cloud Public Edition and Private Edition: each combination of company code and country is one object, and usage does not deplete it.
Configuration
The setup map for electronic documents
The common backbone in SAP S/4HANA (on-premise and Private Edition), in the order consultants usually walk it. The activity names come from SAP Help’s Peru chapter; every country has its own chapter with its own additions, so that chapter stays the final checklist. Tick the steps as you go; nothing is saved.
of 8 steps ticked
In SAP S/4HANA Cloud Public Edition
The same ideas are set in configuration activities (SSCUIs), reached through the Manage Your Solution app, for example Activate Document and Reporting Compliance Features (SSCUI 105518). Partners who need a country SAP does not deliver can build their own eDocument process with the Manage eDocument Type, Manage eDocument Interface and Manage eDocument Process apps plus developer extensibility, on a three-system landscape.
Reference
The DRC toolbox
Transactions, apps, tables, BAdIs and authorization objects found in SAP documentation. Filter by kind or type a code. The Source column says where each one was confirmed.
| Code | Kind | What it is for | Documented for | Source |
|---|---|---|---|---|
EDOC_COCKPIT | Transaction / program | eDocument Cockpit: display, create, submit and monitor eDocuments. | ERP, S/4HANA | SAP Help (Peru) |
EDOC_BACKGROUND | Transaction / program | eDocument Background Processing: schedule jobs that run process actions on selected eDocuments. | S/4HANA | SAP Help (Peru) |
EDOC_COMPLETE | Transaction / program | Set eDocument Status to Completed, by hand. | S/4HANA | SAP Help |
EDOC_RELATION | Transaction / program | Create the relationship between existing eDocuments and their source documents. | S/4HANA | SAP Help (Peru) |
EDOC_MESSAGE_HANDLING | Transaction / program | eDocument Inbound Message Handler. | S/4HANA | SAP Help (Peru) |
SM34 · EDOC_PROCMGR | Transaction / program | Process Manager: process steps, actions and parameters. | S/4HANA | SAP PRESS |
SM34 · EDOC_DCCERRCATE | Transaction / program | Error categories for the app’s Error Analysis page, with the user to notify. | S/4HANA | SAP Help |
/AIF/VMAP | Transaction / program | AIF value mappings, such as SAP units to the codes the authority expects. | S/4HANA | SAP Help (Peru) |
/AIF_CUST | Transaction / program | AIF fix values and fix value tables. | S/4HANA | SAP Help (Peru) |
/IWNGW/VB_REG_P | Transaction / program | Notification providers: activate EDOC_DCC_ERROR_ANAL_NOTIFICATION for error notifications. | S/4HANA | SAP Help |
SBGRFCCONF | Transaction / program | bgRFC configuration: the inbound destination SRF_REPORT_RUN must exist for statutory reporting. | S/4HANA | SAP Help |
J1BNFE | Transaction / program | Brazil: NF-e/CT-e monitor for outbound documents. | Brazil | KBA 1641862 |
J_1BNFE_CF_STATUS_UPDATE | Transaction / program | Brazil: status report for outbound documents sent to the cloud service; KBA 2941021 covers its message J_1BNFE_CF 040. | Brazil | KBA 2941021 |
NFE_MNG_CERT | Transaction / program | Brazil: upload of the company certificate for the cloud service. | Brazil | KBA 2479132 |
EDOC_BR_UPLOAD | Transaction / program | Brazil: manual entry of an incoming NF-e by its access key. | Brazil | SAP blog |
F4306 | Fiori app | Manage Electronic Documents: overview, document list, details, Error Analysis, archived documents. OData service EDOC_DCC_SRV. | S/4HANA 2021+, Cloud | SAP Help |
Manage eDocument Process | Fiori app | With Manage eDocument Type and Manage eDocument Interface, builds custom eDocument processes. | Public Edition | SAP Learning |
F1515 | Fiori app | Run Statutory Reports: reporting tasks, runs, preview, manual adjustment, approval and submission. | S/4HANA | SAP Help |
F2131 | Fiori app | Define Statutory Reports: report definitions, categories and reporting activities. OData service SRF_REPORT_DEFINITION. | S/4HANA | SAP Help |
EDOCUMENT | Table / view | eDocument header: one row per eDocument. | S/4HANA | SAP Help |
EDOCUMENTHISTORY | Table / view | eDocument history: every step and status change. | ERP, S/4HANA | SAP Help |
EDOCUMENTFILE | Table / view | eDocument files, such as the XML sent and received. | S/4HANA | SAP Help |
EDOSRCFILE | Table / view | eDocument source files. | S/4HANA | SAP Help |
EDOMSGDATA | Table / view | Incoming messages, with EDOMSGCONTROL, EDOMSGHISTORY and EDOMSGATTACHMENT. | S/4HANA | SAP Help |
EDOCOMPANYACTIV | Table / view | Source types activated per company code (maintained with SM30). | S/4HANA | SAP Help (Peru) |
GCOV_ADV_LIC_CTR | Table / view | Countries and regions with DRC features activated. | S/4HANA | SAP Help (Peru) |
EDOGENCUSTV | Table / view | General parameters for eDocuments, such as the cockpit’s details pane. | S/4HANA | SAP Help (Peru) |
EDOTYPEV | Table / view | eDocument types and their country-specific tables. | S/4HANA | SAP Help |
TVFKEDOC | Table / view | Links billing document types to eDocument types. | S/4HANA | SAP PRESS |
T003EDOC | Table / view | Links accounting document types to eDocument types. | S/4HANA | SAP PRESS |
EDOINTTYPE | Table / view | Links eDocument types to interface types. | S/4HANA | SAP PRESS |
J_1BNFDOC | Table / view | Brazil: nota fiscal header; line items are in J_1BNFLIN. | Brazil | SAP Help (What’s New) |
J_1BNFE_ACTIVE | Table / view | Brazil: NF-e actual status table; a missing entry raises error J1B_NFE012. | Brazil | KBA 2400284 |
EDOC_ADAPTOR | BAdI | Adjust eDocuments: relevance, XML output, eDocument type, cancellation rules, PDF form. | S/4HANA | SAP PRESS |
EDOC_INTERFACE_CONNECTOR | BAdI | Extend the interfacing logic. | S/4HANA | SAP PRESS |
EDOC_PARTNER_CONNECTOR | BAdI | Send eDocuments to business partners, for example by email. | S/4HANA | SAP PRESS |
EDOC_CUSTOM_FIELDS | BAdI | Add customer fields to the eDocument. | S/4HANA | SAP PRESS |
EDOC_INCOM_CONNECTOR | BAdI | Incoming automation, used with EDOC_FIORI_TARGET_DOC to open target documents from the app. | S/4HANA | SAP Help |
EDOC_ADAPTOR_CLOUD | BAdI | Cloud counterpart for changing the XML output (SET_OUTPUT_DATA). | Public Edition | SAP Learning |
HBCS_FIN_LOC_SRF | BC set | BC set with sample statutory reporting settings for all countries; HBCS_FIN_LOC_SRF_XX for one country. Activate after BCS_FIN_LOC_SRF_FISCAL_YEAR with SCPR20. | S/4HANA | SAP Help |
EDOCUMENT | Archiving | Archiving object; write EDOCUMENT_WRI, delete EDOCUMENT_DEL, reload EDOCUMENT_REL. Info structures SAP_EDOC_01 and SAP_EDOC_02. | S/4HANA | SAP Help |
EDOC_DELETE_OBSOLETE_OBJECTS | Archiving | Deletes incoming messages with status INVALID or REJECTED. | S/4HANA | SAP Help |
SRF_TASK | Archiving | Archiving object for statutory reporting tasks. | S/4HANA | SAP Help |
EDO_BUK | Authorization | eDocument authorization by company code. | S/4HANA | SAP Help (Peru) |
EDO_PROC | Authorization | Authorization by process and process step. | S/4HANA | SAP Help (Peru) |
EDO_ORG | Authorization | Authorization by organizational unit. | S/4HANA | SAP Help (Peru) |
EDO_GLOVAR | Authorization | Maintain global selection variants in the cockpit. | S/4HANA | SAP Help (Peru) |
Nothing matches. Try another word or pick All.
Troubleshooting
Error decoder
Messages and symptoms that SAP has written knowledge base articles about. Pick one to see what it tells you and where SAP documents the fix. Knowledge base articles need an SAP for Me login.
Not Relevant
No eDocument for a billing document; it shows as Not Relevant
What it tells you
DRC did not consider the document relevant, so no eDocument was created. In SAP’s examples the eDocument type was assigned to the billing type although that billing type posts to accounting (it belongs in the accounting document type assignment), or a tax code was missing from a country setting.
Where to look
Check the eDocument type assignments. Use the billing-type assignment only for billing types without a journal entry, such as pro forma invoices. After fixing the setup, create the missing eDocuments from the cockpit.
Applies to: SAP S/4HANA Cloud Public Edition (South Korea and Italy examples)
KBA 3756865 and KBA 3785031EDOCUMENT094
The action is not allowed for any of the selected eDocuments
What it tells you
None of the selected eDocuments allows the action you chose in its current state.
Where to look
Check each document’s process status and the actions its process offers. The app avoids this by letting you click only the actions allowed in each scenario.
Applies to: SAP ERP and SAP S/4HANA (Spain SII example)
KBA 2550955Process step TRIGG_SEND
Status of the eDocument does not allow the execution of process step TRIGG_SEND
What it tells you
The process tried to run a step, such as sending, that the current status does not allow.
Where to look
The KBA shows a case where editing an eDocument in the cockpit triggered a send step. Compare the status with the steps defined for the process.
Applies to: SAP ERP and SAP S/4HANA (India example)
KBA 3016627EDOCUMENT006
Error while inserting record into table EDOCUMENTHISTORY
What it tells you
The history of the eDocument could not be written. SAP reports it mostly in automated background jobs that edit or cancel eDocuments.
Where to look
Review the background jobs that act on the same documents, then follow the KBA.
Applies to: SAP ERP, SAP S/4HANA and the DRC service, all countries
KBA 3595486EDOCUMENT081
Action not defined for process. Check view EDOACTIONSTEPV
What it tells you
An answer arrived for an action that the process does not define. In SAP’s example, an incoming invoice rejected in OpenText VIM did not update the eDocument.
Where to look
Compare the process definition with the action named in the message, then follow the KBA.
Applies to: SAP ERP, SAP S/4HANA, Public Edition and cloud edition (Serbia example)
KBA 3781433Cockpit folders
I want my own folders in the eDocument Cockpit
What it tells you
The cockpit’s folder structure, one folder per country process, cannot be customized. Documents of the same process stay in the same folder.
Where to look
The Manage Electronic Documents app is an alternative view, with counts and filters per process status.
Applies to: SAP ERP, SAP S/4HANA and the DRC service
KBA 3754449Documented, but little known
13 documented tricks that save hours
Each one comes from SAP Help, an SAP Note or a knowledge base article, linked under the tip.
- 01Key users
Jump from the invoice to its eDocument
In the source document, open Services for Object › Relationships. The eDocument appears with its status; double-click to open it in the cockpit. For documents created before the link existed, run EDOC_RELATION.
EDOC_RELATION
- 02Consultants
Turn on the cockpit’s details pane
Set the general parameter Allow Screen with Details Pane in eDocument Cockpit to X. Users then double-click the Logs/File column to see the application log, interface log and last file beside the list. Custom developments do not show in that screen.
EDOGENCUSTV
- 03Consultants
Automate the clicks, but watch the loops
Most cockpit and app actions can run as scheduled jobs with EDOC_BACKGROUND. Watch those jobs: SAP has a knowledge base article on errors writing the eDocument history that appear mainly in automated jobs that edit or cancel eDocuments.
EDOC_BACKGROUND
- 04Key users
Completed is not always accepted
EDOC_COMPLETE closes eDocuments by hand. That is why the app’s Completed total can be bigger than the sum of its process statuses. Ask who closed documents manually before reading the numbers to an auditor.
EDOC_COMPLETE
- 05Consultants
Send errors to the right person automatically
Activate notification provider EDOC_DCC_ERROR_ANAL_NOTIFICATION, define error categories and enter a user in Notifications To. Only one user per category, so use a team user if several people share the work. The user gets the notifications without changing their own settings.
EDOC_DCCERRCATE/IWNGW/VB_REG_P
- 06Key users
Fix one error, solve fifty documents
The app’s Error Analysis page groups documents with errors by category and error code, shows the key part of external error messages, and can email the error details to support.
F4306
- 07Consultants
Upgrade both halves of the app together
Manage Electronic Documents stops working if the back end and front end are on different support package levels, for example S4CORE 109 SP01 with UIS4H 109 SP00. SAP Note 3388028 lists the notes for the app, general and per country.
S4COREUIS4HNote 3388028
- 08Consultants
Archive without losing sight
Archiving object EDOCUMENT selects completed eDocuments by default. Archived ones can still be displayed in the cockpit and the app. Use the delivered archive info structures SAP_EDOC_01 and SAP_EDOC_02 or your own, and activate them in each client.
EDOCUMENT_WRISAP_EDOC_01
- 09Key users
Find the eDocument’s GUID and source key
Every eDocument has a GUID that identifies it in the system, plus a source key that points to its source document. SAP explains how to find both in the cockpit in a knowledge base article. The History option under the Goto menu shows each document’s history and file list.
EDOC_COCKPIT
- 10Consultants
The generic AIF content comes first
Before any country content, AIF needs the generic eDocument settings: global BC sets delivered with SAP Note 2360094, uploaded with SCPR3 and activated with SCPR20. SAP Help states that AIF is fully compliant with the eDocument solution as of version 701 SP06. SAP Note 3214131 describes the AIF implementation and upgrade steps.
Note 2360094SCPR3SCPR20
- 11Consultants
Extend a standard report, and check its data source
An extension inherits all the functions of the standard report definition. In SAP’s own example, the data source behind the VAT return, I_StRpTaxReturnCube, is not released under the C1 stability contract, so its interface can change with an upgrade. Retest extensions after each upgrade.
F2131I_StRpTaxReturnCube
- 12Key users
Missing a reporting task? Refresh it yourself
Reporting Tasks › Update Reporting Tasks in Run Statutory Reports creates or updates the tasks for the reporting entities, year and report you choose, without waiting for the background job.
F1515
- 13Key users
Brazil: an NF-e stuck In process
An outbound NF-e that stays In process, does not show on the SEFAZ site, and makes report J_1BNFE_CF_STATUS_UPDATE end with message J_1BNFE_CF 040 is a known case: SAP documents it in a knowledge base article.
J_1BNFE_CF_STATUS_UPDATEJ1BNFE
Evolution
How DRC came to be
From a framework for a handful of countries to one product for e-documents and statutory reports. Coverage figures are SAP’s own, as published at the time. Gold dots mark Brazil.
- 2019DecemberSAP Document Compliance, built on the eDocument framework by SAP Globalization Services, covers 18 countries and 42 processes on SAP ERP and SAP S/4HANA, according to an SAP user group presentation.
- 2020July · BrazilReceiver acknowledgment (manifestação do destinatário) arrives in the inbound cloud service.
- 2021AugustRelease 2108 of SAP S/4HANA Cloud brings the Document and Reporting Compliance dashboard, a global view of electronic documents.
- 2021SeptemberSAP launches SAP Document and Reporting Compliance, combining SAP Document Compliance with its solutions for advanced compliance reporting (ACR).
- 2021OctoberFor SAP S/4HANA, electronic documents move to the licence SAP Document and Reporting Compliance for SAP S/4HANA; the on-premise licence name stays for SAP ERP.
- 2021October · BrazilOutbound CT-e joins NF-e in the cloud service, with the same screens and tools.
- 2021SAP S/4HANA 2021 releaseThe Manage Electronic Documents app (F4306) arrives as an SAP Fiori alternative to the eDocument Cockpit, with status counts and error analysis.
- 2022OctoberSAP counts ready-to-use scenarios for 416 regulations in 57 countries.
- 2022DecemberSAP releases a new version of the cloud edition on SAP BTP for connectivity to authorities and networks.
- 2023April · BrazilSAP announces the planned end of SAP NFE 10.0 (GRC NF-e) for 31 December 2025 and points to the DRC inbound and outbound options.
- 2026By OctoberSAP Help for SAP S/4HANA 2025 FPS02, dated October 2026, documents Joule explaining and summarizing electronic document errors in the app, rolling out country by country.
Coverage, as SAP published it
Different units, so not a like-for-like count: SAP Document Compliance processes in 2019, DRC regulations in 2022.
Myths
Things people get wrong about DRC
Myth
DRC is a separate tax system you copy your data into.FactDRC runs inside SAP S/4HANA, and its electronic documents part inside SAP ERP too, with no data replication. Only the connection to authorities runs on SAP BTP.
Myth
The cloud edition replaces DRC in SAP S/4HANA.FactIt complements it. Documents are still created and monitored in the business system; the cloud edition handles the connection.
Myth
The Fiori app covers every country the cockpit covers.FactNot yet. In the SAP S/4HANA 2025 documentation the cockpit supports more countries, including Brazil, Chile, Mexico and Peru.
Myth
Completed means the authority accepted it.FactNot always. Transaction EDOC_COMPLETE sets the Completed status by hand, without any answer from the authority.
Myth
If no eDocument was created, the invoice has to be posted again.FactThe cockpit can create and submit eDocuments that were not created when the source document was posted.
Myth
Archived eDocuments are gone from the cockpit.FactArchived eDocuments can be searched and displayed in the cockpit and in the Manage Electronic Documents app.
Frequently asked questions
Do I need SAP BTP to use DRC?
For the electronic exchange, yes: the connection to authorities and networks is delivered on SAP BTP, either as SAP integration packages in SAP Integration Suite or as the DRC cloud edition. Which one applies depends on the country scenario, and SAP supports one per scenario. Brazil’s NF-e has its own SAP cloud services.
eDocument Cockpit or Manage Electronic Documents?
They need basically the same Customizing, so a company using the cockpit can start the app right away. The app adds counts by status, a flow chart, Error Analysis and action filtering, but it is available only as of SAP S/4HANA 2021 and does not yet cover every country the cockpit covers. Check the app’s Supported Tasks by Country/Region page for yours.
Can I add my own fields to an eDocument?
Yes. SAP documents customer-specific fields for the eDocument, and the BAdI EDOC_CUSTOM_FIELDS adds custom fields to the EDOCUMENT table. The app has its own extensibility for custom fields.
Can DRC continue processing incoming invoices from suppliers?
The app supports an incoming automation solution through two BAdIs, EDOC_INCOM_CONNECTOR and EDOC_FIORI_TARGET_DOC, so received electronic documents can be processed further and the target document opened from the app.
What if SAP does not deliver my country?
In SAP S/4HANA Cloud Public Edition, partners can build eDocument processes for countries without SAP-delivered localization, using developer extensibility and the Manage eDocument Type, Interface and Process apps. SAP Learning walks through a full example.
Who gets to see and act on eDocuments?
Access is controlled with authorization objects EDO_BUK (company code), EDO_PROC (process and process step), EDO_ORG (organizational unit) and EDO_GLOVAR (global selection variants), in class AAAB.
Is SAP GRC NF-e still supported?
SAP planned the end of SAP NFE 10.0 for 31 December 2025 and recommends the DRC inbound and outbound invoicing options for Brazil (SAP blog, April 2023). Check the current maintenance status of your contract with SAP.
How much does DRC cost?
SAP gives prices on request. The units differ: the cloud edition is sold in blocks of documents per year, while DRC for SAP S/4HANA Cloud Public and Private Edition counts company code and country combinations (checked October 2026).
Related pages
References
Checked in October 2026. SAP Help pages are for SAP S/4HANA 2025 FPS02 (October 2026) unless the page says otherwise. SAP Notes and knowledge base articles need an SAP for Me login.
- What is SAP Document and Reporting Compliance?SAP S/4HANA 2025
- eDocument CockpitSAP S/4HANA 2025, Peru chapter
- Manage Electronic Documents (F4306)SAP S/4HANA 2025
- Manage Electronic Documents and eDocument Cockpit comparedSAP S/4HANA 2025
- Why the Completed count is higherSAP S/4HANA 2025
- Configuring error notificationsSAP S/4HANA 2025
- Electronic document error handling with JouleSAP S/4HANA 2025
- Processing eDocuments in the backgroundSAP S/4HANA 2025, Peru chapter
- eDocument authorization objectsSAP S/4HANA 2025, Peru chapter
- Activating Document and Reporting Compliance featuresSAP S/4HANA 2025, Peru chapter
- Activating source type documents for company codeSAP S/4HANA 2025, Peru chapter
- Navigating from a source document to an eDocumentSAP S/4HANA 2025, Peru chapter
- Displaying errors in the eDocument CockpitSAP S/4HANA 2025, Peru chapter
- Configurations for SAP Application Interface FrameworkSAP S/4HANA 2025, Peru chapter
- Integrating with SAP Integration SuiteSAP S/4HANA 2025, Peru chapter
- Archiving electronic documents with EDOCUMENTSAP S/4HANA 2025
- Run Statutory ReportsSAP S/4HANA 2025
- Usage of Run Statutory ReportsSAP S/4HANA 2025
- App implementation: Run Statutory ReportsSAP S/4HANA 2025
- App implementation: Define Statutory ReportsSAP S/4HANA 2025
- Update reporting tasksSAP S/4HANA 2025
- Correction, additional correction and clarification phasesSAP S/4HANA 2025
- Extend reportsSAP S/4HANA 2025
- Ad hoc reportingSAP S/4HANA 2025
- Use of custom electronic document processesSAP S/4HANA 2025
- ECD, ECF and EFD ICMS IPI reports (Brazil)SAP S/4HANA 2025
- Nota fiscal fields for the national NFS-e layoutWhat’s New for Functional Localizations
- KBA 3756865 and 3785031: no eDocument createdSAP for Me
- KBA 2550955: action not allowed (EDOCUMENT094)SAP for Me
- KBA 3016627: status does not allow the process stepSAP for Me
- KBA 3595486: error inserting into EDOCUMENTHISTORYSAP for Me
- KBA 3781433: action not defined for processSAP for Me
- KBA 3754449: cockpit folders cannot be customizedSAP for Me
- KBA 3642147: GUID and source key in EDOC_COCKPITSAP for Me
- KBA 3710409: reporting task jobSAP for Me
- KBA 3675589: submission statusSAP for Me
- KBA 1641862: NF-e/CT-e monitor J1BNFESAP for Me
- KBA 2941021: NF-e status update from the cloudSAP for Me
- KBA 2479132: certificate upload for the Brazil cloud serviceSAP for Me
- KBA 2400284: nota fiscal and NF-e status tablesSAP for Me
- KBA 3761940: posting incoming NF-e from DRCSAP for Me
- KBA 2924049: EFD ICMS IPI with DRC Brazil and TDFSAP for Me
- KBA 3777980: EFD-Reinf and the cloud editionSAP for Me
- KBA 3642384: Brazil tax reform troubleshooting guideSAP for Me
- KBA 3784942: CBS and IBS fields in the nota fiscalSAP for Me
- KBA 2922995: EFD-Reinf with DRC Brazil and TDFSAP for Me
- KBA 3047155: an SSCUI in Manage Your SolutionSAP for Me
- SAP Document and Reporting Compliancesap.com
- DRC plans and unitssap.com, checked October 2026
- DRC: cloud or on-premise, not an either-orSAP blog, June 2023
- E-invoicing and reporting compliance summit 2021SAP blog, September 2021
- GRC with SAP S/4HANA Cloud 2111SAP blog, November 2021
- From eDocument Cockpit to Manage Electronic DocumentsSAP blog, September 2022
- SAP S/4HANA update for 2022: DRCSAP blog, October 2022
- Define Statutory Reports: introductionSAP blog, March 2021
- Define Statutory Reports: creating a report categorySAP blog, June 2021
- Extensibility in DRC statutory reportingSAP blog, March 2022
- Ad hoc reporting in advanced compliance reportingSAP blog, March 2020
- SAP Electronic Invoicing for Brazil: end of maintenanceSAP blog, April 2023
- Migration documentation for the Brazil inbound and outbound optionsSAP blog, June 2022
- NFS-e for other cities with partner enablementSAP blog, October 2020
- Outbound CT-e supportSAP blog, October 2021
- NF-e: what happened in 2022SAP blog, December 2022
- Receiver acknowledgment for inboundSAP blog, July 2020
- Manual entry and supplier notifications in the eDocument CockpitSAP blog, January 2021
- Implementation tips: inbound invoicing option for BrazilSAP blog
- eDocument Colombia: cloud initial configurationSAP blog
- Creating electronic document and legal reportSAP Learning
- SAP Document Compliance: current developmentsSAP user group presentation, December 2019
- Service terms: inbound and outbound invoicing options for BrazilSAP, 2022
- What is SAP DRC?SAP PRESS, October 2025
- Technical objects and BAdIs in SAP DRCSAP PRESS, November 2025
- One solution for e-invoicing and tax reporting for SAPPwC Finland, February 2022
- NF-e without CBS and IBS will not be rejectedSefin Rondônia, September 2026
- Ato Técnico Conjunto RFB/CGIBS 1/2026Machado Meyer, August 2026