PUESC

SENT and RMPD message codes and what each one means

SENT and RMPD message codes from the official PUESC specification: SENT100, SENT300, RMPD100, RMPD406 and the rest, who files each and what to do with it.

Published · Author: Makaiev Kostiantyn Oleksandrovych, founder of Sigil RMPD

A screen showing an authentication error message. Photo: Markus Spiske, Pexels
A screen showing an authentication error message. Photo: Markus Spiske, Pexels

SENT and RMPD message codes are read digit by digit: the first gives the carriage situation, the last two the action. In SENT, 1xx belongs to the consignor, 2xx to the consignee and 3xx to the carrier in transit. In RMPD the carrier files RMPD100 and gets RMPD110 with a reference number, while RMPD406 checks status and GPS position.

In brief: a message number is an address rather than a label, and the hundreds digit says where the carriage begins and ends · 1xx the carriage begins in Poland and the consignor files · 2xx it ends in Poland and the consignee files · 3xx it begins and ends outside Poland and the carrier files · 4xx queries and answers, among them SENT406 and RMPD406 about the GPS position · 5xx the system's answer, either a confirmation or the reasons for rejection · the 3xx group has no closing message at all, because closing belongs to the consignee and transit has none.

A client writes "file a SENT300" and the dispatcher types those seven characters into a search box. They are not looking for a lecture on the system, only for an answer to whether this is their job at all. People type the codes themselves into search more often than the names of the services, and RMPD406 most often of all.

How SENT and RMPD message numbers are read
How SENT and RMPD message numbers are read

A message is an XML document that your system or the portal sends to the registry. The number states unambiguously who files, where the goods travel from and to, and what the document does.

How to read a number without the table

The first digit is the situation. One means carriage starting on Polish territory, filed by the consignor. Two means carriage ending in Poland, filed by the consignee. Three means carriage starting and ending outside Poland, which is transit, and the carrier files it.

The last two digits are the action, and they repeat in every group. Zero zero is registration, one an update by the filer, two an update by the carrier, three closing, four cancellation, five a complete filing including carrier data. Ten is the confirmation carrying the reference number, eleven a preview, twenty and thirty the collective filings for road and rail.

Do SENT102 and SENT202 mean the same thing? Almost. Both are an update by the carrier, the first in carriage starting in Poland and the second in carriage ending there.

The SENT messages a carrier meets

CodeName in the specificationWho files
SENT100registration of carriage starting in Polandconsignor
SENT102update of that filingcarrier
SENT103closing of the filingconsignee
SENT104cancellation of the filingconsignor
SENT105complete filing including carrier dataconsignor
SENT120collective filing for road carriageconsignor
SENT200registration of carriage ending in Polandconsignee
SENT202update of that filingcarrier
SENT203closing of the filingconsignee
SENT300registration of carriage outside Poland at both endscarrier
SENT301update of a transit filingcarrier
SENT304cancellation of a transit filingcarrier
SENT310confirmation of registration and the reference numberthe system

SENT300

Registration of a filing for carriage of goods beginning and ending outside Polish territory, by road or rail. It is the only SENT filing made by the carrier itself, and its basis is art. 7 ust. 1 of the SENT act. In plain terms it is transit through Poland, with no Polish consignor and no Polish consignee.

The 3xx group has no closing code, and that is not an omission. Closing is the duty of the receiving party (art. 5 ust. 5 of the SENT act), and in transit no such party exists in Poland. What follows from that in practice is covered in the article on transit and the summons to a check.

SENT500

Confirmation of an update, a cancellation or a closing of a carriage filing, or information about the reasons for rejecting it. One code serves both, so seeing SENT500 settles nothing by itself.

SENT406

A check on the validity of a carriage filing together with retrieval of the last position of the GPS device recorded in SENT-GEO. The answer comes back as SENT416. This is how a position is verified, and its mirror image RMPD406 has an article of its own.

SENT402

A check on the validity of a SENT number without the GPS position, answered by SENT412. When all you need is whether the number is alive, it is the cheaper query.

The RMPD messages, the full set

The RMPD specification of 20 November 2024 describes more documents than the portal shows.

CodeWhat it doesAnswer
RMPD100registration of a filing by the carrierRMPD110
RMPD101editing of a filing by the carrierRMPD111
RMPD103closing of a filingRMPD111
RMPD104cancellation of a filingRMPD111
RMPD110confirmation of registration with the reference numbernone
RMPD111preview of the filing by the carriernone
RMPD400key verification and retrieval of filing previewsRMPD111
RMPD406query on status and SENT-GEO positionRMPD416
RMPD420request for the history of a filingRMPD421
RMPD500the generic system answer, confirmation or rejectionnone

