6/30/25, 6:07 AM

SAP Document and Reporting

Compliance, outbound invoicing option
for Brazil
Generated on: 2025-06-30 06:07:50 GMT+0000

SAP Document and Reporting Compliance, outbound invoicing option for Brazil | Cloud

Public

Original content: https://help.sap.com/docs/SLH_NFe/71b3b178e5cb4a50a88cf2985a14f17c?locale=en-

US&state=PRODUCTION&version=Cloud

Warning

This document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.
The information included in custom documentation may not reflect the arrangement of topics in SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.

For more information, please visit https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit SAP Help Portal. 1
 6/30/25, 6:07 AM

Initial Setup
The steps to get started with SAP Document and Reporting Compliance, outbound invoicing option for Brazil.

This section is a central source of information that provides you with all important details you need to properly create your
subaccount in SAP Business Technology Platform, to be able to proceed with the required configuration for Outbound nota fiscal.

Prerequisites
You've set up your global account and subaccount on SAP BTP.

You've purchased a license for Outbound nota fiscal.

 Caution
You cannot use multiple contracts of SAP Document and Reporting Compliance, outbound invoicing option for Brazil,
with the same SAP ERP or SAP S/4HANA systems and system clients.

You've got the Adobe Forms to generate PDF files of electronic documents.

 Note
Examples are provided for a better understanding. Don't use or insert the example values in your configuration. Only insert the
values in editable fields when indicated accordingly.

1. Creating a Subaccount
Get your access to SAP Business Technology Platform to be able to use SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

2. Enabling Cloud Foundry

Enable Cloud Foundry for this account to make SAP Document and Reporting Compliance, outbound invoicing option for
Brazil available and allow you to create the service instance.

3. Creating a New Space

The services available for SAP Document and Reporting Compliance, outbound invoicing option for Brazil run in the spaces
connected to your subaccount. Create a new space to be able to run the services.

4. Entitling the Service to a Subaccount

Entitle SAP Document and Reporting Compliance, outbound invoicing option for Brazil to your subaccount to ensure that
the service is available.

5. Creating a Service Instance

Create a service instance to associate your subaccount to SAP Document and Reporting Compliance, outbound invoicing
option for Brazil.

6. Creating a New Service Key

You create a new service key to get access to SAP Document and Reporting Compliance, outbound invoicing option for
Brazil.

7. Subscribing to Notifications
After you’ve onboarded to SAP Document and Reporting Compliance, outbound invoicing option for Brazil, you can
subscribe to receive notifications about new features, corrections, or service downtimes.

8. Migrating from SAP Electronic Invoicing for Brazil (SAP NFE)

Migrate from SAP Electronic Invoicing for Brazil (SAP NFE) to SAP Document and Reporting Compliance, outbound
invoicing option for Brazil by performing configuration steps. We provide the configuration steps in SAP NFE for
comparison purposes.

This is custom documentation. For more information, please visit SAP Help Portal. 2
 6/30/25, 6:07 AM

Creating a Subaccount
Get your access to SAP Business Technology Platform to be able to use SAP Document and Reporting Compliance, outbound
invoicing option for Brazil.

Context
If you've purchased licenses for SAP Document and Reporting Compliance, inbound invoicing option for Brazil and SAP Document
and Reporting Compliance, outbound invoicing option for Brazil, use the same subaccount for the initial setup of both services.

Procedure
Follow the steps on Create a Subaccount.

a. Indicate that the provider is AWS, and the region is Brazil (São Paulo).

b. Choose a name for your subdomain that identifies your company. For example, if your company domain is
examplecompany.com, name your subdomain as com-examplecompany-nfe.

Task overview: Initial Setup

Next task: Enabling Cloud Foundry

Enabling Cloud Foundry

Enable Cloud Foundry for this account to make SAP Document and Reporting Compliance, outbound invoicing option for Brazil
available and allow you to create the service instance.

Procedure
Follow the steps on Create Orgs.

Task overview: Initial Setup

Previous task: Creating a Subaccount

Next task: Creating a New Space

Creating a New Space

The services available for SAP Document and Reporting Compliance, outbound invoicing option for Brazil run in the spaces
connected to your subaccount. Create a new space to be able to run the services.

Procedure

To create a new space, follow the steps on Create Spaces.

Note that you don't need to assign quota to the new space after you create it.

This is custom documentation. For more information, please visit SAP Help Portal. 3
 6/30/25, 6:07 AM

Task overview: Initial Setup

Previous task: Enabling Cloud Foundry

Next task: Entitling the Service to a Subaccount

Entitling the Service to a Subaccount

Entitle SAP Document and Reporting Compliance, outbound invoicing option for Brazil to your subaccount to ensure that the
service is available.

Procedure

Follow the steps on Configure Entitlements and Quotas for Subaccounts, under the Entitlements and Quotas from Your
Subaccount section.

To add new service plans to the subaccount, choose the SAP Document and Reporting Compliance outbound nota fiscal service.
Ensure that standard is selected.

Results
The option SAP Document and Reporting Compliance, outbound invoicing option for Brazil must be available for your
subaccount. In the Service Marketplace, search for nfe to see more details.

Task overview: Initial Setup

Previous task: Creating a New Space

Next task: Creating a Service Instance

Related Information
View and Manage Services from the Service Marketplace

Creating a Service Instance

Create a service instance to associate your subaccount to SAP Document and Reporting Compliance, outbound invoicing option
for Brazil.

Procedure

Follow the steps on Creating Service Instances in Cloud Foundry, under the Creating service instances from your subaccount
section.

a. Choose the standard option for the Service Plan.

b. Choose a name for your service instance that identifies your company.

Note that you don't need to configure instance parameters for the service.

This is custom documentation. For more information, please visit SAP Help Portal. 4
 6/30/25, 6:07 AM

Task overview: Initial Setup

Previous task: Entitling the Service to a Subaccount

Next task: Creating a New Service Key

Creating a New Service Key

You create a new service key to get access to SAP Document and Reporting Compliance, outbound invoicing option for Brazil.

Procedure

Follow the steps on Creating Service Keys in Cloud Foundry.

Choose the outbound invoicing option service.

Results
The system generates your service key, which provides you with access to SAP Document and Reporting Compliance, outbound
invoicing option for Brazil. Note that the values of the service key fields (url, clientid, clientsecret), which are present in the JSON
file, are used in various steps of Integration.

Task overview: Initial Setup

Previous task: Creating a Service Instance

Next task: Subscribing to Notifications

Subscribing to Notifications
After you’ve onboarded to SAP Document and Reporting Compliance, outbound invoicing option for Brazil, you can subscribe to
receive notifications about new features, corrections, or service downtimes.

Procedure
1. Go to Cloud Availability Center & Cloud System Notification Subscriptions .

2. Subscribe to the following applications:

a. Cloud Availability Center to get notifications about the cloud products availability and maintenance.

b. Cloud System Notification Subscriptions to get updates specifically about a service, such as updates, downtimes,
or any other relevant communication.

Results
You receive notifications per e-mail.

Note that you have to wait a while after completing the Initial Steps for the service to appear in the Cloud Availability Center.

Task overview: Initial Setup

This is custom documentation. For more information, please visit SAP Help Portal. 5
 6/30/25, 6:07 AM

Previous task: Creating a New Service Key

Next task: Migrating from SAP Electronic Invoicing for Brazil (SAP NFE)

Migrating from SAP Electronic Invoicing for Brazil (SAP NFE)

Migrate from SAP Electronic Invoicing for Brazil (SAP NFE) to SAP Document and Reporting Compliance, outbound invoicing
option for Brazil by performing configuration steps. We provide the configuration steps in SAP NFE for comparison purposes.

Context
This task is relevant only for customers who use SAP NFE. If you start with Outbound nota fiscal, you do not need to perform this
task.

Procedure
Perform the configuration steps below.

In the column Perform These Steps in SAP Document and Reporting Compliance Outbound nota fiscal, you find the configurations
steps to perform, and then the Equivalent in SAP NFE: Navigation in the SPRO Transaction column for comparison.

Perform These Steps in SAP Document and Reporting Equivalent in SAP NFE: Navigation in the SPRO Transaction
Compliance, outbound invoicing option for Brazil

The solution reads the CNPJ from the source system configuration Nota Fiscal Eletronica General Settings Maintain Own Tax
per company code provided in views: CNPJ Main (view Numbers (view /XNFE/CNPJ_MAINTAIN)
V_T001Z_N), parameter J_1BCG or CNPJ Branch (view
J_1BBRANCV- CGC_BRANCH).

Manage Digital Certificates (transaction NFE_MNG_CERT) in ERP Nota Fiscal Eletronica Signature
to upload, update, and delete digital certificates on the Manage
Digital Certificates screen. For more information, see Uploading Tax
Authorities Digital Certificate.

You need to have the credentials to access a cloud solution and Nota Fiscal Eletronica Communication to ERP Back End
integrate it in the source system. See how to generate the System
credentials and do the proper integration: Initial Setup and
Integration.

To upload the certificate, make the settings in Customizing for Nota Fiscal Eletronica Outbound Maintain System
Nota Fiscal Eletronica Signature . Regarding XML validation, Response for Own Tax Numbers (view
the cloud solution validates the XML content using the latest XSD /XNFE/CNPJ_SETTINGS)
as a reference. This validation is done automatically when sending
a NF-e from J1BNFE. If there is an error, the system displays a
message.

The concept of Steps does not exist in the cloud solution, so we do Nota Fiscal Eletronica Outbound Maintain Control
not offer equivalent customizing. Parameters for Process Flow (view /XNFE/CNTRL_PROCFLOW)

The available parameters that control the handling of PI Nota Fiscal Eletronica Outbound Define Control Parameters
Acknowledgments are not relevant in the cloud solution. for Process Steps (view /XNFE/PROCCTRL_OUTB)

The B2B is activated through customer master data using the tag Nota Fiscal Eletronica Outbound Activate B2B (Business
MAILNFE for NF-e and MAILCTE for CT-e in field e-mail. More than Partners, Natural Persons, Foreign Partners)

This is custom documentation. For more information, please visit SAP Help Portal. 6
 6/30/25, 6:07 AM

Perform These Steps in SAP Document and Reporting Equivalent in SAP NFE: Navigation in the SPRO Transaction
Compliance, outbound invoicing option for Brazil

one e-mail address can be informed.​For more information, see

Configuring Email Addresses to Send XML and PDF Files.

This customizing is not relevant as the communication to the cloud Nota Fiscal Eletronica Outbound NF-e NF-e: Maintain
service is done in the source system. The Region (view Connected Authority Systems (view /XNFE/GOVPARNFE)
J_1BBRANCV) and the Environment type (view
J_1BNFE_CUST3_4V), are derived from business place
configuration:​Configure Communication Settings for Business
Place.

