bpost is too late against the Province of Hainaut — and trips over its own Track&Trace: the bpost stamp on the Masspost deposit list counts, not the ‘receipt date’ in the tracking app
bpost sought suspension under extreme urgency of the award of lot 1 (franking of postal items) of a postal services contract of the Province of Hainaut to Postalia Belgium, but the Council of State held the application out of time: the registered notification had been deposited at a Masspost centre on 6 May 2026, as the bpost stamp on deposit list 208 BC proved, and the fact that bpost’s own Track&Trace showed ‘8 May’ as the date of receipt was no excusable error — it was bpost’s own services that had accepted, processed and delivered the item.
What happened?
On 3 July 2025 the Province of Hainaut published in the Belgian Bulletin of Tenders a services contract for the ‘processing of outgoing postal items and associated supplies’; the European notice followed on 7 July 2025. Questions were asked and answered several times, several corrigenda were published and the specifications were amended more than once. The contract was divided into three lots and awarded through an open procedure, each lot by way of a framework agreement with a single operator. The province acted as a central purchasing body for a large number of local authorities: social welfare centres, municipalities, police zones, intermunicipal companies, social housing companies and autonomous municipal undertakings. bpost submitted a tender on 10 September 2025. On 14 April 2026 the province drew up its tender evaluation report, and on 16 April 2026 the provincial executive approved it: lot 1, the costs of franking postal items on which the customer applies the franking itself, with or without collection service, went to Postalia Belgium. The decision was communicated to bpost by email on 6 May 2026. Accounts of the registered letter differed. According to bpost it had been sent on 8 May 2026: that was the ‘date of receipt by bpost’ in the item’s Track&Trace history, and the envelope itself bore no postmark. bpost applied for suspension under extreme urgency on 26 May 2026. Postalia Belgium intervened. The province and Postalia argued that the application was out of time. A member of the province’s staff had deposited the registered letter at a bpost Masspost centre on 6 May 2026, the same day as the email. The proof was the bpost stamp on the deposit list for registered items (‘réquisitoire 208 BC’), bearing a barcode that matched the one on the envelope bpost itself produced. According to the province, the fifteen-day period therefore ran from 7 May and expired on 22 May 2026. At the hearing bpost relied on its good faith and on an excusable error. It had no access to the stamp on the deposit list, the envelope bore no stamp and the tracking app showed 8 May. The discrepancy was said to be due to a major strike by its own staff, which had ended on 6 May 2026. bpost referred to judgments no. 248.491 of 7 October 2020 and no. 250.159 of 18 March 2021, in which, it argued, the Council had accepted the date on which the addressee could rely as the starting point. The presiding judge of the VIth chamber, Florence Piret, sided with the province. Article 8(1) of the Act of 17 June 2013 obliges the contracting authority to send its decision; receipt lies outside that obligation. Notification is therefore the act of the authority sending the decision. Article 9/1 requires an electronic notification and, on the same day, a registered letter, and where the two are not sent simultaneously the period runs from the last dispatch (Article 23(1), second paragraph). The stamp on list 208 BC is the material proof that the registered letter was deposited at a Masspost centre on 6 May 2026; according to bpost’s own Masspost Guide 2026, that list is validated immediately and handed to the customer, and the validation constitutes proof of deposit. Once deposited, the item was in the postal circuit. The fact that Track&Trace wrongly showed 8 May did not turn the late filing into an excusable error: it was not an external event, since it was bpost’s own services that had accepted the item, issued the proof of deposit, and processed and delivered the letter. The strike remained a general assertion; at the hearing no concrete explanation could be given of what had caused the apparently technical failure. The application of 26 May 2026 came more than fifteen days after the double notification and was inadmissible ratione temporis. The Council kept the tender documents (items A to E of the administrative file and Postalia’s items 4 to 7) confidential; page 44 of item B had already been released in redacted form by the province, at bpost’s request and at the auditor’s invitation. bpost bore the 200-euro court fee, the 26-euro contribution and a 770-euro procedural indemnity to the province; Postalia paid 150 euros for its intervention.
Why does this matter?
The judgment sharply confirms that in procurement litigation the time limit starts to run when the notification is sent, not when it is received. What counts is the day the contracting authority hands the registered letter to the postal service — and if the email and the registered letter do not leave on the same day, the later of the two. The bpost stamp on the deposit list serves as proof, even though the tenderer never sees that list and the envelope bears no stamp. What the addressee reads in a tracking app does not shift that date. The case is all the more instructive because the applicant happened to be the postal operator itself. bpost tried to blame the wrong date on a strike and a technical fault, but the Council pointed out that an excusable error requires an external cause: whoever accepts, processes and delivers the item cannot rely on the failures of its own system. The earlier judgments in which the Council accepted the date on which an addressee could rely therefore did not help bpost. For other tenderers the message is broader: a Track&Trace entry or an unstamped envelope is a weak basis for calculating a time limit. The judgment also shows what an authority needs to make a lateness defence stick: an email and a registered letter on the same day, and a stamped proof of deposit whose barcode matches the one on the envelope.
The lesson
For tenderers: count the fifteen days from the earliest possible dispatch date. The law requires the authority to send the registered letter on the same day as the email; so assume the period runs from the day after the email, unless you are certain the registered letter left later. Do not base your planning on a tracking app, a postmark or the moment the letter lands on your desk, and plan to file well before the deadline. Whoever counts on the last day risks the authority producing a stamped deposit list dated a few days earlier. A plea of excusable error only stands a chance with a concrete external cause you can prove. For contracting authorities: send the email and the registered letter on the same day and keep the stamped proof of deposit (for Masspost, list 208 BC) together with each item’s barcode on file. That is exactly what saved the Province of Hainaut here. Also request confidentiality of tender documents explicitly and, where possible, release documents an applicant needs in redacted form.
Ask yourself
Do you count the time limit from the dispatch of the notification, and not from the day you received the registered letter? Do you assume the registered letter was sent on the same day as the email, unless you know for certain it was later? As an authority, do you hold a stamped proof of deposit for every registered notification, with a barcode you can link to the item? Do your email and registered letter leave on the same day, so that no dispute can arise about the ‘last dispatch’? Can you support an excusable error with a concrete external event, or does it remain a general statement?
About this database
The Council of State (Raad van State / Conseil d'État) is Belgium's supreme administrative court. In disputes over public procurement — from contract awards to tenderer exclusions — the Council of State is the final arbiter. The rulings in this database are summarised by TenderWolf in plain language, with practical lessons for tenderers and contracting authorities. View all rulings →