Skip to content
Light
English

Tax reform - Integration layout

This documentation gathers the proposed contract for integrating CBS, IBS, and IS rules and amounts. Each table has its field list, send order, links, and examples.

Table Content Direction
42 - Tax configuration Existing configuration, with two new rule links. ERP → Demander.
42-1 - TributacaoRegraConsumo Calculation mode and CBS and IBS reductions. ERP → Demander.
42-2 - TributacaoAliquotaCBS Standard rate by effective period. ERP → Demander.
42-3 - TributacaoAliquotaIBS State and municipal rates by destination and effective period. ERP → Demander.
42-4 - TributacaoRegraEspecifica Amounts per taxable unit. ERP → Demander.
42-5 - TributacaoRegraIS IS method and parameters. ERP → Demander.
16 - Order Monetary totals of the order taxes. ERP ↔ Demander.
17 - Order item Monetary amounts of the taxes on each item. ERP ↔ Demander.

The identifiers 42-1 through 42-5 represent distinct tables. They are not child rows of the immediately preceding record. Amounts are returned to the ERP in tables 16 and 17; that return is not an export of records 42-1 through 42-5.

  • Field separator: |.
  • Example dates: AAAA-MM-DD.
  • Example decimals: a period as the decimal separator.
  • Reference codes: sent by the ERP and resolved within the authorized company.
  • Empty field: does not automatically equal zero. The final policy must be stated in the validation.
  • Identifier: first position of the record.
  • Existing columns of tables 42, 16, and 17: keep their order. Extensions must not shift legacy fields without adapting the importer and the exporter.

The examples are fictitious. Sizes and versions that have not been defined yet must not be inferred from the values used in the examples.

  1. Send the parameters: 42-2, 42-3, 42-4, and 42-5.
  2. Send the consumption rules: 42-1.
  3. Send the tax configurations: 42, with the codes of the matching rules.
  4. Validate references, company, units, and effective periods before making the set available to the app.

Consistent batch processing is a proposal still to be implemented. Sending records in a given sequence does not prove that the current importer publishes them atomically.

Field or context Target
42.codRegraTributariaConsumo 42-1.codigo.
42.codRegraImpostoSeletivo 42-5.codigo, when applicable.
42-1.codRegimeEspecifico 42-4.codigo, on the specific path shown.
Company and fiscal date CBS rate in effect in table 42-2.
Company, UF, city, and fiscal date IBS rates in effect in table 42-3.

Table 42-1 has no classificacaoTributaria column. The reduction percentages are percReducaoCBS and percReducaoIBS. In table 42-3, the municipality field is named codCidade and represents the IBGE code.

Add the same block to tables 16 and 17, in this order, both when receiving data from the ERP and when sending data to the ERP:

Order in the new block Field Content
1 valorCBS Monetary amount of CBS.
2 valorIBSEstadual Monetary amount of the state component of IBS.
3 valorIBSMunicipal Monetary amount of the municipal component of IBS.
4 valorIS Monetary amount of IS.

On the item, the amounts are totals for the item quantity, not unit amounts. On the order, each field totals the same component across the items. Numbers 1 through 4 are the order inside the additional block, not the absolute positions in the records.

The extensions are detailed in the articles for table 16 and table 17.