SAP integration with Brazil's foreign trade Single Window (Portal Único): credentials, limits and event notices
How does your SAP get the status from the Portal Único without double entry and without being blocked for too many queries? See what Siscomex publishes, with the date we read it, and what to prove in SAP before you automate.
The access rules belong to the agency. The credential and the decision to register a document belong to your company. Our work is on the SAP side: where the status enters and the proof that it arrived correctly.
Start with the question for your role
Four entry points to the same decision: each role starts with its own question about process status.
01Foreign trade
How cargo and declaration status reach the process without double entry.
See the section for this role02Tax and compliance
What proof shows an auditor that the status came from the agency, and at what time.
See the section for this role03IT and integration
Credential, key, authentication, limit and event notice address.
See the section for this role04Management
Who answers for the robot, what the agency does not guarantee and what to ask NTT DATA.
See the section for this roleSAP does not read the Portal Único by itself: someone has to integrate it
SAP holds the order, the invoice and the cost. The official state of the cargo and of the declaration sits in the agency's systems and reaches SAP through an integration layer that polls, is notified by event, or relies on manual entry.
What the agency publishes
Credential, representation, access key, authentication, query limit and event notice, each with a written rule.
What the agency does not publish
Delivery guarantee for the notice, response time and the limits of every function. We did not check these.
What DFSpro proves
That the status stored in SAP came from the agency, at what time, and that the same information was not entered twice.
Import rules and import process are covered in foreign trade in SAP. This page covers only the path of the information to SAP, with the agency's public rule and the date of each reading. It promises no automatic link and makes no decision for you.
Three ways for SAP to know the status, and the cost of each one
The choice changes the query volume, the risk of being blocked and the trail left for audit.
| Way | How it works | Cost and risk |
|---|---|---|
| Periodic polling | A program asks the Portal Único, from time to time, for the state of each known process. | The more processes and the shorter the interval, the closer you get to the limit per hour. It is the way most exposed to blocking. |
| Event notice | The Portal Único sends a notification to the company's address when the status changes, for some documents. | Needs a secure address that is available. We did not read any guarantee of delivery or timing. |
| Manual entry | An analyst opens the portal and copies the status into SAP or a spreadsheet. | Costs time and creates errors. With no reading time and no source, the status has no proof. |
For Duimp (the single import declaration), the Siscomex page of 02/10/2026 advises checking the last change date first and subscribing to events, instead of downloading everything every hour. Read on 16/10/2026.
Registration, profile and certificate: who can query
Access to the Portal Único starts from the Federal Revenue registration, not from an SAP setting.
Account holder
Only companies and representatives authorized to operate in foreign trade before the Federal Revenue have access, according to the Integrate your system page.
Representative
Whoever acts for the company, such as a customs broker or an agent, appears in the register of involved parties with their own link.
Profile
Access is by profile: cargo agent, declarant, depositary, carrier, port operator and third parties, among others.
Digital certificate
The API uses digital certificates, and the official integration service requires the e-CNPJ (company digital certificate) of the contracting party. MP (Provisional Measure) 2.200-2/2001 covers the legal validity of the ICP-Brasil certificate.
What each profile sees defines what your SAP can receive. A wrong profile does not show up as a system error: it shows up as a process that disappears from the list. Sources read on 16/10/2026.
The link that decides what the robot sees
When permission over a cargo bill is missing, the system answers that the query is not allowed. There is no technical failure to alert anyone.
| Point | What applies |
|---|---|
| End date filled in | The link expires on that date. After it, the robot stops seeing the represented party's processes and receives the answer that the query is not allowed. |
| End date blank | The system reads it as unlimited validity. Someone who leaves the company keeps access until somebody ends the link. |
| Answer log | SAP must store the answer received, not only the processes that came back. Without it, the disappearance goes unnoticed. |
| Person in charge of the alert | One person gets the notice when the answer changes to query not allowed. |
The CCT Import manual, air mode (Aug/2025), says the company must keep the register up to date and report the end date of its representatives. Read on 16/10/2026.
A key for a third-party system: whoever uses it acts as if they were the owner
The API documentation describes the steps: the account holder, logged in with a certificate, generates a key pair, chooses profiles and a term, and accepts a statement of responsibility.
- The system that authenticates with the key pair reaches the services as if it were the key's owner.
- Safe custody is up to the user: do not send the key by email and do not store it without encryption.
- The account holder sets the expiry date, and early termination is done by revocation, with immediate effect.
- Misuse falls on the key holder, so the company decides who receives the key and where it is kept.
- When you change integration vendor, revoke the old key and generate a new one with a short term.
- Record who generated it, for which profiles and until when. DFSpro does not keep the client's key or certificate.
Source: Portal Único API documentation, Access Keys page, read on 16/10/2026.
Reuse the token: authenticating on every call goes against the guidance
Authentication returns a token, and the documentation gives a validity of 60 minutes.
- 01
Authenticate once
The robot authenticates and receives the token, valid for 60 minutes according to the documentation.
- 02
Reuse the token
Each query uses the same token while it is valid.
- 03
Renew before it expires
A new request goes out only when the token is close to its end.
- 04
Keep the record
The log shows an interval of more than 60 seconds between authentication requests.
In Systems Notice No. 014/2024, of 02/10/2024, Siscomex announced that it would not accept successive authentication requests within 60 seconds, effective 19/01/2025.
Sources read on 16/10/2026: the Siscomex notice and the API Authentication page. If the rule changed afterwards, the agency's page on the day prevails.
What the agency published and how to design so as not to get blocked
The limit is per user and per one-hour window. Repeat offenses lengthen the block.
| Occurrence in the window | Function block |
|---|---|
| First time | Until the end of the current 1-hour window. |
| Repeat | The current window plus one extra 1-hour window. |
| Third time onward | The current window plus two windows, or 2 hours. |
The block error carries the code PUCX-ER1001, and at 00:00 the blocks end and the count resets. For automated Duimp queries, Siscomex announced on 02/10/2026 a limit of 1,000 queries per hour, per user.
Keep the robot's credential separate from the analyst's, when the profile allows it, so the robot does not block the person working on screen. Store the last state in SAP and refresh by event or by last change date.
What the webhook delivers and what it requires
The Portal Único describes the service as sending notifications about status changes in operations under way.
Available events
DU-E (export declaration), Duimp, license (LPCO) and export cargo control, according to the notifications page.
Recipients
The notification goes to all representatives of the CNPJ. If two of them subscribe the same address, it receives the notification more than once.
Company address
It must accept HTTPS on port 443, with TLS 1.2 or higher.
Delivery failures
There is a way to query failures, and SAP must handle a repeated event with a unique key.
We did not read any delivery guarantee, and the response time must be confirmed with the agency. For drawback and other documents, ask Siscomex about a public interface. Read on 16/10/2026.
The seven states SAP will read in the air mode
The CCT Import manual for air mode (Aug/2025) describes the cargo and defines, in each situation, who answers for the tax in case of loss or surplus.
- 01
Reported
The carrier or the cargo agent reports the bill.
- 02
Manifested
The trip and the bill are in the system.
- 03
In transfer area or not unloaded
A situation that follows the arrival of the trip.
- 04
Received
The depositary creates the lot and receives the cargo.
- 05
Moving between sites
The cargo moves to another site.
- 06
In land transit
The cargo goes on to another location.
- 07
Delivered
The delivery is recorded.
For sea mode, see the Siscomex manual. The market usually calls the sea system Siscarga, and the official documentation we read calls it Siscomex Carga.
Do not mix what the agency says with what the company did
Six common mistakes in a tracking portal, and how SAP avoids them.
Mixed status
Cleared, from the agency, next to paid, from the company, without saying the source. Every status carries its source.
Hidden lag
The status shows the last reading. Without the time, it looks like real time.
Hidden block
A blocked cargo that shows as in progress. The reason for the block must be visible.
Arrival left undefined
Arrival of the trip, presence of the cargo and reception at the site are separate milestones in the manual. Pick one and write the rule.
Legal deadline as SLA
A deadline set by law is not a commitment of the provider. An SLA exists when it is in a contract.
Portal with no owner
Nobody fixes the wrong status and trust fades. Name a person in charge.
Drivers and representatives appear in the answers
The agency's answer may carry the CPF (individual tax ID) and name of individuals.
- 01
Purpose and necessity
LGPD (Brazil's data protection law), art. 6, asks for purpose, adequacy and necessity. Keep only what the process needs.
- 02
Security
Art. 46 requires security measures. Limit who sees the personal field in SAP.
- 03
Retention period
How long to keep it is the client's decision. We record the rule and prove that it runs.
Personal information needs extra care in the integration. Sources read on 16/10/2026: Law 13.709/2018 and the ANPD page on data subject rights. The legal basis for each case is an analysis for your legal team.
Six proof scenarios before you switch on the robot
Store the last state, the reading time, the source and a unique key that prevents duplicates.
| Scenario | How to prove it | Evidence kept |
|---|---|---|
| Expired representation | Simulate an expired end date and check the alert. | Answer of query not allowed and the notice to the person in charge. |
| Limit exceeded | Run a volume above the limit in the robot's test environment. | Code PUCX-ER1001 handled and a new attempt after the window. |
| Duplicate event | Send the same event twice. | A single record, with the count checked. |
| Status that goes back | Store one state and then an earlier one. | Written rule on which one prevails, and history kept. |
| DI replaced by Duimp | Follow the same process across the two declarations. | A single link to the order, without losing the history. |
| Change of customs broker | Revoke one link and create another. | Old and new processes visible to the right person in charge. |
Where the state enters SAP, in which field and with what alert is an implementation design. See tax integration with BTP and API, tax setup and tax testing. The inbound invoice for imports is covered in inbound NF-e, Duimp and import invoice.
What NTT DATA describes, with the date of reading
GUEPARDO is an NTT DATA product. What follows is its public description, read on 16/10/2026, and not our own measurement.
Robots
According to NTT DATA, they read data on Government sites and servers, compare it with the other modules and issue alerts. For sea cargo control, it mentions periodic reading of new cargo, suggested every 3 hours.
Registration with the agency
NTT DATA says that registration in Siscomex happens when the user authorizes it. Your company is the one who authorizes.
Web Follow-up
According to NTT DATA, it is a relationship portal where the customer of the importer, the exporter or the provider tracks processes, with access by company and user.
The frequency NTT DATA suggests is not an agency rule. Whether it fits the official limits depends on the volume of identifiers. The no cost per query in NTT DATA's text refers to the software license and does not change any limit set by the agency.
Questions for NTT DATA
- Does the robot poll within a limit or use event notices?
- How does the product handle Duimp and the 02/10/2026 limit?
- Where are the client's access key and certificate kept, and by whom?
- Does automatic registration with the agency require human approval, and where is the trail?
To read more
The product as a whole: GUEPARDO Global Trade. The set of modules is in the modules hub, and document issuing is in GUEPARDO e-Invoicing.
We design, configure and prove; the credential belongs to the client
DFSpro does
- Defines where the status enters SAP, in which field and with what alert.
- Configures the integration and the reconciliation with the order and the invoice.
- Proves each scenario, with evidence and date.
- As an Authorized Channel, licenses NTT DATA's GUEPARDO, implements the product and supports governance.
Stays with the client
- Certificate, access key and representation.
- The decision to register a document with the agency without human approval.
- The tax and customs thesis.
- The retention period for personal data.
Who defines what, and who decides
The access, limit and notice rules belong to Siscomex, and this page summarizes them with the date they were read. The credential and the decision to register a document with the agency belong to your team. DFSpro designs, configures and proves how your SAP receives and stores the status.
Who published each piece of information, and when
Siscomex and gov.br
- Authentication in the Portal Único (Systems No. 014/2024, 02/10/2024)Read on 16/10/2026
- Limit on automated Duimp queries (02/10/2026)Read on 16/10/2026
- Integrate your system (updated on 02/10/2026)Read on 16/10/2026
- Integra COMEX, gov.br service (last modified 15/12/2025)Read on 16/10/2026
- CCT Import manual, air mode (Aug/2025)Read on 16/10/2026
Portal Único API
Reread the agency's page on the day you decide.
Frequently asked questions about Portal Único integration
01Can my robot use the same credential as my analyst?+
Technically it can, but the limit is per user and per one-hour window, and a robot that polls every hour can block the analyst. We recommend separate credentials, when the profile allows it.
02Who answers if the robot makes a wrong registration with the agency?+
The credential holder, because whoever uses the key acts as the owner. That is why automatic registration without human approval is your company's decision.
03What happens when the agency changes a query limit?+
Siscomex published a new limit for Duimp on 02/10/2026. The design needs a monitor for rule changes and handling of the block error, instead of relying on a fixed value.
04How do I know the robot stopped seeing my processes?+
An expired representation returns query not allowed, with no system error. SAP must store that answer and alert a person in charge, not just list what came back.
05Can SAP be notified instead of polling every hour?+
The Portal Único offers event notices for some documents and requires an HTTPS address from the company. The delivery guarantee and the response time must be confirmed with the agency, so the design keeps a reconciliation query.
06How many processes a month justify automating?+
There is no official number. Below a volume where manual checking fits in the analyst's day, the robot may cost more than it saves. This is judgment, not measurement.
07What proof do I have, in an audit, that the status came from the agency?+
The reading time, the source, the stored answer and a unique key per process. Without these four items, the status is no better than manual entry.
08Does the robot store personal data of drivers or representatives?+
The agency's answer may carry it. Purpose, necessity and retention period are your company's decision, with LGPD as the basis, and the legal analysis is for your team.
09My customs broker already queries for me. Do the two conflict?+
The limit is per user, and each one uses their own credential. The possible conflict is a duplicate record in SAP, which the unique key per process solves.
10How much does the official integration service cost and who contracts it?+
The Integra COMEX service is contracted in the Serpro store, by volume band, and the certificate holder is the one who contracts. Check the Serpro store for current prices, the volume band and the contracting terms.
11What changes in the design when the DI goes away and only Duimp remains?+
By the Siscomex schedule, the DI is switched off operation by operation, and the LI (import license) continues to exist. The design accepts both declarations during the transition and stores the date of each reading.
12Does DFSpro operate the robot?+
No. On the SAP side, DFSpro designs, configures and proves the status path. As an Authorized Channel, it also licenses NTT DATA's GUEPARDO. The credential and the decision to register with the agency stay with your company.
Tell us how process status reaches your SAP today
The conversation covers your environment, the credential and the proof the audit will ask for. Tell us how the status arrives today, who queries it and where it is stored.
To go deeper first: tax integration with BTP and API.