Technical Note 2020.005, available on the NFe Portal, updated existing rules and brought some new validation rules for version 4.0 of NF-e/NFC-e.
This document aims to assist our customers in both the news and the updating of the rules changed in this Technical Note.
After the generation of tax documents, the system will record information in the fields listed below:
CD2 – Digital Tax Records
Table | CD2 |
---|---|
Field | CD2_PSCFST |
Type | Character |
Length | 1 |
Decimal | 0 |
Format | @! |
Title | Ag Pis/CofST |
Description | Aggregate PIS/COFINS-ST |
Context | Real |
Ownership | Edit |
Options | 1=Yes; 2=No |
Help | Indicate whether the PIS/COFINS-ST value will be added to the total tax document. |
The CD2_PSCFST field was created to indicate whether the PIS/COFINS-ST value will be added to the total Tax Document. This field will serve as a basis for filling out the <indSomaPISST> and <indSomaCofinsST> tags created in this Technical Note.
Table | CD2 |
---|---|
Field | CD2_VFCPDI |
Type | Numeric |
Length | 14 |
Decimal | 2 |
Format | @E 99,999,999,999.99 |
Title | Def. Fcp. Val. |
Description | Deferred FECP Value |
Context | Real |
Ownership | Edit |
Help | Value of ICMS for the deferred Fund to Combat Poverty (FCP). |
Table | CD2 |
---|---|
Field | CD2_VFCPEF |
Type | Numeric |
Length | 14 |
Decimal | 2 |
Format | @E 99,999,999,999.99 |
Title | Eff Fcp Vl. |
Description | Effective FECP Value |
Context | Real |
Ownership | Edit |
Help | Value of the ICMS for the Fund to Combat Poverty (FCP) actually due. |
Table | CD2 |
---|---|
Field | CD2_VFCP |
Type | Numeric |
Length | 14 |
Decimal | 2 |
Format | @E 99,999,999,999.99 |
Title | FECP Value |
Description | FECP of target State |
Context | Real |
Ownership | |
Help | Value of the PECP relative to the operation without considering Deferral, if any |
The fields CD2_VFCPDI, CD2_VFCPEF, and CD2_VFCP (already existing) will be responsible for recording the values related to the FECP.
This field is part of Group I80 (Product Traceability). From this update, it becomes alphanumeric and remains not mandatory.
You must fill in the Aggreg. Code in the MATA926 file for the system to manage the tag. For this, in table SB1, enter a group in field B1_Grupo in order to enable traceability control. This group can be created in two ways.
1). In the SIGACFG module
Access: Database > Dictionary > Database
Select the Generic Tables option
In the search field, search for T0 and click edit
Register a group that will have traceability information
2). Using the Product Group file
Access: Files > Product Group
After registering the group, you must fill in the B1_Grupo field to update table SB1
After issuing the sales order and preparing the outgoing document, it is necessary to fill in the Complementary Data to generate Group I80.
Access: Tax Records > Transactions > Manual Outgoing Invoice > Select the invoice > Other Actions > Complements
Select the Traceability option and fill in the Aggreg. Code field for the cAgreg field to be generated within Group I80 (Product Traceability).
In XML, the field will be filled as below.
The NDraw field becomes alphanumeric, and the number of characters allowed has increased to up to 20.
This tag is part of Group I01 - Products and Services /Import Declaration
In our system, the Tag is generated using the information filled in routine MATA926 (Complements).
After issuing the document with a customer registered as Foreign and preparing the document.
Access: Tax Records > Transactions > Manual Outgoing Invoice > Select the invoice > Other Actions > Complements.
In the Export option, fill in the data so that the nDraw field is generated within Group I01.
In XML, the field will be filled as below.
The tpViaTransp field now has more transport options. Which are:
8 = Conduit/Transmission Network
9 = Own means
10 = Dummy Input/Output
11 = Courier
12 = On hands
13 = By trailer
This tag is part of Group I01 - Products and Services /Import Declaration
In our system, the Tag is generated using the information filled in routine MATA926 (Complements).
After entering the import document
Access: Tax Records > Transactions > Manual Incoming Invoice > Select the invoice > Other Actions > Complements.
In the Import option in the Transp. Method field, the new types of International Transport Method have been added to the list. Select the option you want, and the system will generate the tpViaTransp tag according to the information on the screen.
From this update, in the NDI field of Group I01 - Products and Services/Import Declaration, the information of the Single Import Declaration (DUIMP) may be saved.
This information is generated using the Complements routine (MATA926).
Access: Tax Records > Transactions > Manual Incoming Invoice > Select the invoice > Other Actions > Complements.
In the Import option, fill in the field No. of DI/DA to generate the information in the XML file.
SB1 - Products
CCE - Additional Information
CD2 - Digital Tax Records
CD2 - Digital Tax Records
CDL - Export Complement
CD2 - Digital Tax Records
CD5 - Import Complement
CD2 - Digital Tax Records
CD5 - Import Complement