PEPPOL T013 - Tender Withdrawal 1.1

The PEPPOL Business Interoperability Specification, “BIS” from here on after, has been developed by the OpenPEPPOL AISBL Pre Award Coordinating Community and is published as part of the PEPPOL specifications.

Statement of copyright

This PEPPOL Business Interoperability Specification (BIS) document is based on the CEN CWA prepared by the BII workshop specified in the introduction below. The original CEN CWA document contains the following copyright notice which still applies:

The CEN CWA documents and profiles prepared by the BII workshop are not specific to a business area. Subject to agreement with CEN, customizations have been made by PEPPOL to establish the PEPPOL BIS, detailing and adding further guidance on the use of BII profiles.

OpenPEPPOL AISBL holds the copyright in the customizations made to the original document. The customizations appear from the corresponding conformance statement which is attached to this document. For the purpose of national implementations, customizations covered by the conformance statement may be further refined and detailed by PEPPOL Authorities and/or other entities authorized by OpenPEPPOL AISBL, provided that interoperability with PEPPOL BIS is ensured. This PEPPOL BIS document may not be modified, re-distributed, sold or repackaged in any other way without the prior consent of CEN and/or OpenPEPPOL AISBL.

1. Principle and prerequisites

1.1. Scope

This guide aims to provide insight into transaction details for the transaction model T013 - Tender Withdrawal 1.1. The transaction description is meant to be a standalone description to be used as a part of one or more procurement profiles. It describes syntax mappings, requirements, rules and example.

The transactions, specified in this document are intended to be exchanged between the tendering systems of economic operators and contracting bodies. This means that it is expected that the parties have connected their systems to the internet, and that they have middleware in place to enable them to send and receive the transactions in a secure way, using an agreed syntax.

The content model of the transactions can also be used in procurement platforms or notification platforms, so that these platforms as well as procurement systems of economic operators and contracting bodies are based on the same information and process models, which makes them more interoperable. Even if platforms are not technically interoperable, the content model facilitates understanding the tendering documents and to participate in the tendering process.

1.2. Parties and roles

The following parties participate as business partners in this transaction, acting in the roles as defined below

Table 1. parties
Party	Description	Example of roles
Customer	The customer is the legal person or organization who is in demand of a product, service or works.	Buyer, consignee, debtor, contracting body
Supplier	The supplier is the legal person or organization who provides a product, service or works.	Seller, consignor, creditor, economic operator

Table 2. roles
Role	Description
Contracting body	The contracting authority or contracting entity who is buying supplies, services or tendering works.
Economic operator	Party participating with a bid in a procurement process to sell goods, services or works.

2. Transaction business and information requirements

The following tables describe the transaction business and information requirements of "T013 - Tender Withdrawal 1.1", it inherits from CEN WS/BII 3 "Trdm045 - Tender Withdrawal transaction".

The transaction "T013 - Tender Withdrawal 1.1" must be sent to the contracting authority when the economic operator has submitted a tender and decided to withdraw the tender. After "T013 - Tender Withdrawal 1.1", the bid of the Economic Operator is not evaluated. The tender may be resubmitted if the submission deadline has not passed.

Please note that the transaction "T013 - Tender Withdrawal 1.1" has to be sent to contracting authorities when an existing tender is withdrawn. The "T013 - Tender Withdrawal 1.1" for an existing Tender (T005) can be sent before or after submitting an updated Tender (T005). After the submission of a new Tender (T005) the old tender should be withdrawn with the "T013 - Tender Withdrawal 1.1" .

Table 3. Transaction business requirements of T013 - Tender Withdrawal 1.1
ID	Requirement
tbr89-001	The business process, specification names and versions shall be identified.
tbr89-002	The economic operator shall be identified.
tbr89-003	The contracting body shall be identified.
tbr89-004	The creation date and time of the message shall be specified.
tbr89-005	Each message shall have a message ID.
tbr89-006	The message shall contain the Procurement Reference number.
tbr89-007	The message shall contain either credentials issued by the Contracting Body, or the following information about the business: Economic operator ID type Economic operator name Economic operator registration country code Economic operator postal address (standard address elements) Contacting details (standard contact person elements)
tbr89-008	The message shall contain the following information about the qualification or tender: ID Hash signature
tbr89-009	The message shall contain the ID of the Tender Reception Notification.
tbr89-011	The message shall clearly state the Economic Operator wants to withdraw the offer.

3. Data model: Syntax mapping and XML example

3.1. Data model and syntax mapping