The main XML version for the document NF-e or CT-e can be Nota Fiscal Eletronica Outbound NF-e NF-e: Maintain
maintained in NF-e: System Configuration (view Version of Message Types (view /XNFE/XMLVERSDETNF)
J_1BNFE_CUST3_4V). For customizing settings, see Configure
Communication Settings for Business Place. The other XML
versions for events and skipping are maintained centrally in the
cloud service.

The service status check is done whenever a document is sent to Nota Fiscal Eletronica Outbound NF-e NF-e: Maintain
SEFAZ. For more information, see Service Status Screen. The SVC Region-Dependent Settings (view /XNFE/NFE_TSRV)
contingency system is configured centrally in the cloud service.

This view is not relevant for the cloud solution as SAP is Nota Fiscal Eletronica Outbound NF-e NF-e: Maintain
responsible for managing the communication with tax authorities Batch Parameters (view /XNFE/V_BATCHPAR)
web services.

This view is not relevant for the cloud solution as SAP is Nota Fiscal Eletronica Outbound NF-e NF-e: Maintain
responsible for managing the communication with tax authorities Process Determination for Outbound NF-es (view
web services. /XNFE/V_OUTBPD)

This view is not necessary, as status codes are retrieved Nota Fiscal Eletronica Outbound NF-e NF-e: Define
automatically from SEFAZ response. Authority's Status Code (view /XNFE/TSTATT)

If some characters are not accepted by certain State SEFAZ, this is Nota Fiscal Eletronica Outbound NF-e NF-e: Maintain
adjusted centrally in the cloud service. Validation Rules (view /XNFE/NFE_XMLVALIDC)

This customizing is not relevant as the communication to the cloud Nota Fiscal Eletronica Outbound CT-e CT-e: Maintain
service is done in the source system. The Region (view Connected Authority Systems (view /XNFE/GOVPAR)
J_1BBRANCV) and Environment type (view
J_1BNFE_CUST3_4V) are derived from business place
configuration:​Configure Communication Settings for Business
Place.

The main XML version for the document NF-e or CT-e can be Nota Fiscal Eletronica Outbound CT-e CT-e: Maintain
maintained in NF-e: System Configuration (view Version of Message Types (view /XNFE/XMLVERSDET)
J_1BNFE_CUST3_4V).

The service status check is done whenever a document is sent to Nota Fiscal Eletronica Outbound CT-e CT-e: Maintain
SEFAZ. For more information, see Service Status Screen. The QR Region-Dependent Settings (view /XNFE/CTE_TSRV)
Code URL is maintained centrally in the cloud service.​

This BAdI is not relevant, because the signature is done in the cloud Nota Fiscal Eletronica Outbound Business Add-Ins for
solution. Outbound Documents BAdI: Signature for Outbound
Documents

This BAdI​is not relevant, because the cloud solution is also an API Nota Fiscal Eletronica Outbound Business Add-Ins for
solution, which can be integrated to a non-SAP System. Outbound Documents Business Add-Ins for Outbound NF-es
NF-e BAdI: Call Non-SAP System via RFC Communication

This is custom documentation. For more information, please visit SAP Help Portal. 7
 6/30/25, 6:07 AM

Perform These Steps in SAP Document and Reporting Equivalent in SAP NFE: Navigation in the SPRO Transaction
Compliance, outbound invoicing option for Brazil

This BAdI does not have an equivalent in the cloud solution. The Nota Fiscal Eletronica Outbound Business Add-Ins for
extension parameters should be extended in existing BAdIs in the Outbound Documents Business Add-Ins for Outbound NF-es
source system: General Enhancements for Electronic Fiscal NF-e BAdI: Store Extension Parameters from ERP Back-End
Documents (BAdI CL_NFE_PRINT) or Additional Data for Nota System
Fiscal (BAdI J_1BNF_ADD_DATA). For more information, see
Business Add-Ins (BAdIs) for Electronic Fiscal Documents.

This BAdI is not relevant, because the cloud solution is responsible Nota Fiscal Eletronica Outbound Business Add-Ins for
for the messaging. Outbound Documents Business Add-Ins for Outbound NF-es
NF-e BAdI: Automatic Processing of Rejected NF-es

This BAdI is not relevant, because the cloud solution is also an API Nota Fiscal Eletronica Outbound Business Add-Ins for
solution, which can be integrated into a non-SAP System. Outbound Documents Business Add-Ins for Outbound CT-es
CT-e BAdI: Call Non-SAP System via RFC Communication

Task overview: Initial Setup

Previous task: Subscribing to Notifications

Development
You use SAP Document and Reporting Compliance, outbound invoicing option for Brazil through a source system, which is
integrated to the cloud and enables you to proceed with your tasks, without having to implement an entire landscape. The service
runs in the background of your original system, in this case, once you have access to it and are granted with the required
authorizations, you can issue an electronic fiscal document using your source system with a cloud technology.

The SAP Document and Reporting Compliance, outbound invoicing option for Brazil is integrated to your source system through
the REST APIs, which represent each service covered by the system. All REST APIs are responsible to send the invoice information
you have filled while you were issuing your electronic fiscal documents. Considering this scenario, this service uses a JSON format,
which is converted into XML, that will be sent to tax authorities to get their approval.

Class References
In order to create and convert properly the client in each API, the following objects have been included in this integration:

CL_HTTP_CLIENT: Creates the client using the IF_HTTP_CLIENT interface.

CL_SXML_WRITER: Converts our structures into XML data.

CL_ABAP_CONV_IN_CE: Converts ABAP structures into JSON.

See Also

For more information about how to configure your account and integrate it to the cloud, see Initial Setup.

For more information about the APIs, see REST APIs.

Architecture Description

This is custom documentation. For more information, please visit SAP Help Portal. 8
 6/30/25, 6:07 AM
SAP Document and Reporting Compliance, outbound invoicing option for Brazil is built on SAP Business Technology Platform. It
connects your source system to the cloud and, consequently, to tax authorities servers.

For each action required after you issue the electronic fiscal document, your source system calls a REST API specific for your need.
This API calls a SOAP, which is a message exchange protocol, and connects the SAP cloud to the tax authority.

Click on the interactive graphic to get more information about each item.

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

REST APIs
SAP Document and Reporting Compliance, outbound invoicing option for Brazil integrates with your source system through SAP
Business Technology Platform and enables you to complete tasks by using REST APIs, to proceed with your business transactions.
Each API represents a specific service available, with different functionalities.

For more information about APIs, access SAP Business Accelerator Hub .

Related Information
XML Multiple Download
NF-e Authorize
NF-e Event
NF-e Status Service
NF-e Inbound Simple
NFS-e - Electronic Service Nota Fiscal
NF3-e Event
NF3-e Authorize

XML Multiple Download

You use this XML Multipe Download REST API to download a great amount of XMLs of your electronic fiscal documents by
selecting it accordingly.

This is custom documentation. For more information, please visit SAP Help Portal. 9
 6/30/25, 6:07 AM
The XML Multiple Download has the following features:

Downloads several XML at the same time using NF-e Monitor.

Saves the downloaded fiscal documents in a logical directory, once you run it in a batch.

 Note
We recommend you to use this functionality for auditing purposes.

NF-e Authorize
You use the NF-e Authorize REST API to authorize synchronously or asynchronously your Electronic Nota Fiscal (NF-e), in a batch.

The NF-e Authorize has the following features:

Sends your Electronic Fiscal Documents for approval.

Gets the status of your Electronic Fiscal Documents after sending it for authorization. The system returns you the following
status:

Received by messaging system: You NF-e has been received by the system, but has not been sent to tax
authorities yet.

The NF-e document has already been sent: You have sent your NF-e for authorization, but the tax
authorities have not approved it yet.

SEFAZ Server Error: Your NF-e has been sent to the messaging system, however, SEFAZ server might be
offline.

URL not found for tpAmb: The URL is incorrect or no longer valid.

Tenant was not found: The tentant available for your company has not been found by the system.

Tenant is not trusted!: Your tenant is not reliable, then you cannot proceed with this process.

Error processing the receipt: An error occurred while the receipt of your operation is being processed.

Error converting NF-e sent to XML: An error occurred while converting your NF-e sent for approval into
XML.

Error while marshalling NF-e: An error occurred during your NF-e serialization and was not transferred
from your source system to the cloud.

Error processing SEFAZ response: An error occurred while processing SEFAZ response.

Error while updating NF-e status: An error occurred while processing NF-e status and updating it in your
original system.

Stores and keeps the XML of all electronic fiscal documents you have issued, during the legal deadline.

Sends an e-mail automatically to your business partner when your Electronic Nota Fiscal is authorized by the tax
authorities.

Posts an electronic fiscal document under Contingency mode (SVC) when you cannot send it to the tax authorities under
normal circumstances, such an interruption in SEFAZ server.

Verifies if your application it's online or not. Once you proceed with this checking, the system returns you a status for it.

This is custom documentation. For more information, please visit SAP Help Portal. 10
 6/30/25, 6:07 AM
Check below the process flow for it:

1. Your source system sends the electronic fiscal document to SAP Document and Reporting Compliance, outbound invoicing
option for Brazil.

2. The service puts everything together in a batch.

3. Sends the electronic fiscal documents you have issued to SEFAZ.

4. Connects with SEFAZ server.

5. Gets the status provided by SEFAZ and sends this information to your original system.

6. Your source system gets the NF-e status from SAP Document and Reporting Compliance, outbound invoicing option for
Brazil.

For more information about SEFAZ status code, see SEFAZ web portal.

Brazilian Tax Authorities

You issue an electronic fiscal document and, in order to proceed with your business transaction and release your goods, you need
to request the Brazilian tax authorities for approval, in this case SEFAZ (Secretaria da Fazenda).

Once you send an NF-e for approval, such document is received by the government server that returns you its status, if it is
authorized or rejected.

For more information about Brazilian Tax Authorities, see SEFAZ webpage.

NF-e Event
The NF-e Event REST API determines the actions related to electronic fiscal documents that enables you to communicate it with
Brazilian tax authorities.

The NF-e Events has the following features:

Sends a cancellation request for Brazilian tax authorities when you have an electronic fiscal document that needs to be
cancelled, moreover notify your recipients about it.

Creates an Electronic Correction Letter (CC-e) in order to adjust any incorrect information in your NF-e, after SEFAZ
authorization, and inform the Brazilian government and your recipients that your such document had to be rectified.

Enables you to skip a document number, or a series, that is not going to be used anymore, and inform Brazilian tax
authorities your action followed by a reason for that. This feature applies to the following scenarios:

