DUIMP attributes: LFAA launches an NCM data preparation tool

Brazil’s transition to the New Import Process is changing how goods are described and identified before government agencies. Under the previous model, much information appeared in free descriptions, highlights and specific forms. The Product Catalog, DUIMP and LPCO increasingly request it as structured data.

LFAA provides an NCM attribute consultation tool at lfaa.com.br/atributos. It displays attributes associated with an eight-digit NCM, organizes collection of product and transaction data and exports a record for review.

What attributes are

According to Brazil’s Single Window, attributes are specific pieces of information provided in a structured, itemized form for each NCM code. They can be used in the Product Catalog, DUIMP and Licenses, Permits, Certificates and Other Documents — LPCO.

Their purpose is to improve identification for customs, administrative, statistical, tax and valuation controls. Depending on the product, they may request material, composition, application, operation, dimensions, capacity, model or other technical characteristics. These details are not always present on the invoice, packing list or commercial catalog.

The cost of discovering information too late

If a mandatory attribute is found only while preparing the DUIMP, the importer may need to return to the manufacturer or supplier. When production or transit has begun, there is less room to correct the information.

• delayed Product Catalog preparation
• revision of the goods description
• differences between commercial documents and structured data
• difficulty answering technical attributes
• late identification of possible administrative controls

How the LFAA tool works

The application separates CATP/Product attributes, which describe and register the product, from DUIMP/Transaction attributes, which relate to the specific import operation. Users can associate the part number and complete description with the consultation.

Visual status distinguishes completed, pending-confirmation and missing information. The record can be exported as PDF or JSON to support internal review and requests to suppliers.

The database reference matters

The application identifies the reference date and environment of the data consulted. LFAA’s embedded production database is updated on Monday mornings, and users may load a JSON file obtained directly from the official source.

The Single Window replaces its official XML and JSON files daily to reflect changes in links between attributes and NCM codes. Training data may also include attributes still under construction. A saved record is therefore a snapshot of the database used, not a permanent list.

What the tool does not replace

Consulting attributes does not confirm tariff classification. An incorrect NCM may show a plausible list linked to the wrong classification. The tool also does not automatically determine whether an LPCO is required, which agency is responsible, whether a tax or tariff benefit applies, or which tax treatment should be adopted.

LPCO analysis remains tied to the official administrative-treatment simulator and the actual characteristics of the goods and transaction. Classification, attributes, administrative treatment and taxation are connected but are not equivalent.

Human analysis remains essential

The main risk is turning a consultation tool into an automatic decision mechanism. The presence of an attribute alone does not prove that a control applies, and its absence does not remove the need to review legislation, description and intended use.

Used correctly, the records can improve product-data governance by revealing information to request from suppliers, gaps in the ERP, incomplete registrations, differences among part number, description and NCM, and internal responsibility for validation. The tool directs technical analysis; it does not eliminate it.