| Aviso | ||
|---|---|---|
| ||
This document contains the features of the tax configurator from release 12.1.22.10 onwards. For previous releases, we recommend the following documentation: CFGTRIB - Tax Configurator - 12.1.33 |
Product: | Microsiga Protheus® |
Versions: | 12.1.22.10 |
Occurrence: | Generic Tax Configurator |
Índice outline true
This feature was created to tackle the complexities of the Brazilian tax system, aiming to enable the creation of taxes in a fully configurable way. This routine gathers the main elements of a fiscal operation involving states of origin, destination, products,
Credit Reversal - With Product Resale
The configurator of generic taxes is available on the menu of module Tax Records (SIGAFIS), on menu Updates → Facilitators → Tax Configurator (routine FISA170).
When you access the tax configurator, all registers needed for configuring are grouped and organized on the left side menu.
The routines are arranged in two main groups, Tax Rules and Financial Rules. This This manual pertains the registers of group Tax Rules. For further information on the group Tax Rules, click click https://tdn.totvs.com/x/NBu9Gg
| Informações | ||
|---|---|---|
| ||
You can find the date and time of the routines involved in the tax configurator in Other Actions option Routine List:
This option displays the sources' date and time information:
|
...
Use this routine to register generic taxes. This is the first registration you make for the system to process a new tax.
Example
In this register, fill in the following data:
Section Tax Definition:
Tax = Through this field, set the code for the new tax. Define it at will, though you cannot repeat it. This field is required.
Description = In this field, enter the description of the new tax. Describe it as you wish, to make identifying this tax easier.
Sphere = This field specifies the sphere of this tax. The options are 1 - Federal, 2 - State or 3 - Local. This field is not required.
Kind = In this field, select the tax kind. The options are 1-Tax, 2-Contribution, 3-Fund or 4-Fee.
Section Identifier - TOTVS ID:
Tax ID = In this field, enter the code that identifies the generic tax. We call this code the TOTVS ID.
The TOTVS ID concept enables the identification of a generic tax. The system automatically generates a fixed number for this ID. This ID basically calls "From To", from a generic tax with a random code set by the user to an actual, known tax.
Only fill in this field when you need to state the value of the generic tax in an ancillary obligation, such as SPED Fiscal; otherwise, there is no need to fill it in.
| Informações |
|---|
Customers are notified through notices and documents every time TOTVS IDs are released, with all the required procedures. |
...
Use this routine to register a tax reference unit, with its respective quotation, on a monthly basis.
In this register, fill in the following data:
Section URF Definition
In this section, provide data to define and identify the URF.
Unit Code: In this field, enter the identifier code. This field is required and you can register no more than one URF with the same code, because this code is used for linking with the other entities, such as the rate rule.
Description: In this field, enter the URF description. Describe it as you wish, to make identifying the URF easier.
Section URF Values:
In this section, enter URF values on a monthly basis. When calculating the tax, the URF value is obtained in accordance with the month and year of document issue.
Month: In this field, enter the reference month for the URF value.
Year: In this field, enter the reference year for the URF value.
Value: URF value corresponding to the previously entered month and year.
...
Use this routine to create progressive table rules, with data from the ranges composing a given progressive table as well as deduction values and rates. For example, you can use this routine to calculate Income Tax.
In this register, fill in the following data:
Section Progressive Table:
In this section, provide data to define and identify the Progressive Table.
Code: In this field, enter the identifier code. This field is required and you can register no more than one rule with the same code, because this code is used for linking with the other entities.
Description: In this field, enter the rule description. Describe it as you wish, to make identifying the rule easier.
Section Enter Range Values:
In this section, enter range values, one at a time.
Initial Value: In this field, enter the initial value of the range.
Final Value: In this field, enter the final value of the range.
Rate: In this field, enter the rate of the range.
Deduction Value: In this field, enter the value to be deducted from the range.
...
Use this routine to configure taxes that require base value, increase or MVA. Configuring scenarios by NCM, specifying: tax, states of origin/destination, effective period, tax classification or measurement unit of product.
In this register, fill in the following data:
Section NCM:
NCM Code: In this field, enter the NCM code. This field is required and you can register no more than one rule with the same NCM, because this NCM is used for linking with the other entities.
Description: This field is automatically filled in with the NCM description registered in Protheus.
Section Taxes:
Tax: Tax Code to be bound to the NCM rule, which may have MVA, Base Value or Rate Increase. Tax examples: ICMS, ICMS ST, IPI, PIS, COFINS and more.
Description: This field is automatically filled in with the tax description registered in the Tax Configurator.
Added Value Margin:
Source State: State of Origin. If you want all States, enter **
Destination State: State of Destination. If you want all States, enter **
Start Date: Start Date of MVA validity
End Date: End Date of MVA validity
MVA: MVA calculation rate
MVA Auxiliary Index: MVA auxiliary index
Source State: State of Origin. If you want all States, enter **
Destination State: State of Destination. If you want all States, enter **
Start Date: Start Date of MVA validity
End Date: End Date of MVA validity
Measurement Unit: Product measurement unit to be used for calculating the Base Value
Base Value: Base Value to be added to tax calculation
Origin State: State of Origin of a product. If you want all States, enter **
Destination State: State of Destination of a product. If you want all States, enter **
Start Date: Start Date of MVA validity
End Date: End Date of MVA validity
Increase Percentage: Percentage of Increase used for calculating FECP or Increase.
Increase Auxiliary Index: Auxiliary index for calculating Increase
| Informações |
|---|
When calculating the tax in Protheus routines, the Tax Configurator tries to classify the operation, if the tax has any link to the NCM register, considering: NCM, Tax, State of Origin/Destination, Effective Period and Measurement Unit. |
| Aviso | ||
|---|---|---|
| ||
From continuous dispatch of February/2023 onwards, in the Rule by NCM register, the Added Value Margin, Base Value and Rate Increase tabs feature a new field for specifying the CEST code to classify that rule. |
...
Dependents Register
Use this routine to handle all rules involving the deduction of values by dependents. We created this routine to eliminate the need for using parameters in SX6.
In this register, we basically define the deduction value per dependent, as well as the date criterion for using this deduction.
In this register, fill in the following data:
Section Enter the Rule Code:
Rule Code: In this field, enter the identifier code. This field is required and you can register no more than one rule with the same code, because this code is used for linking with the other entities.
Description: In this field, enter the rule description. Describe it as you wish, to make identifying the rule easier.
Section Rule Configuration:
Value per dependent: Deduction value per dependent, to be multiplied by the registered quantity.
Date to be used when searching the balance per dependent: Date type with which the bill related to the invoice in Financials is queried. 1 = Issue; 2 = Actual Due Date; 3 = Booking Date; 4 = No Query in Financials.
| Informações |
|---|
This rule is linked to the calculation index I:DED_DEPENDENTES. This index also remains available in the formula component. Primarily it must be bound to Calculation Rule - Tax Documents, though you may use it in other rules by formula, if needed. The deduction value per dependent is obtained by multiplying the value per dependent entered in the register by the quantity of dependents of the supplier. The system then checks whether the deduction value was already used on the bill's date of maturity, issue or booking. If not, the deduction is used as expected; otherwise, the value is no longer used on the same day, in accordance with the criterion adopted in the deduction per dependent rule. |
...
Use this routine to set rules for obtaining the local tax rate, depending on the service provision code (SX5 - Table 60), whether local or federal, of the tax and city in which the local tax is due.
In this register, fill in the following data:
Section Service Code:
Service Code: In this field, enter the service code. This field is required and you can register no more than one rule with the same code, because this code is used for linking with the other entities.
Description: This field is automatically filled in with the service code description registered in Protheus.
Section Taxes:
Tax: Tax Code to be bound to the service code, which may have a general rate configuration for all cities or a specific configuration per city.
Description: This field is automatically filled in with the tax description registered in the Tax Configurator.
Rate: Default rate for all cities that fit the rule.
Section Specific Rate by City:
State: State that contains the specific rate by city
City Code: Code of city that contains the specific rate.
Description: This field is automatically filled in with the description of the city selected.
Specific Rate: Specific rate for the city that fits the rule.
| Informações |
|---|
There is no need to enter this rule code in any register. Once you configure an Operation Tax Profile that includes the ISS code, a rate rule with the calculation index I:ALQ_SERVICO in the formula and bind all configurations in Calculation Rule - Tax Documents, Protheus will be ready to try to classify the tax using the service rate at the Invoice time. |
...
Use this routine to register the CSTs of several taxes, such as ICMS, IPI, PIS, COFINS and more. When you access the configurator for the first time, the system runs an automatic load based on the CSTs already found in it, with the CST codes of ICMS (generic table S2), CSOSN (generic table SG), IPI (generic table S3), ISS (generic table S9), PIS (generic table SX) and COFINS (generic table SX).
In this register, fill in the following data:
Section Tax Status Code
In this section, provide data to define and identify the CST.
Code: In this field, enter the identifier code. This field is required and you can register no more than one with the same code, because this code is used for linking with the other entities, such as the bookkeeping rule.
Description: In this field, enter the description of the new tax status code group. Describe it as you wish, to make identifying the register easier.
Tax ID: Enter the code that identifies the generic tax that will contain a tax classification procedure. This Tax ID is the TOTVS ID code mentioned in the tax register.
Start Date: Start Date of CST register validity; that is, if the tax document date is previous to the start date of validity, the register is not used for CST classification. If it is after or equal, then the register is used. This field is required.
End Date: End Date of CST register validity. Of course, this is used only when the end date is known. When the end date of validity is not known, leave it blank.
Section CST:
In this section, enter the tax classification code and its respective description for the Tax ID selected.
CST: Enter the tax classification code.
Description: Description of the new tax classification code.
...
Use this routine to set the form generation rules (Table SF6). In various situations, when the invoice is issued, the need arises to generate forms, something currently done in legacy taxes through questions (Dictionary - SX1) in routines MATA461 and MATA103. With this routine, it is no longer necessary to fill in questions, but rather to configure it. The customer is free to define exactly in which situation their form should be generated or not.
In this register, fill in the following data:
Rule Definition Section
In this section, provide data to define and identify the CST.
Code (CJ4_CONDIGO): In this field, enter the identifier code. This field is required and you can register no more than one with the same code, because this code is used for linking with the other entities, such as Calculation Rule - Tax Documents.
Description (CJ4_DESCR): In this field, enter the description of the new bookkeeping rule. Describe it as you wish, to make identifying the register easier.
Section Form Generation Mode:
Mode for Bookkeeping Form Generation (CJ4_MODO): Mode of tax Payment form generation. 1=Invoice and 2=Verification.
View Form When Generating the Invoice (CJ4_VTELA): Option to view the form onscreen when adding the document.
Increase Form (CJ4_MAJSEP): Enter whether to generate separate forms when generating the form, if there is a tax increase calculation.
Section Form Generation Criterion:
State of Origin and Destination (CJ4_ORIDES): Generation of tax payment form for operations: 1=Interstate Only; 2=Internal Only; 3=Neutral.
Import or Export (CJ4_IMPEXP): Generation of tax payment form: 1=Import Only; 2=Export Only; 3=Neutral.
State Registration at State of Destination (CJ4_IE): Generate form for collection at State of Destination when: 1=Has SR; 2=Lacks SR; 3=Neutral.
Section GNRE Due Date:
Due Date (CJ4_CFVENC): Due Date Option: 1=Add business days; 2=Fixed Day current month; 3=Fixed Day following month.
Quantity of Days to Add (CJ4_QTDDIA): Quantity of days to be added in accordance with the option selected in due date configuration field (CJ4_CFVENC).
Date of Fixed Day (CJ4_DTFIXA): Fixed date for GNRE due date. This field is enabled in accordance with option 2 or 3 of field (CJ4_CFVENC).
Section GNRE Complementary Information:
CNPJ/EIN (CJ4_CNPJ): Printing of participant CNPJ/EIN in GNRE.
State Registration (CJ4_IEGUIA): State registration to be printed in GNRE. 1=Participant; 2=Sigamat (Company Register in Protheus); 3=SR of State.
State (CJ4_UF): State to be used when printing the GNRE: 1=Parameter (MV_ESTADO); 2=State of Origin; 3=State of Destination; 4=Invoice State.
Add. Info (CJ4_INFCOM): Code of additional information to be recorded in the Form complement.
Description (CJ4_DESINF): Description of additional information selected in field (CJ4_INFCOM).
...
Use this routine to define which revenue code to use in the National Form for Collection of State Taxes (GNRE).
During the process of recording the generic tax GNRE, the revenue code classification will be requested. Based on the user definition, revenue codes can be defined by document template and State, so no other type of binding is needed in the tax configurator.
In this register, fill in the following data:
Section Rule Definition:
Tax Code (CJ5_CODIGO): Code of tax that contains the rule for generating the revenue code. Tax examples: ICMS, ICMS ST, IPI, PIS, COFINS and more.
Description (CJ5_DESCR): This field is automatically filled in with the tax description registered in the Tax Configurator.
Section Document Templates Definition:
Document Template (CJ7_ESPECI): Kind of tax document. (SX5 - Table 42). If you want to configure all kinds, enter ALL.
Description (CJ7_DESCR): Description of tax document kind registered in generic table.
Section Code by State:
State (CJ6_ESTADO): State that contains the rule. If you want to configure all states, enter **.
Revenue Code (CJ6_CODREC): Code of Revenue. Example: 100013 - Communication ICMS.
Revenue Det. (CJ6_DETALH): Details on Revenue. If the state lacks revenue code details, this field remains blank.
Reference (CJ6_REF): Reference period. Example: Monthly, 1st Fortnight, 2nd Fortnight, etc.
...
Use this routine to register FCA (Update and Conversion Factor) Economic Indicators for each State/Period.
In this register, fill in the following data:
Section FCA (Update and Conversion Factor) Economic Indicators:
State (F0R_UF): State at issue.
Period (F0R_PERIOD): Reference year and month.
Indicator (F0R_INDICE): Economic index for conversion factor.
| Informações |
|---|
To use this register, bind its index (I:INDICE_AUXILIAR_FCA) to a formula. Refer to Calculation Formula Details for further utilization information. |
...
Use this register to define product tax profiles in accordance with criteria set by the customer themselves, for use in the generic taxes calculation.
In this register, fill in the following data:
In this section, enter a code and a description to identify the profile registered. Be mindful that the product profile rule code cannot be repeated.
On this grid, enter which products integrate the profile. There must be at least one line on this grid. The product cannot repeat itself in the same profile, and must have at least one product entered.
On this grid, enter the origins that belong in this profile. There must be at least one line on this grid. The product origin cannot repeat itself in the same profile, and must have at least one origin entered.
...
In this routine, enter operation profiles through CFOPs, Operation Type and Service Code, following criteria set by the customer, to be used in the generic tax engine configuration.
This register has an automatic load of profile suggestions that facilitate its use.
In this section, enter a code and a description to identify the profile registered. Be mindful that the product profile rule code cannot be repeated.
In this register, fill in the following data:
On this grid, enter which CFOPs compose this profile. There must be at least one line on this grid
On this grid, enter which Operation Types compose this profile. There must be at least one line on this grid.
If you need to use all operation types in the profile, you do not need to type all operation types. Just add a line to the grid with the code "ALL" for the system to automatically use all operation types.
On this grid, enter which Service Codes compose this profile. If not a service operation profile, leave this tab blank.
...
Use this routine to define participant profiles to calculate generic taxes, following criteria set by the customer.
In this register, fill in the following data:
In this section, enter a code and a description to identify the profile registered. Be mindful that the product profile rule code cannot be repeated.
In this section, define which participants compose the participants profile through fields:
Type: Use this field to define the participant type: 1 - Supplier (SA2) or 2 - Customer (SA1)
Participant: In this field, enter the participant code. This will be a customer or supplier code in accordance with the type specified previously.
Store: In this field, enter the participant's store, whether a customer or supplier store depending on the previously specified participant type.
| Aviso | ||
|---|---|---|
| ||
A profile may have one or more participants, though the participant cannot be repeated in the same profile. |
...
Use this register to define origin and destination tax profiles in accordance with criteria set by the customer themselves, for use in the generic taxes calculation.
This register has an automatic load of profile suggestions that facilitate its use.
In this register, fill in the following data:
In this section, enter a code and a description to identify the profile registered. Be mindful that the product profile rule code cannot be repeated.
On this grid, enter the States of origin and destination that compose the profile.
Origin State: In this field, enter the state of origin of the operation.
Target State: In this field, enter the state of destination of the operation.
| Aviso | ||
|---|---|---|
| ||
The combination of State of Origin + State of Destination cannot be repeated within the same profile. |
...
Use this routine to register a calculation base rule. When the tax is calculated, this rule is interpreted and the resulting value is used as calculation base.
In this register, fill in the following data:
In this section, enter the definition and identification data of the rule and source value; that is, the starting value for base composition.
Rule Code: In this field, enter the identifier code. This field is required and you can register no more than one rule with the same code, because this code is used for linking with the other entities.
Description: In this field, enter the rule description. Describe it as you wish, to make identifying the rule easier.
Source Value: In this field, select the starting value for composing the calculation base. The available options are:
| Dica |
|---|
All options refer to the respective calculated value in the document item. |
In this section, define the additions and subtractions to be applied on the source value selected in field Source Value.
Fields Discount, Shipping, Insurance, Expenses, ICMS Exemp. and ICMS Withheld have the same goal and define the action of each value, respectively.
The available options are:
1 - No Action: The value at issue does not affect the source value.
2 - Subtract: The value at issue is subtracted from the source value.
3 - Add: The value at issue is added to the source value.
In this section, if applicable, enter whether a reduction will be applied to the calculated base.
Reduction %: In this field, enter the reduction percentage to be applied to the calculation base.
Reduction Type: This field defines the moment in which the reduction configured in field Reduction % should be applied. Before or after additions and deductions. The options are:
1 - Reduce before additions/deductions: The base reduction is applied before additions and deductions.
Example:
1,000.00 * 70% = 700.00
= 700.00 + 150.00 = 850.00
= 850.00
2 - Reduce after additions/deductions: The base reduction is applied after additions and deductions.
Example:
1,000.00 + 100.00 + 50.00 = 1,150.00
= 1,150.00 * 70% = 805.00
= 805.00
In this section, available only when the source value is equal to 02 - Quantity, define whether to convert the quantity entered in the item to a specific measurement unit (only for purposes of defining the generic tax calculation basis).
Unit: In this field, enter the measurement unit to be used in the calculation base conversion.
The quantity is converted in accordance with the settings of fields already found in the product register; that is, the 1st and 2nd measurement units, the conversion factor and the conversion type, following these criteria:
If no specific measurement unit is defined, no conversion is made; therefore, the calculation base is exactly the quantity entered in the document item.
Example:
Resulting calculation base: 3.00
If you define a specific measurement unit and it corresponds to the first product measurement unit, no conversion is made either; therefore, the calculation base is exactly the quantity entered in the document item.
Example:
Resulting calculation base: 3.00
If you define a specific measurement unit and it corresponds to the second product measurement unit, the quantity entered in the document item is converted in accordance with the conversion type and factor defined in the product at issue.
Example:
Resulting calculation base: 30.00
If you define a specific measurement unit and it corresponds neither to the first nor to the second product unit, then the calculation base cannot be defined; therefore, the tax at issue is not calculated.
Example:
Resulting calculation base: 0.00.
...
Use this routine to register rate rules for generic taxes. This rule is interpreted when bookkeeping the tax document and the value obtained through it is used as a generic tax rate.
In this register, fill in the following data:
In this section, define the rule code, a description and the source value of the rate, in accordance with the fields below:
Rule Code = In this field, define the rule code. This field is required and you can define as you wish, though you cannot repeat it.
Description = In this field, enter the description of the rate rule. Describe it as you wish, to make identifying this tax easier.
Source Value = This field is required. Enter the source of the rate through the options below:
| Aviso | ||
|---|---|---|
| ||
If the source value is not calculated in the tax document, the generic tax rate is zero; hence, the generic tax is also not calculated. |
This section is only enabled when field Source Value is set to option 04. Here you can manually define the fixed rate through fields:
Rate Type = In this field, define the type of rate. Use option 1 - Percentage to define the rate as a percentage and option 2 - Measurement Unit to define the rate as a fixed value to be applied in the tax calculation.
Rate = In this field, enter the manual rate.
This section is only enabled when field Source Value is set to option 05. In this section, define the use of a URF as rate through fields:
URF Code = Enter the code of the previously registered URF.
URF Perc. = In this field, enter the URF percentage to be used. By default, this field is set to 100% URF utilization.
| Dica |
|---|
The URF value is obtained using the bookkeeping period of the invoice; hence, if there is no value for the invoice period when registering the URF, the rate is zero and, consequently, the tax is not calculated. |
...
This register aims to configure the tax bookkeeping. This rule register is similar to the TIO register, regarding Record and CST field configurations.
This rule is bound within Calculation Rule - Tax Documents in field "Bookkeeping" (F2B_CODESC).
In this register, fill in the following data:
Section Bookkeeping Rule Definition:
In this section, define the rule code and a description. The code is exclusive and cannot be changed or repeated.
Section Levy:
In this section, define who the tax is levied, including the tax classification, tax levy, reduced installment levy, effect on invoice total and the deferral percentage.
Section Tax Status Code:
In this section, define which CST to use for bookkeeping a tax configured in routine Calculation Rule - Tax Documents.
| Aviso | ||
|---|---|---|
| ||
The rules defined in this register are used for recording Table CJ3 – Bookkeeping by Item. |
...
This register aims to register the generic tax; that is, to define when and how to perform the calculations, using previously registered profiles and rules. This register also defines how to generate financial bills and whether the tax is used in the verification of generic taxes. Thus you can calculate, collect and verify new taxes in a simple and quick way, with no need to create new parameters or new system fields.
For example, suppose we previously register the tax XPTO, a tax for which the following hypotheses exist: Withholding by Tax Authorities, Credit and Collection on Verification. The need to create three calculation rules for this tax soon arises; that is, three tax calculation variations, one for withholding by tax authorities, another for credit and the third one for verification. Thus, you must create the calculation rules for each tax variation. Be mindful that the routine allows registering as many variations as needed.
This section aims to identify the tax calculation rule using a code, description and validities.
Rule Code (F2B_REGRA): In this field, define the calculation rule code of generic tax. This code is required and cannot be repeated within the same validity. This code is displayed in the fiscal document taxes tab when the tax is calculated.
Description (F2B_DESC): This required field helps to identify the tax calculation rule. This description is displayed in the taxes tab when the tax is calculated.
Tax (F2B_TRIB): In this required field, enter the tax code to which this rule belongs. A tax may have several calculation rules; however, a calculation rule can have only one tax.
Start Date (F2B_VIGINI): Enter the start date of calculation rule validity; that is, if the tax document date is before the start date of validity, the tax rule is not calculated. If after or equal to it, then the calculation rule can be executed. This field is required.
End Date (F2B_VIGFIM): Enter the end date of tax rule validity. Of course, this is used only when the end date is known. When the end date of validity is not known, leave it blank.
When you fill in the initial and final validities, the system checks whether the document date is between the initial and final validities. When there is only the initial validity, the system checks the document date with the initial validity and regards the blank final validity as valid/in effect.
This section aims to define how to calculate the tax, how to generate the financial bills (if any) and how to generate it on verification (if any).
Calculation Base (F2B_DESC): Define the calculation base to calculate the tax through a previously registered Calculation Base rule. Be mindful that if the value set in the Calculation Base Rule is not found in the tax document, the generic tax is also not calculated.
Rate (F2B_RALIQ):Define the rate to calculate the tax through a previously registered rate rule. Be mindful that if the value set in the Rate Rule is not found in the tax document, the generic tax is also not calculated.
Financial (F2B_RFIN):In this field, enter a financial rule that defines how to generate the financial bill of this tax. Fill in this field only when you need to generate bills for withholding by tax authorities or collections on tax document issue, otherwise leave it blank. We must emphasize that if the tax must be collected through a verification, it is very likely that you should not fill in this field, otherwise the tax may be collected twice, in the tax document and also in the verification.
| Dica |
|---|
For further information on how to register the financial rule, refer to https://tdn.totvs.com/x/NBu9Gg |
Round Config (F2B_RND):In this field, define the bill rounding rule, whether rounded or truncated. This field is not required. If blank, the calculated value is rounded by default. This field operates jointly with parameter MV_RNDSOBR. For further information on this parameter, refer to the documentation https://tdn.totvs.com/x/2Ni-HQ
Verification Rule (F2B_RAPUR): In this field, enter the verification rule to define how to state and calculate tax values in the generic taxes verification. This field is not required. Fill it in only when the tax must be collected through a verification. We must emphasize that if the tax has an entered financial rule, it is very likely that you should not fill in this field, otherwise the tax may be collected twice, in the tax document and also in the verification.
Bookkeeping (F2B_CODESC): In these fields, enter the bookkeeping rule that defines whether to book the tax as charged, exempt or others. Also the CST of the tax, among other settings allowed by the register.
Tax for Increase (F2B_TRBMAJ): In this field, select a tax to calculate the increase.
Deduction per Dependent (F2B_DEDDEP): Rule code that contains data on the calculation base deduction per dependent.
Progressive Table (F2B_DEDPRO): Rule code for progressive table deduction.
Form Gen. Rule (F2B_RGGUIA): Rule code for GNRE generation.
Auxiliary Calculation Base (F2B_RBASES): Rule code of secondary calculation base, for scenarios with base value calculation, when there is a need to calculate two calculation bases and use the one with the highest value.
Greater or smaller value between bases (F2B_MAXMIN): Select an auxiliary base in field F2B_RBASES to activate the field. Select 1=Higher - to load the higher value between the calculation base and the auxiliary calculation base. Select 2=Lower - to load the lower value between the calculation base and the auxiliary calculation base.
This section aims to define when to calculate the tax, based on Origin/Destination, Participant, Operation and Product profiles.
The generic tax calculation rule is only executed when the invoice data (State of Origin, State of Destination, Participant, CFOP, Operation Type, Product and Product Origin) match all the profiles entered in this section.
Ori/Des Prof. (F2B_PEROD): In this field, define the Origin/Destination Profile for the calculation rule. Be mindful that the States of Origin and Destination of the tax document are compared with the States of Origin and Destination that compose this profile.
Part Prof. (F2B_PERFPA): In this field, define the Participant Profile for the calculation rule. Be mindful that the Participant (client or supplier) of the tax document is compared with the Customers and Suppliers that compose this profile.
Oper Prof. (F2B_PERFOP): In this field, define the Operation Profile for the calculation rule. Be mindful that the CFOP and Operation Type (if any) of the tax document are compared with the CFOPS and Operation Types that compose this profile.
Prod Prof. (F2B_PERFPR): In this field, define the Product Profile for the calculation rule. Be mindful that the Product and Product Origin of the tax document are compared with the Products and Product Origins that compose this profile.
| Nota | ||
|---|---|---|
| ||
We must emphasize that, to perform the calculation, all four profiles must match the invoice data. Of the tax document only matches one, two or three profiles, the calculation does not occur. |
...
Use this routine to register messages. In this initial stage, this register services the messages used in EFD ICMS IPI in records 0460 (Tax Entry Notes Table), C195 (Tax Entry Notes (Codes 01, 1B, 04 and 55)) and C197 (Other tax obligations, adjustments and data on values from tax documents).
In this register, fill in the following data:
Rule Code: Enter the Rule Code.
Description: Enter the name of the Message Rule
Filter Field:
In field CJ8_TPREGR (Rule Type), selecting Taxes enables, in field CJ8_TRIFIL (Rule to be queried), the 3 spheres (State, Federal and Local), and, by selecting one of the options for query, the field CJ8_REGTRA (Tax) is filtered by Rule Type;
CJ8_TRIFIL (Rule to be queried)
CJ8_REGTRA (Tax)
If Rule Type is equal to Generic Taxes, field CJ8_TBCONF (Generic Tax) is enabled with the query in table F2B (Tax Rules).
If, in field CJ8_TPREGR (Rule Type), you select Invoice Data, then, in field CJ8_TRIFIL (Rule to be queried) the options Invoice Header and Items' Data are enabled. By selecting one of the options, then the field CJ8_CONSUL (Value to be Added to Formula) displays information such as Invoice Type, Operation Type, Item Number, Value of Goods, etc.
After selecting the previous information, you may add the content selected in field CJ8_CONSUL (Value to be Added to the Formula) to field CJ8_MENSG (Message Composition), by clicking the Add button. After the addition, just click Validate Message.
Use this routine to register the Entry Adjustment Codes, linking it to a Tax Document Rule to be created by the user, in accordance with its bookkeeping, hence stating the entry code data when the document is generated.
Thus, with this register we unify:
Access - Updates → Facilitators → Taxes Configurator
In this register, fill in the following data:
*Required Fields
**Fields not Viewable in Browser
Section Entry Adjustment Rule Register. Fill in with Rule header data, where we find the fields:
Section Entries. Fill in the fields related to entry, validity and form codes.
Section Values. Fill out the fields with values to inform EFD ICMS IPI records.
| Aviso | ||
|---|---|---|
| ||
Field CJA_VLOUTR records in Table CDA in field CDA_VLOUTR. This field in CDA is exclusive in Tax Configurator. This recording in CDA is automatically performed to configure how the Entry Adjustment Code understands the ICMS value to be transferred to Record C197, whether in field Value or field ICMS Other. Be mindful that this process is fully independent from configurations performed in Legacy flow, using reflex register x field Vl REG 197 . |
Description | CDA Recording | Source of the Information |
Msg Code Desc. Rec. 0460 | CDA_TXTDSC | CJA_TXTDSC |
Complementary Msg Code | CDA_CODCPL | CJA_CODCPL |
Entry Msg Code | CDA_CODMSG | CJA_CODMSG |
Use ICMS Value Other | CDA_VLOUTR | CJA_VLOUTR |
Calculation Rule | CDA_REGCAL | CJA_REGCAL |
Base Option | CDA_OPBASE | CJA_NFBASE |
Rate Option | CDA_OPALIQ | CJA_NFALIQ |
Group Entry Code | CDA_AGRLAN | CJA_GERMSG |
Section Messages. Enter the message data to be used in records 0460, C195 and C197.
Follow the steps below to configure how to use the Adjustment Rule register
b. Register the NCM Rules
c. Register the Tax Status Code
...
Calculation Base Rule
ICMS Base Example
ICMS Base Exempted via Formula Example.
iii. IPI Base Example
b. Rate Rule
c. Bookkeeping Rule
d. Calculation Rule - Tax Documents
In this register, we link the above relationship registers to be used in invoice calculations.
i. ICMS Example - Entries Tab
The proposal of the register is to centralize the entry codes in the widest adjustment rule possible, so there is no need to create multiple entry adjustment rule registers for similar profiles; therefore, for release 12.1.2210, we have added two fields not illustrated in the example above, in which the user can choose when to use the entry code:
Field Operation - Valid Values (01-Inflow| 02-Outflow| 03-Return)
Field Operation Type - Valid Values (01-Origin State| 02-Destination State)
In the illustration above, we can see that several entry codes have been attributed even from another state, the branch of the example being SP.
Through fields Operation and Operation Type, the user can define when to use the entry code. In the example, an entry code was registered for the State of Rio de Janeiro, in which the fields Operation and Operation Type are respectively configured as "Outflow"|"State of Destination"; that is, the entry code is only displayed when an outgoing invoice is issued with RJ as its State of Destination.
In tab Entries, we also have the field "Message Type" with 3 possible options:
01- Entry Code by Period - In this configuration for EFD ICMS/IPI file creation purposes, the entry codes are grouped by period in accordance with the block in which a specific entry code fits the SPED.
02- Entry Code by Invoice - In this configuration for EFD ICMS/IPI file creation purposes, the entry codes are grouped by invoice in accordance with the block in which a specific entry code fits the SPED. Example: Block C195 and C197.
03- Entry Code by Item - In this configuration, for EFD ICMS/IPI file creation purposes, the entry codes do not have grouping; that is, they are detailed by item, as the record was originally recorded in CDA table.
ii. Tab Values
In tab Values, define how values are displayed in accordance with the entry code. This tab is very useful for the composition of block C197 and similar blocks in SPED FISCAL.
iii. Tab Messages
Use this tab to bind the messages registered in routine FISA178 (Message Register). In the example below, the fields are used in various ways:
Note: Fill out the field "Complement Msg Code" to correctly display it in SPED FISCAL.
iv. IPI Example
The IPI dynamic is similar to ICMS.
Rule TRIB03, created with Exempted ICMS, was used in the Entry Adjustment register and will be stated in TAB Entry of the Financial Spreadsheet. This rule aims to calculate the values needed for display in the Entries indicated.
| Aviso | ||
|---|---|---|
| ||
The Tax Rule Code entered in the Entry Adjustment register in field CJA_REGCAL must be a rule created by the customer, as needed and as the entry is understood. |
This register aims to define how to generate financial bills of generic tax verification, linking a financial bill rule to a tax through fields:
Tax: In this field, we define the tax to be processed in generic tax verification, which will need to generate a financial bill with the debit balance of the verification.
Bill Rule: In this field, enter the bill rule to be executed in verification, when generating the financial bill. For further information on how to register a financial rule, refer to https://tdn.totvs.com/x/NBu9Gg
...
This register aims to define how to state and calculate generic tax values in generic tax verification, enabling the composition settings of verification reversals, credit and debit values.
This register has an automatic load of rule suggestions that facilitate its use.
In this section, enter a code and description to identify the verification rule.
...
After each verification, if debits have not surpassed credits, a credit balance is generated and this balance is carried forward to the next period for later use. Double click any of the credit balance lines (carried over, used or to be carried over) to list the balances used in the verification at issue, with their respective periods of origin, and also how much of each balance was used in the verification. Balances are consumed in order of generation; that is, from older to newer.
Com objetivo de auxiliar a conferência do cálculo dos tributos genéricos, disponibilizamos o relatório de tributos genéricos por documento fiscal, desta forma será possível conferir os valores dos tributos por item de documento fiscal, independentemente se o tributo gerou retenção, recolhimento ou apuração.
Para processar o relatório basta preencher as perguntas iniciais:
Data Inicial: Indique a data inicial para processamento do relatório
Data Final: Indique a data final para processamento do relatório
Seleciona Filiais: Esta pergunta quais filiais deverão ser consideradas para processamento do relatório, a opção 1-Sim abrir uma tela para selecionar uma ou mais filiais, já opção 2-Não considera somente a filial logada.
Tributo: Neste campo informaremos qual tributo deverá ser processado no relatório. Somente será permitir processar um tributo por relatório.
Confirmando o processamento do relatório, serão listadas as notas que possuírem tributo genérico calculado no período e filial(s) especificado(s), considerando as notas fiscais que gravaram livro fiscal (tabelas SFT/SF3). Após a conclusão do relatório as informações nas seguintes estrutura:
Seção de cabeçalho do relatório:
Filial = Aqui será demonstrada a filial da nota fiscal
Operação NF = Este campo identifica a operação da nota fiscal nas seguintes hipóteses:
Regra do Tributo = Neste campo será demonstrado o código da regra do tributo.
Descrição da Regra = Neste campo será exibida a descrição da regra de cálculo do tributo.
Seção de detalhamento do relatório:
A seção será composta pelas seguintes colunas:
Número NF = Número do documento fiscal.
Série NF = Série do documento fiscal.
Cod. Participante = Código do cliente/fornecedor.
Loja Participante = Loja do cliente/fornecedor.
Data = Data de emissão.
Item NF = Número do item.
CFOP = CFOP do item.
Unidade de Medida = Unidade de medida do item.
Base de Cálculo - Quantidade = Base de cálculo em quantidade do tributo genérico.
Base de Cálculo Tributo = Base de cálculo do tributo.
Alíquota Tributo = Alíquota do tributo genérico.
Valor Tributo = Valor calculado do tributo genérico.
Com objetivo de auxiliar a conferência da escrituração dos tributos genéricos, disponibilizamos o relatório de conferência de escrituração por documento fiscal (analítico ou sintético), desta forma será possível conferir os valores dos tributos por item ou aglutinado por documento fiscal para os tributos que foram escriturados.
Para processar o relatório basta preencher as perguntas iniciais:
Data Inicial: Indique a data inicial para processamento do relatório
Data Final: Indique a data final para processamento do relatório
Seleciona Filiais: Esta pergunta quais filiais deverão ser consideradas para processamento do relatório, a opção 1-Sim abrir uma tela para selecionar uma ou mais filiais, já opção 2-Não considera somente a filial logada.
Tributo: Neste campo informaremos qual tributo deverá ser processado no relatório. Somente será permitir processar um tributo por relatório.
Opção: Indique a opção do relatório, se deverá ser 1-Analítico ou 2-Sintético.
Confirmando o processamento do relatório, serão listadas as notas que possuírem tributo genérico calculado no período e filial(s) especificado(s), considerando as notas fiscais que gravaram livro fiscal (tabelas SFT/SF3) e a tabela de escrituração do configurador de tributos (CJ3).
Após a conclusão do relatório as informações nas seguintes estrutura para 1-Analítico:
Após a conclusão do relatório as informações nas seguintes estrutura para 2-Sintético:
O objetivo deste relatório é auxiliar a conferência dos valores apresentados na apuração dos tributos genéricos. Para imprimir o relatório basta selecionar a apuração processada, ir em Outras Ações da apuração e selecionar a opção Relatório de Conferência da Apuração, que automaticamente o relatório será impresso.
O relatório tem 5 seções:
Débitos
Créditos
Ajustes
Saldo Credor
Resumo da Apuração
Seção de Débitos
A seção Débitos demonstrará os valores de origem de nota fiscal que geraram débito na apuração, bem como os valores das devoluções, esta seção é detalhada por regra de cálculo do tributo.
Seção de Créditos
A seção Créditos tem o mesmo princípio da seção Débitos, porém aqui será demonstrando os valores dos Créditos e suas devoluções.
Seção de Ajustes
A seção dos ajustes demonstrará os eventuais ajustes manuais de débito e de créditos feitos na apuração dos tributos genéricos.
Exemplos de ajuste de Débito e Crédito respectivamente:
Seção de Saldos
A seção de saldos demonstra o detalhamento dos valores que compõem o saldo credor, exibindo a data de origem do saldo, o valor inicial do saldo no período, o valor utilizado no período e o saldo final do período.
Seção de Resumo
A seção de resumo da apuração demonstrará os totais da apuração:
Para auxiliar na criação e manutenção dos perfis, foram disponibilizados facilitadores no menu Outras Ações -> Facilitador, localizados no cadastro de cada perfil. Através destes facilitadores, é possível efetuar inclusões ou exclusões em lote, sem necessidade de fazê-lo item a item.
O facilitador oferece possibilidade de montar um filtro na tabela de origem, e então realizar a inclusão ou exclusão do resultado deste filtro de uma só vez no(s) perfil(is) selecionado(s).
Para os Perfis Tributários de Produto e de Participantes, quando usado a palavra chave TODOS, englobando todos os produtos, clientes ou fornecedores. Não será possível fazer a manutenção desses registros individualmente, visto que fisicamente não existe o vínculo de cada produto, cliente ou fornecedor nos cadastros existentes.
Nesta etapa deve ser selecionada qual operação será realizada: Inclusão ou Exclusão:
Nesta etapa deve ser selecionado o perfil (ou os perfis) nos quais a inclusão ou exclusão será efetuada:
Nesta etapa deve ser feito o filtro que será aplicado na respectiva tabela para seleção dos registros que serão incluídos ou excluídos do(s) perfil(is) selecionado(s):
Nesta etapa são listados os registros resultantes do filtro aplicado. Os registros que, de fato, devem ser incluídos ou excluídos devem ser selecionados:
Nesta última etapa deve ser efetuada a conferência/confirmação das operações que serão efetuadas:
Ao clicar em confirmar as operações serão efetuadas e os perfis selecionados serão alterados.
Além do facilitador existente no próprio cadastro dos perfis existem, ainda, outras duas formas para vincular produtos, clientes e fornecedores a um ou mais perfis.
Para utilizar esta funcionalidade:
1. Acesse o cadastro em questão.
2. Selecione um registro.
3. Clique em "Alterar" ou "Visualizar"
4. Acesse o menu "Outras Ações -> Perfis Tributários"
Serão listados os perfis nos quais o registro em questão está vinculado:
Através dos botões "Vincular a Outro(s) Perfil(s)" E "Desvincular do Perfil Selecionado" é possível vincular o registro a um ou mais perfis e também desvinculá-lo caso seja necessário.
Além das duas formas citadas anteriormente, também é possível vincular um registro a um ou mais perfis no momento da inclusão. Após a inclusão efetiva do registro, o sistema irá validar se existem um ou mais perfis tributários cadastrados. Se existirem, a seguinte mensagem será exibida:
Ao clicar em sim, serão listados os perfis cadastrados e neste momento o registro já poderá ser vinculado a um ou vários perfis:
...
To support the checking of generic tax calculations, we offer the report of generic taxes per tax document, so you can check tax values per tax document item, regardless of whether the tax generated withholding, payment or verification.
To process the report, just fill in the initial questions:
Start Date: Enter the start date to process the report.
End Date: Enter the end date to process the report.
Select Branches: This asks which branches to use for processing the report. Option 1-Yes opens a screen for selecting one or more branches, whereas option 2-No uses only the logged branch.
Tax: In this field, enter the tax to be processed in the report. You can only process one tax per report.
Once you confirm the report's processing, the invoices that have generic taxes calculated in the specified period and branch(es) are listed, considering invoices from tax records (tables SFT/SF3). After the report is finished, the data on the following structure:
Report Header Section:
Branch = Here the branch of the invoice is stated
Invoice Operation = This field identifies the invoice operation in the following hypotheses:
Tax Rule = This field states the tax rule code.
Rule Description = This field displays the rule description of the tax calculation.
Report Detail Section:
The section is composed of the following columns:
Invoice Number = Number of tax document.
Invoice Series = Series of tax document.
Participant Code = Code of customer/supplier.
Participant Store = Store of customer/supplier.
Date = Date of issue.
Invoice Item = Number of item.
CFOP = CFOP of item.
Measurement Unit = Measurement unit of item.
Calculation Base - Quantity = Calculation base in quantity of generic tax.
Tax Calculation Base = Calculation base of tax.
Tax Rate = Rate of generic tax.
Tax Value = Calculated value of generic tax.
...
To help checking the bookkeeping of generic taxes, we offer the report of bookkeeping checking per tax document (detailed or summary), so you can check the tax values by item or grouped by tax document for the taxes carried.
To process the report, just fill in the initial questions:
Start Date: Enter the start date to process the report.
End Date: Enter the end date to process the report.
Select Branches: This asks which branches to use for processing the report. Option 1-Yes opens a screen for selecting one or more branches, whereas option 2-No uses only the logged branch.
Tax: In this field, enter the tax to be processed in the report. You can only process one tax per report.
Option: Enter the option of the report, whether 1-Detailed or 2-Summary.
Once you confirm the report's processing, the invoices that have generic taxes calculated in the specified period and branch(es) are listed, considering invoices from tax records (tables SFT/SF3) and the bookkeeping table of the tax configurator (CJ3).
After the report is finished, the data on the following structure for 1-Detailed:
After the report is finished, the data on the following structure for 2-Summary:
...
This report supports checking the values displayed on the generic tax verification. To print the report, just select the verification processed, access Other Actions of the verification and select the option Verification Checking Report. The system automatically prints the report.
The report has 5 sections:
Debits
Credits
Adjustments
Credit Balance
Verification Summary
Debits Section
Section Debits states the original invoice values that generated debit in the verification, as well as the return values. This section is detailed by tax calculation rule.
Credits Section
The Credits section has the same principle as the Debits section; however, it states the values of Credits and their returns.
Adjustments Section
The Adjustments section states occasional manual adjustments of debit and credit done in the generic taxes verification.
Examples of Debit and Credit adjustments, respectively:
Balances Section
The balances section states the value details that compose the credit balance, displaying the start date of the balance, the initial value of the balance in the period, the value used in the period and the final balance of the period.
Summary Section
The summary section of the verification states the verification totals:
...
To support the creation and maintenance of profiles, we offer facilitators in menu Other Actions -> Facilitator, found in the register of each profile. You can use these facilitators to add or delete batches, with no need to do it item by item.
The facilitator enables the assembly of filters in the source table, then the addition or deletion of filter results all at once in the profile(s) selected.
For Participant and Product Tax Profiles, when the key word ALL is used, encompassing all products, customers or suppliers. You cannot perform maintenance on these records individually, given that the existing registers lack a physical link to each product, customer or supplier.
On this stage, select the operation to be executed: Addition or Deletion:
On this stage, select the profile (or profiles) in which the addition or deletion will be performed:
On this stage, create the filter to be applied to the respective table, for selecting the records to be added or deleted from the profile(s) selected:
On this stage, list the records that result from the filter applied. Select the records that must actually be added or deleted:
In this last stage, check/confirm the operations to be executed:
Click Confirm to execute the operations and change the profiles selected.
...
Besides the facilitator found in the profile register itself, there are also two other ways to link products, customers and suppliers to one or more profiles.
To use this feature:
The profiles to which the record at issue is linked are listed:
Through buttons "Link to Other Profile(s)" AND "Unlink from the Profile Selected", you can link the record to one or more profiles and also unlink it when needed.
...
Beside the two aforementioned methods, you can also link a record to one or more profiles when adding the record. After you have effectively added the record, the system validates whether one or more tax profiles have been added. If any, the following message is displayed:
Click Yes to list the profiles registered. At this point you can already link the record to one or to several profiles:
| Dica | ||
|---|---|---|
| ||
This feature is controlled by parameter | ||
| Dica | ||
| ||
Esta funcionalidade é controlada pelo parâmetro MV_FACAUTO (Default = .F.). Se o parâmetro for configurado como If the parameter is set to .F. então a mensagem não será exibida e o registro deverá ser vinculado aos perfis, se necessário, utilizando-se qualquer uma das outras formas mencionadas. |
, then the message is not displayed and you must link the record to the profiles using any of the other methods mentioned, if needed. |
...
If the customer needs the history of changes for some configurator routines, they can find a feature that will help them with this information in Other Actions > History of ChangesCaso seja necessário obter o histórico de alteração de algumas rotinas do configurador foi criado dentro de Outras Ações > Histórico de Alterações uma funcionalidade para auxiliar o cliente com essas informações.
...
In the registers of Calculation Base Rule Nos cadastros de Regra de Base de Cálculo (FISA161), Regra de Alíquota Rate Rule (FISA162) e Regra de Cálculo - Documentos Fiscais and Calculation Rule - Tax Documents (FISA160) foi disponibilizada uma nova aba com a fórmula do cálculo que o Protheus irá interpretar, we offer a new tab with the calculation formula that Protheus will interpret.
Nessa nova aba será possível editar a formula clicando apenas no botão Editar Fórmula, ao clicar no botão é liberado os seguintes campo:
Próximo passo é selecionar o tipo da regra a ser consultada:
São criados automaticamente pelo sistema.
O Valor de Origem são valores que o Protheus já conhece e já foi calculado no momento da execução da fórmula, esses valores podem ser Valor da Mercadoria, Quantidade, Valor Contábil, Valor zero de base de cálculo ou alíquota, entre outros.
Exemplo:
Problema - Configurar uma alíquota com valor zero
Criarei uma nova Regra de Alíquota, selecionarei o Valor Origem = 06 - Fórmula Manual, na fórmula faço o seguinte passo:
...
In this new tab, just click the Edit Formula button to edit the formula, activating the following field:
The next step is to select the rule type to be queried:
The system creates them automatically.
Protheus already knows the Origin Value, having already calculated it on formula execution. This value can be the Value of Goods, Quantity, Accounting Value, Zero value of Calculation Base or Rate, etc.
Example:
Problem - Configure a rate with value zero
I will create a new Rate Rule and set the Origin Value = 06 - Manual Formula, taking the following step in the formula:
Select this option to enable the field Rule Query and select a Calculation Base Rule from the system. Thus, you can add another procedure to the formula, for the calculation base rule set in the system in any register with the Calculation Formula Details tab.
Example:
Problem - I need my calculation base to be the Value of Goods + BRL 100.00
In the system, I already have the Calculation Base Rule RB0001 selected in field Origin Value = 01- Value of Goods.
I will create a new Base Rule and set the Origin Value = 11 - Manual Formula, taking the following step in the formula:
Select this option to enable the field Rule Query and select a Rate Rule from the system. Thus, you can add another procedure to the formula, for the rate rule set in the system in any register with the Calculation Formula Details tab.
It is used the same way as the Calculation Base Rule.
Select this option to enable the field Rule Query and select a Tax Reference Unit from the system. Thus, you can add the URF procedure to the formula in any register, or even to the rate, without selecting the Origin Value - 05 - Tax Reference Unit (URF).
Select the URF register and choose the operation, whether to add, subtract, multiply or divide the value. Click the operator button, then add the value. If you want to leave only the fixed value in the formula, click Clear and add the value.
Use this binding to use a property from a tax in another tax.
Select this option to enable the field Tax to filter the query and the field Rule Query.
Field Tax to filter the query displays the taxes registered in the system. This field is useful for filtering the query of field Rule Query.
Field Rule Query displays some tax variations, such as
Ao selecionar essa opção é habilitado o campo Consulta de Regras, com isso é possível selecionar alguma Regra de Base de Cálculo que exista no sistema. Assim você poderá adicionar na fórmula outro tratamento de uma regra de base de cálculo configurada no sistema em qualquer cadastro que possua a aba de Detalhamento da Fórmula de Cálculo.
Exemplo:
Problema - Preciso que minha base de cálculo seja Valor da Mercadoria + R$100,00 reais
No sistema já possuo a Regra de Base de cálculo RB0001 que está selecionado no campo Valor Origem = 01- Valor da Mercadoria.
Criarei uma nova Regra de Base, selecionarei o Valor Origem = 11 - Fórmula Manual, na fórmula faço o seguinte passo:
...
Ao selecionar essa opção é habilitado o campo Consulta de Regras, com isso é possível selecionar alguma Regra de Alíquota que exista no sistema. Assim você poderá adicionar na fórmula outro tratamento de uma regra de alíquota configurada no sistema em qualquer cadastro que possua a aba de Detalhamento da Fórmula de Cálculo.
A forma de utilizar é a mesma da Regra de Base de Cálculo.
...
Ao selecionar essa opção é habilitado o campo Consulta de Regras, com isso é possível selecionar alguma Regra de Unidade Referência Fiscal que exista no sistema. Assim você poderá adicionar na fórmula o tratamento da URF em qualquer cadastro ou até mesmo na alíquota sem selecionar o Valor Origem - 05 - Unidade de Referência Fiscal (URF).
Selecione o cadastro da URF e escolha a ação que deseja fazer com o valor, caso o valor deva ser somado, subtraído, multiplicado, dividido, clicar no botão do operador e depois adicione o valor. Caso queira deixar apenas o valor fixo na fórmula, é preciso clicar no botão Limpar e depois adicionar o valor.
...
Utilizar essa amarração quando desejar utilizar uma propriedade de um tributo em outro tributo.
Ao selecionar essa opção é habilitada o campo Tributo para filtrar a consulta e o campo Consulta de Regras.
Campo Tributo para filtrar a consulta irá mostrar tributos cadastrados no sistema, esse campo serve para filtrar a consulta do campo Consulta de Regras.
Campo Consulta de Regras irá mostrar algumas variações do tributo, como:
...
The system creates them automatically.
We have created the calculation index for operations that require a specific procedure, so Protheus can manage to identify that the formula may contain a service rate, a deduction for dependents, an NCM (Tax Reference Unit) rule (MVA, Base Value, Increase) previously registered in the earlier stages of the tax configurator.
Example:
Problem - Configure a service rate for my generic tax
I will create a new Rate Rule and set the Origin Value = 06 - Manual Formula, taking the following step in the formula:
São criados automaticamente pelo sistema.
Foi criado o Índice de cálculo para operações que necessitam de tratamento específico, pois dessa forma o Protheus conseguirá identificar que aquela fórmula poderá conter uma alíquota de serviço, uma dedução por dependentes, uma regra de NCM (MVA, Pauta, Majoração) previamente cadastrada nas etapas anteriores do configurador de tributos.
Exemplo:
Problema - Configurar uma alíquota de serviço para meu tributo genérico
Criarei uma nova Regra de Alíquota, selecionarei o Valor Origem = 06 - Fórmula Manual, na fórmula faço o seguinte passo:
...
Select this option to enable the field Value to be added to formula, so you can add a fixed value for the calculation base rule, rate or even for the Calculation Rule of the tax.
Enter the value desired and choose the operation, whether to add, subtract, multiply or divide the value. Click the operator button, then add the value. If you want to leave only the fixed value in the formula, click Clear and add the value.
...
In this session, we show what the ICMS verification looks like when there are legacy entry codes (TIO) x Tax Configurator.
Example of an incoming invoice:
Example of an outgoing invoice:
Screen with verification of Local ICMS:
The system begins to perceive whether the entry originates in the configurator.
Given the same entry code and legacy as well as tax configurator both use them, the behavior is the same:
See code "SP100090748"
This behavior expands other verification tabs
Ao selecionar essa opção é habilitado o campo Valor a ser adicionado na fórmula, com isso é possível informar um valor fixo para a regra de base de cálculo, alíquota ou até mesmo a Regra de Cálculo do tributo.
Preencha com o valor desejado e escolha a ação que deseja fazer com o valor, caso o valor deva ser somado, subtraído, multiplicado, dividido, clicar no botão do operador e depois adicione o valor. Caso queira deixar apenas o valor fixo na fórmula, é preciso clicar no botão Limpar e depois adicionar o valor.
Nessa sessão será mostrado como ficará a apuração do ICMS quando houver códigos de lançamentos do legado (TES) x Configurador de Tributos.
Exemplo de uma NF de entrada:
Exemplo de um NF de Saída:
Tela com apuração do ICMS Próprio:
O sistema passa a distinguir se a origem do lançamento é do configurador.
Caso tenha o mesmo código de lançamento e eles sejam utilizados tanto pelo legado quanto pelo configurador de tributos, o comportamento é o mesmo:
Vide o código "SP100090748"
Esse comportamento se expande as outras abas de apuração.
ICMS-ST
DIFAL
Débitos Especiais
Special Debits
Crédito Extra Credit - ApuraçãoVerification
Em todos os cenários acima foi necessário criar uma regra de ajuste de lançamento no configurador de tributos, nas quais serão detalhadas na pasta de documentação "Cálculos do Configurador de Tributos"
...
In every scenario above, we had to create an entry adjustment rule in the tax configurator. Access the documentation folder "Tax Configuration Calculation" for details.
Nesta seção será mostrado como fica o arquivo do SPED com relação as mensagens cadastradas na rotina de Regra de Ajuste Lançamento do configurador de tributos.
Na ilustração abaixo é feito a amarração das mensagens com uma regra de ajuste.
Ao gerar os movimentos de Entrada ou Saída de nota, o sistema vai armazenar os registros na tabela CDA e as mensagens decodificadas na tabela CJL, na qual serão amarrados com uma ID.
Obs.: A parte abaixo será de teor técnico e foge um pouco da experiência do usuário, todavia é necessário para entendimento do fluxo da rotina.
This section shows how the SPED file relates to the messages registered in routine Entry Adjustment Rule of the tax configurator.
In the illustration below, the binding of messages to an adjustment rule is executed.
When you generate invoice Inflow or Outflow transactions, the system stores the records to table CDA and the decoded messages in table CJL, in which they are bound to an ID.
Note: The section below is technical and diverges from user experience, though it is necessary for comprehension of routine flow.
Table CDA - Adjustment Code EntriesTabela CDA - Lançamentos de Código de Ajuste:
Tabela Table CJL - Controle de Mensagens Decodificadas:Decoded Message Control:
To put it simply, I took only one of the IDs related to code SP40090227 of item 1 or the invoicePara simplificar peguei somente uma das ID's referente ao código SP40090227 do item 1 da NF.
Obs.Note: O campo Field CJL_INDICE determina para qual bloco a mensagem deverá ser direcionada.determines to which block the message must be directed.
After processing the monthly verifications, find below an example of how the Após o processamento das apurações mensais, abaixo um exemplo de como fica o arquivo da EFD ICMS/IPI file looks:
Com a disponibilização do configurador de tributos, alguns tributos calculados com configuração legado(cadastro de produto, exceção fiscal, UFxUF, cadastro de TES etc) poderão ser configurados e gerenciados também por meio do configurador de tributos.
Abaixo a lista com os tributos calculados atualmente pelo sistema que estão disponíveis no configurador:
You can also use the tax configurator to configure and manage some taxes calculated with legacy settings (product register, tax exception, StateXState, TIO register, etc.).
See below a list of the taxes currently calculated by the system, which are available in the configurator:
Tax | Description | ||
AFRMM | Additional Freight for Merchant Marine Modernization | ||
FABOV | Beef Cattle Breeding Support Fund | ||
FACS | Soybean Cultivation Support Fund | ||
FAMAD | Timber Support Fund | ||
FASE/MT | Mato-Grossense Seed Cultivation Support Fund | ||
FETHAB | State Fund for Transport and Housing | ||
FUNDERSUL | Development Fund for the Road System of the State of Mato Grosso do Sul | ||
FUNDESA | Animal Health Protection Development Fund | ||
IMA/MT | Mato-Grossense Cotton Institute | ||
SEST/SENAT | Transport Social Service/Transport Learning National Service | ||
TPDP | Public Spending Processing Fee for the State of Paraiba | ||
SENAR | Rural Learning National Service | ||
PIS | Social Integration Program | ||
COF | Contribution to the Financing of the Social Security | ||
II | Import Tax | ||
IRF | Withheld Income Tax | ||
INSS | National Institute of Social Security | ||
ISS | Service Tax | ||
ICMS | Tax on Circulation of Goods and Services | ||
IPI | Tax on Industrialized Products | ||
CIDE | Contribution for Intervention in the Economic Domain | ||
CPRB | Social Security Contribution on Gross Revenue | ||
FEEF | Fiscal Balance State Fund | ||
CSL | Social Contribution on Net Profit | ||
PROTEG | Social Protection Fund of the State of Goias | ||
FUMIPQ | Municipal Stimulus Fund for Micro and Small Businesses | ||
CRDPRE | Presumed Credit for ICMS | ||
CRPRST | Presumed Credit on Rendering of Transport Services with | ||
| Tributo | Descrição | ||
|---|---|---|---|
| AFRMM | Adicional do Frete para Renovação da Marinha Mercante | ||
| FABOV | Fundo de Apoio a Bovinocultura de Corte | ||
FACS | Fundo de Apoio à Cultura da Soja | ||
FAMAD | Fundo de Apoio à Madeira | ||
FASE/MT | Fundo Mato-Grossense de Apoio à Cultura da Semente | ||
FETHAB | Fundo Estadual de Transporte e Habitação | ||
FUNDERSUL | Fundo de Desenvolvimento do Sistema Rodoviário do Estado de Mato Grosso do Sul | ||
FUNDESA | Fundo de Desenvolvimento e Defesa Sanitária Animal | ||
IMA/MT | Instituto Mato-Grossense do Algodão | ||
SEST/SENAT | Serviço Social do Transporte/Serviço Nacional de Aprendizagem do Transporte | ||
TPDP | Taxa de Processamento de Despesa Pública do Estado da Paraíba | ||
| SENAR | Serviço Nacional de Aprendizagem Rural | ||
| PIS | Programa de Integração Social | ||
| COF | Contribuição para Financiamento da Seguridade Social | ||
| II | Imposto de Importação | ||
| IRF | Imposto de Renda Retido na Fonte | ||
| INSS | Instituto Nacional do Seguro Social | ||
| ISS | Imposto Sobre Serviço | ||
| ICMS | Imposto sobre Circulação de Mercadorias e Serviços | ||
| IPI | Imposto sobre Produtos Industrializados | ||
| CIDE | Contribuição de Intervenção no Domínio Econômico | ||
| CPRB | Contribuição Previdenciária Sobre a Receita Bruta | ||
| FEEF | Fundo Estadual de Equilíbrio Fiscal | ||
| CSL | Contribuição Social Sobre o Lucro Líquido | ||
| PROTEG | Fundo de Proteção Social do Estado de Goiás | ||
| FUMIPQ | Fundo Municipal de Fomento à Micro e Pequena Empresa | ||
| CRDPRE | Crédito Presumido para ICMS | ||
| CRPRST | Crédito Presumido Sobre Prestação Serviço de Transporte comICMS/ST | ||
CPPROD | PRODEPE - | Programa de Desenvolvimento do Estado de PernambucoState of Pernambuco Development Program | |
CRDPCT | Crédito Presumido Pela Carga TributáriaPresumed Credit by Tax Load | ||
SECP15 | Aposentadoria Especial Special Retirement 15 | anosyears | |
SECP20 | Aposentadoria Especial Special Retirement 20 | anosyears | |
SECP25 | Aposentadoria Especial Special Retirement 25 | anosyears | |
INSSPT | Employer INSS | Patronal||
DIFAL | Diferencial de AlíquotaRate Differential | ||
CMP | Complementary ICMS | Complementar||
ANTEC | Antecipação de ICMS Advance | ||
FECPIC | FECP ICMS | ||
FCPST | FECP ICMS ST | ||
FCPCMP | Complementary ICMS FECP | ICMS Complementar||
COFRET | COFINS | RetençãoWithholding | |
COFST | COFINS Substituição TributariaCOFINS Tax Replacement | ||
PISRET | PIS | RetençãoWithholding | |
PISST | PIS | Substituição TributariaTax Replacement | |
ISSBI | ISS | Bi Tributado Double Taxation - CPOM | |
PISMAJ | Majoração das Alíquota do PIS ImportaçãoImport PIS Rate Increase | ||
COFMAJ | Majoração das Alíquota do COFINS ImportaçãoImport COFINS Rate Increase | ||
DED | Dedução ISS / ICMS | / ISSDeduction | |
FRTAUT | Frete AutônomoAutonomous Freight | ||
DZFICM | Desoneração de ICMS por Isenção de Imposto para Zona Franca de ManausICMS Tax Exemption for Manaus Free Trade Zone | ||
DZFPIS | Desoneração de PIS por Isenção de Imposto para Zona Franca de ManausPIS Tax Exemption for Manaus Free Trade Zone | ||
DZFCOF | Desoneração de COFINS por Isenção de Imposto para Zona Franca de Manaus | COFINS Tax Exemption for Manaus Free Trade Zone | |
ESTICM | Credit and Debit Reversal in ICMS Verification | ESTICM | Estorno do Crédito e Débito na Apuração de ICMS|
ICMSST | ICMS | Substituição TributáriaTax Replacement | |
FRTEMB | Frete EmbarcadorFreight Shipment | ||
CRDOUT | Crédito Outorgado |
Caso o mesmo tributo seja configurado para ser calculado através dos cadastros legado e também no configurador, as regras do configurador terão maior prioridade. De qualquer forma é interessante desabilitar o calculo dos tributos legado uma vez que este esteja cadastrado no configurador de tributos.
Conforme a evolução do configurador, esta lista de tributos aumentará, e mais tributos legado poderão ser cadastrados aqui no configurador de tributos.
Principais rotinas do configurador de tributos genéricos:
...
Granted Credit |
If the same credit is configured to be calculated through legacy registers and also in configurator, the configurator rules have higher priority. Anyways, disabling the legacy tax calculation makes sense, once it is registered in the tax configurator.
As the configurator evolves, this list of taxes will increase, and you will be able to register more legacy taxes in the taxes configurator.
...
Main routines of generic tax configurator:
Routine | Description |
Tax | FISA168.PRW |
Tax Ref. Unit | FISA167.PRW |
Progressive Table Rule | FISA160A.PRW |
Rules per NCM | FISA160B.PRW |
Rules by Dependents | FISA160C.PRW |
Service Provision Code Rules | FISA160D.PRW |
Tax Status Code | FISA160I.PRW |
Bookkeeping Form | FISA160L.PRW |
Revenue Code | FISA160M.PRW |
FCA Economic Indicators | FISA121.PRW |
Product Profile | FISA166.PRW |
Operation Profile | FISA165.PRW |
Participant Profile | FISA164.PRW |
Origin/Destination Profile | FISA163.PRW |
Calculation Base Rule | FISA161.PRW |
Rate Rule | FISA162.PRW |
Bookkeeping Rule | FISA160J.PRW |
Calculation Rule - Tax Documents | FISA160.PRW |
Message Register | FISA178.PRW |
Entry Adjustment Rule | FISA181.PRW |
Verification Bill Rule | FISA176.PRW |
Verification Rule | FISA169.PRW |
Generic Taxes Verification | FISA173.PRW |
Report of Generic Taxes per Tax Document | FISR160.PRW |
Bookkeeping Checking Report | FISR160A.PRW |
Verification Checking Report | FISR161.PRW |
Main tables of generic tax configurator:
Table | Description |
F20 | Tax Profiles |
Principais tabelas do configurador de tributos genéricos:
|
F21 |
Orig./Dest. |
Tax Profile |
F22 |
Participant Tax Profile |
F23 |
Operation Tax Profile |
F24 |
Product Tax Profile |
F25 |
Origin x |
Product Profile |
F26 |
Operation Type Profile |
F27 |
Calculation Base |
Rule |
F28 |
Rate Rule |
F29 |
Tax Reference Unit |
F2A |
URF Values |
F2B |
Tax Rule |
F2C |
From/ |
To Taxes |
F2D |
Calculated Generic Taxes |
F2E |
Tax Register |
F2F |
Tax Bills x Invoice |
F2G |
Verification Rule |
F2H |
Generic Tax Verification |
F2I |
Generic Tax Verification Balances |
F2J |
Verification Summary by Rule |
F2K |
Gen Tax Detailed Summary |
F2L |
Gen. |
Tax Verification Bills |
F2M |
Gen. Tax Verification Adjustments |
F2N |
Verification Bill Rules |
CIQ |
Progressive Table |
CIR |
Progressive Table Items |
CIS |
NCM Rule Header |
CIT |
Tax x |
Rule |
CIU |
Additional Tax Rule by NCM |
CIV |
Rule by Dependents |
CIX |
ISS Rule Header |
CIY |
ISS Rate by City | |
CJ0 | CST - |
Header | |
CJ1 | CST - Item |
CJ2 |
Bookkeeping Rule |
CJ3 |
Bookkeeping by Item |
CJ4 |
Tax Payment Form Rule |
CJ5 |
Revenue Code Rule |
CJ6 |
Revenue Code by State |
CJ7 |
Revenue Code Doc Template |
CJ8 |
Message Register |
CJ9 |
Entry Adjustment Rule Header |
CJA |
Items - Entry Adjustment Rule |
CJL |
Decoded Messages Control |
| Aviso | ||
|---|---|---|
| ||
O compartilhamento das tabelas eventualmente poderá ser alterado se necessário, para melhor atender as configurações das regras dos tributos. As únicas tabelas que não poderão ter o modo de compartilhamento alterado são as tabelas You can change table sharing if you need, to better meet tax rule settings. The only tables the sharing of which cannot be changed are F2D, F2F, F2H, F2I, F2J, F2K, F2L e and F2M. |
Os valores dos tributos poderão ser contabilizados de duas formas, no processamento da apuração e no contabilização do documento fiscal.
Para contabilizar o tributo na apuração, foram criados dois novos códigos de lançamento padrão, 767 para inclusão e 768 para exclusão/estorno, quando estes lançamentos padrão são executados, o título gerado do tributo com valor a pagar estará devidamente posicionado.
...
There are two ways to book tax values, when processing the verification and when booking the tax document.
To book the tax in the verification, we have created two new standard entry codes: 767 for addition and 768 for deletion/reversal. When you execute these standard entries, the tax bill generated with a value payable will be duly selected.
To book the tax in the tax document, there is no need to create any standard entry code. The same already existing codes are used for invoice booking, in which case the tax values become available in table F2D (Calculated Generic Taxes), which are linked to the tax document through fields D1_IDTRIB and D2_IDTRIB. In this case, we must emphasize that there may be more than one tax calculated by tax document item, so there may be more than one transaction in tables F2D for the tax document item Já para contabilizar o tributo no documento fiscal, não foi necessário criado nenhum código de lançamento padrão, serão utilizados os mesmo códigos já existentes para contabilização da nota fiscal, e neste caso os valores dos tributos estarão disponíveis na tabela F2D(Tributos Genéricos Calculados), que são vinculados com o documento fiscal por meio dos campos D1_IDTRIB e D2_IDTRIB. Neste caso é importante ressaltar que pode haver mais de um tributo calculado por item de documento fiscal, então poderá haver mais de uma movimentação na tabela F2D para o item de documento fiscal (SD1, SD2).
...
...
...
Use the tax configurator when you need to calculate, collect or verify a specific tax, such as the various existing state fundsO configurador de tributos deverá ser utilizado nas situações que houver necessidade de calcular, recolher ou apurar determinado tributo, por exemplo os diversos fundos estaduais existentes, ICMS, IPI, ISS, entre outros. Ao configurar um tributo legado, como o ICMS, no configurador e possuir a configuração do tributo no TES o configurador irá sobrescrever as configurações do legado no momento do cálculo do imposto ou escrituração.
Neste caso o sistema não atende o requisito mínimo, que é estar atualizado pelo menos com o release 12.1.23, o sistema precisa ser atualizado para ter esta funcionalidade disponível.
Neste caso deverá ser aberto um ticket no suporte técnico, explicando a necessidade de configuração, com embasamento legal, para que seja analisada a possibilidade de disponibilizar novas opções de configuração.
Para que um tributo seja listado na apuração pelo menos uma de suas variações (regra de cálculo) deve possuir uma regra de apuração vinculada.
Não há necessidade de alterar nada nas movimentações. Basta vincular uma regra de apuração em uma ou mais regras de cálculo e processar a apuração novamente.
Sim existe, para esta tarefa existem os facilitadores dos perfis de Participante, Produtos, Operações e UF Origem/Destino.
Os facilitadores fornecem mecanismos de filtros, para que as inclusões ou exclusões sejam realizadas em lote, pois dependendo da quantidade de registros seria uma tarefa inviável de ser realizada manualmente. Os facilitadores estão disponíveis no próprio cadastros de perfis.
Sim existe, para gerar o título neste contexto, no módulo SIGAFAT (Faturamento), na geração do Documento de Saída, será apresentada a tela de parâmetros. Ajuste a pergunta: Gera Tit FUNRURAL/Conf Trib ? com a opção Sim. Desta forma os tributos calculados que possuírem regra financeira vinculada poderão ter os títulos gerados.
etc. When you configure a legacy tax, such as ICMS, in the configurator, and you have the configuration of the tax in TIO, the configurator overwrites the legacy configurations at the time of bookkeeping or tax calculation.
In this case, the system does not meet the minimum requirements. You should at least update the system to release 12.1.23 to obtain this feature.
In this case, open a ticket to technical support explaining the need for configuration, with legal basis, so they may analyze the feasibility of making new configuration options available.
To list a tax on the verification, at least one of its variations (calculation rule) must have a linked verification rule.
There is no need to change anything in the transactions. Just link a verification rule to one or more calculation rules and process the verification again.
Yes, there is! This task has facilitators for Participant, Products, Operations and Origin/Destination State profiles.
The facilitators provide filter mechanisms for batch additions and deletions, as a great quantity of records would make the manual performance of this task unfeasible. The facilitators are available in the profile register itself.
Yes, there is. To generate the bill in this context, in module SIGAFAT (Billing), the parameters screen is displayed when you generate the Outgoing Document. Adjust the question: Generate FUNRURAL Bill/Tax Conf? with option Yes. Thus, the calculated taxes that have a linked financial rule can read the generated bills.
To correctly configure the Manaus Free Trade Zone discount in the configurator, create a generic TIO (ICMS Calc. = No and IPI Calc. = No) and fully configure the Base, Rate and Calculation Rule in the configurator. Another alternative is to use 06 - Origin ICMS Base in the calculation base profile of the configuratorPara configurar corretamente o o desconto da Zona Franca de Manaus no configurador deve-se criar uma TES genérica (Calc. ICMS = Não e Calc. IPI = Não) e fazer toda a configuração de Base, Alíquota e Regra de calculo no configurador. Outra alternativa é utilizar no perfil de base de calculo do configurador 06 - Base ICMS origem.
