KMU Plus

User navigation



Language navigation

KMU Plus

Close

KMU Plus

KMUplus differs from Print & Send solely in terms of the type of data delivery. After processing by the dispatcher, the processing steps in KMUplus and Print & Send are identical.

As a general principle, the information from the E-Post Print & Send user manual applies to use of KMUplus.

The specifications for KMUplus can be found here.

The major differences between KMUplus and Print & Send are listed below.

1 Input data

1.1 PDF data format

KMUplus only accepts PDF data.

The PDF must be supplied as PDF/A-1b. PDF format is required to ensure no issues arise during the subsequent steps, including sending to the E-Post Office inbox and printing.
The key points of the PDF/A-1b standard are:

  • Conformity with PDF version 1.4
  • All fonts must be embedded
  • The colour profile must be embedded if it is referenced
  • No encryption
  • No transparencies

The PDF format is described more precisely in ISO 19005-1.

All other data formats are rejected and an error message will be displayed.

Any payment slips may only be present on the last page of a document.

The addresses may not contain any PP lines as these will be set out by downstream systems.

The addresses must be set out at the following positions:

  • Address area address on left: left 24 mm, top 52 mm, width: 59 mm, height: 31 mm
  • Address area address on right: left 120 mm, top 52 mm, width: 59 mm, height: 31 mm

Orders must be correctly sorted:

  • All addresses in an order must be positioned in the same location.
  • If the order features payment slips, these must be of the same type.
  • If the order features payment slips, each document must contain a payment slip.

1.2 Address data in white line

White lines must be placed at the top of each document (where the address is located) to ensure secure processing.

White line area: left 0 mm, top 0 mm, width: 210 mm, height: 8 mm

The entire white lines must be positioned within the white line area.

No other elements may be placed within the white line area.

The colour of the white lines is irrelevant.

The font type or font size is irrelevant.

A maximum of 7 address lines are possible.

The white lines are removed during processing.

1.2.1 EXAMPLE

##AL1:John Sample## ##AL2:Sample road 1## ##AL3:9999 Sample town## ##AL4:Sample country## ##AL5:## ##AL6:## ##AL7:## 

1.3 Order metadata

The following metadata must be supplied to process KMUplus orders (* = only possible via KMUplus):

Attribute Characteristics
Franking A Mail*, B Mail*, A Mail Plus*, Registered (R)*, B Mail bulk mailing*
Category Invoice, Offer, Quotation, Information, Contract
Print type Simplex, Duplex
Envelope Blank C5, blank C4, automatic*
Window* right*, left*
Payment slip No inpayment slip, ES 105 CHF, ESR 609 CHF, ESR+ 609 CHF, Bank 303 CHF, ESR Bank 609 CHF, ESR+ Bank 609 CHF
Print option Printing by Swiss Post, PDF download
Signature No signature, Swiss Post signature
Subject Free text field (maximum length 64 characters)
Reply to Free text field (e-mail address mandatory)
Remark Free text field (maximum length 40 characters)

1.3.1 Automatic envelope

The same restrictions apply to automatic envelope allocation as for the individual envelopes.

The difference is that violations of the C5 envelope restrictions do not lead to cancellation but rather to a transfer to a C4 envelope.

For the “Envelope” = Automatic feature, the respective consignment is packed as follows:

Maximum C5 sheet = 14
  • Number of Simplex pages < 15 = C5
  • Number of Duplex pages < 29 = C5
Maximum C4 sheet = 80
  • Number of Simplex pages > 14 = C4
  • Number of Duplex pages > 28 = C4

If the feature is “Envelope” = Automatic, the number of pages per envelope is checked and the order is cancelled if the number is too high.

Maximum C4 sheet = 80
  • Simplex cancellation if the number of pages > 80
  • Duplex cancellation if the number of pages > 160

If the consignment is split, one order will become two orders in KMUplus. These can be viewed individually in order management.

1.3.2 B Mail bulk mailing

If “B Mail bulk mailing” is submitted as the franking for an order, a check will be performed to see how many consignments will be physically produced.

