Table 42-4 - TributacaoRegraEspecifica
The TributacaoRegraEspecifica table uses the identifier 42-4. It receives from the ERP the monetary parameters per taxable unit used on the specific path shown.
Direction: ERP → Demander (import only).
Layout fields
Section titled “Layout fields”| Order | Field description | Format and size | Required | Version | Note |
|---|---|---|---|---|---|
| 1 | IDENTIFICADOR |
FIXO=42-4 (4) | Yes | To be defined | Fixed identifier of this table: 42-4. |
| 2 | codigo |
Text (size to be defined) | To be defined | To be defined | Specific parameter code in the ERP. |
| 3 | descricao |
Text (size to be defined) | To be defined | To be defined | Description of the treatment. |
| 4 | inicioVigencia |
Date (AAAA-MM-DD) | To be defined | To be defined | Start date of application. |
| 5 | fimVigencia |
Date (AAAA-MM-DD) | To be defined | To be defined | End date of application. |
| 6 | unidade |
Text (size to be defined) | To be defined | To be defined | Taxable unit. Teaching example: L. The set of units must be validated. |
| 7 | valorCBSUnidade |
Decimal (precision to be defined) | To be defined | To be defined | Monetary amount of CBS per taxable unit. |
| 8 | valorIBSUnidade |
Decimal (precision to be defined) | To be defined | To be defined | Aggregate monetary amount of IBS per taxable unit. |
Integration rules
Section titled “Integration rules”- Codes sent by the ERP are resolved in the context of the company authorized for the integration.
- The
|character separates the fields. The examples keep the separator after the last field. - Numeric values in the examples are fictitious and use a period as the decimal separator.
- The contract for resending, deletion, and update by effective period must be validated. Do not assume deletion because a record is missing from an incremental send.
Link and taxable quantity
Section titled “Link and taxable quantity”- Table 42-1 references
42-4.codigothroughcodRegimeEspecifico. - The quantity must be in the taxable unit, with a validated conversion factor when it differs from the commercial unit.
- In the example, each code identifies one version of the parameter. A new version uses a new code and a controlled update of the link. The final strategy depends on validation.
- Do not apply the standard percentage calculation of the same taxes again when the specific treatment replaces it.
- The field
valorIBSUnidadeis an aggregate. The split betweenvalorIBSEstadualandvalorIBSMunicipalon order and item records remains pending. Do not infer that split from the percentages in table 42-3. - Whether the tax applies depends on the operation validated by the ERP. The presence of the parameter does not create a new charge on every resale.
Record examples
Section titled “Record examples”42-4|E1|Gasolina demonstrativa|2033-01-01|2033-12-31|L|0.90|1.70|