The data model and syntax mapping for Tender Withdrawal can be found at Syntax mapping for T013 - Tender Withdrawal 1.1. The data model and syntax mapping explains how to use the UBL (or an underlying syntax) to support the Tender Withdrawal information transaction requirements. It provides the syntax mappings from each UBL (or syntax) element to the Tender Withdrawal information elements of this transaction.

3.2. XML example

The following XML example illustrates the structure of an instance of T013 - Tender Withdrawal 1.1.

Link to example file

Example file for T013 - Tender Withdrawal 1.1

<?xml version="1.0" encoding="UTF-8" ?>
<TenderWithdrawal
        xmlns="urn:oasis:names:specification:ubl:schema:xsd:TenderWithdrawal-2"
        xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
        xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="
                urn:oasis:names:specification:ubl:schema:xsd:TenderWithdrawal-2
                http://docs.oasis-open.org/ubl/cs01-UBL-2.2/xsd/maindoc/UBL-TenderWithdrawal-2.2.xsd
                urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2
                http://docs.oasis-open.org/ubl/os-UBL-2.2/xsdrt/common/UBL-CommonBasicComponents-2.2.xsd
                urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2
                http://docs.oasis-open.org/ubl/os-UBL-2.2/xsdrt/common/UBL-CommonAggregateComponents-2.2.xsd">
    <cbc:UBLVersionID>2.2</cbc:UBLVersionID>
    <cbc:CustomizationID>urn:fdc:peppol.eu:prac:trns:t013:1.1</cbc:CustomizationID> (1)
    <cbc:ProfileID>urn:fdc:peppol.eu:prac:bis:p007:1.1</cbc:ProfileID> (2)
    <cbc:ID schemeURI="urn:uuid">78068F50-6696-4F44-B6FB-A8A43DA04A53</cbc:ID> (3)
    <cbc:ContractFolderID>CA2B5B8C-61A5-4797-8E27-47D7D22EAC29</cbc:ContractFolderID> (4)
    <cbc:IssueDate>2021-02-12</cbc:IssueDate> (5)
    <cbc:IssueTime>00:00:00Z</cbc:IssueTime> (6)
    <cbc:WithdrawOfferIndicator>true</cbc:WithdrawOfferIndicator> (7)
    <cac:TenderDocumentReference>
        <cbc:ID schemeURI="urn:uuid">243A177F-E4E9-4FC8-B97E-BB1A950DD8F8</cbc:ID> (8)
        <cac:Attachment>
            <cac:ExternalReference>
                <cbc:DocumentHash>72182B98A9DAB9A553CCF161EA049D41337E51DFDF74DDC8AB7B68E7CFFB7D1B</cbc:DocumentHash> (9)
                <cbc:HashAlgorithmMethod>http://www.w3.org/2001/04/xmlenc#sha256</cbc:HashAlgorithmMethod> (10)
            </cac:ExternalReference>
        </cac:Attachment>
    </cac:TenderDocumentReference>
    <cac:TenderNotificationDocumentReference>
        <cbc:ID schemeURI="urn:uuid">49af1fe0-c0af-4a98-8ffa-309408f9cfac</cbc:ID> (11)
    </cac:TenderNotificationDocumentReference>
    <cac:ContractingParty>
        <cac:Party>
            <cbc:EndpointID schemeID="9930">DE122268496</cbc:EndpointID> (12)
            <cac:PartyIdentification> (13)
                <cbc:ID schemeID="0204">991-1234512345-06</cbc:ID> (14)
            </cac:PartyIdentification>
            <cac:PartyName>
                <cbc:Name>Beschaffungsamt des BMI</cbc:Name> (15)
            </cac:PartyName>
        </cac:Party>
    </cac:ContractingParty>
    <cac:TendererParty>
        <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (16)
        <cac:PartyIdentification>
            <cbc:ID schemeID="0088">7300010000001</cbc:ID> (17)
        </cac:PartyIdentification>
        <cac:PartyName>
            <cbc:Name>Aankoopbureau</cbc:Name> (18)
        </cac:PartyName>
        <cac:PostalAddress> (19)
            <cbc:StreetName>Hauptstraße 54</cbc:StreetName> (20)
            <cbc:AdditionalStreetName>Eingang über Nebenstraße</cbc:AdditionalStreetName> (21)
            <cbc:CityName>Berlin</cbc:CityName> (22)
            <cbc:PostalZone>12045</cbc:PostalZone> (23)
            <cbc:CountrySubentity>Berlin</cbc:CountrySubentity> (24)
            <cac:Country> (25)
                <cbc:IdentificationCode>DE</cbc:IdentificationCode> (26)
           </cac:Country>
        </cac:PostalAddress>
        <cac:Contact> (27)
            <cbc:Name>Maximilian Mustermann</cbc:Name> (28)
            <cbc:Telephone>+49 231 7000-7000</cbc:Telephone> (29)
            <cbc:Telefax>+49-711-9876543</cbc:Telefax> (30)
            <cbc:ElectronicMail>max.mustermann@example.com</cbc:ElectronicMail> (31)
        </cac:Contact>
    </cac:TendererParty>
