DataTransfer – Appendix 3
Description of DataTransfer reports
1. Introduction
1.1 Who is this appendix for?
This Appendix contains technical information relating to Swiss Post DataTransfer reports.
1.2 What information will you receive about DataTransfer?
DataTransfer Manual: Overview and functional descriptions for DataTransfer
Brief description of DataTransfer services, letters with barcode (BMB) via DataTransfer, Letter ID, “Create a Dispatch List” via DataTransfer and Parcel Post easy via SFTP, an explanation of how DataTransfer works and an illustration of the registration and test procedure. This is aimed primarily at DataTransfer decision-makers.
DataTransfer – Appendix 1: Description of DataTransfer customer interface: Parcels, Express, Solutions, letters with barcode (BMB) and Letter ID
Description of the notification structure and data to be submitted for parcels, Express, Solutions, BMB, Letter ID plus technical specifications such as input file formats and naming conventions.
DataTransfer – Appendix 2: Description of customer interface “Create a Dispatch List”
Description of the data to be submitted for “Create a Dispatch List” and overview of “Create a Dispatch List” reports.
DataTransfer – Appendix 3: Description of DataTransfer reports
Description of the contents of reports for BMB, parcels and Swiss-Express, but excluding “Create a Dispatch List”.
DataTransfer – Appendix 5: Description of the DataTransfer customer interface: EAD submission
Description of the technical information for electronic data delivery of EAD (Electronic Advance Data) for international letter mail containing goods.
1.3 Validity
The manual is updated online. Changes are set out in Section 5 in the release notes.
The old PDFs will cease to be valid with the publication of the new instructions. This page shows the current version.
1.4 Abbreviations and terms used
| Abbreviation | Description |
|---|---|
| AMP-Key | Swiss Post customer identification number |
| DL | Dispatch list |
| BLN | Electronic cash on delivery |
| BMB | Letters with barcode |
| DataTransfer | Name of service for electronically transmitting data to Swiss Post |
| Letter ID | Addressed and uniquely identifiable letters (with DMC) are delivered using the Letter ID provider |
| LSO | Delivery note for letters with barcode are used by the BMB provider when dispatching mailings |
| Parcel Post easy | Parcel post without dispatch list |
| PKZIP 2.0 | Compression standard for reducing file size. Nowadays, almost all files with the extension .zip are in PKZIP 2.0 format |
| PMI | PostMail International |
| PRZL | Product or additional service, e.g. Signature |
| PVS | Mail processing system (Providers as per DataTransfer Manual, Section 3.1) |
| T&T | Track consignments (Track & Trace) |
| XSD | XML Schema Definition: For creating and verifying XML files |
1.5 Support
Post CHLtd
Support DataTransfer
Wankdorfallee 4
3030 Berne
Switzerland
E-mail: datatransfer@swisspost.ch
1.6 Test support
If you have any questions regarding consignment data simulation, please feel free to contact us. Please send your tests to the following address:
Post CH Ltd
Testsupport LS14
Wankdorfallee 4
3030 Bern
Switzerland
E-mail: testsupport.bmb@swisspost.ch
2. Reports
2.1 Reports
Various DataTransfer reports are available. When you register for DataTransfer, you can decide which reports you would like to receive. You can send an e-mail to DataTransfer Support or notify your Swiss Post customer advisor at any time if you would like to stop receiving reports or wish to receive additional ones.
The reports contain events for Parcels, Express and Solutions for consignments that are being sent, but not for those being forwarded or returned.
You can find a description of the reports for parcels, Express, Solutions, BMB and Letter ID in the DataTransfer Manual.
| Report title | Format | Provider “Parcels” | Provider “Express” |
|---|---|---|---|
| Report no. 1, Letters with barcode (BMB) | XML and CSV | – | – |
| Report no. 2, BMB and Court Document Online | XML and CSV | – | – |
| Report no. 3, Parcels with no processing events | XML and CSV | X | X |
| Report no. 7, Parcels with no electronic advance notification | XML and CSV | X | X |
| Report no. 8, Return shipments | XML, CSV and XLS (Excel 2003) | X | – |
| Report no. 11, Processing status (initial report) 11 Additional updates during the day: from 7.45 a.m. (11_01), from 10 a.m. (11_02), from 1 p.m. (11_03), from 3.30 p.m. (11_04) | XML, CSV and XLS (Excel 2003) | X | X |
| Report no. 12, Irregular processing (available only for PostPac Priority and Swiss-Express “Moon”) Requested time of delivery: from 7.45 a.m., from 10.45 a.m., from 1 p.m., from 3.30 p.m. | XML, CSV and XLS (Excel 2003) | X1 | X1 |
| Report no. 14, Address quality and codes | XLS | X | X |
| Report no. 15 and 151, Letters with barcode (BMB), all events for franking licence | XML | – | – |
| Report no. 16 and 161, BMB and court documents with electronic confirmation of receipt, all events for franking licence | XML | – | – |
| Report no. 17, Archive data for court documents | PDF/A | – | – |
| Parcel Post easy proof of processing | – | X | X |
| Report no. 18, Archive data for electronic return receipts (eAR) | PDF/A | – | – |
| Report no. 19, Letter returns data (transfer only possible via SFTP) | CSV and PDF | – | – |
| Report no. 20, Letter ID consignments | CSV | – | – |
| Report no. 21, notifications of move | CSV | – | – |
| Report title | Format | Provider “Solutions” | Provider “BMB” | Provider “Letter ID” |
|---|---|---|---|---|
| Report no. 1, Letters with barcode (BMB) | XML and CSV | – | X | – |
| Report no. 2, BMB and Court Document Online | XML and CSV | – | X | – |
| Report no. 3, Parcels with no processing events | XML and CSV | – | – | – |
| Report no. 7, Parcels with no electronic advance notification | XML and CSV | – | – | – |
| Report no. 8, Return shipments | XML, CSV and XLS (Excel 2003) | – | – | – |
| Report no. 11, Processing status (initial report) 11 Additional updates during the day: from 7.45 a.m. (11_01), from 10 a.m. (11_02), from 1 p.m. (11_03), from 3.30 p.m. (11_04) | XML, CSV and XLS (Excel 2003) | X | – | – |
| Report no. 12, Irregular processing (available only for PostPac Priority and Swiss-Express “Moon”) Requested time of delivery: from 7.45 a.m., from 10.45 a.m., from 1 p.m., from 3.30 p.m. | XML, CSV and XLS (Excel 2003) | – | – | – |
| Report no. 14, Address quality and codes | XLS | – | – | – |
| Report no. 15 and 151, Letters with barcode (BMB), all events for franking licence | XML | – | X | – |
| Report no. 16 and 161, BMB and court documents with electronic confirmation of receipt, all events for franking licence | XML | – | X | – |
| Report no. 17, Archive data for court documents | PDF/A | – | X | – |
| Parcel Post easy proof of processing | – | X | – | – |
| Report no. 18, Archive data for electronic return receipts (eAR) | PDF/A | – | X | – |
| Report no. 19, Letter returns data (transfer only possible via SFTP) | CSV and PDF | – | – | X |
| Report no. 20, Letter ID consignments | CSV | – | – | X |
| Report no. 21, notifications of move | CSV | – | X | – |
1 ↑ Only available for PostPac Priority and Swiss-Express “Moon”
Transmission of reports
The reports are transmitted via SFTP, e-mail or sedex to the address specified during registration. The report entitled “Parcel post easy proof of mailing” can only be received via SFTP.
The reports can be delivered to up to three different e-mail addresses. The length of all the e-mail addresses together must not exceed 255 characters. You can provide e-mail addresses when you register, or send them as change requests to DataTransfer Support. All reports to which you have subscribed will be sent to these e-mail addresses. SFTP reports can only be sent to one account.
All reports sent by e-mail are transmitted in zip format
(PKZIP 2.0) only. The files have the extension “.zip”.
Format
You can transfer the data in XML format and receive each individual report in another format (e.g. CSV). Similarly, you can use different channels for sending and receiving data.
2.1.1 List of event codes (“EventNumber”)
An event is reported only once per consignment number in the reports with the sorting and delivery events. An updated list of all event codes can be found on our technical homepage: Technical DataTransfer support.
2.2 Naming conventions
2.2.1 DataTransfer reports in XML, CSV or XLS Naming conventions for “XML” or “CSV” formats
SenderID_Name_Update_Timestamp.Format
| Attribute | Description |
|---|---|
| SenderID | As per information from DataTransfer Support |
| Name | Name as per the table below |
| Update | “01”, “02”, “03” or “04” used only for updates 1–4 of Report 11 |
| Timestamp | Creation date/time in the format “YYYYMMDDHHMMSS” |
| Format | “xml” or “csv” |
Naming convention for “XLS” formats
SenderID_Name_Update_Timestamp_Content.Format
| Attribute | Description |
|---|---|
| SenderID | As per information from DataTransfer Support |
| Name | Name as per the table below |
| Update | “01”, “02”, “03” or “04” used only for updates 1–4 of Report 11 |
| Timestamp | Creation date/time in the format “YYYYMMDDHHMMSS” |
| Content | “content” or “empty” |
| Format | “xls” (Excel) |
Report names
| Report no. | Report title | Name for filenames |
|---|---|---|
| 3 | Parcels with no processing events | Report3 |
| 7 | Parcels with no electronic advance notification | Report7 |
| 8 | Return shipments | Report8 |
| 11 | Processing status | Report11 |
| 12 | Irregularities | Report12 |
| 14 | Address quality and codes | Report14 |
Example for XML, all reports (without updates for Report 11)
- 112_Report7_20120127220812.xml
Example for XLS (Excel), all reports (without updates for Report 11)
- 112_Report12_20120127100459_content.xls
- 112_Report12_20120128095812_empty.xls
Examples for XML, CSV or XLS, Report 11, update 2
- XML: 112_Report11_Report11_02_20130606073110.xml
- CSV: 112_Report11_Report11_02_20130606073110.csv
- XLS: 112_Report11_Report11_02_20130606073110_content.xls
2.2.2 “Parcel post easy proof of processing”
Report Naming convention
SenderID_Fralic_Reportname_Timestamp.Format
| Attribute | Description |
|---|---|
| SenderID | As per information from DataTransfer Support |
| Fralic | Franking licence |
| Reportname | Name of the report |
| Timestamp | Creation date/time in the format “YYYYMMDDHHMMSS” |
| Format | “xml.gz” or “xml.gz” The extension “.gz” means that the file is compressed (zipped) |
Example
112_37123456_ProofOfProcessing-PPe_20050901144002.XML.gz
The files are available for download from the SFTP account for 9 days and are then deleted from the system automatically.
2.2.3 “Letters returns data” report (19 and 20)
Naming convention
SenderNo_ReportNo._Version_Language_Format_InvoiceReferenceNo.
_ProcessingDayReturns_Meter_TimeStampFileCreation.Format
| Attribute | Description |
|---|---|
| SenderID | As per information from DataTransfer Support |
| ReportNo. | Name of the report |
| Version | Version number of the report |
| Language | Language of the report |
| Format | Format number of the report |
| InvoiceReference No. | Invoice reference number |
| ProcessingDayReturns | Processing day in the format YYYYMMDD |
| Meter | Sequence number |
| TimeStamp-FileCreation | Time of creation of the report |
| Format | “xml” / “csv” / “csv + pdf” |
Example
- 112_Report19_01_DE_2_52345678_20200225_000001_20200227020208.csv
- 112_Report20_01_DE_2_52345678_20200225_000001_20200227020208.csv
- 112_Report19_03_DE_1_50424402_20210529_000001_20210531020154.csv
- 112_Report19_03_DE_2_50424402_20210529_000001_20210531020154.csv
2.2.4 BMB report via DataTransfer Naming convention (Reports 1, 2, 15, 151, 16 and 161)
SenderID_Name_Timestamp.Format
| Attribut | Description |
|---|---|
| SenderID | As per information from DataTransfer Support |
| Name | Name as per the table below |
| Timestamp | Creation date/time in the format “YYYYMMDDHHMMSS” |
| Format | “xml” or “csv” |
Naming convention (Report 18)
SenderID_Name_Language_Fralic_Creation date of the archive PDFs_Number of delivered archive PDFs_receipt.format
| Attribute | Description |
|---|---|
| SenderID | As per information from DataTransfer Support |
| Name | Name as per the table below |
| Language | Language of the report |
| Fralic | Franking licence |
| Creation date of archive PDFs | Creation date |
| Number of delivered archive PDFs | Number |
| receipt | fixed value |
| Format |
Examples
100_Report18_EN_20130816_20130418144715_980301013600000010.pdf
Example with PDF/A
100_Report18_EN_010136_20130816_30_receipt.pdf
Example without PDF/A
100_Report18_EN_020237_20130816_0_receipt.pdf
Report names
| Report no. | Report title | Name for filenames |
|---|---|---|
| 1 | Letters with barcode (BMB), all events for consignments with advance data submission | PMReport1 |
| 2 | BMB and court documents with electronic confirmation of receipt, all events for consignments with advance data submission | PMReport2 |
| 15 | Letters with barcode (BMB), all events for franking licence | Report15 |
| 151 | Letters with barcode (BMB), all events for franking licence, twice a day | Report151 |
| 16 | BMB and court documents with electronic confirmation of receipt, all events for franking licence | Report16 |
| 161 | BMB and court documents with electronic confirmation of receipt, all events for franking licence, twice a day | Report161 |
| 17 | Archive data for court documents | Report17 |
| 18 | Confirmations of receipt | Report18 |
Examples
100_PMReport1_20061128140559.xml
100_Report15_201307250559.xml
Example of Report 17 PDF
100_Report17_EN_20130816_20130418144715_980301013600000010.pdf
Examples of receipt PDF
Example with PDF/A
100_Report17_EN_010136_20130816_30_receipt.pdf
Example without PDF/A
100_Report17_EN_020237_20130816_0_receipt.pdf
2.2.5 “Archive data for court documents” report
Data file format
Report 17 (PDF format) includes all confirmations of receipt for the court documents that have been sent in the archive format PDF/A. You will still receive the report even if no data is available on the day of delivery. For each court document that is delivered, you will receive a confirmation of receipt in PDF/A format.
PDF/A filename structure
[SenderID]_[ReportName]_[Language]_[TimestampCreationPDF]
_[TimestampConsignment]_[ConsignmentID].pdf
- TimestampCreationPDF = YYYYMMDD
- TimestampCreation = YYYYMMDDhhmmss
Example of sender 982:
982_Report17_DE_20130816_20130418144715_980301013600000010.pdf
Receipt PDF filename structure
[SenderID]_[ReportName]_[Language]_[Fralic]_[TimestampCreationPDF]
_[MeterPDFA]_receipt.pdf
- Fralic = 6-digit franking licence
- TimestampCreationPDF = YYYYMMDD
Example of sender 982:
982_Report17_DE_010136_20130816_1_receipt.pdf
2.2.6 “Archive data for electronic return receipts (eAR)” report
Data format
Report 18 (PDF format) includes all confirmations of receipt for registered items with the eAR value-added service that have been sent in the archive format PDF/A. You will still receive the report even if no data is available on the day of delivery. You will receive one confirmation of receipt per registered item delivered in PDF/A format.
PDF/A file name structure
[SenderID]_[ReportName]_[Language]_[TimestampCreationPDF]_
[TimestampConsignment]_[ConsignmentID].pdf
- TimestampCreationPDF = YYYYMMDD
- TimestampConsignment = YYYYMMDDhhmmss
Example sender 982:
982_Report18_DE_20130816_20130418144715_980301013600000010.pdf
Receipt PDF file name structure
[SenderID]_[ReportName]_[Language]_[FraLic]_
[TimestampCreationPDF]_[MeterPDFA]_receipt.pdf
- Fralic = 8-digit franking licence
- TimestampCreationPDF = YYYYMMDD
Example sender 982:
982_Report18_DE_91010146_20130816_1_receipt.pdf
3. Data content of reports
3.1 “Processing events for letters with barcode” (Report 1) and “Letters with barcode, all data for franking licence” (Report 15 and 151)
Report 1 contains all the processing events for consignments you have sent by submitting data via DataTransfer.
Report 15 contains all processing events for consignments for your franking licence, even if no data has been submitted (e.g. due to system failures, process errors, etc.). Report 151 is identical to Report 15, but is provided twice a day (morning and afternoon).
3.1.1 Data content
You will receive an XML example for this report in electronic format at Technical DataTransfer support → Letters with barcode.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value/ comment |
|---|---|---|---|---|---|
| <Root> | - | Min. 1 | Max. 1 | - | - | - |
| <Sender> | - | Min. 1 | Max. 1 | - | - | - |
| SenderID | Unique sender ID allocated when registering with DataTransfer | - | Numeric | 10 | master data DataTransfer |
| SenderName | Unique sender name allocated when registering with DataTransfer | - | Alphanumeric | 20 | master data DataTransfer |
| Report Created | Date and time when report was created | - | Numeric | YYYYMMDDHHMMSS | - |
| <Provider> | Service group | Min. 1 | Max. | - | - | - |
| ProviderID | Identification code for service group | - | Alphanumeric | 50 | 44EB502C-4848- 4BE0-AADA-D8BAE7C6CA7F |
| ProviderName | Name of service group | - | Alphanumeric | 20 | Swiss Post |
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Item/> | - | - | - | - | - |
| SendingID | Unique consignment number (consignment / delivery note / order / dispatch list number, etc.) | Min. 1 | Max. | Alphanumeric | 50 | master data DataTransfer |
| ItemID | Identifier assigned by customer, may be identical to “SendingID” or “IdentCode”. For court documents, the customer’s internal reference “Note” is transmitted in this attribute. The enforcement number can be transmitted in enforcement documents. | - | Alphanumeric | 200 | master data DataTransfer |
| Identcode | Consignment barcode (for parcels, express and domestic BMB, the only valid format is 18 numeric digits). BMB international: 13 alphanumeric characters | - | Alphanumeric | 18 | master data DataTransfer |
| DFUTransfer-DateTime | Transfer date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | BMB |
| ZipCode | Postcode of the destination | - | Numeric | 4 | BMB |
| ItemWeight | Consignment weight in grammes | - | Numeric | 6 | BMB |
| EventDateTime | Event date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | BMB |
| EventNumber | Event code as per Section 2.1.1 | - | Numeric | 6 | BMB |
| EventNumber_Sub | Return reason associated with event code as per Section 2.1.1 | K | Alphanumeric | 30 | BMB |
| EventZipCode | Postcode of the event location | - | Numeric | 6 | BMB |
| RespiteDate | Deadline date | K | Alphanumeric | YYYY-MM-DD | BMB |
| </Data> | - | Min. 1 | Max. 1 | - | - | - |
| </Provider> | - | Min. 1 | Max. 1 | - | - | - |
| </Sender> | - | Min. 1 | Max. 1 | - | - | - |
| </Root> | - | Min. 1 | Max. 1 | - | - | - |
“Electronic confirmations of receipt for letters with barcode” (Report 2) and “Letters with barcode,
all data for franking licence” (Report 16 and 161)
Report 2 and Report 16 contain one link (EB_Confirmation) per consignment on the electronic confirmation of receipt. This link leads directly to the PDF for confirmation of receipt in consignment tracking (Track consignments). In order to be able to download the confirmation of receipt, it is necessary to have access rights to the “Track consignments” online service in the “My Post” customer portal. You can request this via the “My Post” customer portal or from your customer advisor. Customers who use SuisseID can also log in to the “My Post” customer portal directly using these certificates.
If you want to download these PDF documents for court documents automatically, you can use the “Track consignments” web service. For details, please visit the “Track consignments” web service.
In Bericht 2 sind alle Daten zu den BMB-Sendungen vorhanden, zu denen vorgängig eine Dateneinlieferung über DataTransfer stattgefunden hat.
In Bericht 16 sind alle Daten zu den BMB-Sendungen Ihrer Frankierlizenz vorhanden, auch wenn keine Dateneinlieferung stattgefunden hat. Der Bericht 161 ist identisch mit Bericht 16, wird aber zweimal täglich bereitgestellt (morgens und nachmittags).
3.2.1 Data content
For an XML example of this report in electronic form, please go to Technical DataTransfer support → Letters with barcode.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value/ comment |
|---|---|---|---|---|---|
| <Root> | - | Min. 1 | Max. 1 | - | - | - |
| <Sender> | - | Min. 1 | Max. 1 | - | - | - |
| SenderID | Unique sender ID allocated when registering with DataTransfer | - | Numeric | 10 | master data DataTransfer |
| SenderName | Unique sender name allocated when registering with DataTransfer | - | Alphanumeric | 20 | master data DataTransfer |
| Report Created | Date and time when report was created | - | Numeric | YYYYMMDDHHMMSS | - |
| <Provider> | Service group | Min. 1 | Max. | - | - | - |
| ProviderID | Identification code for service group | - | Alphanumeric | 50 | 44EB502C-4848- 4BE0-AADA-D8BAE7C6CA7F |
| ProviderName | Name of service group | - | Alphanumeric | 20 | Swiss Post |
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Data> | - | Min. 1 | Max.* | - | - | - |
| SendingID | Unique consignment number (consignment / delivery note / order / dispatch list number, etc.) | Min. 1 | Max. | Alphanumeric | 50 | Input data |
| ItemID | For court documents, the customer’s internal reference “Note” is transmitted in this attribute. | - | Alphanumeric | 200 | Input data |
| Identcode | Consignment barcode (for parcels, express and domestic BMB, the only valid format is 18 numeric digits). BMB international: 13 alphanumeric characters | - | Alphanumeric | 18 | - |
| DFUTransfer-DateTime | Transfer date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | Input data |
| ZipCode | Postcode of the destination | - | Numeric | 4 | - |
| ItemWeight | Consignment weight in grammes | - | Numeric | 6 | BMB |
| EventDateTime | Event date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | Input data |
| EventNumber | Event code as per Section 2.1.1 | - | Numeric | 6 | BMB |
| EventNumber_Sub | Return reason associated with event code as per Section 2.1.1 | K | Alphanumeric | 30 | BMB |
| EventZipCode | Postcode of the event location | - | Numeric | 6 | BMB |
| EB_Confirmation | Link to electronic confirmation of receipt | K | Alphanumeric | 200 | BMB |
| EB_REC_Name | Recipient name for court document consignment | K | Alphanumeric | 35 | BMB |
| EB_Relation | Relationship of the person receiving the item to the intended recipient | K | Alphanumeric | 35 | BMB |
| RespiteDate | Deadline date | K | Alphanumeric | YYYY-MM-DD | BMB |
| </Data> | - | Min. 1 | Max. 1 | - | - | - |
| </Provider> | - | Min. 1 | Max. 1 | - | - | - |
| </Sender> | - | Min. 1 | Max. 1 | - | - | - |
| </Root> | - | Min. 1 | Max. 1 | - | - | - |
3.3 Archive data for court documents (Report 17)
Around 90 days after the consignment has been posted, you will receive the confirmation of receipt for your court document in PDF/A format with a digital signature for your archiving.We will send you one PDF per court document delivered.
This means that the document will retain its authenticity even after the expiry of the postal archiving period of three years.
3.4 Archive data for electronic return receipts (eAR) (Report 18)
Around 90 days after the consignment has been posted, you will receive the archive data for your registered item with the eAR value-added service in PDF/A format with a digital signature for your archiving. We will send you one PDF per registered item delivered. This means that the document will retain its authenticity even after the expiry of the postal archiving period of three years.
3.5 “Parcels with no processing events” report (Report 3)
With Report 3, you will receive data on parcels without processing results.
3.5.1 Data content
For an XML example of this report in electronic form, please go to Technical DataTransfer support → Parcels/Express/VinoLog.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value/ comment |
|---|---|---|---|---|---|
| <Root> | - | Min. 1 | Max. 1 | - | - | - |
| <Sender> | - | Min. 1 | Max. 1 | - | - | - |
| SenderID | Unique sender ID allocated when registering with DataTransfer | - | Numeric | 10 | DataTransfer master data |
| SenderName | Unique sender name allocated when registering with DataTransfer | - | Alphanumeric | 20 | DataTransfer master data |
| Report Created | Date and time when report was created | - | Numeric | YYYYMMDDHHMMSS | - |
| <Provider> | Service group | Min. 1 | Max. | - | - | - |
| ProviderID | Identification code for service group | - | Alphanumeric | 50 | 44EB502C-4848- 4BE0-AADA-D8BAE7C6CA7F |
| ProviderName | Name of service group | - | Alphanumeric | 20 | Swiss Post |
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Item/> | - | - | - | - | - |
| SendingID | Unique consignment number (consignment / delivery note / order / dispatch list number, etc.) | Min. 1 | Max. “N” | Alphanumeric | 50 | Input data |
| ItemDate | Transfer date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS:TTT | Sorting or delivery |
| ItemID | Parcel/pallet identifier assigned by customer, may be identical to “SendingID” | - | Alphanumeric | 50 | DataTransfer master data |
| IdentCode | Consignment barcode (for parcels, express and domestic BMB, the only valid format is 18 numeric digits). BMB international: 13 alphanumeric characters | - | Alphanumeric | 50 | Input data |
| DFUTransfer-DateTime | Transfer date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | Input data |
| </Data> | - | Min. 1 | Max. 1 | - | - | Input data |
| </Provider> | - | Min. 1 | Max. 1 | - | - | - |
| </Sender> | - | Min. 1 | Max. 1 | - | - | - |
| </Root> | - | Min. 1 | Max. 1 | - | - | - |
3.6 “Parcels with no electronic advance notification” report (Report 7)
With Report 7, you will receive data on parcels with no electronic advance notification (suitable for checking DataTransfer quality).
3.6.1 Data content
For an XML example of this report in electronic form, please go to Technical DataTransfer support → Parcels/Express/VinoLog.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value/ comment |
|---|---|---|---|---|---|
| <Root> | - | Min. 1 | Max. 1 | - | - | - |
| <Sender> | - | Min. 1 | Max. 1 | - | - | - |
| SenderID | Unique sender ID allocated when registering with DataTransfer | - | Numeric | 10 | DataTransfer master data |
| SenderName | Unique sender name allocated when registering with DataTransfer | - | Alphanumeric | 20 | DataTransfer master data |
| Report Created | Date and time when report was created | - | Numeric | YYYYMMDDHHMMSS | - |
| <Provider> | Service group | Min. 1 | Max. | - | - | - |
| ProviderID | Identification code for service group | - | Alphanumeric | 50 | DataTransfer master data |
| ProviderName | Name of service group | - | Alphanumeric | 20 | DataTransfer master data |
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Item/> | - | - | - | - | - |
| IdentCode | Parcel/express consignment barcode, 18 digits, numerical. | - | Alphanumeric | 18 | DataTransfer master data |
| ItemDateTime | Processing date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | DataTransfer master data |
| </Data> | - | Min. 1 | Max. 1 | - | - | - |
| </Provider> | - | Min. 1 | Max. 1 | - | - | - |
| </Sender> | - | Min. 1 | Max. 1 | - | - | - |
| </Root> | - | Min. 1 | Max. 1 | - | - | - |
3.7 “Return shipments” report (Report 8)
With Report 8, you will receive data on parcels which were returned, based on your franking licence.
3.7.1 Data content
For an XML example of this report in electronic form, please go to Technical DataTransfer support → Parcels/Express/VinoLog.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value/ comment |
|---|---|---|---|---|---|
| <Root> | - | Min. 1 | Max. 1 | - | - | - |
| <Sender> | - | Min. 1 | Max. 1 | - | - | - |
| SenderID | Unique sender ID allocated when registering with DataTransfer | - | Numeric | 10 | DataTransfer master data |
| SenderName | Unique sender name allocated when registering with DataTransfer | - | Alphanumeric | 20 | DataTransfer master data |
| Report Created | Date and time when report was created | - | Numeric | YYYYMMDDHHMMSS | - |
| <Provider> | Service group | Min. 1 | Max. | - | - | - |
| ProviderID | Identification code for service group | - | Alphanumeric | 50 | DataTransfer master data |
| ProviderName | Name of service group | - | Alphanumeric | 20 | DataTransfer master data |
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Item/> | - | - | - | - | - |
| IdentCode | Parcel/express consignment barcode, 18 digits, numerical. | - | Alphanumeric | 18 | Mailing |
| ItemDateTime | Processing date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | Mailing |
| </Data> | - | Min. 1 | Max. 1 | - | - | - |
| </Provider> | - | Min. 1 | Max. 1 | - | - | - |
| </Sender> | - | Min. 1 | Max. 1 | - | - | - |
| </Root> | - | Min. 1 | Max. 1 | - | - | - |
3.7.2 Sample report in Excel format
3.8 “Processing status” report (Report 11)
With Report 11, you will receive data on the processing status of your parcels. This report can be obtained up to four times each day.
3.8.1 Data content
For an XML example of this report in electronic form, please go to Technical DataTransfer support → Parcels/Express/VinoLog.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value/ comment |
|---|---|---|---|---|---|
| <Root> | - | Min. 1 | Max. 1 | - | - | - |
| <Sender> | - | Min. 1 | Max. 1 | - | - | - |
| SenderID | Unique sender ID allocated when registering with DataTransfer | - | Numeric | 10 | DataTransfer master data |
| SenderName | Unique sender name allocated when registering with DataTransfer | - | Alphanumeric | 20 | DataTransfer master data |
| Report Created | Date and time when report was created | - | Numeric | YYYYMMDDHHMMSS | - |
| <Provider> | Service group | Min. 1 | Max. | - | - | - |
| ProviderID | Identification code for service group | - | Alphanumeric | 50 | DataTransfer master data |
| ProviderName | Name of service group | - | Alphanumeric | 20 | DataTransfer master data |
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Item/> | - | - | - | - | - |
| SendingID | Unique consignment number (consignment / delivery note / order / dispatch list number, etc.) | - | - | 50 | Input data |
| ItemID | Parcel/pallet identifier assigned by customer, may be identical to “SendingID” or “IdentCode”. | - | - | 50 | Input data |
| IdentCode | Parcel/express consignment barcode, 18 digits, numerical. | - | Alphanumeric | 18 | Input data |
| AdrZ1 | - | - | Alphanumeric | 35 | Input data |
| AdrZ2 | - | - | Alphanumeric | 35 | Input data |
| AdrZ3 | - | - | Alphanumeric | 35 | Input data |
| AdrZ4 | - | - | Alphanumeric | 35 | Input data |
| AdrZ5 | - | - | Alphanumeric | 35 | Input data |
| AdrZ6 | - | - | Alphanumeric | 35 | Input data |
| AdrZ7 | - | - | Alphanumeric | 35 | Input data |
| DFUTransferDateTime | Transfer date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | Input data |
| ItemWeight | Weight in grams | - | Numeric | 6 | - |
| EventDateTime | Event date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | Sorting |
| EventNumber | Event code as per Section 2.1.1 | - | Numeric | 2 | Delivery |
| EventDescription | Event description | K | Alphanumeric | 100 | DataTransfer master data |
| EventNumber_Sub | Sub-event | - | Numeric | 2 | Delivery |
| Event_SubDescription | Description of sub-event | K | Alphanumeric | 500 | DataTransfer master data |
| EventZipCode | Postcode of the event location | K | Numeric | 6 | Delivery |
| PrZl | - | K | Alphanumeric | 500 | Sorting |
| DeliveredTo | Name of the recipient of the consignment | K | Alphanumeric | 30 | Input data |
| TrackAndTrace | T&T Business URL with parameters, barcode ID and language code | - | Alphanumeric | 160 | Delivery |
| </Data> | - | Min. 1 | Max. 1 | - | - | - |
| </Provider> | - | Min. 1 | Max. 1 | - | - | - |
| </Sender> | - | Min. 1 | Max. 1 | - | - | - |
| </Root> | - | Min. 1 | Max. 1 | - | - | - |
3.9 “Irregularities” report (Report 12)
With Report 12, you will receive data about potentially irregular processing (only possible for PostPac Priority and Swiss-Express “Moon”). This report can be obtained up to four times each day.
3.9.1 Data content
You can obtain an electronic copy of the XLS (Excel) example of this report at Technical DataTransfer support → Parcels/Express/VinoLog.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value/ comment |
|---|---|---|---|---|---|
| <Root> | - | Min. 1 | Max. 1 | - | - | - |
| <Sender> | - | Min. 1 | Max. 1 | - | - | - |
| SenderID | Unique sender ID allocated when registering with DataTransfer | - | Numeric | 10 | DataTransfer master data |
| SenderName | Unique sender name allocated when registering with DataTransfer | - | Alphanumeric | 20 | DataTransfer master data |
| Report Created | Date and time when report was created | - | Numeric | YYYYMMDDHHMMSS | - |
| <Provider> | Service group | Min. 1 | Max. | - | - | - |
| ProviderID | Identification code for service group | - | Alphanumeric | 50 | DataTransfer master data |
| ProviderName | Name of service group | - | Alphanumeric | 20 | DataTransfer master data |
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Item/> | - | - | - | - | - |
| SendingID | Unique consignment number (consignment / delivery note / order / dispatch list number, etc.) | - | Alphanumeric | 50 | Input data |
| ItemID | Parcel/pallet identifier assigned by customer, may be identical to “SendingID” or “IdentCode”. | - | Alphanumeric | 50 | Input data |
| IdentCode | Parcel/express consignment barcode, 18 digits, numerical. | - | Alphanumeric | 18 | PDS: Sorting |
| AdrZ1 | - | - | Alphanumeric | 35 | Input data |
| AdrZ2 | - | - | Alphanumeric | 35 | Input data |
| AdrZ3 | - | - | Alphanumeric | 35 | Input data |
| AdrZ4 | - | - | Alphanumeric | 35 | Input data |
| AdrZ5 | - | - | Alphanumeric | 35 | Input data |
| AdrZ6 | - | - | Alphanumeric | 35 | Input data |
| AdrZ7 | - | - | Alphanumeric | 35 | Input data |
| DFUTransferDateTime | Transfer date and time | - | Alphanumeric | YYYY-MM-DDTHH:MM:SS | Input data |
| TrackAndTrace | T&T Business URL with parameters, barcode ID and language code | - | Alphanumeric | 160 | PDS: Sorting |
| </Data> | - | Min. 1 | Max. 1 | - | - | - |
| </Provider> | - | Min. 1 | Max. 1 | - | - | - |
| </Sender> | - | Min. 1 | Max. 1 | - | - | - |
| </Root> | - | Min. 1 | Max. 1 | - | - | - |
3.10 Letter returns data (Report 19, version 2)
You have stored a “... with data” returns instruction in the dynamic data matrix code (Letter ID), and you would like to receive the returns data daily.
With report 19 (version 2), the returns data are provided for download on the Swiss Post server on a daily basis. The report contains the processed returns from two days before, i.e.
current date minus two days. A data file (CSV or XML with returns data) and an image file (PDF) are created daily.
Additionally, the options can be selected “per reason for return” or “per return”.
3.10.1 Data content
You will receive a CSV example for this report in electronic form at Technical DataTransfer support → Create dispatch list.
3.10.2 Sample report in Excel format
3.11 Letter returns data (Report 19, version 3, with movers files)
with movers files)You have stored a “... with data” returns instruction in the dynamic data matrix code (Letter ID), and you would like to receive the returns data daily.
With Report 19 (version 3, with movers’ files), the returns data is provided for download on the Swiss Post server on a daily basis. The report contains the processed returns from two days before, i.e. current date minus two days. If a movers’ address is known for the consignment to be returned, this will be provided for a charge. A CSV file is generated every day.
Report 19.3 can be obtained in two formats. Format 1 (csv) and format 2 (csv + PDF).
3.11.1 Data content
You will receive a CSV example for this report in electronic form at Technical DataTransfer support → Create dispatch list.
3.11.2 Sample report in Excel format
3.12 Letter returns data (Report 19, version 4, PDF per return)
You have stored a “... with data” returns instruction in the data matrix code (Letter ID), and you would like to receive the returns data daily.
With Report 19 (version 4), the returns data are provided for download on the Swiss Post server on a daily basis. The report contains the processed returns from two days before, i.e. current date minus two days. One data file (CSV or XML with returns data) and N image files (PDF) are created daily. In the data file, the file name of the related PDF image is listed in the last column for each record.
3.12.1 Data content
Ein CSV-Beispiel zu diesem Bericht erhalten Sie in elektronischer Form unter Technische Unterstützung DataTransfer → Aufgabeverzeichnis erstellen.
For a CSV example of this report in electronic form, please go to Technical DataTransfer support → Create dispatch list.
3.12.2 Sample report in Excel format
3.13 Letter ID consignments (Report 20)
The report is sent daily and contains the first sorting result of Letter ID consignments (with dynamic Letter ID).
The report is triggered by Swiss Post making available and preparing the first sorting events (generally by 9 a.m., otherwise by 10 a.m. at the latest, on weekdays).
Reporting on the following events is possible:
- Consignment in delivery, including expected delivery date
- Return item
3.13.1 Data content
You will receive an Excel example for this report in electronic form at Technical DataTransfer support → Create dispatch list.
3.13.2 Sample report in Excel format
3.14 Notifications of move (Report 21)
This report is sent daily and contains the relevant notifications of move for your company. The report is triggered by customers that have moved wishing to tell selected companies on the Swiss Post homepage about their move.
This report is sent daily and, based on an agreement with the Address Competence Center, contains the notifications of move relevant for your company. If you are interested, please contact your customer advisor. The report is triggered by customers that have moved wishing to tell selected companies on the Swiss Post homepage about their move.
3.14.1 Data content
For an Excel example of this report in electronic form, please go to Technical DataTransfer support → Create dispatch list.
3.14.2 Sample report in CSV format
3.15 “Address quality and codes” report (Report 14)
With report 14, you will receive data on address quality with codes.
3.15.1 Data content
You will receive an Excel example for this report in electronic form at Technical DataTransfer support → Parcels/Express/VinoLog.
3.15.2 “Address quality and codes” sample report in Excel spreadsheet format
3.15.3 “Parcels” sample report in Excel spreadsheet format (with incorrect addresses)
3.15.4 Error messages
The following error messages are listed in the report:
| Error message | Explanation |
|---|---|
| Street missing or does not match postcode/town | According to the master data, the postcode requires a street. However, this could not be found in the lines provided. |
| House number required but not found | According to the master data, the street requires a house number. However, this could not be found in the lines provided. |
| Incorrect house number | According to the master data, the house number does not exist in this street. |
| “P.O. Box” missing from address | The keyword “P.O. Box” (including all alternative spellings) could not be found in the lines provided. |
| Address format does not match specification | Address does not match the conventions for Swiss addresses. |
3.16 “Parcel post easy proof of processing” report
With the “Parcel post easy proof of processing” (PpE) report, you will receive data about the PpE processing statement (the submission is possible only via a SFTP account).
3.16.1 Data content
For an XML example of this report in electronic form, please go to Technical DataTransfer support → Parcels/Express/Vinolog.
| <Element> Attribute | Description | Property | Data type | Format (max. length) | Default value Data source |
|---|---|---|---|---|---|
| <Data> | - | Min. 1 | Max. 1 | - | - | - |
| <Row> | - | Min. 1 | Max. 1 | - | - | - |
| debtorNumber | Debtor number | Min. 1 | Max. * | Numeric | 8 | - |
| debtorName | Debtor name | Min. 1 | Max. * | Alphanumeric | 71 | - |
| invoiceReference | Invoice reference | Min. 0 | Max. * | Numeric | 9 | - |
| postageLicense | Franking licence | Min. 1 | Max. * | Alphanumeric | 8 | - |
| invoiceNumber | Invoice number | Min. 0 | Max. * | Numeric | 12 | Cannot be provided. |
| documentNumber | Directory number | Min. 0 | Max. * | Numeric | 10 | - |
| ZE | Delivery event | Min. 0 | Max. * | Alphanumeric | 1 | - |
| sortingDate | Sorting date | Min. 1 | Max. * | Alphanumeric | DD.MM.YYYY | - |
| identificationCode | Identcode | Min. 1 | Max. * | Alphanumeric | 20 | - |
| product | Product | Min. 1 | Max. * | Alphanumeric | 50 | - |
| weight | Weight | Min. 1 | Max. * | Alphanumeric | 30 | - |
| tariffLevel | Tariff band | Min. 1 | Max. * | Alphanumeric | 30 | - |
| ZLIncl | Value-added service incl. | Min. 0 | Max. * | Alphanumeric | 30 | - |
| priceExclVAT | Price excl. VAT | Min. 1 | Max. * | Numeric | 14.4 | - |
| priceInclVAT | Price incl. VAT | Min. 1 | Max. * | Numeric | 14.4 | - |
| ZL | Value-added service | Min. 0 | Max. * | Alphanumeric | 30 | - |
| ZLExclVAT | Value-added service price excl. VAT | Min. 1 | Max. * | Numeric | 14.4 | - |
| ZLInclVAT | Value-added service incl. VAT | Min. 1 | Max. * | Numeric | 14.4 | - |
| </Row> | - | Min. 1 | Max. 1 | - | - | - |
| </Data> | - | Min. 1 | Max. 1 | - | - | - |
3.17 Delivery note for letters with barcode
4. Additional publications
- DataTransfer manual “Overview and functional descriptions for DataTransfer”
- DataTransfer – Appendix 1 “Description of DataTransfer customer interface”
- DataTransfer – Appendix 2 “Description of the ‘Create a Dispatch List‘ customer interface:“
- DataTransfer – Appendix 4 “Description of the ‘Address maintenance’ customer interface”
- DataTransfer – Appendix 5 “Description of the DataTransfer customer interface: ‘EAD submission (Electronic Advance Data) submission for international letter mail containing goods (PDF, 767.2 KB)”
5. Release Notes
5.1 Changes
- <Identcode> field now alphanumerical and various smaller additions and amendments
- Reports 15 and 16 updated
- Report 19 updated
- Implementation on microsite