In the event of more than 349 physical consignments, the consignments will be franked and charged as a B Mail bulk mailing.

If there are fewer than 350 physical consignments, the consignments will be franked and charged as regular B Mail.

2 Interfaces

The data for KMUplus can be submitted as follows:

Interface Data input File formats
SFTP PDF with complete metadata in white text PDF
SFTP PDF with address data in white text and XML with metadata pdf, xml

2.1 SFTP

The interface used for automatic processing operations which are to be executed without a GUI functionality is SFTP. SFTP has an advantage over FTP in that the connection is encrypted and the credentials cannot be intercepted.

Authentication is performed via a public key (Specifies that a user name and service key provider are required to use this authentication method. All users have their own private key.)

2.1.1 Transmission errors

There is a distinction between 2 possible error groups.

  1. Connection problems
  2. File transfer failed

The error groups can result from various termination causes. The link below presents the various causes of termination.

List of possible SFTP error codes

The error messages are displayed differently during operations depending on the system used. The user will be shown a message directly if transferring manually via an SFTP client. In the case of automatic processing, the sending system is responsible for alerting the user about a failed connection or failed file transfer. If the system does not pass the message on to the user, log file monitoring would need to be set up.

2.1.2 Meta data in white line (PDF)

Only one PDF file is transmitted for this data delivery type. It is therefore necessary to pack this as a ZIP, but the customer is provided with the option of doing this. It is important that the PDF is located directly within the ZIP file and not within a folder inside the ZIP file. Furthermore, the ZIP file may not be password protected.

To facilitate traceability and support, the files must be named as follows:

  • PDF = KMUPLUS_SenderID_FreierText_timestamp.pdf
  • ZIP = KMUPLUS_SenderID_FreierText_timestamp.zip

The file names should only differ in terms of the file extension. The time stamp should have the following format: YYYYMMDDhhmm (201803281330)

To ensure the metadata can be read by KMUplus, it must be placed in a “white line”.

The position of the white line is underneath the coordinates shown below.

X = 0 Y = 0 width = 210 height = 8

Name Description Possible values Mandatory/optional field Mandatory/optional content
AL1 Address field 1 Free text field Mandatory Optional
AL2 Address field 2 Free text field Mandatory Optional
AL3 Address field 3 Free text field Mandatory Optional
AL4 Address field 4 Free text field Mandatory Optional
AL5 Address field 5 Free text field Mandatory Optional
AL6 Address field 6 Free text field Mandatory Optional
AL7 Address field 7 Free text field Mandatory Optional
CAT EPOF category, required for statistics 01 = invoice 02 = offer 03 = quotation 04 = information 06 = contract Mandatory Mandatory
DUP Simplex or Duplex printing false = Simplex true = Duplex Mandatory Mandatory
ENV Envelope type C5 = C5 envelope (up to 14 sheets) C4 = C4 envelope (up to 80 sheets) auto = automatic switch from C5 to C4 if sheets >14 Mandatory Mandatory
ADW Transparent window on envelope
left = transparent window left right = transparent window right Mandatory Mandatory
FRM Payment slip form on last page of the consignment 01 = No payment slip 02 = ES 105 CHF 03 = ESR 609 CHF 04 = ESR+ 609 CHF 05 = ES Bank 303 CHF 06 = ESR Bank 609 CHF 07 = ESR+ Bank 609 CHF Mandatory Mandatory
ANT Remark on e-letters sent (e.g. Important) Free text field (maximum length 40 characters) Mandatory Optional
RPY Response address for error messages and responses from recipients Free text field (e-mail address mandatory) Mandatory Mandatory
SBJ Subject of e-letters sent Free text field (maximum length 64 characters) Mandatory Mandatory
PCO Default setting of franking type B1 = B Mail B2 = B Mail bulk mailing (min. 350 consignments) A = Mail A+ = A Mail Plus R = Registered Mandatory Mandatory
PMO Print option Internal = printing by Swiss Post external = PDF download Mandatory Mandatory
SGN Signing of e-letters false = no signature true = Swiss Post signature Mandatory Mandatory
OFN Original file name Free text field Mandatory Mandatory
SID  Sender ID Customer number Mandatory Mandatory
Company ID no. Username Free text field (e-mail address mandatory) Mandatory Mandatory

