Between a purchase order leaving procurement and a goods receipt being posted sit four documents, three mailboxes and at least one phone call. German mid-sized companies have recognised the problem: according to the Procurement Barometer for Mid-Sized Companies, published by a procurement software vendor together with the German Association for Supply Chain Management, Procurement and Logistics (BME) and ESB Business School, six out of ten (BME) have already digitalised their procurement processes, 10 percent (BME) are not digitally active at all, and 33 percent (BME) have no detailed digital processes for supplier qualification. In the following year's edition 88.9 percent (BME) of procurement leads see fast supplier onboarding as a growth driver. A supplier portal is exactly that: a two-lane rail on which purchase order, order confirmation, despatch advice and goods receipt travel as records rather than as attachments. This article describes the four stations, their deadlines, the connection to ERP and shop, and the sequence for introducing such a portal without a large programme.
Key takeaways
- A supplier portal replaces the mailboxes between the systems: the four stations - purchase order, order confirmation, despatch advice, goods receipt - become visible to both sides with the same status and timestamp.
- The demand sits there: in the most recent Procurement Barometer for Mid-Sized Companies 70.1 percent (BME) of procurement leads name supplier management as the field with the greatest need for digitalisation - ahead of order processing at 56 percent (BME).
- Goods receipt is a timestamp with legal effect: an agreed acceptance or verification procedure may take no more than 30 calendar days (European Parliament and Council) from receipt of the goods unless expressly agreed otherwise.
- The portal feeds the invoicing leg: until 31 December 2026 any company may still send paper to business customers; for supplies in 2027 that route is left to issuers with a prior-year turnover of no more than 800,000 euros (German VAT Act) or to EDI; from 2028 it closes.
- Connected, not isolated: EDI formats dominate electronic invoice receipt at 71 percent (Bitkom), and only 43.54 percent (Eurostat) of German enterprises with ten or more persons employed run an ERP system at all.
Where mid-sized procurement actually stands
The Procurement Barometer for Mid-Sized Companies - published by a procurement software vendor together with the BME and ESB Business School - surveyed 304 procurement professionals for its 2024 edition and paints a split picture. Six out of ten (BME) respondents say they have already digitalised their procurement processes, three out of ten plan to do so, and 10 percent (BME) are not digitally active at all. They locate the greatest need for digitalisation in supplier management at 71 percent (BME) and in order processing at 56 percent (BME) - the two fields a supplier portal serves. The 2025 edition put the same indicator at 80.6 percent (BME), the 2026 edition at 70.1 percent (BME): the ranking holds across all three waves, the value moves. Together the surveys reveal no awareness problem but an implementation problem.
What is striking is where things stall. 33 percent (BME) of the companies surveyed have no detailed digital processes for supplier qualification, so onboarding runs through forms and follow-up questions. 46.6 percent (BME) consider their systems for supply chain risk management inadequate. Willingness is not the issue: 85 percent (BME) are open to new technologies for digitalising procurement and finance processes, and 81.5 percent (BME) rely on real-time communication and platforms to strengthen their resilience. What is missing is the shared place where both sides see the same transaction. That is what B2B portals are built for, and why such a project starts with a review of the processes rather than a software selection.
Portal, shop or EDI - which is which?
The four document stations of procurement
The process is far older than any software that models it today. The message types purchasing and suppliers have used for decades come from the UN/EDIFACT directory: the standard comprises more than 200 (GS1 Germany) message types and, according to GS1 Germany, is used by more than 300,000 (GS1 Germany) companies worldwide. It was published in 1988 (GS1 Germany) by the United Nations, with the syntax laid down in ISO 9735. Four of these messages are decisive for procurement and describe the four stations a supplier portal has to model. Whether they arise as an EDIFACT file, as XML or as a browser form is a question of transport, not of process.
| Station | Direction | Content | Without a portal |
|---|---|---|---|
| Purchase order (ORDERS) | Buyer to supplier | Item, quantity, price, requested date, address | PDF to a shared address, no proof of receipt |
| Order confirmation (ORDRSP) | Supplier to buyer | Commitment, deviation in quantity, price or date | A reply email that nobody links to the order line |
| Despatch advice (DESADV) | Supplier to buyer | Packages, shipping unit, contents, arrival date | Often missing; the warehouse learns of it at the dock |
| Goods receipt (RECADV) | Buyer to supplier | Received quantity, short delivery, defect, timestamp | A handwritten note on the delivery slip |
| Invoice (INVOIC) | Supplier to buyer | Line items, tax details, reference to order and delivery note | PDF in the mailbox, matched by hand |
Kept as records, these five documents form a chain that can be checked by machine: every order confirmation has an order, every goods receipt an advice, every invoice a confirmed quantity. A deviation shows up at the station rather than in invoice verification six weeks later. Ranges with their own rules add further fields - return date and condition for loan equipment, as described in the article on rental items in the B2B shop, or the current safety data sheet for chemicals, see hazardous substances in the B2B shop. The chain stays the same, only the payload grows.
Why a portal is more than a shared mailbox
The difference between a portal and a mailbox is not the interface but the state. An email is an event: it goes out, it is read or it is not, and then reconstruction begins. A portal transaction is a state: sent, seen, confirmed, confirmed with deviations or overdue - and that state sits in the same place for both sides. That is why 81.5 percent (BME) of procurement leads rely on real-time communication and platforms rather than email. The gap remains wide: only 35.46 percent (Eurostat) of German enterprises with ten or more persons employed exchange supply chain information electronically with suppliers or customers.
In practice this means three things. Every transaction has a unique number under which both sides find it, not a subject line that mutates on reply. Every change of state carries a timestamp and an author, so a date change can be read off instead of asserted. And there are roles: the supplier's planner sees open orders, accounting sees invoice status, the buying organisation sees both. That separation is the building block a customer portal needs on the sales side - which is why many projects build the supplier portal on the same foundation as the self-service portal for customers.
The core of the difference
Master data: the invisible part of the portal
Before the first order can run, the supplier has to exist in the system with the details that will be needed later. This is where the largest gap opens: 33 percent (BME) of the companies surveyed have no detailed digital processes for supplier qualification. In practice a form goes back and forth by email, and nobody sees whether the insurance certificate is still valid. A portal reverses the obligation: the supplier maintains their own data, the system checks completeness, procurement approves. A process with an unknown duration becomes a process with a status.
Self-registration
The supplier enters company name, VAT identification number, bank details and contacts. Procurement approves instead of retyping from an email.
Certificates with an expiry date
Tax clearance, insurance, quality certificates: every document carries an end of validity, and the portal requests the new version before the old one expires.
Evidence for due diligence
Since the start of 2024 the German Supply Chain Due Diligence Act has applied from 1,000 employees (German Supply Chain Due Diligence Act) upwards. Supplier details then have to be current and documented.
Item master per supplier
Supplier item number, packaging unit, minimum order quantity and replenishment time belong to the supplier record, not to a spreadsheet.
Terms with a validity period
Scale prices and agreements carry a validity period. An expiring condition shows up before the next order, not during invoice verification.
Traceable changes
Every change to bank details or invoice address is logged and approved separately - the classic entry point for redirected payments.
The benefit shows in the second year, not on the day the record is created. A supplier master that maintains itself ages more slowly than a quarterly spreadsheet, and it answers the questions asked when something goes wrong: which suppliers still deliver this item, which certificates are missing, which terms expire next quarter. Respondents say the system situation is often weak: 46.6 percent (BME) consider their risk management systems inadequate. Where call-offs come into play, the article on framework contracts and call-off orders is worth a look.
Goods receipt: two timestamps, not one
Goods receipt is where procurement ends and accounting begins. Arrival and inspection are two different data points, and both have legal effect. Where an acceptance or verification procedure is agreed, European law allows it no more than 30 calendar days (European Parliament and Council) from receipt of the goods unless the contract expressly says otherwise. German law mirrors this: an agreement under which the inspection period runs for more than 30 days (German Civil Code) after receipt is effective only if expressly made and not grossly unfair. A portal that stamps arrival and inspection separately supplies exactly these data.
- Arrival at the dock and completed inspection are two separate timestamps
- Every goods receipt line references an order line and a despatch advice
- Short deliveries, over-deliveries and defects are states, not free text
- The response to the supplier leaves the system without procurement acting
- Partial deliveries stay open instead of closing the order line
- The inspection status is identical in the portal and in the ERP
The separation sounds pedantic but decides the payment leg. Without an agreed payment date the period runs 30 calendar days (European Parliament and Council) after receipt of the invoice or an equivalent request for payment. If the invoice arrives first, the start depends on the inspection status - and that sits in the portal. A folder at the dock leaves the clock in an assumption. How closely stock, delivery time and goods receipt are linked is set out in the article on real-time availability and delivery times.
Deadlines that end up in the document
The invoice as the fifth station
The invoice is the fifth station and the only one whose format is prescribed by law. The obligation to receive already applies, the obligation to send arrives in two stages: for supplies carried out before 1 January 2027, invoices to business customers may still be sent on paper until 31 December 2026, or - with the recipient's consent - in another electronic format, with no turnover threshold at all. Only for supplies carried out in 2027 does a threshold apply: the route is then left to issuers whose total turnover in the previous year did not exceed 800,000 euros (German VAT Act), alongside exchange by EDI under Recommendation 94/820/EC, which stays open regardless of turnover. From 2028 none of these transitional rules remains. The starting position was weak: weeks before the receiving obligation took effect, only 45 percent (Bitkom) of surveyed companies with 20 or more employees could receive an electronic invoice, and 55 percent (Bitkom) used one for outgoing invoices. The BME saw the same lag: two out of ten (BME) companies were not prepared.
Two tasks follow for the portal. The invoice needs a reference to order and goods receipt, otherwise verification stays manual. And it needs deadline monitoring: the invoice must be issued within six months (German VAT Act) of performing the service, provided the transaction is not exempt from tax. One document type may stay simple: invoices whose total does not exceed 250 euros (German VAT Implementation Ordinance) get by with reduced mandatory details. The detail is covered in our article on the e-invoicing mandate and ERP connection and on the e-invoicing page.
Anyone supplying public sector clients knows the route: in federal procurement the electronic invoice is mandatory, with exceptions that include invoices following a direct award up to 1,000 euros (German E-Invoicing Ordinance); the ordinance also exempts invoices whose data is classified as requiring secrecy, procurement by the foreign service and other purchasing abroad, and procedures in which one authority acts for another. The scale shows in a federal figure: in 2024 alone around 3.9 million (Federal Ministry for Digital Affairs and Government Modernisation) electronic invoices arrived through the federal invoice receipt platforms. On the sending side the economy is weaker: only 24.41 percent (Eurostat) of German enterprises with ten or more persons employed send invoices in a format suitable for automatic processing. A portal that accepts the invoice in structured form closes that gap for the small supplier.
Connecting to ERP and shop
A portal without a connection is a second data store, which costs more than it saves. So what can it dock onto? Only 43.54 percent (Eurostat) of German enterprises with ten or more persons employed use ERP software to share information between functional areas; the EU average is 46.45 percent (Eurostat), and Bavaria measures 44 percent (Bavarian State Office for Statistics). At the same time EDI formats dominate electronic invoice receipt at 71 percent (Bitkom). A portal has to serve both: the structured route for large partners and the interface for everyone else. The transport options are set out in the article on API architecture; the fundamentals of coupling to the merchandise management system are described under ERP integration.
{
"document_type": "goods_receipt",
"order": "B-2026-04187",
"delivery_note": "LS-77213",
"supplier": "L-1042",
"arrival_dock": "2026-09-15T07:21:00+02:00",
"inspection_completed": "2026-09-15T11:04:00+02:00",
"inspection_deadline": "2026-10-15",
"lines": [
{
"line": 10,
"item": "A-2041",
"supplier_item": "GS-4488-B",
"advised": 240,
"received": 236,
"unit": "PCE",
"status": "short_delivery",
"defect": null
},
{
"line": 20,
"item": "A-3117",
"supplier_item": "GS-9021-A",
"advised": 60,
"received": 60,
"unit": "PCE",
"status": "complete",
"defect": null
}
]
}What matters about such a response is not the format but who produces it and who reads it. It is produced in the warehouse and read in the supplier's ERP and in the buying organisation. Once it reaches both systems, the phone call about the short delivery becomes unnecessary. The same logic applies in reverse for connections to procurement systems on the customer side, as the article on PunchOut and OCI catalogues shows. And because every order needs an approval, the authorisation logic belongs in the design from the outset, see approval workflows and budgets.
Rollout in stages, not as a large programme
A supplier portal can be built in stages, and that is the cheaper sequence. The market shows why: B2B online trade by wholesalers and manufacturers in Germany reached around 509 billion euros (IFH KÖLN) in 2024, with the company's own online channel remaining the most important sales route at 76 percent (IFH KÖLN). As reasons for running their own online shop, the B2B companies surveyed name winning new customers at 44 percent (IFH KÖLN) and improving customer satisfaction through self-service at 43 percent (IFH KÖLN). The same argument applies on the buying side with the roles swapped.
- Master data and certificates: self-registration, approval, documents with an expiry date. This stage leaves the document chain untouched.
- Purchase order and order confirmation: orders appear in the portal, the supplier confirms or reports a deviation. The transaction status replaces the chasing email.
- Despatch advice: the supplier announces packages and arrival date, so the warehouse plans the dock instead of discovering it.
- Goods receipt and response: quantity, short delivery and defects are recorded and played back, with separate timestamps.
- Invoice: structured receipt with a reference to order and goods receipt, deadline monitoring, handover to accounting.
- Reporting: open confirmations, overdue inspections, on-time performance per supplier, expiring certificates.
The sequence has a practical reason: each stage can be accepted on its own and learned one at a time. Introducing all five documents at once means negotiating five changes with every partner at once - and then getting feedback by email about a portal meant to replace exactly that. It also helps to align the stages with existing systems: anyone working on an interface landscape attaches the portal to the same integration layer rather than beside it.
What changes after the first months
After the first months, what changes most is what procurement talks about. Instead of asking whether an order arrived, the question becomes why a line has been sitting without confirmation for four days. The first costs a phone call, the second a decision. The planning horizon changes too: the European VAT rules for electronic invoicing will be amended again with effect from 1 July 2030 (Council of the European Union), and for cross-border transactions the invoicing deadline is to be set at ten days (Council of the European Union) after the chargeable event. A document chain built today is better built so formats and deadlines can be swapped out.
A supplier portal is therefore less a product than a decision about where the truth lives. As long as that place is a mailbox, every report remains a reconstruction. Once it is a transaction with a status, on-time performance, inspection duration and open confirmations can be measured without a list. The willingness exists: 85 percent (BME) of surveyed mid-sized companies open to new technologies in procurement and finance. The rest is decided by sequence: master data, then documents, then metrics. The building blocks are in our overview of B2B portals, the route to prioritisation in e-commerce consulting.
Sources and studies
Related Articles
Framework Contracts and Call-off Orders in a B2B Store
Map framework contracts, quotas and call-off orders digitally in a B2B store: negotiated fixed price, visible remaining quota and approvals in Shopware.
From Fax to Automated B2B Ordering: Sales Transformation
How to digitise your B2B sales: process automation, order management, self-service portals, the link into the ERP and a return on investment you can measure.
VAT in the B2B shop: validating VAT IDs correctly
Checking VAT IDs in the B2B shop: simple and qualified confirmation, 26 status messages of the interface, reverse charge wording and the evidence to retain.