Páginas filhas
  • NF-e Implementation Procedures (Specific Handling - SIGAFIS)

Below we have detailed the configuration of all fields, parameters, entry points and necessary settings for the issuance of NF-e.



Fields

1. Notice, in their tables, the configuration of the following fields:

Tables

SF1/SF2/SF3/SFT/SE1

NF_NFELE Eletr. (F1_NFELETR/ F2_NFELETR/ F3TR/ FT_NFELETR/E1_NFELETR)

In these fields, enter the Electronic Invoice No. issued by the Government of São Paulo regarding this RPS (Temporary receipt of Services).

Tables

SF1/SF2/SF3/SFT

NF-e Issuance (F1_EMINFE/ F2_EMINFE/ F3_EMINFE/ FT_EMINFE)

In these fields, enter the date when the Electronic Invoice was issued by the local government.

NF-e Time (F1_HORNFE/ F2_HORNFE/ F3_HORNFE/ FT_HORNFE)

Enter the time when the Electronic Invoice was issued by the local government.

Verif. Cd. NF-e (F1_CODNFE/ F2_CODNFE/ F3_CODNFE/ FT_CODNFE)

Enter the verification code for Electronic Invoice. The verification code indicates the authenticity of invoice issued by the local government.

Grant. Cred. (F1_CREDNFE/ F2_CREDNFE/ F3_CREDNFE/ FT_CREDNFE)

Enter the value of credit granted by Electronic Invoice issue. This credit can be used to deduct values to be paid from IPTU to taxpayers established in the city of São Paulo.

Table SC9

Serv. Code (C9_CODISS)

Code of service rendered in sales order.

SF4 Table

Tax Payment (F4_ISSST)

Inform whether the tax is paid inside or outside the city (ISS).

SF3 Table

Tax Payment (F3_ISSST)

Inform whether the tax is paid inside or outside the city (ISS). This field is used to store the history of ISS payment configuration in tax bookkeeping.

Important:


The sending file of RPS in badge requires that the RPS status is entered as the following:

T – Normal operation (taxation according to document issued);

I – Operation exempt or not taxable, run in the city of São Paulo;

F – Operation exempt or not taxable by the city of São Paulo, run in another city;

C - Canceled;

E – Strayed.

If fields F4_ISSST and F3_ISSST are set, the status of the RPS to be sent in remittance file is composed based on the content entered in these fields, with the ISS taxation setting. Note:

Customer Location

F4_LFISS - ISS Tax Records

F4_ISSST - Tax Payment

RPS Status

São Paulo

Taxed

1 – Within Municipality

T

São Paulo

Taxed

2 – Outside Municipality

F

São Paulo

Exempt/Others

1 – Within Municipality

I

São Paulo

Exempt/Others

2 – Outside Municipality

F

São Paulo

Taxed

Not filled out

T

São Paulo

Exempt/Others

Not filled out

I

Other

Taxed

1 – Within Municipality

T

Other

Taxed

2 – Outside Municipality

F

Other

Exempt/Others

1 – Within Municipality

I

Other

Exempt/Others

2 – Outside Municipality

F

Other

Taxed

Not filled out

F

Other

Exempt/Others

Not filled out

F



If fields F4_ISSST and F3_ISSST are not set, the status of the RPS to be sent in remittance file is composed based on the customer city, with the ISS taxation setting. Note:

Customer Location

F4_LFISS - ISS Tax Records

RPS Status

São Paulo

Taxed

T

São Paulo

Exempt/Others

I

Other

Taxed

F

Other

Exempt/Others

F

Whether set or not, fields F4_ISSST and F3_ISSST, if the document is canceled, the RPS status to be sent is C. Status E is not sent as there is control of strayed documents.


2. In the event of integration with the TMS - Transportation Management environment, only fields DUE_INSCRM and DUL_INSCRM must be set. If the requestor of transportation is located in São Paulo (State of São Paulo), this information must be completed, as the Government of São Paulo requires the Municipal Registration to be entered in these situations.


DUE Table

Mun. Reg. (DUE_INSCRM)

Enter the Municipal Registration of transportation requestor.

DUL Table

Mun. Reg. (DUL_INSCRM)

Enter the Municipal Registration of transportation requestor address.



Parameters

1. In the Configurator module, option Module/Files/Parameters, note the configuration of the following parameters:

The following parameters are used only by service providers to generate RPS - Temporary Receipt of Services.

MV_NFESERV

Indicates if the description of service provided in Electronic Tax Invoice and in RPS is composed by:
1 - sales order + description SX5 or
2 - only SX5.

The content can be configured as follows:

1 – for the description of the service provided to be sent in the text file for the government to be composed by sales order (C5_MENNOTA). If it does not exist, the description of the service code provided is displayed (X5_DESCRI).

2 – for the description of the service provided to be sent in text file to the government to be composed only by description of code of service provided (X5_DESCRI).

MV_NFEQUEB