RMPD100

Registration of a filing by the carrier, the document everything starts with. The registry answers it with RMPD110 carrying the reference number. The three routes for sending it are set out in the article on ways to file RMPD.

RMPD406

A query on the status of a filing and on the last SENT-GEO position, answered by RMPD416. There is a practical limit here that we found on our own integration and that PUESC support confirmed on 11 August 2026. Only the portal serves this query; the web service rejects its schema outright.

RMPD460

No such code exists. It is searched for often, being an easy mistyping of 406 on a phone.

RMPD500

The generic answer of the RMPD system, carrying both confirmations of registration, change, cancellation and closing, and notices of rejection with a list of errors. The rule codes inside it, R01 to R30, are taken apart in the FAQ on RMPD and rejection codes using our own production data.

ID SISC

The unique number PUESC assigns to a person or a company at registration and that you then use in dealings with the fiscal authorities through the portal. Once registration is confirmed it appears under Mój pulpit | Moje dane, and the document titled "Informacja o rejestracji danych i nadaniu ID SISC" sits under Mój pulpit | Dokumenty.

How does ID SISC differ from EORI? In the reach of the system. EORI is a customs number shared across the European Union. ID SISC lives in the Polish fiscal and customs system, and it is given even to a person with no business activity, because it is assigned when the account is created. What registration itself looks like is shown in the step by step guide.

The reference number and the keys

The reference number is what the registry returns for an accepted filing, and it is what the driver produces on the road. It is valid for 10 days from the day it is issued (art. 11 ust. 1 of the SENT act), not from the declared start of carriage.

Keys are a separate thing often confused with the number. In SENT the carrier receives a key along with the number, and messages SENT400 and SENT401 serve to verify keys and to generate new ones. In RMPD the same role falls to RMPD400.

What actually concerns a carrier

On an ordinary run a non-EU carrier deals with four codes. It files RMPD100, receives RMPD110, reads RMPD500 when something went wrong, and uses RMPD406 when a position has to be shown. SENT300 joins them only when the carriage both begins and ends outside Poland.

What to do

  1. Read the first digit of the number to see straight away whose action it is.
  2. Check whether a code quoted in a client's email belongs to the carrier at all.
  3. Open the contents of SENT500 and RMPD500, since one code carries both outcomes.
  4. Ask for a position through RMPD406 on the portal, not through the web service.
  5. Keep the reference number together with the date it was issued.

What not to do

  • Assuming SENT100 and RMPD100 are the same. The first is filed by the consignor, the second by the carrier.
  • Searching the registry for RMPD460. It does not exist.
  • Checking the specification, where message names are unambiguous.
  • Waiting for a transit SENT filing to be closed. The 3xx group has no closing code.

Sigil handles the RMPD family of documents. We explain SENT messages as a phenomenon, but we do not file them for you.

A demo or training for your team

30 minutes online. We show how Sigil™ files an RMPD from a CMR and answer questions about your runs.

Frequently asked questions

What is SENT300 and do I have to file it?
It is the filing for carriage that begins and ends outside Poland, made by the carrier. The basis is art. 7 ust. 1 of the SENT act. If the goods are loaded or unloaded in Poland, SENT300 is not your document, because the consignor or the consignee files instead.
How does SENT100 differ from RMPD100?
In the system and in who files. SENT100 registers carriage beginning in Poland and is filed by the consignor. RMPD100 is the carrier's filing in the register of international carriage and is made by a non-EU carrier. Both live on PUESC, but they are separate duties.
What should I do when RMPD500 arrives?
Read what is inside, because the code carries both a confirmation and a rejection. The specification describes RMPD500 as the generic answer of the system to registration, change, cancellation and closing, together with a notice of rejection. Inside sits a rule code between R01 and R30, and that is what tells you what to fix.
Does the code RMPD460 exist?
No. There is no such message in the RMPD specification. Almost always the code meant is RMPD406, the query on the status of a filing and the last SENT-GEO position, which the system answers with RMPD416.
Who closes a transit SENT300 filing?
Nobody, and the group has no closing code. Closing is the duty of the receiving party (art. 5 ust. 5 of the SENT act), and transit through Poland has no such party. In the specification the 3xx group has registration, update and cancellation, but no closing.

Sources

Official specifications, read in the original:

PUESC service pages:

Legislation:

Platform data: the RMPD406 limit over the web service, confirmed by PUESC support on 11 August 2026, and search statistics for the 28 days to 6 October 2026.

Sigil™ turns a CMR into an RMPD declaration and files it with PUESC, with every field checked against the original.

More about PUESC