[Poland] Deep Dive: Killing VLPOD in S/4HANA – How KIS Ruling 0114-KDIP1 Fixes E-Commerce Billing

For years, SAP Solution Architects designing B2B and B2C e-commerce flows in Poland have fought a losing battle against logistics realities and tax compliance. When selling under DAP (Delivered At Place) Incoterms, ownership and tax liability technically transfer when the courier hands the parcel to the customer.

Because the exact delivery date is unknown at the time of warehouse dispatch, SAP standard logic forced us into architectural nightmares. On July 1, 2026, the Polish National Tax Information (KIS) issued ruling 0114-KDIP1-2.4012.317.2026.2.RM, stating that e-commerce companies can legally issue invoices without indicating the sales/delivery date if it is impossible to determine at the time of billing.

Here is how we use this legal victory to obliterate legacy custom code and simplify your S/4HANA Core.

The Problem: The VLPOD Nightmare

Before this ruling, to remain compliant, architects had to activate the Proof of Delivery (VLPOD) framework.

[TRENCH NOTE] If you have ever implemented VLPOD, you know it is an operational bottleneck. When the warehouse posts Goods Issue (PGI), the outbound delivery is hard-blocked for billing. You are forced to wait for an inbound EDI 214 message from the courier (DHL, DPD, InPost) to update the exact delivery date in SAP before transaction VF01 can finally generate the invoice.