There are seven fields available for the address. The sender is free to choose the position of the address within the 7 lines. However, at least 2 lines must be filled in. The sender must fill in the address in the following order to ensure the PDB can recognize the address:

  1. Title (optional)
  2. First name and last name (mandatory)
  3. Street and number (optional)
  4. Postcode and town (mandatory)

The individual features of the white text are separated by a double #. It is recommended that the white text be created with a font size of no more than 3pt. The existing white line will be removed during the subsequent preparation process (for digital mailing) or overwritten (for physical printing), which means the white line does not need to be white as its name would suggest but can instead be used with any colour.

2.1.2.1 EXAMPLE

##AL1:Mr## ##AL2:John Sample## ##AL3:Sample street11## ##AL4:8000 Sample city## ##AL5:Switzerland## ##AL6:## ##AL7:## ##CAT:01## ##DUP:false## ##ENV:C5## ##ADW:left## ##FRM:02##ANT:Important## ##RPY:epost@samplejohnag.com## ##SBJ:Here is a message## ##PCO:A+## ##PMO:internal## ##SGN:false## ##OFN:Testfile_all_meta_pdf.pdf## ##SID:21600011## ##UID:john.sample@samplejohnag.com##

2.1.3 Metadata as an XML

Since the XML file serves as a trigger, it is advisable to supply the data (PDF and XML) in a ZIP file. It is important that the two files are located directly within the ZIP file and not within a folder inside the ZIP file. Furthermore, the ZIP file may not be password protected.

To facilitate traceability and support easier, the files must be named as follows:

  • XML = KMUPLUS_SenderID_FreierText_timestamp.xml
  • PDF = KMUPLUS_SenderID_FreierText_timestamp.pdf
  • ZIP = KMUPLUS_SenderID_FreierText_timestamp.zip

The file names should only differ in terms of the file extension. The time stamp should have the following format: YYYYMMDDhhmm (201803281330)

If the sender is unable to pack the two files in a ZIP file, they can also be transferred separately. If this option is chosen, the PDF file must be fully transferred before transferring the XML file.

Below is an example of an XML file showing how the metadata must be submitted. An XSD was created to validate the XML. The XML file was deliberately kept simple, which means the XSD can only validate whether the values used correspond to the field type.

Here is a table listing the metadata which can be set by the sender with the corresponding values:

Name Description Possible values Mandatory/optional
category EPOF category, required for statistics 01 = invoice 02 = offer 03 = quotation 04 = information 06 = contract Mandatory
duplex Simplex or Duplex printing false = Simplex true = Duplex Mandatory
envelope Envelope type C5 = C5 envelope (up to 14 sheets) C4 = C4 envelope (up to 80 sheets) auto = automatic switch from C5 to C4 if sheets >14 Mandatory
addressWindow Transparent window on envelope left = transparent window left right = transparent window right Mandatory
form Payment slip form on last page of the consignment 01 = No payment slip 02 = ES 105 CHF 03 = ESR 609 CHF 04 = ESR+ 609 CHF 05 = ES Bank 303 CHF 06 = ESR Bank 609 CHF 07 = ESR+ Bank 609 CHF Mandatory
mailAnnotition Remark on e-letters sent (e.g. Important) Free text field (maximum length 40 characters) Optional
mailReplyTo Response address for error messages and responses from recipients Free text field (e-mail address mandatory) Mandatory
mailSubject Subject of e-letters sent Free text field (maximum length 64 characters) Mandatory
postalCode Default setting of franking type B1 = B Mail B2 = B Mail bulk mailing (min. 350 consignments) A = Mail A+ = A Mail Plus R = Registered Mandatory
printMode Print option Internal = printing by Swiss Post external = PDF download Mandatory
signing Signing of e-letters false = no signature true = Swiss Post signature Mandatory
originalFileName Original file name Free text field Mandatory
senderid Sender ID Free text field (length 8 characters) Mandatory
userid Username Free text field (e-mail address mandatory) Mandatory

