ISSUE OF NF-E WITHOUT BATCH (NFEISSU2)

The process (Technical name: NFEISSU2) consists of the following steps:

1. Create NF-e (technical name NFOCREAT)
   The NF-e data is validated and transformed into XML.
    Note

   If the validation or transformation fails, the NF-e data can be corrected and send again from the feeder system (ERP). The error reason can be displayed by clicking the Application Log field in the Status Overview of the NF-e Monitor.
2. Sign NF-e (technical name NFOSIGNA)
   The NF-e is signed with the certificate of the NF-e issuer CNPJ (Maintain the SSF settings in Customizing activity Maintain System Response for Own Tax Numbers in Process Settings and Customizing (Outbound)).
3. Authorize NF-e (technical name NFOAUTH1)
   Every single NF-e is sent to the government system for authorization individually and you immediately receive the NF-e status information. The status code can be authorized (for example: 100), or not authorized. For details about the status codes, see the current SEFAZ NF-e manual on the SEFAZ website. Before sending of single NF-e, the system checks the current service status. For more Information about the service status check, see Process Settings and Customizing (Outbound).
    Note

   The NF-es are not directly sent to the authorities, but via a report that is scheduled as a background job. This report is the same report that is used for sending the NF-es in batches. For more information, see the detailed description of the reports (/XNFE/NFE_BATCH_PROCESS,/XNFE/NFE_BATCH_CREATE ) in NF-e Batch Job Planning (Outbound).
4. Trigger B2B Process (optional) (technical name NFOTRB2B)
   The B2B process is created as a separate process, for more information see the description of the Send NF-e to Business Partner (technical name NFEB2BSD) process below.
    Note

   This step is only relevant if the NF-e was authorized.
5. Notify Feeder System (technical name NFOUPDFS)
   The status code is transferred to the feeder system (ERP).

After the successful execution of these steps, the process of issuing an NF-e is complete. However, the process can continue if a cancellation or skipping is triggered in the feeder system (ERP).

Fonte: NF-e Processing (Outbound) for Layout 3.10 & Pedro Baroni