Indicates that, if different service codes exist in Sales Order, an invoice must be generated for each code.

Content:

T – to break in more than one invoice.

F – to invoice in only one invoice.

MV_ESPECIE

Contains the types of tax documents used when issuing invoices.

The content must be configured as follows:

Series=Type;Series=Type

Example: 1=RPS

Note:

If the service invoice is issued together with the product invoice (combined invoice), the service part issued with the product part no longer has tax validity, which must be converted into an electronic invoice.

If the option selected performs service invoicing apart from product invoicing, a new type, RPS, was available, which can be used, associating it with a new series, in order to be used in RPS issue. In this case, you must make the required configurations for the number of this new series to start on the last numbering of the last service invoice issued, entering this new series in the parameter MV_ESPECIE and associating it with the RPS.

When you need to keep using the combined invoice, the service part must be sent to the local government in order to be converted into an electronic invoice. In this case, you do not need to configure the series and the parameter MV_ESPECIE.

MV_TRNDISS

Establishes if the ISS rounding must be carried out by document or by item, in which:
1 = by document;

2 = by item.

The parameter must be configured with 1 (per document), indicating that ISS value is only truncated at the end of the process, in the document total.

MV_RNDISS

Indicates the default of rounding in ISS calculation, in which:
.T. = Rounds up value.

.F. = Does not round, presents the truncated value.

This parameter must be configured with F (truncate) because the electronic invoice generation program of São Paulo calculates ISS discarding decimal places from the third position. Example: the tax generated results in R$ 356,318. For government of São Paulo, this value must be presented as R$ 356.31.

MV_RNDRNE

Indicates the rounding of default for ISS.

 F = normal.

T = default used by the Government of São Paulo.

MV_NFECONJ

Establishes what types of tax documents are used in the issuance of combined invoices (product + service) for Electronic Invoice.

Example of content: TYPE/TYPE/

·    If it does not use type to issue conjugated invoice, enter BLANK. Example: NF/NFSC/BRANCO

·    If it does not use issuance of conjugated invoice, leave this parameter without content.

MV_MAPARES

Establishes way to use summary map:
U – to use summary map, but it is not mandatory.

O – to use summary map, being mandatory.

To work with the concept of Electronic Invoice, the parameter MV_MAPARES must be configured with No, that is, Summary Map is not used because there is no process to use it in the Electronic Invoice process. The implementation method that uses Summary Map to generate Electronic Invoice has been analyzed by São Paulo government. Entries are only processed by voucher, generating the record type 3 concerning RPS export to local government.

N – who does not use summary map.

MV_NFEINSC

Indicates the Municipal Registration of the taxpayer that is presented in the generation of remittance file of the Electronic Invoice - SP.

Example of content: 99999999

