E-Procurement

E-procurement (German: E-Vergabe or elektronische Vergabe) is the end-to-end digital handling of public tender procedures via dedicated, certified electronic procurement platforms. From the initial contract notice to the final award, the entire workflow runs paperless, encrypted and audit-proof. Postal submission, fax forms or sealed envelopes physically delivered to a contracting authority are no longer permitted above EU thresholds since 2018.

The core of e-procurement is electronic communication between contracting authority and bidders. Five typical components form the workflow:

1. Electronic publication of the tender notice on a procurement platform and, for EU-wide procedures, additionally on TED.
2. Digital download of tender documents by all interested bidders, usually after free registration.
3. Bidder communication through the platform (clarification questions, answers, negotiation minutes).
4. Encrypted bid submission with an advanced or qualified electronic signature, depending on the procedure.
5. Digital bid opening and electronic award or rejection notice under § 134 GWB.

E-procurement is part of an EU-wide modernization of public buying. The aim is not only efficiency but also competition: a bidder from Lisbon can apply to a notice from a federal authority in Berlin as easily as a local SME from Brandenburg. Cross-border participation becomes practically feasible.

In Germany, however, the landscape is fragmented. The federal government, the 16 states and thousands of municipalities use different platforms, including evergabe-online.de (federal procurement office platform), DTVP (Deutsches Vergabeportal), Vergabe24, Subreport ELViS, Staatsanzeiger eServices, Vergabe.NRW and 180+ further portals. Each has its own registration process, user interface and technical requirements. For companies bidding nationwide or across industries, this means juggling multiple accounts, logins and notification systems.

E-procurement is therefore both a legal obligation and a complexity driver. It is also the precondition for AI-powered search and monitoring, without digital data, an automated tender intelligence layer would be impossible. This is exactly where solutions like Patterno Hit come in: they aggregate the fragmented platform landscape and deliver qualified matches in a single inbox.

The obligation to use e-procurement is anchored in EU law and transposed into German law. Three layers apply:

EU level. Directive 2014/24/EU requires all member states to use electronic communication in procurement procedures. Since October 18, 2018, all EU-wide procedures above thresholds must run fully electronically. The eForms standard (Implementing Regulation (EU) 2019/1780) has harmonized the data formats for TED notices since October 25, 2023.

Federal level (above EU thresholds). § 9 VgV sets the principles of electronic communication: contracting authorities must use electronic means for notice, tender documents, bidder communication and bid submission. These means must be non-discriminatory, generally available, compatible with common ICT products and accessible. § 10 VgV details requirements for the electronic tools used; § 11 VgV details requirements for the electronic transmission of bids. Parallel rules exist in §§ 7 ff. SektVO (utilities) and § 7 VSVgV (defence and security).

Below EU thresholds. Since January 1, 2022, electronic communication is also largely mandatory under § 38 UVgO. However, German states have implemented UVgO differently, Saxony, for example, applies deviating rules. For construction works below thresholds, § 11 EU VOB/A governs electronic communication.

Signature requirements. The contracting authority specifies in the notice which signature level applies for bid submission: simple text form, advanced electronic signature (AES) under eIDAS or qualified electronic signature (QES). For security-sensitive procedures QES may be required; in standard cases an advanced signature via the platform's certified mailbox suffices.

A mid-sized IT system house from Münster with 80 employees wants to bid for a federal ministry framework contract "cloud migration services". Contract value: around €4 million, clearly above the EU threshold for services.

The entire workflow runs digitally:

1. The contracting authority publishes the notice on Monday on evergabe-online.de and on TED in parallel. The system house receives an automatic alert in its Patterno Hit dashboard the same day, because its search profile "cloud, Microsoft 365, migration, public authority, above €500k" triggers a match.
2. The bid manager downloads the tender documents from the platform, specifications, conditions, draft contract, eligibility requirements.
3. Three days before the deadline the system house submits a technical clarification question about the required BSI certification. The answer is anonymized and shared with all bidders via the platform, a critical transparency mechanism.
4. On the deadline day the system house uploads its encrypted bid (PDF/A of the main offer, price sheets as XML, eligibility evidence as attachments) and signs it with an advanced electronic signature. The platform confirms receipt to the second, deadline proof on record.
5. At the bid opening the contracting authority opens all bids digitally under the four-eyes principle. A handwritten opening protocol is no longer needed; the system generates it automatically.
6. Six weeks later the system house receives the electronic pre-award notice under § 134 GWB. After the ten-day standstill period, the contract is awarded, again via the platform.

Total bidder effort: about 14 person-days. Without e-procurement, additional printing, binding, courier delivery and physical attendance at the opening would have added at least two more days.

Every year bidders fail on formal errors that are objectively avoidable. The five most typical pitfalls in e-procurement:

• Last-minute uploads. Uploading large files (drawings, attachments, BIM models) in the final 15 minutes before the deadline risks an upload abort due to network load or platform latency. A late bid leads to mandatory exclusion under § 57 VgV, no discretion.
• Wrong signature level. If the notice requires a qualified electronic signature (QES), simple text form or a basic advanced signature is insufficient. The platform often only flags this at the opening, when correction is impossible.
• Single-user account. If the only platform account is tied to one employee who happens to be on sick leave or vacation, the company can miss the deadline. Best practice: at least two authorized users per platform.
• Neglected platform inbox. Clarification questions, requests for explanation or pre-award notices are delivered exclusively through the platform inbox. Whoever does not check it daily misses deadlines for challenges or additional document requests.
• Incompatible file formats. Some platforms accept only PDF/A, others additionally require XML-based GAEB files for specifications. The wrong format leads to exclusion if the notice explicitly mandates a format.

Companies that consistently win public contracts treat e-procurement as a sales process, not an IT problem. Five recommendations from practice:

• Maintain a platform inventory. Keep a central overview of every platform you are registered on, including credentials in a password manager, contact persons and last login. This prevents orphaned accounts and re-registrations under time pressure.
• The 48-hour upload rule. Submit bids at least 48 hours before the deadline. If a technical issue arises, there is still time to contact support or retry. Platform support teams are often unavailable on Friday afternoons.
• Trial run on every new platform. Before the first real bid on an unknown platform, perform a dummy upload to test file formats, signature flow and upload speed.
• Central search layer. Instead of subscribing to 20 platform newsletters, use a central AI-driven search. Patterno Hit, for example, aggregates 180+ portals, learns your business profile and delivers only the tenders that are truly relevant, every morning.
• Maintain document templates. Eligibility evidence, self-declarations, reference lists and capacity statements should exist as versioned templates. For each new procedure you only review tender-specific adjustments instead of starting from scratch.