</TenderWithdrawal>

4. Code lists

Any element with the semantic data type = code, can mandate the use of a specific code list (or a fixed value). The applicable code lists can be found in the Code list section. In this section, you can find the valid codes, their names and description, and also links to where the same code list is used elsewhere in the transaction, or in other PEPPOL BIS transactions.

Information elements that are ruled by codelists in this transaction are also described in the Syntax mapping for Tender Withdrawal: Syntax mapping for T013 - Tender Withdrawal 1.1

The following code lists for coded elements and identifier schemes are used by the transaction.

4.1. Code list for identifier schemes

Table 4. Code list for identifier schemes
Business Term	Allowed Scheme	Applicable Xpath
Economic operator electronic address identifier	schemeID attribute is mandatory and must use values from EAS codes	cac:RequestorParty/cbc:EndpointID/@schemeID
Contracting body electronic address identifier	schemeID attribute is mandatory and must use values from EAS codes	cac:ResponderParty/cbc:EndpointID/@schemeID
Economic operator identifier	schemeID attribute is mandatory and must use values from ICD codes	cac:RequestorParty/cac:PartyIdentification/cbc:ID/@schemeID
Contracting body identifier	schemeID attribute is mandatory and must use values from ICD codes	cac:ResponderParty/cac:PartyIdentification/cbc:ID/@schemeID

5. PEPPOL Identifiers

PEPPOL has defined a Policy for use of Identifiers that specifies how to use identifiers in both its transport infrastructure and within the documents exchanged across that infrastructure. It also introduces principles for any identifiers used in the PEPPOL environment. The e-Tendering pilot adopts and extends the PEPPOL Policy in the following ways:

5.1. Party Identifiers used in business (UBL) documents

All party identifiers (cac:PartyIdentification/cbc:ID) have an optional scheme identifier attribute '@schemeID'. If used, the value shall be chosen from the code list ICD codes.

Examples of usage in cac:PartyIdentification

<cac:PartyIdentification>
        <cbc:ID schemeID="0088">5790000435968</cbc:ID> (1)
</cac:PartyIdentification>

1	schemeID attribute is optional, but when used, the codes must be from ICD codes

5.2. Electronic address identifier used in business (UBL) documents

All electronic address identifiers (cbc:EndpointID/@schemeID) use the Electronic Address Scheme code list (EAS), maintained by CEF (CEF Code lists).

Valid values are found here: EAS codes.

Examples of usage in cbc:EndpointID

<cbc:EndpointID schemeID="0184">DK87654321</cbc:EndpointID> (1)

1	schemeID attribute is mandatory and must use values from EAS codes

5.3. Document Identifiers used in business (UBL) documents

5.3.1. UBL Version ID

This transaction model is using the UBL 2.2 syntax. The namespace of the XML-message does only communicate the major version number. Since it is important for the receiver to also know what minor version of the syntax that is used, the element UBLVersionID must be stated with the value 2.2:

Examples of usage in PartyIdentification and EndpointID

<cbc:UBLVersionID>2.2</cbc:UBLVersionID>

5.3.2. Profile ID

ProfileID identifies what business process a given message is part of, and are connected to one business process, and may contain multiple document types.

Valid profile identifiers are described in the Syntax mapping for Tender Withdrawal - Syntax mapping for T013 - Tender Withdrawal 1.1 - and the corresponding BIS document, see Main documentation site.

5.3.3. Customization ID

The PEPPOL Customization ID identifies the specification of content and rules that apply to the transaction. Profiles are connected to one business process (ProfileID), and may contain multiple transactions. Valid document instances shall contain corresponding ProfileID and CustomizationID.

CustomizationID is a string without spaces. Which customization identification should be used, is based on which transaction is sent.

For implementers, please note that the process identifiers in the document instance MUST correspond to the SMP process identifier.

