Documentation / Transports and SENT

Import transports

Besides creating transports by hand, you can bring them into IntelliSent: from PUESC, by the SENT number and key or by PUESC's XML, or from a CSV file. Add from another source on the transport list offers both.

From a SENT number and key, or XML

Use this for a carriage someone else registered, for example when you are its carrier or recipient, or when PUESC's answer to your own notification has not reached IntelliSent.

1. Click Add from another source, then From given SENT number and Key or XML (or press Alt + I on the list).
2. Paste the data:
   • SENT numbers with keys, one per line: the SENT number (starting with SENT) and the receiver's key (starting with KD or KR), plus the KS key if you have it, separated by spaces, tabs or commas;
   • or SENT XML received from PUESC, such as SENT 112, pasted or read from .xml files. The text must start with the XML declaration (<?xml …?>); several documents may follow one another.
3. Check the data before importing lists what IntelliSent read from each line and points out a line without a SENT number or a key.
4. Click Import SENT.

For SENT numbers, IntelliSent asks PUESC for each notification with SENT 400 and creates the transport from its answer; the transport appears on the list once PUESC answers. From XML, the transport is created at once.

You can also paste SENT numbers and keys straight into the list's search box: IntelliSent recognises them and offers the import.

From a CSV file

The CSV import makes draft transports from a file, for example an export from your ERP system. It is under Add from another source, Transport CSV import, and in Data import.

1. Click Download the current CSV template for the columns IntelliSent expects.
2. Fill in one line per transport. File format and rules on the page lists every column and its allowed values.
3. Upload the CSV file, or a ZIP of several CSV files.
4. Choose the Default post-action: create drafts only (No automatic sending), or send a SENT message, such as SENT 100 or SENT 105, right after each transport is created. A postAction column in the file takes precedence over this default.
5. Add the Additional recipient key emails and Additional carrier key emails that every transport should get, if any.
6. The Validation preview shows each row as Ready to import or Needs correction, with the reasons and any warnings.
7. Click Import Transports. Tick Stop the import if at least one row is invalid to import nothing while a row has an error.

The result lists every row with the transport it created, or why it was not imported.

The file's rules in short:

• Values are separated by a semicolon (;). A value containing a semicolon goes in double quotes.
• UTF-8, with or without BOM; a file that is not valid UTF-8 is read as Windows-1250.
• The first line holds the column names, in any order. Every further line is one transport.
• Dates as 2026-10-17, or with a time as 2026-10-17T08:30:00. A date in the past is set to today, with a warning.
• Numbers with a decimal point or comma and no thousands separator.
• The post-action decides what else is needed: SENT 100 needs the loading place's coordinates, SENT 105 the coordinates of both places, the transport document and the driver.

The older 34-column Polish export, starting with "Rodzaj transportu;Typ zgloszenia", is accepted too.