2.1.3.1 EXAMPLE XML

XML

<?xml version="1.0" encoding="UTF-8"?> 
<SPS>
  <Processing>
   <category>01</category>
   <duplex>false</duplex>
   <envelope>C5</envelope>
   <addressWindow>left</addressWindow>
   <form>03</form> 
  <mailAnnotation>Wichtig</mailAnnotation>
   <mailReplyTo>hans.muster@mail.com</mailReplyTo>
   <mailSubject>Ihre Rechnung</mailSubject>
   <postalCode>A</postalCode>
   <printMode>internal</printMode>
   <signing>false</signing>
   <originalFileName>Rechnung_Hans_Muster.pdf</originalFileName>
  </Processing>
  <Sender>
   <senderId>00100443</senderId>
   <userId>susi.muster@mail.com</userId>
  </Sender>
</SPS>

2.1.3.2 EXAMPLE XSD to validate the XML

XSD

<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="SPS">
<xs:complexType>
<xs:sequence>
<xs:element name="Processing">
<xs:complexType>
<xs:sequence>
<xs:element name="category">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="01"/>
<xs:enumeration value="02"/>
<xs:enumeration value="03"/>
<xs:enumeration value="04"/>
<xs:enumeration value="06"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element type="xs:boolean" name="duplex"/>
<xs:element name="envelope">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="C5"/>
<xs:enumeration value="C4"/>
<xs:enumeration value="auto"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="addressWindow">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="form">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="01"/>
<xs:enumeration value="02"/>
<xs:enumeration value="03"/>
<xs:enumeration value="04"/>
<xs:enumeration value="05"/>
<xs:enumeration value="06"/>
<xs:enumeration value="07"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="mailAnnotation" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="40"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="mailReplyTo">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="([.a-zA-Z0-9_-])+@([a-zA-Z0-9_-])+(([a-zA-Z0-9_-])*.([a-zA-Z0-9_-])+)+"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="mailSubject">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="80"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="postalCode">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="A"/>
<xs:enumeration value="A+"/>
<xs:enumeration value="B1"/>
<xs:enumeration value="B2"/>
<xs:enumeration value="R"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="printMode">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="internal"/>
<xs:enumeration value="external"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element type="xs:boolean" name="signing"/>
<xs:element type="xs:string" name="originalFileName"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Sender">
<xs:complexType>
<xs:sequence>
<xs:element name="senderId">
<xs:simpleType>
<xs:restriction base="xs:integer">
<xs:pattern value="[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="userId">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="([.a-zA-Z0-9_-])+@([a-zA-Z0-9_-])+(([a-zA-Z0-9_-])*.([a-zA-Z0-9_-])+)+"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

3 Validation

3.1 Validation of file format and readability (steps 1 & 2)

The file format and readability of the submitted documents are validated for all delivery methods.

The permitted file types are PDF and XML (depending on the delivery method).

3.2 Validation of address completeness

The number of address fields filled in is checked per consignment for each delivery.

Validation is successful if at least 2 address fields are completed. This process does not encompass validating the content.

3.3 Validation of metadata completeness

The metadata fields will be verified for every consignment or order (depending on the delivery method).

Validation is successful if all the metadata fields are complete (both mandatory and optional fields).

Field SFTP Meta PDF SFTP PDF with XML
Category CAT category
Duplex DUP duplex
Envelope type ENV envelope
Transparent window on envelope ADW addressWindow
Payment slip form FRM form
Remark ANT mailAnnotation
Reply-to address RPY mailReplyTo
Subject SBJ mailSubject
Type of franking PCO postalCode
Print option PMO printMode
Signature SGN signing
Original file name OFN originalFileName
Sender ID SID senderId
User ID UID userId
Address line 1 AL1 -
Address line 2 AL2 -
Address line 3 AL3 -
Address line 4 AL4 -
Address line 5 AL5 -
Address line 6 AL6 -
Address line 7 AL7 -
Other fields for SFTP XML
- -