By generating the magnetic file for export to local government, the taxpayer city registration is displayed with the content of the parameter MV_NFEINSC when such parameter exists and is filled out. Otherwise, the Municipal Registration entered in the Wizard of Electronic Invoice export routine (exemplified in topic Generation of Export Magnetic File for the government").



Inbound documents

1. If specific settings are needed, some points of entry are enabled.

Name

MTValRps

Purpose

Validate the series chosen during the issuance of RPS and it can block the billing.

Parameter [01]

cSerNF – chosen series

Return

Logical (.T. or .F.), depending on the validation made by the point of entry. If it returns .F., RPS is not generated.

Name

MTImpNFE

Purpose

Makes validations/updates when each electronic invoice is imported through the return file of the city government. This point of entry is located right below the updates of each of of the electronic invoices, that is, each imported NF-e is mentioned. In this moment, tables SF2 and SF3 are positioned in the registration that was just updated.

Parameter [01]

cArqPro: name of return file chosen during import, including the localization directory.

Example: c:\ NFe_R_99999999_20060901_20060926.txt

Return

None.

Name

MTDescrNFE

Purpose

Compose description of services rendered in operation. This description is used to print RPS and to generate the export file for the government.

Parameter [01]

RPS No. generated (F3_NFISCAL)

Parameter [02]

Series of Initial RPS

Parameter [03]

Customer Code/Store

Parameter [04]

Customer Store;

Return

String with description to be displayed

Notes

The string must have no more than 99 characters. If the description returned by the entry point surpasses this limit, the program reduced the return in 999 characters.

If line breaks are necessary in the description to be displayed, enter character “|” (chr124), as, for the magnetic file of sending to the government, the line break setting is necessary. 999 characters are printed, including line breaks, that is, the more line breaks set, the less characters are printed, due to the number of characters lost with the break.

Example:

The point of entry returns line breaks as the following:

“Services provided:|WASHING|POLISHING|”

Which, during printing, are displayed as:

Services provided:

Washing

Polishing



Name

MTObsNFE

Purpose

Supplement the information to be printed in the Other Information board only to print the RPS. This information is not sent to the government. The field Other Information of Electronic Invoice is generated automatically by the government.

Parameter [01]

RPS No. generated (F3_NFISCAL)

Parameter [02]

Series of Initial RPS

Parameter [03]

Customer Code/Store

Parameter [04]

Customer Store;

Return

String with additional information to be presented.

Notes

The string must have no more than 600 characters. If the string description with the additional information returned by the entry point surpasses this limit, the program reduces the return in 600 characters, as the content of field F3_OBSERV and indications of generation through tax coupon are added to this description, if they exist.

If line breaks are necessary in the description to be displayed, insert the character “|” (chr124), as, for the magnetic file of sending to the government, the setting of line break is necessary. 600 characters are printed, including line breaks, that is, the more line breaks set, the less characters are printed, due to the number of characters lost with the break.

Example:

The point of entry returns line breaks as the following:

“RPS Notes :|PIS: R$ 10.00|Cofins: R$ 10.00

Which, during printing are displayed as:

RPS Notes:

PIS: R$ 10.00

Cofins: R$ 10.00

Name

MTGravNFE

Purpose

Handle files saved by automatic routine of MATA916. RPS generated are saved in the directory provided by user (in the local machine). If these files must be handled, this point of entry can be used.

Parameter [01]

Directory entered by user to save RPS generated by routine MATA916.

Example: C:\TXTS\

Parameter [02]

Name of file generated by routine This name is composed by RPS No. + RPS Series, with extension .Doc.

Example: 0000001_UNI.DOC

Return

None.

Notes

This point of entry is called with each file generated. Example: if the filter provided by the user returns 10 RPS, the point of entry is called 10 times, each one of the savings, informing the name of each one of the .DOC files generated.

Name

MTCliNFE

Purpose

Edit the customer's information which is displayed when printing RPS (both graphic as with integration with MS-Word®) and in generation of remittance file for the government.

Parameter [01]

RPS No. generated (F3_NFISCAL)

Parameter [02]

Series of Initial RPS

Parameter [03]

Customer Code/Store

Parameter [04]

Customer Store;

Return

An array, containing the following information of the customer (all array positions are character type):

[01]: Name

[02]: CNPJ/CPF No. (no masks)

[03]: Municipal Registration

[04]: Address

[05]: District

[06]: Postal Code (CEP)

[07]: City

[08]: State

[09]: E-mail

[10]: State Registration

[11]: Country code

[12]: Information if the customer is or not responsible for the tax (“1” = Yes; “2” = No)

Notes

This entry point is run when generating the remittance magnetic file to the government, when printing graphic RPS and when printing RPS via integration with MS-Word®. MTCliNfe is only called if all return array positions are completed, that is, the array must include 12 positions.

Name

MTCHKNFE

Purpose

To perform validations with information of the Electronic Invoice entered in the footer of the Inflow Invoice by MATA103, confirming the inclusion of the tax document or not.

Parameter [01]

Array including Electronic Invoice information with the following positions:

[01]: NF-e number

[02]: Verification Code

[03]: Issue

[04]: Date of Issue

[05]: Credit Value:

[06]: RPS Number

Return

.T. or .F., indicating confirmation inclusion of tax document or not.

Notes

This point of entry is run during the confirmation of inclusion of tax document of entry through MATA103.



Configurations

Important Information on Customer Register

1. To import address data correctly, check the rule on how to fill out the Address field in the Customer Register:

  • Enter the address type with three characters. Example: STREET, AV. (avenue), LN. (lane). If the street type is entered with more than three characters, the system automatically reduces it for three characters. Example: If AVENUE is entered in the export file generation, AVE is displayed.
  • After entering this information, insert a blank space;
  • Enter the public way name with a comma at the end;
  • Enter the establishment/residence number.
  • Enter complement, if any.

Examples:
Av. Braz Leme, 1399

Pamplona Street, 752

Edit Santos Lane, 885

Ipês Street, 88 ap. 32

Note:

If the customer is in Distrito Federal, the address is not divided into public area type, public area name and number because addresses in this place do not follow this pattern. In these cases, we present all the address in positions of 186 to 235 of the remittance file to the Goverment.

If the customer is out of Brazil, this completion rule is not necessary. According to the instructions of São Paulo government, concerning acquirers out of Brazil, the fields Postal Code (358-365), State (356 to 357) and City (306 to 355) must not be filled out. Besides, the District field must present information about acquirer's city and country.

2. If the taxpayer is in São Paulo Rio de Janeiro, the taxpayer City Registration must be duly filled out. This information is required and validated by the local government website.

3. Fields like address, district and city are also mandatory. The file of RPS dispatch in lots is not imported if this information is not displayed.

4. If the taxpayer is from São Paulo, enter SÃO PAULO in the city field in order to identify that the customer is a local citizen.

5. For taxpayers located in the city of São Paulo, the City Registration must be presented. Therefore, make sure that the register of taxpayers located in São Paulo has the valid City Registration registered.