Table 5. Customization ID to be used for this transaction.
TransactionID	Transaction name	Short Description	`cbc:CustomizationID`
T013	Tender Withdrawal	The EO sends the Tender Withdrawal to the CA.	urn:fdc:peppol.eu:prac:trns:t013:1.1

6. Description of selected parts of the transaction

The transaction including business terms, business rules and code lists are based upon the definitions of "Trdm045 - Tender Withdrawal transaction" described in "Profile 53 — Tender Withdrawal" (CWA 17027-118:2016).

6.1. Process control

6.1.1. Specification identification

Identifier for the set of rules and transactions for the Tender Withdrawal Reception Notification.

<cbc:CustomizationID>urn:fdc:peppol.eu:prac:trns:t013:1.1</cbc:CustomizationID> (1)

1	The value for the specification identification is always "urn:fdc:peppol.eu:prac:trns:t013:1.1".

6.1.2. Business Process Type Identifier

Identifier for the business process context of the Tender Withdrawal Reception Notification.

<cbc:ProfileID>urn:fdc:peppol.eu:prac:bis:p007:1.1</cbc:ProfileID> (1)

1	The value for the business process type identifier is always "urn:fdc:peppol.eu:prac:bis:p007:1.1".

6.2. Document References

6.2.1. Document identifier

Identifier of the Tender Withdrawal Reception Notification itself.

<cbc:ID schemeURI="urn:uuid">78068F50-6696-4F44-B6FB-A8A43DA04A53</cbc:ID> (1)

1	The Document Identifier must be expressed in a UUID syntax (RFC 4122), as stated it has to be stated in the schemeURI.

6.2.2. Reference Number

An identifier that is specified by the buyer and used as a reference number for all documents in the procurement process. It is also known as procurement project identifier, procurement reference number or contract folder identifier. In UBL the reference number is represented by the ContractFolderID.

<cbc:ContractFolderID>CA2B5B8C-61A5-4797-8E27-47D7D22EAC29</cbc:ContractFolderID> (1)

1	The Reference Number must be expressed in a UUID syntax (RFC 4122).

6.2.3. Tender Document Reference

The tender reception notification contains the reference to the tender document sent by the economic operator. The contracting authority should refer to the tender by using the document hash, and the hash algorithm method used.

Tender document reference ID

<cac:TenderDocumentReference>
    <cbc:ID schemeURI="urn:uuid">243A177F-E4E9-4FC8-B97E-BB1A950DD8F8</cbc:ID> (1)

1	DocumentReference Identifier for a Call for Tender Reference must be expressed in a UUID syntax (RFC 4122).

Document hash algorithm

<cac:Attachment>
    <cac:ExternalReference>
        <cbc:DocumentHash>72182B98A9DAB9A553CCF161EA049D41337E51DFDF74DDC8AB7B68E7CFFB7D1B</cbc:DocumentHash> (1)
        <cbc:HashAlgorithmMethod>http://www.w3.org/2001/04/xmlenc#sha256</cbc:HashAlgorithmMethod> (2)
    </cac:ExternalReference>
</cac:Attachment>

1	Document digest of a tender document. Used as a reference to the tender document to be withdrawn.
2	Document hash algorithm must be "http://www.w3.org/2001/04/xmlenc#sha256".

6.2.4. Tender Notification Document Reference

Identifier of the tender reception notification message.

<cac:TenderNotificationDocumentReference>
    <cbc:ID schemeURI="urn:uuid">49af1fe0-c0af-4a98-8ffa-309408f9cfac</cbc:ID> (1)
</cac:TenderNotificationDocumentReference>

1	Tender Notification Document Reference for a Call for Tender Reference must be expressed in a UUID syntax (RFC 4122).

6.3. Parties

6.3.1. Contracting Body

The contracting authority or contracting entity who is buying supplies, services or public works using a tendering procedure as described in the applicable directive (Directives 2014/24/EU, 2014/25/EU).

Contracting Body is represented in UBL 2.2 using Contracting Party:

<cac:ContractingParty>
    <cac:Party>
        <cbc:EndpointID schemeID="9930">DE122268496</cbc:EndpointID> (1)
        <cac:PartyIdentification> (2)
            <cbc:ID schemeID="0204">991-1234512345-06</cbc:ID> (3)
        </cac:PartyIdentification>
        <cac:PartyName>
            <cbc:Name>Beschaffungsamt des BMI</cbc:Name> (4)
        </cac:PartyName>
    </cac:Party>