3.4 Validation of metadata content

The metadata content will be verified for every consignment or order (depending on the delivery method).

For metadata fields without any selection options, the content will be verified for syntax or length.

For metadata fields which need to feature a unique value across all consignments, verification is performed to ascertain whether this has been observed.

Validation is successful if all metadata fields only contain permitted values and, if required, that these are unique.

Field
SFTP Meta PDF SFTP PDF with XML Permitted values Value unique
Category CAT category 01 02 03 04 06 Yes
Duplex DUP duplex false true Yes
Envelope type ENV envelope C5 C4 auto Yes
Transparent window on envelope ADW addressWindow left right Yes
Payment slip form FRM form 01 02 03 04 05 06 07 Yes
Remark ANT mailAnnotation Free test field -> maximum length 40 characters Yes
Reply-to address RPY mailReplyTo E-mail address -> verification of e-mail syntax Yes
Subject SBJ mailSubject Free text field -> maximum length ?? Characters Yes
Type of franking PCO postalCode A B1 B2 A+ R Yes 
Print option PMO printMode internal external Yes
Signature SGN signing false true Yes
Original file name OFN originalFileName Free text field Yes
Sender ID SID senderId Number field -> length of 8 characters Yes
User ID UID userId E-mail address -> verification of e-mail syntax Yes
Address line 1 AL1 - Free text field No
Address line 2 AL2 - Free text field No
Address line 3 AL3 - Free text field No
Address line 4 AL4 - Free text field No
Address line 5 AL5 - Free text field No
Address line 6 AL6 - Free text field No
Address line 7 AL7 - Free text field No
Other fields for SFTP XML - - tbd tbd

3.5 Validation of pages’ clearance zone

Each page of the order is checked to ascertain whether content is located in the clearance zones.

Validation is successful if the page’s clearance zones have not been breached, i.e. no content is contained within the clearance zones.

Clearance zone Position x Position y Width Height
Upper edge 0 0 210 3
Lower edge 0 294 210 3
Left edge 0 0 3 297
Right edge 207 0 3 297
PTL sticker 0 139 10 20
Direct mailing envelope 0 277 15 20
Technical line 0 287 58 10

3.6 Validation of addresses’ clearance zone

A check is performed on all first pages of a consignment to ensure there is no content in the address’s clearance zone. The transparent window feature on the envelope (addressWindow, ADW) is used to determine whether the corresponding clearance zones are on the left or right.

Validation is successful if there is no content in the clearance zone.

The clearance zone is located at the following coordinates:

Clearance zone Position x Position y Width Height
Address left (upper area) 21 38 86 14
Address left (right area) 83 52 25 32
Address right (upper area) 117 38 86 14
Address right (right area) 179 52 25 32

The address itself is located at the following coordinates:

Address area Position x Position y Width Height
Address left 22 52 61 31
Address right 118 52 61 31

3.7 Validation of inpayment slip clearance zone (optional)

Verification only takes place if a value other than “01” appears in the metadata field form (FRM). If there is a different value, verification is performed to see whether there is content in the clearance zones. Verification only takes place on the respective last page of a consignment.

3.8 Validation criteria

Validation is successful if there is no breach of a clearance zone. Below you will find the exact specifications of inpayment slip clearance zones.

Blocked zones in payment slips
## This is where the inpayment slips can be defined
## The values are to be given in mm and separated by a semicolon “;”
## n values can be defined for 3 forms:
## SZ-ESR-1 to SZ-ESR-n ## SZ-ESRplus-1 to SZ-ESRplus-n
## SZ-ES-1 to SZ-ES-n
##
## X; Y; WIDTH; HEIGHT; LEFT / RIGHT / TOP / BOTTOM
SZ-ES-1=1.80;198.50;57.60;29.50;1.80mm/2.00mm/10.50mm/1.50mm
SZ-ES-2=63.40;198.50;56.40;29.50;2.00mm/90.20mm/10.50mm/1.50mm
SZ-ES-3=25.20;231.00;34.00;7.00;25.20mm/13.10mm/1.50mm/22.00mm
SZ-ES-4=85.80;231.00;34.00;7.00;13.10mm/90.20mm/1.50mm/22.00mm
SZ-ES-5=63.40;275.83;138.98;4.23;63.40mm/7.62mm/15.93mm/2.12mm
SZ-ES-6=124.10;284.30;78.28;4.23;124.10mm/7.62mm/2.12mm/8.47mm