You are no longer using this document number.

You had an error during the issuing of your electronic fiscal document.

Posts an electronic fiscal document under Contingency mode (SVC) when you cannot send it to the tax authorities under
normal circumstances, such as a SEFAZ server disruption.

Stores and keeps the XML of all electronic fiscal documents you have issued and its events.

Sends an e-mail automatically to your business partner when you run such events and your request is approved by SEFAZ.

Resends the same e-mail to your business partner, if necessary.

Enables you to select a check box that compaires the structure and fields of your NF-e with the XSD provided by SEFAZ, as
a result it validates your XML schema when you send an event request for authorization.

This is custom documentation. For more information, please visit SAP Help Portal. 11
 6/30/25, 6:07 AM

 Note
This functionality is available through an activation.

Verifies if your application it's online or not. Once you proceed with this checking, the system returns you a status for it.

NF-e Status Service

The NF-e Status Service REST API returns you the status from Brazilian tax authorities for your electronic fiscal document and a
disruption in their server, if any.

NF-e Status Service has the following features:

Gets the status for your electronic fiscal document, if it is authorized, rejected or still in processing.

Gets the information if SEFAZ server is online or offline.

Verifies the availability of the service in both servers, normal and SVC.

NF-e Inbound Simple

An API that helps you manage inbound NF-es that your supplier has issued and sent to you.

The NF-e Inbound Simple REST API allows you to manage documents for the inbound NF-e process.

 Note
The API leaves XML files of official documents stored and available for consulting, for legal compliance reasons.

The NF-e Inbound Simple API has the following features:

Receives the XML file of a new official document. During this part of the processing, the API does the following:

Validates the XML file according to the current SEFAZ layout, checking if the file structure is correct and if it
corresponds to an NF-e, or Electronic Correction Letters (CC-e) or Cancellation events.

Saves the key information fields in the database, and saves the XML file. Both the fields and the XML file are then
made available to the source system.

Validates the digital signature of the XML file, and checks the document status in the SEFAZ database.

Retrieves all the new inbound invoice documents for a specific CNPJ. During this part of the processing, the API does the
following:

Returns the key information fields from the database.

Deletes the information from the database after it’s no longer needed - note that the XML file remains available.

Downloads the XML file of an existing official document.

NFS-e - Electronic Service Nota Fiscal

The NFS-e - Electronic Service Nota Fiscal REST API enables you to send your Provisional Service Receipt - RPS (Recibo Provisório
de Serviços) and request tax authorities approval for an NFS-e. To complete this procedure, you issue your RPS and sends it to the

This is custom documentation. For more information, please visit SAP Help Portal. 12
 6/30/25, 6:07 AM
city hall, which returns you the NFS-e authorized.

NFS-e has the following features:

Sends your NFS-e for municipal tax authorities and request their approval.

Allows you to cancel or send a replacement for an NFS-e when you issue such electronic fiscal document that contains any
incorrect information.

Enables you to issue an NFS-e under contingency mode, in case the tax authorities server is offline.

Stores the XML for all electronic fiscal document you have issued.

Receives and stores the Provisional Service Receipt - RPS (Recibo Provisório de Serviços), generates a batch and
communicates the status with your source system.

Gets the result of this process and sends back to your source system with the status of your NFS-e, as requested from it.

Enables you to download the correspondent XML of your NFS-e.

Verifies if your application is online or not. Once you proceed with this checking, the system returns you a status for it.

 Note
These features are only available for the cites of São Paulo and Rio de Janeiro.

Administrative Process in ERP

The Administrative Process is a procedure you start on through ERP, after issuing your Provisional Service Receipt - RPS (Recibo
Provisório de Serviços) and send it using NFS-e - Electronic Service Nota Fiscal REST API. This process has to be done in the
following cases:

Your NFS-e needs to be cancelled, but the respective ISS collection form (guia de recolhimento de Imposto Sobre Serviços)
has already been issued.

You need to create a replacement for the original NFS-e.

In these scenarios, you need to follow the steps described below:

1. You request the cancellation of your NFS-e in your source system.

2. Tax authorities rejects your request.

3. You print your NFS-e and contact the City Hall request an authorization to cancel such document.

4. Your NFS-e is properly cancelled.

5. You repeat the cancellation request in your source system to update the status of your NFS-e, otherwise it keeps in process.

6. Your source system updates the status as Cancelled.

 Note
This process is only possible to be done in case your ISS collection form (guia de recolhimento de Imposto Sobre Serviços) has
not been paid yet, in a deadline of six months after its issuing. Moreover, the cancellation scenario for an Administrative
Process is only available for the city of São Paulo.

Whether you are located in São Paulo city, once you have completed this process, the system changes the number and replaces it
for the new one. The previous number is kept only in the Writer screen for further reference.

This is custom documentation. For more information, please visit SAP Help Portal. 13
 6/30/25, 6:07 AM

NF3-e Event
The NF3-e Event REST API determines the actions related to electronic fiscal documents that enable you to communicate it with
Brazilian tax authorities.

The NF3-e Events have the following features:

1. Sends a cancellation request for Brazilian tax authorities when you have an electronic fiscal document that needs to be
cancelled, moreover notify your recipients about it.

2. Posts an electronic fiscal document under Contingency mode (SVC) when you can’t send it to the tax authorities under
normal circumstances, such as a SEFAZ server disruption.

3. Stores and keeps the XML of all electronic fiscal documents you’ve issued and its events.

4. Sends an e-mail automatically to your business partner when you run such events and your request is approved by SEFAZ.

5. Resends the same e-mail to your business partner, if necessary.

NF3-e Authorize
You use the NF3-e Authorize REST API, in a batch, to authorize synchronously or asynchronously your Electronic Nota Fiscal (NF3-
e).

The NF3-e Authorize has the following features:

1. Sends your Electronic Fiscal Documents for approval.

2. Gets the status of your Electronic Fiscal Documents after sending it for authorization. The system returns you the following
status:

Received by messaging system: Your NF3-e has been received by the system but hasn’t been sent to tax authorities
yet.

The NF3-e document has already been sent: You’ve sent your NF3-e for authorization, but the tax authorities
haven’t approved it yet.

SEFAZ Server Error: Your NF3-e has been sent to the messaging system, however, SEFAZ server might be offline.

URL not found for tpAmb: The URL is incorrect or no longer valid.

Tenant wasn’t found: The tenant available for your company hasn’t been found by the system.

Tenant isn’t trusted! Your tenant isn’t reliable, then you can’t proceed with this process

Error processing the receipt: An error occurred while the receipt of your operation is being processed.

Error converting NF3-e sent to XML: An error occurred while converting your NF3-e sent for approval into XML.

Error while marshaling NF3-e: An error occurred during your NF3-e serialization and wasn’t transferred from your
source system to the cloud.

Error processing SEFAZ response: An error occurred while processing SEFAZ response.

Error while updating NF3-e status: An error occurred while processing NF3-e status and updating it in your original
system.

3. Stores and keeps the XML of all electronic fiscal documents you’ve issued, during the legal deadline.

This is custom documentation. For more information, please visit SAP Help Portal. 14
 6/30/25, 6:07 AM
4. Sends an e-mail automatically to your business partner when your Electronic Nota Fiscal is authorized by the tax
authorities.

5. Posts an electronic fiscal document under Contingency mode (SVC) when you can’t send it to the tax authorities under
normal circumstances, such an interruption in SEFAZ server.

6. Once you proceed with this checking, the system returns you a status for it.

Integration
The steps that you need to follow to integrate your system to SAP Document and Reporting Compliance, outbound invoicing
option for Brazil.

Prerequisites

You have an SAP Business Technology Platform subscription for NF-e application.

You have followed the steps described in Initial Setup.

You have the following products and releases (these are the ones supported by the service):

SAP S/4HANA

SAP S/4HANA Cloud Public Edition

SAP ERP as of release 605

You have a configured digital certificate.

You have the following service key information:

Service URL

UAA URL

UAA Client ID

UAA Client Secret

You have implemented NF-e, CT-e, and NFS-e.

NF-e, CT-e, NFS-e Specifics

You can issue electronic fiscal documents in SAP S/4HANA, SAP S/4HANA Cloud Public Edition, or SAP ERP. Each system
processes specifics electronic fiscal documents.

Uploading the TLS Communication Certificate

You upload the TLS communication certificate to assign electronic fiscal documents (NF-e, CT-e, NFS-e, and MDF-e). You
upload the certificate just once, for all electronic fiscal documents.
Connecting the Source System to SAP Business Technology Platform
You activate the business function and then you can make cloud-specific settings in the SAP Document and Reporting
Compliance, outbound invoicing option for Brazil.
Integrating with SAP S/4HANA
You can integrate SAP Document and Reporting Compliance, outbound invoicing option for Brazil with SAP S/4HANA. You
are able to issue an NF-e, CT-e, or NFS-e in SAP S/4HANA, the system sends the electronic fiscal documents to continue
your business transactions.
This is custom documentation. For more information, please visit SAP Help Portal. 15
 6/30/25, 6:07 AM
Integrating with SAP S/4HANA Cloud Public Edition
Additional steps that you need to carry out to activate the integration of SAP S/4HANA Cloud Public Edition with SAP
Document and Reporting Compliance, outbound invoicing option for Brazil. You can issue an NF-e, CT-e or, NFS-e in SAP
S/4HANA Cloud Public Edition, the system sends the electronic fiscal documents to continue your business transactions.
Integrating with SAP ERP
Additional steps that you need to carry out to activate the integration of SAP ERP with SAP Document and Reporting
Compliance, outbound invoicing option for Brazil. You can issue an NF-e, CT-e, or NFS-e in SAP ERP, the system sends the
electronic fiscal documents to continue your business transactions.

Uploading the TLS Communication Certificate

You upload the TLS communication certificate to assign electronic fiscal documents (NF-e, CT-e, NFS-e, and MDF-e). You upload
the certificate just once, for all electronic fiscal documents.

Prerequisites
You have a license for SAP Document and Reporting Compliance, outbound invoicing option for Brazil.

Context

We recommend you to use the Windows operating system. The procedure is the same, regardless of the browser.

Procedure
1. Search for the DigiCert Global G2 TLS RSA SHA256 2020 CA1 entry on DigiCert .

2. Download the certificate in the DER/CRT format.

3. In the source system, access the Trust Manager: Display (STRUST) transaction.

4. For both SSL client SSL Client (Anonymous) and SSL client SSL Client (Standard): choose Import Certificate in the
Certificate pane and add the certificate you exported on the previous steps. Then, to complete the upload, choose Add to
Certificate List.

