Skip to main content
KSeF 2.0 · authentication

KSeF authentication statuses: 415, 425, 450, 470 and 480

Signing in to KSeF ends with a status that is checked separately from sending itself. Besides certificate errors (code 460) there are statuses about permissions, a revoked session, a token and a block. Code 450 means something else here than on an invoice (invoice 450).

FlexigoTech · Editor in charge: Víctor Gómez · Updated 5 November 2026

Key facts

Module
KSeF 2.0
Versions
Odoo 17, 18, 19 and 20
Checked
in the module's source code, version 20.0 · against the sources linked at the end
Reading time
3 min

What each status means

415
“Uwierzytelnianie zakończone niepowodzeniem” (authentication failed), details “Brak przypisanych uprawnień” (no permissions assigned): the person or entity on the certificate holds no permissions in the context of that NIP.
425
“Uwierzytelnienie unieważnione” (authentication revoked), details “Uwierzytelnienie i powiązane refresh tokeny zostały unieważnione przez użytkownika”: someone closed that sign-in session.
450
“Uwierzytelnianie zakończone niepowodzeniem z powodu błędnego tokenu” (failed because of a bad token), with details such as “Token unieważniony”, “Token nieaktywny”, “Nieprawidłowy czas tokena” or “Token nie może być użyty w kontekście {contextIdentifier}”: it is about signing in with a KSeF token.
470
“Uwierzytelnianie zakończone niepowodzeniem”, details “Próba wykorzystania metod autoryzacyjnych osoby zmarłej” (attempt to use the credentials of a deceased person).
480
“Uwierzytelnienie zablokowane” (authentication blocked), details “Podejrzenie incydentu bezpieczeństwa. Skontaktuj się z Ministerstwem Finansów przez formularz zgłoszeniowy.” (suspected security incident; contact the Ministry through its form).
500 and 550
“Nieznany błąd” (unknown error) and “Operacja została anulowana przez system” (cancelled by the system), with details “Przetwarzanie zostało przerwane z przyczyn wewnętrznych systemu. Spróbuj ponownie” (processing stopped for internal reasons; try again).
KSeF authentication statuses card
Status 415 with its API description and the other sign-in statuses: 425, 450, 470 and 480, plus codes 21301 and 21304.

KSeF tokens and Odoo

Odoo 18, 19 and 20 have a function to sign in with a KSeF token in their code, but nothing calls it: they only sign in with the certificate. So a 450 at sign-in does not come from Odoo. If you see one, it comes from another program that uses a token, such as an accounting office's. KSeF tokens are revoked automatically when their owner loses permissions.

For the other statuses Odoo shows “KSeF Authentication failed with status …: …” with the description and without the details. For 415 and 470 the description is the same, so only the details field tells them apart.

Access tokens, refresh, and codes 21301 and 21304

ItemKSeFOdoo 18, 19 and 20
accessTokenValid for a dozen or so minutes, as set in its exp fieldAfter an HTTP 401 it refreshes it and repeats the request once.
refreshTokenUp to 7 daysThe scheduled action “Refresh KSeF tokens” signs in again with the certificate every 6 days.
21301 “Brak autoryzacji.” (no authorisation)When redeeming or refreshing tokens, for example “Token KSeF został unieważniony.” (KSeF token revoked)You see “Failed to refresh KSeF access token. You may need to re-authenticate manually. Error: 400 Client Error…”, without the code.
21304 “Brak uwierzytelnienia.” (no authentication)“Operacja uwierzytelniania o numerze referencyjnym {referenceNumber} nie została znaleziona.”Same: the code does not reach the screen.
Diagram: what KSeF returns for sign-in statuses 415-480 and what Odoo 20 shows
Diagram based on the l10n_pl_edi code of Odoo 20 and the KSeF API 2.9.0 specification; struck-through items are what Odoo does not keep or do.

What to do

  • 415, or 21301 after permissions were removed: the company owner grants permissions in KSeF to the person on the certificate, and you save the certificate in Odoo's settings again.
  • 425: someone revoked the sign-in session; save the certificate again so Odoo signs in afresh.
  • 480: do what KSeF says and contact the Ministry of Finance through its form; retrying the sign-in will not help.
  • 500 or 550: try again.

Our module, Poland KSeF 2.0 Validator, keeps a list of KSeF certificates and tokens with their expiry dates, but it does not sign in to KSeF and does not see these statuses.

Keep reading

Signing in to KSeF with a certificate: code 460 and XAdES signature errorsKSeF code 460 and exceptions 9101-9105, 21111, 21115, 21117, 21217, 21401 and 21406 at certificate sign-in. What Odoo 18-20 do not show and what to check.KSeF code 450: “Błąd weryfikacji semantyki dokumentu faktury”KSeF code 450 means the FA(3) invoice was rejected after its content was checked. Where the real reason is, what Odoo 18, 19 and 20 do not show and how to send it again.KSeF codes 410 and 415: seller permissions and attachmentsKSeF 410 “Nieprawidłowy zakres uprawnień” and 415 for invoices with attachments: what triggers them in the Ministry's tests and what to check in Odoo 18-20.
Checked in the module's source code (version 20.0) and the linked sources

Sources