SZ-ESR-1=1.80;198.50;57.60;29.50;1.80mm/2.00mm/10.50mm/1.50mm
SZ-ESR-2=63.40;198.50;56.40;29.50;2.00mm/2.15mm/10.50mm/1.50mm
SZ-ESR-3=124.10;222.92;82.90;7.08;2.15mm/3mm/34.92mm/3.78mm
SZ-ESR-4=25.40;231.00;34.00;7.00;25.40mm/13.20mm/1.50mm/1.50mm
SZ-ESR-5=85.80;231.00;34.00;7.00;13.20mm/2.15mm/1.50mm/1.50mm
SZ-ESR-6=1.80;240.00;41.10;6.75;1.80mm/2.00mm/1.00mm/2.28mm
SZ-ESR-7=47.90;240.00;10.40;6.75;3.00mm/2.05mm/1.00mm/2.28mm
SZ-ESR-8=63.40;240.00;41.10;6.75;3.05mm/1.50mm/2.00mm/25.21mm
SZ-ESR-9=108.50;240.00;10.20;6.75;2.50mm/2.20mm/2.00mm/25.21mm
SZ-ESR-10=124.10;236.55;80.28;33.55;3.20mm/5.62mm/2.78mm/2.87mm
SZ-ESR-11=1.80;250.30;57.60;26.40;1.80mm/0.95mm/1.28mm/20.30mm
SZ-ESR-12=63.40;275.83;138.98;4.23;3.05mm/7.62mm/3.87mm/16.94mm

SZ-ESRplus-1=1.80;198.50;57.60;29.50;1.80mm/2.00mm/10.50mm/1.50mm
SZ-ESRplus-2=63.40;198.50;56.40;29.50;2.00mm/2.15mm/10.50mm/1.50mm
SZ-ESRplus-3=124.10;222.92;82.90;7.08;2.15mm/3mm/34.92mm/3.78mm
SZ-ESRplus-4=25.40;231.00;34.00;7.00;25.40mm/2.85mm/1.50mm/12.3mm
SZ-ESRplus-5=85.80;231.00;34.00;7.00;24.20mm/2.15mm/1.50mm/37.83mm
SZ-ESRplus-6=124.10;236.55;80.28;33.55;3.20mm/5.62mm/2.78mm/2.87mm
SZ-ESRplus-7=1.80;250.30;57.60;26.40;1.80mm/4.00mm/1.28mm/20.30mm
SZ-ESRplus-8=63.40;275.83;138.98;4.23;3.05mm/7.62mm/3.87mm/16.94mm

SZ-BES-1=1.80;198.50;57.60;9.60;1.80mm/2.00mm/10.50mm/1.35mm
SZ-BES-2=1.80;210.80;57.60;17.20;1.80mm/2.00mm/1.35mm/1.50mm
SZ-BES-3=63.40;198.50;56.40;9.60;2.00mm/90.20mm/10.50mm/1.35mm
SZ-BES-4=63.40;210.80;56.40;17.20;2.00mm/90.20mm/1.35mm/1.50mm
SZ-BES-5=25.20;231.00;34.00;7.00;25.20mm/13.10mm/1.50mm/22.00mm
SZ-BES-6=85.80;231.00;34.00;7.00;13.10mm/90.20mm/1.50mm/22.00mm
SZ-BES-7=63.40;275.83;138.98;4.23;63.40mm/7.62mm/15.93mm/2.12mm
SZ-BES-8=124.10;284.30;78.28;4.23;124.10mm/7.62mm/2.12mm/8.47mm