Connecting the Source System to SAP Business Technology

Platform
This is custom documentation. For more information, please visit SAP Help Portal. 16
 6/30/25, 6:07 AM
You activate the business function and then you can make cloud-specific settings in the SAP Document and Reporting
Compliance, outbound invoicing option for Brazil.

You activate the LOG_LH_NFE business function to connect your source system from On-Premise environment to SAP BTP. Once
you activate the business function, the SAP Document and Reporting Compliance, outbound invoicing option for Brazil is turned
on accordingly.

Procedure

To activate the business function, proceed as follows:

1. In your source system, SAP S/4HANA or SAP ERP, access the SFW5 transaction.

2. Choose an industry solution in the Business Function Set dropdown list.

3. Enter the object Business Function Cloud NF-e (LOG_LH_NFE).

4. Click on Activate Changes.

Result

The LOG_LH_NFE business function is activated. After that, you can make cloud-specific settings in the NF-e: System
Configuration - Cloud (J_1BNFE_CUST4_1V) view.

 Note
To activate this business function, you need a specific license, which is bound to LOD-LH-NFE component and to the software
component.

Integrating with SAP S/4HANA

You can integrate SAP Document and Reporting Compliance, outbound invoicing option for Brazil with SAP S/4HANA. You are able
to issue an NF-e, CT-e, or NFS-e in SAP S/4HANA, the system sends the electronic fiscal documents to continue your business
transactions.

The following graphic displays the integration process with SAP S/4HANA.

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

This is custom documentation. For more information, please visit SAP Help Portal. 17
 6/30/25, 6:07 AM
1. You issue an electronic fiscal document in SAP S/4HANA requests a new token, which is generated through and it
communicates with and it communicates with SAP Document and Reporting Compliance, outbound invoicing option for
Brazil.

2. SAP S/4HANA requests a new token, which is generated through and it communicates with SAP BTP. This step is only
completed if it has expired.

3. SAP Document and Reporting Compliance, outbound invoicing option for Brazil enables a token code that is valid for 12
hours.

4. SAP S/4HANA sends the electronic fiscal document, in order to get authorization and continue your business transactions.

Creating a Client Profile

Create an OAuth2 client profile in the SAP S/4HANA source system.
Defining Proxy Configuration
You configure an optional proxy for your company when defining the connection details to the SAP Business Technology
Platform.
Configuring the Client Profile
SAP Document and Reporting Compliance, outbound invoicing option for Brazil integrates to SAP S/4HANA through an
authentication and authorization service. However, to be able to proceed with your tasks using this service, you need to
configure your profile previously registered.
Configure Communication Settings for Business Place
You define the communication settings for SAP Document and Reporting Compliance, outbound invoicing option for Brazil.
To proceed with such action, you make customizing settings in the NF-e: System Configuration (J_1BNFE_CUST3_4V)
view.
Define Business Place for Outbound Scenario
Define a business place to connect with the service link.

Creating a Client Profile

Create an OAuth2 client profile in the SAP S/4HANA source system.

Procedure
1. Access the Object Navigator (SE80) transaction and open the repository browser.

2. Locate your package. Then, right-click your package and choose Create More OAuth 2.0 Client Profile .

3. Under Create OAuth 2.0 Client Profile, proceed as follows:

a. Client Profile: enter the chosen name for your profile.

Choose a name that starts with the letter "Z".

b. Type: choose Default.

4. Activate your entry and save it in a correction request, so that you can use the client profile in your company environments.

Task overview: Integrating with SAP S/4HANA

Related Information
Defining Proxy Configuration
Configuring the Client Profile
Configure Communication Settings for Business Place
Define Business Place for Outbound Scenario

This is custom documentation. For more information, please visit SAP Help Portal. 18
 6/30/25, 6:07 AM

Defining Proxy Configuration

You configure an optional proxy for your company when defining the connection details to the SAP Business Technology Platform.

Context

Use these settings only when your company requires connections between your backend system and external services to be made
through a proxy that needs authentication.

Procedure
1. Go to SM59 transaction and choose Create.

2. To fill out the fields, follow Establishing a Connection Using a Destination (SM59) and use the instructions on the next
steps.

3. Enter the following data:

Name: enter NFEACCESSHOST.

Description: enter a description for your entry. This description is recommended.

Connection Type: choose G HTTP connections to external server.

4. Under Technical Settings, proceed as follows:

Host: enter the URL that is outside the UAA group in the JSON file, that you get when you create your service key, as
described in Creating a New Service Key. Remove the https:// from the NF-e service URL.

Port: enter 443.

Path Prefix: keep this field empty.

 Note
Your proxy information must be filled in the Proxy Host, Proxy Service, Proxy User and Proxy PW Status fields.

5. Under Logon/Security, proceed as follows:

Logon with User: choose Do not use a user.

Logon with Ticket: choose Do not send logon ticket.

SSL: choose Active.

SSL Certificate: choose DFAULT SSL Client (Standard).

Inform the OAuth 2.0 Client Profile you've created on Creating a Client Profile.

Results

To test the communication, fill /nfe-authorize/health in the Path Prefix field, under Technical Setting. Save, choose
Connection Test and check the results.

A new tab called Test Results is available on your screen with the following status:

Status HTTP: 200

Status Text: OK

If you get a different response, verify your connection by checking your firewall configuration settings.

This is custom documentation. For more information, please visit SAP Help Portal. 19
 6/30/25, 6:07 AM
Do not forget to clean the Path Prefix field after your testing.

Another option is to use the Status Service option in the NF-e/CT-e Monitor (J1BNFE) transaction and check the results.

Task overview: Integrating with SAP S/4HANA

Related Information
Creating a Client Profile
Configuring the Client Profile
Configure Communication Settings for Business Place
Define Business Place for Outbound Scenario

Configuring the Client Profile

SAP Document and Reporting Compliance, outbound invoicing option for Brazil integrates to SAP S/4HANA through an
authentication and authorization service. However, to be able to proceed with your tasks using this service, you need to configure
your profile previously registered.

Procedure
1. Access the OAuth 2.0 Clients (OA2C_CONFIG) transaction.

2. Choose Create, available in the Overview section.

3. Under Create a new OAuth 2.0 Client, proceed as follows:

a. OAuth 2.0 Client Profile: select the client profile you've created.

b. Fill out the configuration name.

c. Fill out the OAuth 2.0 Client ID with your respective Client ID (Client ID is the tenant provided by Cloud Foundry).

4. Save your entries by choosing OK.

5. Under Details Administration , proceed as follows:

a. General Settings: enter your client secret.

b. Authorization Server Settings: fill out the endpoints information.

Enter the UAA URL that you get when you create your service key. Remove the https:// from the URL.

Make sure the URL for the Token Endpoint field ends with /oauth/token. If it doesn‘t, you can add it manually.

c. Client Authentication choose: Basic

d. Resource Access Authentication choose Header Field

e. Selected Grant Type choose: Client Credentials.

6. Choose Enter to complete this procedure.

Task overview: Integrating with SAP S/4HANA

Related Information
Creating a Client Profile
Defining Proxy Configuration
Configure Communication Settings for Business Place

This is custom documentation. For more information, please visit SAP Help Portal. 20
 6/30/25, 6:07 AM
Define Business Place for Outbound Scenario
Creating a New Service Key

Configure Communication Settings for Business Place

You define the communication settings for SAP Document and Reporting Compliance, outbound invoicing option for Brazil. To
proceed with such action, you make customizing settings in the NF-e: System Configuration (J_1BNFE_CUST3_4V) view.

Procedure
1. In transaction SPRO, choose Cross-Application Components General Application Functions Nota Fiscal CNPJ
Business Place Define Business Place .

2. Click on the Clock icon.

3. Enter your company code.

4. Select the branch for which you want to make the communication settings, then choose Electronic Fiscal Document
Configuration New Entries .

5. In the New Entries screen, enter the relevant information for your branch.

 Note
You must not select the Auto. Server Det. checkbox for SAP Document and Reporting Compliance, outbound invoicing
option for Brazil.

If your document is an NF-e, fill out the NF model field with 55 Nota Fiscal - Model 55.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Select the SAP Mess. Systm checkbox.

Leave the Destination field blank.

Fill out the XML Version field with 4,00.

Fill out the Normal field with 1.

Fill out the Contingency field with one of the following values:

2: Contingência FS-IA, com impressão do DANFE em formulário de segurança

5: Contingência FS-DA, com impressão do DANFE em formulário de segurança

Fill out the Issue Process field with 0.

Fill out the Event Group field with 0001.

If your NF model is an NFS-e, fill out the NF model field with 0.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

This is custom documentation. For more information, please visit SAP Help Portal. 21
 6/30/25, 6:07 AM
Select the SAP Mess. Systm checkbox.

Leave the Destination field blank.

Fill out the XML Version field with 1,00.

Fill out the Normal field with 1.

Fill out the Contingency field with 2: Contingência FS-IA, com impressão do DANFE em
formulário de segurança.

Fill out the Issue Process field with 0.

Fill out the Event Group field with 0001.

If your NF model is a CT-e, fill out the NF model field with 57 Conhecimento de Transporte Eletrônico
(CT-e) Model 57.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Select the SAP Mess. Systm checkbox.

Leave the Destination field blank.

Fill out the XML Version field with 4,00.

Fill out the Appl. Version field with SAP CT-E CLOUD.

Fill out the Normal field with 1.

Fill out the Contingency field with 5: Contingência FS-DA, com impressão do DANFE em
formulário de segurança.

Fill out the Issue Process field with 0.

Fill out the Event Group field with 0001.

Results
The source system is able to communicate correctly with SAP Document and Reporting Compliance, outbound invoicing option
for Brazil.

If your source system used to communicate with other products, it will no longer communicate with other products after you make
these settings.

Task overview: Integrating with SAP S/4HANA

Related Information
Creating a Client Profile
Defining Proxy Configuration
Configuring the Client Profile
Define Business Place for Outbound Scenario

This is custom documentation. For more information, please visit SAP Help Portal. 22
 6/30/25, 6:07 AM

Define Business Place for Outbound Scenario

Define a business place to connect with the service link.

Prerequisites
To complete this task, you need to activate an enterprise business function by following the steps described in Connecting the
Source System to SAP Business Technology Platform. Otherwise, you can get the error message Cloud NF-e should be active to
enable this customizing.

Context
You define a combination of company code, business place, nota fiscal model, and nota fiscal type that you’re going to connect to
SAP Document and Reporting Compliance, outbound invoicing option for Brazil. This connection can be partial, complete, or
phased. To proceed with such action, you make customizing settings in the NF-e: System Configuration - Cloud
(J_1BNFE_CUST4_1V) view.

