Siscomex and Portal Unico integration explained

What the integration actually connects

For importers in Brazil, two systems sit at the center of every operation. Siscomex records trade declarations and controls the flow of an import or export. The Portal Unico de Comercio Exterior is the single window that ties customs together with the other government agencies, tax debit, and administrative control.

The word "integration" gets used loosely, so it helps to be precise. When people say Siscomex and Portal Unico integration, they usually mean one of two things:

• Government side: how the trade system talks to the single window, LPCO, and the tax modules behind the scenes.
• Company side: how your own ERP, spreadsheets, and documents feed data into those systems without a person retyping it.

Kadmoon works on the second one. The government plumbing already exists. The manual work sits between your data and the fields the Portal Unico expects.

The data that has to line up

A DUIMP pulls from several sources at once. Each source is owned by a different team, which is why mismatches are so common.

| Data block | Usual source | Common failure | |------------|--------------|----------------| | Product attributes | Product Catalog | Missing or wrong NCM attributes | | Commercial values | Invoice and PO | FOB value in the wrong currency | | Freight and insurance | Forwarder | Estimated figures never updated | | Administrative control | LPCO | License found only after arrival | | Tax calculation | Fiscal team | Wrong tax base for ICMS |

When these blocks are keyed by hand into the Portal Unico, one transposed digit repeats on every field that depends on it.

Where a bespoke integration removes work

A made-to-order system sits between your systems and the single window and does the repetitive parts. In practice that looks like this:

• The Product Catalog is filled from your item master, so each product is described once and reused on later shipments.
• Invoice data maps straight into the DUIMP draft, with currency and Incoterms handled by rule instead of memory.
• LPCO requirements are checked against the NCM before the cargo ships, not after it lands.
• Tax figures for II, IPI, PIS, COFINS, and ICMS are calculated from the same source data, so the declaration and your cost sheet agree.

You still review and file. The system removes the typing, the copy and paste, and the silent mismatches that trigger a document review.

API access versus screen work

Parts of the Portal Unico expose services that a system can call directly. Other steps still happen on screen through a broker. A bespoke build is honest about that split:

• Where a service exists, the integration sends and reads data automatically.
• Where only the screen exists, the system prepares a clean, validated package so the person filing spends seconds, not hours.

The goal is not to pretend everything is automated. It is to shrink the manual surface to the smallest possible set of decisions.

Validation before filing

The biggest saving is not speed of entry. It is catching errors before they reach customs. A tailored layer checks the operation against your own rules first:

• NCM present and consistent with the product description.
• Customs value that includes freight and uses the correct exchange rate.
• Quantity, weight, and value that agree across invoice, packing list, and bill of lading.
• Required LPCO attached and valid for the arrival date.

You can see how those numbers build up in the import cost calculator, then feed the same figures into the declaration.

What to look for in a build

If you are scoping an integration, judge it on the boring details:

• Does it map to your NCM and Product Catalog, not a generic template?
• Does it flag mismatches between documents before you file?
• Does it keep a record of what was sent, so an audit is a lookup and not a search?

Those three points separate a real integration from a form that looks nice and still needs a person to fill it.

Closing

Siscomex and the Portal Unico already talk to each other. The work that remains is getting your data into them cleanly, and that is exactly the part a bespoke Kadmoon system takes off your team's desk.