SZ-BESR-1=1.80;198.50;57.60;9.60;1.80mm/2.00mm/10.50mm/1.35mm
SZ-BESR-2=1.80;210.80;57.60;17.20;1.80mm/2.00mm/1.35mm/1.50mm
SZ-BESR-3=63.40;198.50;56.40;9.60;2.00mm/2.15mm/10.50mm/1.35mm
SZ-BESR-4=63.40;210.80;56.40;17.20;2.00mm/2.15mm/1.35mm/1.50mm
SZ-BESR-5=124.10;222.92;82.90;7.08;2.15mm/3mm/34.92mm/3.78mm
SZ-BESR-6=25.40;231.00;34.00;7.00;25.40mm/13.20mm/1.50mm/1.50mm
SZ-BESR-7=85.80;231.00;34.00;7.00;13.20mm/2.15mm/1.50mm/1.50mm
SZ-BESR-8=1.80;240.00;41.10;6.75;1.80mm/2.00mm/1.00mm/2.28mm
SZ-BESR-9=47.90;240.00;10.40;6.75;3.00mm/2.05mm/1.00mm/2.28mm
SZ-BESR-10=63.40;240.00;41.10;6.75;3.05mm/1.50mm/2.00mm/25.21mm
SZ-BESR-11=108.50;240.00;10.20;6.75;2.50mm/2.20mm/2.00mm/25.21mm
SZ-BESR-12=124.10;236.55;80.28;33.55;3.20mm/5.62mm/2.78mm/2.87mm
SZ-BESR-13=1.80;250.30;57.60;26.40;1.80mm/0.95mm/1.28mm/20.30mm
SZ-BESR-14=63.40;275.83;138.98;4.23;3.05mm/7.62mm/3.87mm/16.94mm

SZ-BESRplus-1=1.80;198.50;57.60;9.60;1.80mm/2.00mm/10.50mm/1.35mm
SZ-BESRplus-2=1.80;210.80;57.60;17.20;1.80mm/2.00mm/1.35mm/1.50mm
SZ-BESRplus-3=63.40;198.50;56.40;9.60;2.00mm/2.15mm/10.50mm/1.35mm
SZ-BESRplus-4=63.40;210.80;56.40;17.20;2.00mm/2.15mm/1.35mm/1.50mm
SZ-BESRplus-5=124.10;222.92;82.90;7.08;2.15mm/3mm/34.92mm/3.78mm
SZ-BESRplus-6=25.40;231.00;34.00;7.00;25.40mm/2.85mm/1.50mm/12.3mm
SZ-BESRplus-7=85.80;231.00;34.00;7.00;24.20mm/2.15mm/1.50mm/37.83mm
SZ-BESRplus-8=124.10;236.55;80.28;33.55;3.20mm/5.62mm/2.78mm/2.87mm
SZ-BESRplus-9=1.80;250.30;57.60;26.40;1.80mm/4.00mm/1.28mm/20.30mm
SZ-BESRplus-10=63.40;275.83;138.98;4.23;3.05mm/7.62mm/3.87mm/16.94mm

3.9 Validation of number of sheets per envelope

All consignments within an order are verified in terms of the number of pages, the envelope (ENV) selected on this basis, and the Duplex (duplex, DUP) setting.
Validation is successful if:

Envelope value Number of Simplex pages Number of Duplex pages
C5 <=14 <=28
C4 <=80 <=160
auto <=80 <=160

3.10 Validation of franking licenses for A Mail Plus and Registered

Verification only takes place if the sender selected either A Mail Plus or Registered for the franking type (postalCode, PCO). If these two franking types are selected, a check is performed to see whether the sender possesses the corresponding franking license. fralizprint-aplus for A Mail Plus and fralizprint-registered for Registered.

3.11 Error messages

The customer will be notified of a validation error by e-mail:

  1. An error message is sent to the customer’s reply-to address by e-mail
  2. The basis of the error is indicated in the e-mail and described
  3. The error message can optionally be sent via SFTP
  4. The processing procedure is cancelled