Procedure
1. In transaction SPRO, choose Cross-Application Components General Application Functions Nota Fiscal CNPJ
Business Place Define Business Place .

2. Click on the Clock icon.

3. Enter your company code.

4. Select the business place that you want to connect to this service, then choose Electronic Fiscal Document
Configuration - Cloud New Entries .

5. Specify the nota fiscal model and the nota fiscal type, and insert the start date as of when that entry is valid.

For each combination of company code, business place, and nota fiscal model, you can fill out the nota fiscal type and the
start date according to how your data must be connected, as follows:

Partial connection (only some nota fiscal types are migrated to the cloud at a particular point in time): fill out the
nota fiscal types that you want to migrate to the cloud, and indicate the start date.

Complete connection (all nota fiscal types are migrated to the cloud at a particular point in time): leave the nota
fiscal type field blank, and indicate the start date.

Phased connection (different nota fiscal types are migrated to the cloud at different points in time): first, make a
partial connection by filling out the nota fiscal types that you want to migrate, and indicate the start date. Then,
make a complete connection by leaving the nota fiscal type field blank, and indicate a start date that's more recent
than the first partial connection.

The system always considers the entries with the most recent start date for a combination of company code, business
place, nota fiscal model, and nota fiscal type.

6. Enter the URL that is outside the UAA group in the JSON file, that you get when you create your Service Key, as described
in Creating a New Service Key. Remove the https:// from the NF-e service URL.

7. Fill out the OAuth2 Profile field with the client profile that you’ve created, as described in Creating a Client Profile.

8. Select the Disable e-mail functionality checkbox, if you want to disable B2B notification e-mails.

When the B2B notification e-mails are enabled, the system uses the e-mail addresses assigned with specific values for each
document type in the Maintain Business Partner (BP) transaction. For more information, see Configuring Email Addresses
to Send XML and PDF Files.

9. Save your entries.

This is custom documentation. For more information, please visit SAP Help Portal. 23
 6/30/25, 6:07 AM

Results

The system connects the service link with the combination of company code, business place, nota fiscal model, and nota fiscal
type.

Example

Partial connection: on the following table, only nota fiscal types NE and QM are migrated to the cloud, as of January 1, 2020.

Example of J_1BNFE_CUST4_1V View Entries: Partial Connection

Company Code Business Place NF Model NF Type Valid From

BR01 1234 55 - Nota Fiscal - Model NE 01.01.2020

55

BR01 1234 55 - Nota Fiscal - Model QM 01.01.2020

55

Complete connection: on the following table, all nota fiscal types are migrated to the cloud, as of June 1, 2020.

Example of J_1BNFE_CUST4_1V View Entries: Complete Connection

Company Code Business Place NF Model NF Type Valid From

BR02 5678 55 - Nota Fiscal - Model 01.06.2020

55

Phased connection: on the following table, only nota fiscal types NE and QM are migrated to the cloud, as of March 1, 2020. Then,
all nota fiscal types are migrated to the cloud, as of September 1, 2020.

Example of J_1BNFE_CUST4_1V View Entries: Phased Connection

Company Code Business Place NF Model NF Type Valid From

BR03 3456 55 - Nota Fiscal - Model NE 01.03.2020

55

BR03 3456 55 - Nota Fiscal - Model QM 01.03.2020

55

BR03 3456 58 - Manifesto Eletrônico 01.09.2020

de Documentos Fiscais -
Model 58

Task overview: Integrating with SAP S/4HANA

Related Information
Creating a Client Profile
Defining Proxy Configuration
Configuring the Client Profile
Configure Communication Settings for Business Place

Integrating with SAP S/4HANA Cloud Public Edition

This is custom documentation. For more information, please visit SAP Help Portal. 24
 6/30/25, 6:07 AM
Additional steps that you need to carry out to activate the integration of SAP S/4HANA Cloud Public Edition with SAP Document
and Reporting Compliance, outbound invoicing option for Brazil. You can issue an NF-e, CT-e or, NFS-e in SAP S/4HANA Cloud
Public Edition, the system sends the electronic fiscal documents to continue your business transactions.

The following graphic displays the integration process.

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

1. You issue an electronic fiscal document in SAP S/4HANA Cloud Public Edition and it communicates with SAP Document
and Reporting Compliance, outbound invoicing option for Brazil.

2. SAP S/4HANA Cloud Public Edition requests a new token, which is generated through SAP Business Technology Platform.
This step is only completed if it has expired.

3. SAP Document and Reporting Compliance, outbound invoicing option for Brazil enables a token code that is valid for 12
hours.

4. SAP S/4HANA Cloud Public Edition sends the electronic fiscal document, in order to get authorization and continue your
business transactions.

The only messaging system available for SAP S/4HANA Cloud Public Edition is SAP Document and Reporting Compliance,
outbound invoicing option for Brazil. You can't integrate a third-party messaging system with SAP S/4HANA Cloud Public Edition
to issue the following electronic documents:

NF-e (document model 55)

CT-e (document model 57)

NFS-e for São Paulo and Rio de Janeiro. To issue NFS-e for other cities, see Partner Enablement for Outbound nota fiscal.

Prerequisites

Business role Administrator (SAP_BR_ADMINISTRATOR).

Business catalog Communication Management (SAP_CORE_BC_COM).

1. Create Communication System

2. Create Communication Arrangement

3. Configure Communication Settings for Business Place

You define the communication settings for SAP Document and Reporting Compliance, outbound invoicing option for Brazil.
To proceed with such action, you make the settings in the Brazil Business Place configuration item.

This is custom documentation. For more information, please visit SAP Help Portal. 25
 6/30/25, 6:07 AM

Create Communication System

You have to activate a communication arrangement with Web Services in your SAP S/4HANA, in order to be able to integrate it to
the cloud. The communication arrangement is Nota Fiscal Brazil (SAP_COM_0261) and, to complete this process, you need to
follow the procedure below.

Procedure
1. Log on in your Fiori Launchpad, in SAP S/4HANA Cloud Public Edition.

 Note
You need an Admin role to log on and proceed with this task.

2. Select the Communication Systems tile.

3. Click on New.

4. Enter your System ID and System Name, in the New Communication System dialog box.

5. Select Create.

6. Enter the host name of the system, which is the URL outside of the UAA group in the JSON file, that you get when you
create your Service Key, as described in Creating a New Service Key.

7. Enter the https port.

8. Fill the endpoints information, in the Auth. Endpoint and Token Endpoint fields, accordingly.

This is custom documentation. For more information, please visit SAP Help Portal. 26
 6/30/25, 6:07 AM

 Note
All the respective URLs are provided by Cloud Foundry and are the Service URL and UAA URL mentioned in the
prerequisites.

Make sure the URL for the Token Endpoint field ends with /oauth/token. If it doesn‘t, you can add it manually.

9. Click on + icon, in User For Outbound Communication section.

10. Enter OAuth 2.0 in Authentication Method field.

11. Enter your client ID and client secret information from the Service Key, as described in Creating a New Service Key.

12. Click on Create.

13. Click on Save to complete this task.

Parent topic: Integrating with SAP S/4HANA Cloud Public Edition

Next: Create Communication Arrangement

Create Communication Arrangement

You have to activate a communication arrangement with Web Services in your SAP S/4HANA to be able to integrate it to the cloud.
The communication arrangement is Nota Fiscal Brazil (SAP_COM_0261) and, to complete this process, you need to follow the
procedure below.

Procedure
1. Log on in your Fiori Launchpad, in SAP S/4HANA Cloud Public Edition.

 Note
You need an Admin role to log on and proceed with this task.

2. Select Communication Arrangement tile.

3. Click on New, in Communication Arrangement screen.

4. Enter SAP_COM_0261 in the Scenario field, in New Communication Arrangement dialog box.

5. Fill out the Arrangement Name field. You can choose the name, if necessary.

6. Click on Create to complete this step.

7. Go to Common Data section.

This is custom documentation. For more information, please visit SAP Help Portal. 27
 6/30/25, 6:07 AM
8. Fill out the Communication System field by using the one you created in step Create Communication System.

9. In Job Execution Details, define how often outbound services must automatically retrieve status information from cloud
services.

10. Click on Save to complete this task.

Parent topic: Integrating with SAP S/4HANA Cloud Public Edition

Previous: Create Communication System

Next task: Configure Communication Settings for Business Place

Configure Communication Settings for Business Place

You define the communication settings for SAP Document and Reporting Compliance, outbound invoicing option for Brazil. To
proceed with such action, you make the settings in the Brazil Business Place configuration item.

Procedure
1. In the Manage your Solution app, ensure that the configuration changes are applied to local version Brazil, then choose
Configure Your Solution Brazil Business Place Define Business Places Configure .

2. Enter your company code.

3. Select the branch for which you want to make the communication settings, then double-click Electronic Fiscal Document
Configuration.

4. In the Electronic Fiscal Document Configuration screen, choose New Entries.

5. In the New Entries screen, enter the relevant information for your branch.

If your document is an NF-e, fill out the NF model field with 55 Nota Fiscal - Model 55.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Fill out the XML Version field with 4,00.

Fill out the Contingency field with one of the following values:

2: Contingência FS-IA, com impressão do DANFE em formulário de segurança

5: Contingência FS-DA, com impressão do DANFE em formulário de segurança

This is custom documentation. For more information, please visit SAP Help Portal. 28
 6/30/25, 6:07 AM
Fill out the Event Group field with 0001.

If your NF model is an NFS-e, leave the NF model field empty.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Fill out the XML Version field with 1,00.

Fill out the Contingency field with 2: Contingência FS-IA, com impressão do DANFE em
formulário de segurança.

Fill out the Event Group field with 0001.

If your NF model is a CT-e, fill out the NF model field with 57 Conhecimento de Transporte Eletrônico
(CT-e) Model 57.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Fill out the XML Version field with 4,00.

Fill out the Contingency field with 5: Contingência FS-DA, com impressão do DANFE em
formulário de segurança.

Results
The source system is able to communicate correctly with SAP Document and Reporting Compliance, outbound invoicing option
for Brazil.

If your source system used to communicate with other products, it will no longer communicate with other products after you make
these settings.

Task overview: Integrating with SAP S/4HANA Cloud Public Edition

Previous: Create Communication Arrangement

Integrating with SAP ERP

Additional steps that you need to carry out to activate the integration of SAP ERP with SAP Document and Reporting Compliance,
outbound invoicing option for Brazil. You can issue an NF-e, CT-e, or NFS-e in SAP ERP, the system sends the electronic fiscal
documents to continue your business transactions.

1. Defining Service Authentication

You create an RFC connection to define the service authentication when you set up your connection to SAP Business
Technology Platform.