</cac:ContractingParty>

1	At first the EndpointID with its schemeID has to be clarified. The schemeID is a mandatory attribute of the EndpointID and has to be chosen according to the EndpointID.
2	Following the EndpointID the Identification of the Party has to be given in the same manner.
3	The same value as in the EndpointID also the EndpointID has to be given into the ID and the corresponding attribute for the schemeID.
4	Additional to the Party Identification the Party Name has to be given, as it is registered.

6.3.2. Economic Operator

Any natural or legal person or public entity or group of such persons and/or entities, including any temporary association of undertakings, which offers the execution of works and/or a work, the supply of products, or the provision of services on the market.

The Economic Operator is represented in UBL 2.2 using the Tenderer Party:

<cac:TendererParty>
    <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (1)
    <cac:PartyIdentification>
        <cbc:ID schemeID="0088">7300010000001</cbc:ID> (2)
    </cac:PartyIdentification>
    <cac:PartyName>
        <cbc:Name>Aankoopbureau</cbc:Name> (3)
    </cac:PartyName>
    <cac:PostalAddress> (4)
        <cbc:StreetName>Hauptstraße 54</cbc:StreetName> (5)
        <cbc:AdditionalStreetName>Eingang über Nebenstraße</cbc:AdditionalStreetName> (6)
        <cbc:CityName>Berlin</cbc:CityName> (7)
        <cbc:PostalZone>12045</cbc:PostalZone> (8)
        <cbc:CountrySubentity>Berlin</cbc:CountrySubentity> (9)
        <cac:Country> (10)
            <cbc:IdentificationCode>DE</cbc:IdentificationCode> (11)
       </cac:Country>
    </cac:PostalAddress>

1	Electronic address of the economic operator. At first the EndpointID with its schemeID has to be clarified. The schemeID is an attribute of the EndpointID and has to be chosen according to the EndpointID.
2	Following the EndpointID the Identification of the Party has to be given in the same manner.
3	Additional to the Party Identification the Party Name has to be given.
4	Furthermore, the PostalAdress of the Economic operator can be given.
5	The main address line in an address. Usually the street name and number or post office box.
6	An additional address line in an address that can be used to give further details supplementing the main line.
7	The common name of a city where the address is located.
8	The identifier for an addressable group of properties according to the relevant postal service, such as a ZIP code or Post Code.
9	The subdivision of a country such as region, county, state, province etc.
10	Country tag for the Country Code
11	The registration country code of the economic operator. The country should always be given by using ISO code 3166 alpha 2. A code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the alpha-2 representation.

6.3.3. Tenderer Party Contact

Used to provide contacting information for a party in general or a person. Optional information additional to the Economic Operator.

<cac:Contact> (1)
    <cbc:Name>Maximilian Mustermann</cbc:Name> (2)
    <cbc:Telephone>+49 231 7000-7000</cbc:Telephone> (3)
    <cbc:Telefax>+49-711-9876543</cbc:Telefax> (4)
    <cbc:ElectronicMail>max.mustermann@example.com</cbc:ElectronicMail> (5)
</cac:Contact>

1	Introduction to the contact. The contact consists of four additional elements.
2	The name of the contact point.
3	A phone number for the contact point.
4	A fax number for the contact point
5	An e-mail address for the contact point.

6.4. Document Date Time

Issue date and time must be sent.

Issue date is a xs:date data type, and the date is specified as "YYYY-MM-DD" where:

YYYY - four digit year
MM - two digit month (01 to 12)
DD - two digit day (0)

Issue time is a xs:time data type, and the time is specified as "hh:mm:ss" where:

hh - two digits of hour (00 to 23) (am/pm NOT allowed).
mm - two digits of minute (00 to 59)
ss - two digits of second (00 to 59)
TZD - time zone designator (Z or +hh:mm or -hh:mm)

The issue date and time refer to the issuance of the tender receipt notification.

The issue time must specify the time zone.

Example of Issue date/time and Registered date/time

<cbc:IssueDate>2021-02-12</cbc:IssueDate> (1)
<cbc:IssueTime>00:00:00Z</cbc:IssueTime> (2)

1	Date when the referred document was issued by the sending party.
2	Time when the referred document was issued by the sending party, granular to seconds and timezone.

6.5. Withdraw Offer Indicator

Indicates that the economic operator states that he wants to withdraw the offer (true).

<cbc:WithdrawOfferIndicator>true</cbc:WithdrawOfferIndicator> (1)

1	Boolean, must be true to act according to the message.