PUESC errors at login, signing and permissions

A dispatcher could not get into PUESC in the morning, because the password would not take. They tried three times, and after the fourth attempt the portal stopped asking for a password at all. The filing for the run sat still, the driver waited for a number, and the account was blocked for thirty minutes with not a word about it on the screen.

PUESC is the Polish fiscal and customs portal through which SENT and RMPD filings are made.

In short: three wrong passwords block access for 30 minutes, after which it returns on its own · an emergency code for two-factor login is available once in twenty-four hours and is valid for 10 minutes · for a signing problem the portal itself advises changing browser first and trying again · the customs certificate is free, you generate it yourself under "Mój pulpit | Moje dane", and the password to its key cannot be recovered · a channel permission error is not a transient error: in our own data 240 attempts over two days changed nothing · the same account can send filings successfully on one day and have no right to check their status, because those are different channels.

PUESC errors fall into two groups, and which one yours belongs to decides everything. A transient error, such as a dropped connection, passes by itself and resending helps. An access error, such as a missing channel permission or an invalid signature, will never pass, however many times you press send.

What to do when you cannot log in

Three wrong passwords block access to the account for 30 minutes, and the portal says nothing about it on screen. After 30 minutes the ability to log in returns automatically, with no action on your part. If you cannot wait, a Help Desk SISC consultant lifts the block over the phone.

Three things are worth having ready for that call, because the consultant will ask for them. They are the email address that serves as the account login, a PESEL number or the number of the document given at registration, and your first and last name. The account login is tied to a particular person, so that is exactly what the consultant checks.

A forgotten password is reset without a phone call. The login window carries a "Nie pamiętasz hasła?" option, where you enter the email address that is your login and a code from an image. If the details are right, an email arrives with a link to reset the password.

What to do when access to the code app is lost

Two-factor login has an emergency exit, and it carries two limits worth knowing in advance. The "Potwierdzenie logowania" view holds an option reading "Nie mam dostępu do aplikacji Google Authenticator", which sends a one-time code to the same mailbox that serves as the login.

The first limit: such a code may be used only once in twenty-four hours. Once that is exhausted the portal refuses and only Help Desk SISC remains. The second limit: the code is valid for 10 minutes from being sent, and after that it expires.

After a correct code the portal offers to switch the second factor off. It can be switched back on under "Moje dane", so the decision is not final.

What to do when the mailbox that is your login is lost

The case looks hopeless, yet a procedure exists and it depends on whether you hold a signature. Where a dispatcher has left the company along with their mailbox, this is exactly that case.

Without a qualified signature and without a profil zaufany there is one road: going in person, with a document proving identity, to the nearest customs and tax office, its branch or a customs post. The addresses sit on Podatki.gov.pl.

With a qualified signature or a profil zaufany the whole thing is done by email. An application for a new login states the old address, access to which has been lost, and the new address that will become the login. The application is signed, and the subject line must read "ZMIANA LOGINU PUESC PROCEDURA SPECJALNA", because without that subject the message goes elsewhere.

Why a document will not sign

PUESC accepts three kinds of signature, and it is worth knowing which one you hold. They are the kwalifikowany podpis elektroniczny, the podpis zaufany made with a trusted profile, and an advanced signature verified by a customs certificate.

The customs certificate is free, and that is the least known item on the list. You generate it yourself: log in to PUESC, go to "Mój pulpit | Moje dane | CERTYFIKATY CELNE" and press the generate button. Signing with it runs through the CertSign program, which on Windows installs the Ministry of Finance certification centre's own certificates on first run, after which they are available to Chrome and Edge.

One thing has to be done right first time while generating. The password to the key cannot be recovered, and losing it leaves generating a new key and a new certificate. Record it where the company keeps its other passwords, not in one employee's browser.

When a document will not sign, PUESC advises starting with the simplest step: change browser and try again. That is the portal's own advice rather than our guess, and it is worth doing before writing to the Help Desk. If the private key has become, or may have become, known to anyone else, the certificate has to be suspended or revoked at once through Help Desk SISC.

Why a filing bounces on missing permissions

Because PUESC has four communication channels and not every service is available on each of them. The channels are screen forms, a web service in system-to-system mode, email carrying a ready file, and uploading a document on the account. The page on channels advises outright checking the service description for whether it is offered over the web service channel.

From that come two messages that look opaque and mean the same thing. "Konfiguracja schematu nie zezwala na wysyłkę bieżącym kanałem" means this service does not travel by this channel. A message saying the user "nie jest uprawniony do korzystania z kanału SENT DIRECT" means the channel is missing a permission, not that the filing is bad.

The most unpleasant part is that an account can work by halves. In our own data, on 10 and 11 August 2026 the same nine filings went through successfully to the register via AcceptDocument and received their RMPD_110 confirmation, while checking their status via RMPD_406 bounced on permissions that same day. The carrier then sees "I cannot check the status" and draws the false conclusion that the account is broken. What the status check itself shows is set out in the piece on RMPD406.

Which errors are worth resending and which are not

The division is simple and worth remembering. A transient error passes by itself; an access error never passes. Below are our own data for the period from 24.06.2026 to 13.10.2026, from the PUESC exchange log.

The first two rows are one and the same incident: 240 attempts over two days changed nothing, because a permission was missing on the portal's side rather than on the line. The third row is different: the message signature verification error met four filings across three months and passed between attempts, so resending makes sense. The fourth disappeared after three attempts.

These errors should not be confused with a refusal by the register itself. A refusal arrives with a code from R01 to R30 and means the filing reached the register but failed its checks; what each code means is collected in the piece on a PUESC refusal to register a filing. Where the portal is down altogether, the emergency procedure applies, described separately in the piece on PUESC being unavailable.

What to do

1. 1Wait 30 minutes after three wrong passwords, because access comes back on its own.
2. 2Have the login mailbox, a PESEL or the registration document number, and your name ready before calling the Help Desk.
3. 3Generate the customs certificate in advance, because it is free and tends to be needed exactly when there is no time.
4. 4Record the certificate key password where the company keeps passwords, because it cannot be recovered.
5. 5Change browser before reporting a signing problem, because that is the portal's own first piece of advice.
6. 6Read the text of the message before resending: a word about permissions means repeating will not help.
7. 7Check whether the service you need is available on the channel you are sending it through.

What not to do

• ✗Do not resend after a message about permissions. In our data 240 attempts over two days achieved nothing.
• ✓Apply for the channel permission, because the problem sits with the account, not the filing.
• ✗Do not assume the account is broken when the status check fails. Sending filings may be working perfectly meanwhile.
• ✓Test sending and status checking separately, because they are different channels.
• ✗Do not keep the certificate key password only in one employee's browser. It cannot be recovered, and the employee will leave.
• ✓Keep it where the company keeps the rest of its passwords.
• ✗Do not burn emergency login codes needlessly. One comes once in twenty-four hours and lasts 10 minutes.

Sigil handles RMPD declarations. Access to the PUESC account and the certificates stay with the company, because the account is theirs.