2. Defining Proxy Configuration

You configure an optional proxy for your company when defining the connection details to the SAP Business Technology
Platform.

This is custom documentation. For more information, please visit SAP Help Portal. 29
 6/30/25, 6:07 AM
3. Configure Communication Settings for Business Place
You define the communication settings for SAP Document and Reporting Compliance, outbound invoicing option for Brazil.
To proceed with such action, you make customizing settings in the NF-e: System Configuration (J_1BNFE_CUST3_4V)
view.

4. Define Business Place for Outbound Scenario

Define a business place to connect with the service link.

Defining Service Authentication

You create an RFC connection to define the service authentication when you set up your connection to SAP Business Technology
Platform.

Context

To complete these steps, you use the data available in your service key, as described under Initial Setup.

Procedure
1. Go to transaction SM59 and choose Create. To fill out the fields, follow Establishing a Connection Using a Destination
(SM59) and use the instructions on the next steps.

2. Enter this data:

Name: enter NFEACCESSTOKEN.

Description: enter a description for your entry. This description isn’t mandatory, but recommended.

Connection Type: choose G HTTP connections to external server.

3. Under Technical Settings, proceed as follows:

Host: enter the UAA URL that you get when you create your service key, as described in Creating a New Service Key.
Remove the https:// from the UAA URL.

Port: enter 443.

Path Prefix: enter /oauth/token?grant_type=client_credentials.

4. Under Logon/Security, proceed as follows:

Log on with HTTP basic authentication.

User: enter your client ID from the service key, as described in Creating a New Service Key.

Password: enter your client secret from the service key, as described in Creating a New Service Key.

 Note
After you enter the password, the Password field isn’t visible anymore, and PW Status is updated to status
Saved.

SSL: choose Active.

SSL certificate: choose DFAULT SSL Client (Standard).

5. Choose Connection Test.

Results

This is custom documentation. For more information, please visit SAP Help Portal. 30
 6/30/25, 6:07 AM
A new tab called Test Results is available on your screen with the following status:

Status HTTP: 200

Status Text: OK

If you get a different response, verify your connection by checking your proxy and firewall configuration settings.

Task overview: Integrating with SAP ERP

Next task: Defining Proxy Configuration

Defining Proxy Configuration

You configure an optional proxy for your company when defining the connection details to the SAP Business Technology Platform.

Context

Use these settings only when your company requires connections between your backend system and external services to be made
through a proxy that needs authentication.

Procedure
1. Go to SM59 transaction and choose Create.

2. To fill out the fields, follow Establishing a Connection Using a Destination (SM59) and use the instructions on the next
steps.

3. Enter the following data:

Name: enter NFEACCESSHOST.

Description: enter a description for your entry. This description is recommended.

Connection Type: choose G HTTP connections to external server.

4. Under Technical Settings, proceed as follows:

Host: enter the URL that is outside the UAA group in the JSON file, that you get when you create your service key, as
described in Creating a New Service Key. Remove the https:// from the NF-e service URL.

Port: enter 443.

Path Prefix: keep this field empty.

 Note
Your proxy information must be filled in the Proxy Host, Proxy Service, Proxy User and Proxy PW Status fields.

5. Under Logon/Security, proceed as follows:

Logon with User: choose Do not use a user.

Logon with Ticket: choose Do not send logon ticket.

SSL: choose Active.

SSL Certificate: choose DFAULT SSL Client (Standard).

Results
This is custom documentation. For more information, please visit SAP Help Portal. 31
 6/30/25, 6:07 AM
To test the communication, fill /nfe-authorize/health in the Path Prefix field, under Technical Setting. Save, choose
Connection Test and check the results.

A new tab called Test Results is available on your screen with the following status:

Status HTTP: 200

Status Text: OK

If you get a different response, verify your connection by checking your firewall configuration settings.

Do not forget to clean the Path Prefix field after your testing.

Another option is to use the Status Service option in the NF-e/CT-e Monitor (J1BNFE) transaction and check the results.

Task overview: Integrating with SAP ERP

Previous task: Defining Service Authentication

Next task: Configure Communication Settings for Business Place

Configure Communication Settings for Business Place

You define the communication settings for SAP Document and Reporting Compliance, outbound invoicing option for Brazil. To
proceed with such action, you make customizing settings in the NF-e: System Configuration (J_1BNFE_CUST3_4V) view.

Procedure
1. In transaction SPRO, choose Cross-Application Components General Application Functions Nota Fiscal CNPJ
Business Place Define Business Place .

2. Click on the Clock icon.

3. Enter your company code.

4. Select the branch for which you want to make the communication settings, then choose Electronic Fiscal Document
Configuration New Entries .

5. In the New Entries screen, enter the relevant information for your branch.

 Note
You must not select the Auto. Server Det. checkbox for SAP Document and Reporting Compliance, outbound invoicing
option for Brazil.

If your document is an NF-e, fill out the NF model field with 55 Nota Fiscal - Model 55.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Select the SAP Mess. Systm checkbox.

Fill out the Destination field with NFEACCESSTOKEN.

Fill out the XML Version field with 4,00.

This is custom documentation. For more information, please visit SAP Help Portal. 32
 6/30/25, 6:07 AM
Fill out the Normal field with 1.

Fill out the Contingency field with one of the following values:

2: Contingência FS-IA, com impressão do DANFE em formulário de segurança

5: Contingência FS-DA, com impressão do DANFE em formulário de segurança

Fill out the Issue Process field with 0.

Fill out the Event Group field with 0001.

If your NF model is an NFS-e, fill out the NF model field with 0.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Select the SAP Mess. Systm checkbox.

Leave the Destination field blank.

Fill out the XML Version field with 1,00.

Fill out the Normal field with 1.

Fill out the Contingency field with 2: Contingência FS-IA, com impressão do DANFE em
formulário de segurança.

Fill out the Issue Process field with 0.

Fill out the Event Group field with 0001.

If your NF model is a CT-e, fill out the NF model field with 57 Conhecimento de Transporte Eletrônico
(CT-e) Model 57.

In the Valid from field you enter the date that you've started to use the SAP Document and Reporting Compliance,
outbound invoicing option for Brazil.

In the Electronic Fiscal Document Configuration box you fill out the following fields:

Fill out your type of environment.

Select the SAP Mess. Systm checkbox.

Leave the Destination field blank.

Fill out the XML Version field with 4,00.

Fill out the Appl. Version field with SAP CT-E CLOUD.

Fill out the Normal field with 1.

Fill out the Contingency field with 5: Contingência FS-DA, com impressão do DANFE em
formulário de segurança.

Fill out the Issue Process field with 0.

Fill out the Event Group field with 0001.

This is custom documentation. For more information, please visit SAP Help Portal. 33
 6/30/25, 6:07 AM

Results
The source system is able to communicate correctly with SAP Document and Reporting Compliance, outbound invoicing option
for Brazil.

If your source system used to communicate with other products, it will no longer communicate with other products after you make
these settings.

Task overview: Integrating with SAP ERP

Previous task: Defining Proxy Configuration

Next task: Define Business Place for Outbound Scenario

Define Business Place for Outbound Scenario

Define a business place to connect with the service link.

Prerequisites

To complete this task, you need to activate an enterprise business function by following the steps described in Connecting the
Source System to SAP Business Technology Platform. Otherwise, you can get the error message Cloud NF-e should be active to
enable this customizing.

Context

You define a combination of company code, business place, nota fiscal model, and nota fiscal type that you’re going to connect to
SAP Document and Reporting Compliance, outbound invoicing option for Brazil. This connection can be partial, complete, or
phased. To proceed with such action, you make customizing settings in the NF-e: System Configuration - Cloud
(J_1BNFE_CUST4_1V) view.

Procedure
1. In transaction SPRO, choose Cross-Application Components General Application Functions Nota Fiscal CNPJ
Business Place Define Business Place .

2. Click on the Clock icon.

3. Enter your company code.

4. Select the business place that you want to connect to this service, then choose Electronic Fiscal Document
Configuration - Cloud New Entries .

5. Specify the nota fiscal model and the nota fiscal type, and insert the start date as of when that entry is valid.

For each combination of company code, business place, and nota fiscal model, you can fill out the nota fiscal type and the
start date according to how your data must be connected, as follows:

Partial connection (only some nota fiscal types are migrated to the cloud at a particular point in time): fill out the
nota fiscal types that you want to migrate to the cloud, and indicate the start date.

Complete connection (all nota fiscal types are migrated to the cloud at a particular point in time): leave the nota
fiscal type field blank, and indicate the start date.

Phased connection (different nota fiscal types are migrated to the cloud at different points in time): first, make a
partial connection by filling out the nota fiscal types that you want to migrate, and indicate the start date. Then,

This is custom documentation. For more information, please visit SAP Help Portal. 34
 6/30/25, 6:07 AM
make a complete connection by leaving the nota fiscal type field blank, and indicate a start date that's more recent
than the first partial connection.

The system always considers the entries with the most recent start date for a combination of company code, business
place, nota fiscal model, and nota fiscal type.

6. Enter the URL that is outside the UAA group in the JSON file, that you get when you create your Service Key, as described
in Creating a New Service Key. Remove the https:// from the NF-e service URL.

7. Select the Disable e-mail functionality checkbox, if you want to disable B2B notification e-mails.

When the B2B notification e-mails are enabled, the system uses the e-mail addresses assigned with specific values for each
document type in the Maintain Business Partner (BP) transaction. For more information, see Configuring Email Addresses
to Send XML and PDF Files.

8. Save your entries.

Results
The system connects the service link with the combination of company code, business place, nota fiscal model, and nota fiscal
type.

Example
Partial connection: on the following table, only nota fiscal types NE and QM are migrated to the cloud, as of January 1, 2020.

Example of J_1BNFE_CUST4_1V View Entries: Partial Connection

Company Code Business Place NF Model NF Type Valid From

BR01 1234 55 - Nota Fiscal - Model NE 01.01.2020

55

BR01 1234 55 - Nota Fiscal - Model QM 01.01.2020

55

Complete connection: on the following table, all nota fiscal types are migrated to the cloud, as of June 1, 2020.

Example of J_1BNFE_CUST4_1V View Entries: Complete Connection

Company Code Business Place NF Model NF Type Valid From

BR02 5678 55 - Nota Fiscal - Model 01.06.2020

55

Phased connection: on the following table, only nota fiscal types NE and QM are migrated to the cloud, as of March 1, 2020. Then,
all nota fiscal types are migrated to the cloud, as of September 1, 2020.

Example of J_1BNFE_CUST4_1V View Entries: Phased Connection

Company Code Business Place NF Model NF Type Valid From

BR03 3456 55 - Nota Fiscal - Model NE 01.03.2020

55

BR03 3456 55 - Nota Fiscal - Model QM 01.03.2020

55

This is custom documentation. For more information, please visit SAP Help Portal. 35
 6/30/25, 6:07 AM

Company Code Business Place NF Model NF Type Valid From

BR03 3456 58 - Manifesto Eletrônico 01.09.2020

de Documentos Fiscais -
Model 58

Task overview: Integrating with SAP ERP

Previous task: Configure Communication Settings for Business Place

Uploading the TLS Communication Certificate

You upload the TLS communication certificate to assign electronic fiscal documents (NF-e, CT-e, NFS-e, and MDF-e). You upload
the certificate just once, for all electronic fiscal documents.

Prerequisites
You have a license for SAP Document and Reporting Compliance, outbound invoicing option for Brazil.

Context
We recommend you to use the Windows operating system. The procedure is the same, regardless of the browser.

Procedure
1. Search for the DigiCert Global G2 TLS RSA SHA256 2020 CA1 entry on DigiCert .

2. Download the certificate in the DER/CRT format.

3. In the source system, access the Trust Manager: Display (STRUST) transaction.

4. For both SSL client SSL Client (Anonymous) and SSL client SSL Client (Standard): choose Import Certificate in the
Certificate pane and add the certificate you exported on the previous steps. Then, to complete the upload, choose Add to
Certificate List.

This is custom documentation. For more information, please visit SAP Help Portal. 36
 6/30/25, 6:07 AM

Connecting the Source System to SAP Business Technology

Platform
You activate the business function and then you can make cloud-specific settings in the SAP Document and Reporting
Compliance, outbound invoicing option for Brazil.

You activate the LOG_LH_NFE business function to connect your source system from On-Premise environment to SAP BTP. Once
you activate the business function, the SAP Document and Reporting Compliance, outbound invoicing option for Brazil is turned
on accordingly.

Procedure
To activate the business function, proceed as follows:

1. In your source system, SAP S/4HANA or SAP ERP, access the SFW5 transaction.

2. Choose an industry solution in the Business Function Set dropdown list.

3. Enter the object Business Function Cloud NF-e (LOG_LH_NFE).

4. Click on Activate Changes.

Result

The LOG_LH_NFE business function is activated. After that, you can make cloud-specific settings in the NF-e: System
Configuration - Cloud (J_1BNFE_CUST4_1V) view.

 Note
To activate this business function, you need a specific license, which is bound to LOD-LH-NFE component and to the software
component.

Integrating with SAP S/4HANA

You can integrate SAP Document and Reporting Compliance, outbound invoicing option for Brazil with SAP S/4HANA. You are able
to issue an NF-e, CT-e, or NFS-e in SAP S/4HANA, the system sends the electronic fiscal documents to continue your business
transactions.

The following graphic displays the integration process with SAP S/4HANA.

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 37
 6/30/25, 6:07 AM

Please note that image maps are not interactive in PDF outputs.

1. You issue an electronic fiscal document in SAP S/4HANA requests a new token, which is generated through and it
communicates with and it communicates with SAP Document and Reporting Compliance, outbound invoicing option for
Brazil.

2. SAP S/4HANA requests a new token, which is generated through and it communicates with SAP BTP. This step is only
completed if it has expired.

3. SAP Document and Reporting Compliance, outbound invoicing option for Brazil enables a token code that is valid for 12
hours.

4. SAP S/4HANA sends the electronic fiscal document, in order to get authorization and continue your business transactions.

1. Creating a Client Profile

Create an OAuth2 client profile in the SAP S/4HANA source system.

2. Configuring the Client Profile

SAP Document and Reporting Compliance, outbound invoicing option for Brazil integrates to SAP S/4HANA through an
authentication and authorization service. However, to be able to proceed with your tasks using this service, you need to
configure your profile previously registered.

3. Configuring the Value Append

Configure the value append to be able to use the MDF-e (Manifesto Eletrônico de Documentos Fiscais) in your system. The
MDF-e value is not delivered in the system.

4. Define Business Place for Outbound Scenario

Define a business place to connect with the service link.

Creating a Client Profile

Create an OAuth2 client profile in the SAP S/4HANA source system.

Procedure
1. Access the Object Navigator (SE80) transaction and open the repository browser.

2. Locate your package. Then, right-click your package and choose Create More OAuth 2.0 Client Profile .

3. Under Create OAuth 2.0 Client Profile, proceed as follows:

a. Client Profile: enter the chosen name for your profile.

Choose a name that starts with the letter "Z".

b. Type: choose Default.

4. Activate your entry and save it in a correction request, so that you can use the client profile in your company environments.

This is custom documentation. For more information, please visit SAP Help Portal. 38
 6/30/25, 6:07 AM

Task overview: Integrating with SAP S/4HANA

Next task: Configuring the Client Profile

Configuring the Client Profile

SAP Document and Reporting Compliance, outbound invoicing option for Brazil integrates to SAP S/4HANA through an
authentication and authorization service. However, to be able to proceed with your tasks using this service, you need to configure
your profile previously registered.

Procedure
1. Access the OAuth 2.0 Clients (OA2C_CONFIG) transaction.

2. Choose Create, available in the Overview section.

3. Under Create a new OAuth 2.0 Client, proceed as follows:

a. OAuth 2.0 Client Profile: select the client profile you've created.

b. Fill out the configuration name.

c. Fill out the OAuth 2.0 Client ID with your respective Client ID (Client ID is the tenant provided by Cloud Foundry).

4. Save your entries by choosing OK.

5. Under Details Administration , proceed as follows:

a. General Settings: enter your client secret.

b. Authorization Server Settings: fill out the endpoints information.

Enter the UAA URL that you get when you create your service key. Remove the https:// from the URL.

Make sure the URL for the Token Endpoint field ends with /oauth/token. If it doesn‘t, you can add it manually.

c. Client Authentication choose: Basic

d. Resource Access Authentication choose Header Field

e. Selected Grant Type choose: Client Credentials.

6. Choose Enter to complete this procedure.

Task overview: Integrating with SAP S/4HANA

Previous task: Creating a Client Profile

Next task: Configuring the Value Append

Related Information
Creating a New Service Key

Configuring the Value Append

Configure the value append to be able to use the MDF-e (Manifesto Eletrônico de Documentos Fiscais) in your system. The MDF-e
value is not delivered in the system.

This is custom documentation. For more information, please visit SAP Help Portal. 39
 6/30/25, 6:07 AM

Context

 Note
The model 58 is not supported in the system. The SAP system does not support mapping or monitoring for MDF-e, these
developments should be handle as custom development.

Procedure
1. Open the J_1BMODEL domain in your system.

2. Follow the steps on Creating Fixed Value Appends to configure the MDF-e value.

3. Configure the value 58 for the Manifesto Eletrônico de Documentos Fiscais (MDF-e) and save this value in the J_1BMODEL
domain.

Task overview: Integrating with SAP S/4HANA

Previous task: Configuring the Client Profile

Next task: Define Business Place for Outbound Scenario

Define Business Place for Outbound Scenario

Define a business place to connect with the service link.

Prerequisites
To complete this task, you need to activate an enterprise business function by following the steps described in Connecting the
Source System to SAP Business Technology Platform. Otherwise, you can get the error message Cloud NF-e should be active to
enable this customizing.

You also need to configure the MDF-e value appends by following the steps described in Configuring the Value Append.

Context
You define a combination of company code, business place, nota fiscal model, and nota fiscal type that you’re going to connect to
SAP Document and Reporting Compliance, outbound invoicing option for Brazil. This connection can be partial, complete, or
phased. To proceed with such action, you make customizing settings in the NF-e: System Configuration - Cloud
(J_1BNFE_CUST4_1V) view.

Procedure
1. In transaction SPRO, choose Cross-Application Components General Application Functions Nota Fiscal CNPJ
Business Place Define Business Place .

2. Click on the Clock icon.

3. Enter your company code.

4. Select the business place that you want to connect to this service, then choose Electronic Fiscal Document
Configuration - Cloud New Entries .

5. Specify the nota fiscal model and the nota fiscal type, and insert the start date as of when that entry is valid.

For each combination of company code, business place, and nota fiscal model, you can fill out the nota fiscal type and the
start date according to how your data must be connected, as follows:

This is custom documentation. For more information, please visit SAP Help Portal. 40
 6/30/25, 6:07 AM
Partial connection (only some nota fiscal types are migrated to the cloud at a particular point in time): fill out the
nota fiscal types that you want to migrate to the cloud, and indicate the start date.

Complete connection (all nota fiscal types are migrated to the cloud at a particular point in time): leave the nota
fiscal type field blank, and indicate the start date.

Phased connection (different nota fiscal types are migrated to the cloud at different points in time): first, make a
partial connection by filling out the nota fiscal types that you want to migrate, and indicate the start date. Then,
make a complete connection by leaving the nota fiscal type field blank, and indicate a start date that's more recent
than the first partial connection.

The system always considers the entries with the most recent start date for a combination of company code, business
place, nota fiscal model, and nota fiscal type.

6. Enter the URL that is outside the UAA group in the JSON file, that you get when you create your Service Key, as described
in Creating a New Service Key. Remove the https:// from the NF-e service URL.

7. Fill out the OAuth2 Profile field with the client profile that you’ve created, as described in Creating a Client Profile.

8. Select the Disable e-mail functionality checkbox, if you want to disable B2B notification e-mails.

When the B2B notification e-mails are enabled, the system uses the e-mail addresses assigned with specific values for each
document type in the Maintain Business Partner (BP) transaction. For more information, see Configuring Email Addresses
to Send XML and PDF Files.

9. Save your entries.

Results

Example

Company Code Business Place NF Model NF Type Valid From

BR03 3456 58 - Manifesto Eletrônico 01.09.2020

de Documentos Fiscais -
Model 58

Task overview: Integrating with SAP S/4HANA

Previous task: Configuring the Value Append

Integrating with SAP ERP

Additional steps that you need to carry out to activate the integration of SAP ERP with SAP Document and Reporting Compliance,
outbound invoicing option for Brazil. You can issue an NF-e, CT-e, or NFS-e in SAP ERP, the system sends the electronic fiscal
documents to continue your business transactions.

1. Defining Service Authentication

You create an RFC connection to define the service authentication when you set up your connection to SAP Business
Technology Platform.

2. Configuring the Value Append

Configure the value append to be able to use the MDF-e (Manifesto Eletrônico de Documentos Fiscais) in your system. The
MDF-e value is not delivered in the system.

3. Define Business Place for Outbound Scenario

Define a business place to connect with the service link.

This is custom documentation. For more information, please visit SAP Help Portal. 41
 6/30/25, 6:07 AM

Defining Service Authentication

You create an RFC connection to define the service authentication when you set up your connection to SAP Business Technology
Platform.

Context
To complete these steps, you use the data available in your service key, as described under Initial Setup.

Procedure
1. Go to transaction SM59 and choose Create. To fill out the fields, follow Establishing a Connection Using a Destination
(SM59) and use the instructions on the next steps.

2. Enter this data:

Name: enter NFEACCESSTOKEN.

Description: enter a description for your entry. This description isn’t mandatory, but recommended.

Connection Type: choose G HTTP connections to external server.

3. Under Technical Settings, proceed as follows:

Host: enter the UAA URL that you get when you create your service key, as described in Creating a New Service Key.
Remove the https:// from the UAA URL.

Port: enter 443.

Path Prefix: enter /oauth/token?grant_type=client_credentials.

4. Under Logon/Security, proceed as follows:

Log on with HTTP basic authentication.

User: enter your client ID from the service key, as described in Creating a New Service Key.

Password: enter your client secret from the service key, as described in Creating a New Service Key.

 Note
After you enter the password, the Password field isn’t visible anymore, and PW Status is updated to status
Saved.

SSL: choose Active.

SSL certificate: choose DFAULT SSL Client (Standard).

5. Choose Connection Test.

Results
A new tab called Test Results is available on your screen with the following status:

Status HTTP: 200

Status Text: OK

If you get a different response, verify your connection by checking your proxy and firewall configuration settings.

This is custom documentation. For more information, please visit SAP Help Portal. 42
 6/30/25, 6:07 AM

Task overview: Integrating with SAP ERP

Next task: Configuring the Value Append

Configuring the Value Append

Configure the value append to be able to use the MDF-e (Manifesto Eletrônico de Documentos Fiscais) in your system. The MDF-e
value is not delivered in the system.

Context

 Note
The model 58 is not supported in the system. The SAP system does not support mapping or monitoring for MDF-e, these
developments should be handle as custom development.

Procedure
1. Open the J_1BMODEL domain in your system.

2. Follow the steps on Creating Fixed Value Appends to configure the MDF-e value.

3. Configure the value 58 for the Manifesto Eletrônico de Documentos Fiscais (MDF-e) and save this value in the J_1BMODEL
domain.

Task overview: Integrating with SAP ERP

Previous task: Defining Service Authentication

Next task: Define Business Place for Outbound Scenario

Define Business Place for Outbound Scenario

Define a business place to connect with the service link.

Prerequisites

To complete this task, you need to activate an enterprise business function by following the steps described in Connecting the
Source System to SAP Business Technology Platform. Otherwise, you can get the error message Cloud NF-e should be active to
enable this customizing.

You also need to configure the MDF-e value appends by following the steps described in Configuring the Value Append.

Context
You define a combination of company code, business place, nota fiscal model, and nota fiscal type that you’re going to connect to
SAP Document and Reporting Compliance, outbound invoicing option for Brazil. This connection can be partial, complete, or
phased. To proceed with such action, you make customizing settings in the NF-e: System Configuration - Cloud
(J_1BNFE_CUST4_1V) view.

This is custom documentation. For more information, please visit SAP Help Portal. 43
 6/30/25, 6:07 AM

Procedure
1. In transaction SPRO, choose Cross-Application Components General Application Functions Nota Fiscal CNPJ
Business Place Define Business Place .

2. Click on the Clock icon.

3. Enter your company code.

4. Select the business place that you want to connect to this service, then choose Electronic Fiscal Document
Configuration - Cloud New Entries .

5. Specify the nota fiscal model and the nota fiscal type, and insert the start date as of when that entry is valid.

For each combination of company code, business place, and nota fiscal model, you can fill out the nota fiscal type and the
start date according to how your data must be connected, as follows:

Partial connection (only some nota fiscal types are migrated to the cloud at a particular point in time): fill out the
nota fiscal types that you want to migrate to the cloud, and indicate the start date.

Complete connection (all nota fiscal types are migrated to the cloud at a particular point in time): leave the nota
fiscal type field blank, and indicate the start date.

Phased connection (different nota fiscal types are migrated to the cloud at different points in time): first, make a
partial connection by filling out the nota fiscal types that you want to migrate, and indicate the start date. Then,
make a complete connection by leaving the nota fiscal type field blank, and indicate a start date that's more recent
than the first partial connection.

The system always considers the entries with the most recent start date for a combination of company code, business
place, nota fiscal model, and nota fiscal type.

6. Enter the URL that is outside the UAA group in the JSON file, that you get when you create your Service Key, as described
in Creating a New Service Key. Remove the https:// from the NF-e service URL.

7. Fill out the OAuth2 Profile field with the client profile that you’ve created, as described in Creating a Client Profile.

8. Select the Disable e-mail functionality checkbox, if you want to disable B2B notification e-mails.

When the B2B notification e-mails are enabled, the system uses the e-mail addresses assigned with specific values for each
document type in the Maintain Business Partner (BP) transaction. For more information, see Configuring Email Addresses
to Send XML and PDF Files.

9. Save your entries.

Results

Example

Company Code Business Place NF Model NF Type Valid From

BR03 3456 58 - Manifesto Eletrônico 01.09.2020

de Documentos Fiscais -
Model 58

Task overview: Integrating with SAP ERP

Previous task: Configuring the Value Append

NF3-e Specifics

This is custom documentation. For more information, please visit SAP Help Portal. 44
 6/30/25, 6:07 AM
In this section, you perform setting for NF3-e solution, only. Follow the steps to proceed with NF3-e integration.

NF3-e Integration Steps

Step Sequence Topic Description

1 Setting the Metering Flag in On-Premise This is a mandatory step. In this step you
System confirm that you use this service for the
exchange of electronic documents.

This setting assures that your electronic

document isn't counted twice.

2 Setting up the Communication to Process Implementation of BAdI to set up a

Electronic Fiscal Documents communication between SAP source
system and external systems.

3 Connecting the Source System to SAP Activate the business function to connect
Business Technology Platform the source system from On-Premise to SAP
BTP.

Uploading the TLS Communication Certificate

You upload the TLS communication certificate to assign electronic fiscal documents (NF-e, CT-e, NFS-e, and MDF-e). You upload
the certificate just once, for all electronic fiscal documents.

Prerequisites

You have a license for SAP Document and Reporting Compliance, outbound invoicing option for Brazil.

Context
We recommend you to use the Windows operating system. The procedure is the same, regardless of the browser.

Procedure
1. Search for the DigiCert Global G2 TLS RSA SHA256 2020 CA1 entry on DigiCert .

2. Download the certificate in the DER/CRT format.

3. In the source system, access the Trust Manager: Display (STRUST) transaction.

4. For both SSL client SSL Client (Anonymous) and SSL client SSL Client (Standard): choose Import Certificate in the
Certificate pane and add the certificate you exported on the previous steps. Then, to complete the upload, choose Add to
Certificate List.

This is custom documentation. For more information, please visit SAP Help Portal. 45
 6/30/25, 6:07 AM

Setting the Metering Flag in On-Premise System

In your on-premise system, you confirm that you use this service for the exchange of electronic documents. This information
ensures that the electronic document isn't counted 2 times: once, upon creation in the back-end and a second time during the
processing of the electronic document using the service.

Prerequisites
This feature has been delivered with Framework 25 (SAP Note 2927542 ). Ensure that this SAP Note is implemented.

Context

 Caution
This step is mandatory. Correct metering settings indicate that you're properly charged for your use of the solution.

If you don't perform this step, SAP will charge you when you process an electronic document both in the cloud service (SAP
Document and Reporting Compliance, outbound invoicing option for Brazil) and in the on-premise system.

When you license the SAP Document and Reporting Compliance, outbound invoicing option for Brazil solution, the metric for
licensing is the volume of processed documents. Considering that the solution also uses the eDocument Cockpit (which is used
widely in other countries/regions), specifically for Brazil you must confirm that you use this service only for the exchange of
electronic documents. This information ensures that the electronic document isn't counted 2 times in the licensing: first when it's
created on the source system, then when it's processed by the service.

Procedure
1. In your on-premise source system, for example SAP S/4HANA, in customizing for Cross-Application Components
General Application Functions eDocuments General Settings Define Process Communication Through SAP
Document Compliance Cloud Services (EDOCOMPPROCCOMV) and for a combination of Company Code and eDoc.
Process, mark the Service check box.

For example, in eDoc. Process, enter BREEINVOUT.

If you leave the Company Code empty, your configuration will work for any company codes.

2. Save your entries.

This is custom documentation. For more information, please visit SAP Help Portal. 46
 6/30/25, 6:07 AM

Setting up the Communication to Process Electronic Fiscal

Documents
To set up a communication process between your SAP source system, external systems, and the tax authorities, which is required
for the processing of electronic fiscal documents, you implement the EDOC_INTERFACE_CONNECTOR BAdI.

Procedure

Create an implementation of the eDocument Interface connector (EDOC_INTERFACE_CONNECTOR) BAdI.

You've to implement the interface's methods. But you don't have to implement any code, just create the implementation.

You can access the BAdI in transaction SE18, or in Customizing for Cross-Application Components under General Application
Functions eDocument General Settings Business Add-Ins BAdI: Define Interface Connector for eDocument .

Connecting the Source System to SAP Business Technology

Platform
You activate the ISU_LOC_EDO_BR_EE business function to connect your source system from On-Premise environment to SAP
BTP. Once you activate the business function, the SAP Document and Reporting Compliance, outbound invoicing option for Brazil
is turned on accordingly.

Procedure
To activate the business function, proceed as follows:

1. In your source system, SAP S/4HANA or SAP ERP, access the SFW5 transaction.

2. Choose an industry solution in the Business Function Set dropdown list.

3. Enter the object IS-U Localization for Brazil: eDocument NF3-e ( ISU_LOC_EDO_BR_EE).

4. Click on Activate Changes.

Result

The ISU_LOC_EDO_BR_EE business function is activated.

Service Offboarding
If you decide to stop using SAP Document and Reporting Compliance, outbound invoicing option for Brazil, perform the following
steps in the correct order.

Procedure
1. Delete your service instances. Check Deleting Service Instances.

2. Remove the entitlements in the corresponding subaccounts.

3. Contact your account executive to cancel the subscriptions for the service.

Related Information
This is custom documentation. For more information, please visit SAP Help Portal. 47
 6/30/25, 6:07 AM
Delete Spaces
Delete Orgs
Delete a Subaccount

This is custom documentation. For more information, please visit SAP Help Portal. 48