e-Delivery Note (e-İrsaliye)
Create e-Delivery notes automatically from the shipping document and track recipient responses (accept, partial, reject) in SAP.
What problem does it solve?
Every taxpayer shipping goods must issue delivery notes electronically. When shipping is planned in SAP but the e-Delivery note is issued in another tool, a missing document discovered after the truck has left causes problems at customs and inspection points.
How does the solution work?
The solution creates the e-Delivery note from the SD delivery or MM stock transfer document, carries plate, driver and dispatch details onto it and submits it to GİB. The recipient's accept, partial-accept or reject response is written back to the SAP document, and on partial acceptance the quantity to be invoiced follows that response. Incoming e-Delivery notes are matched to goods receipts.
What changes in practice?
Because the e-Delivery note is generated from the shipping document, shipment and document stay consistent. The delivery-invoice-goods-receipt chain is tracked in one document flow and reconciliation differences fall at source.
Benefits
- The e-Delivery note is generated from the shipping document; no re-entry in a separate tool
- Recipient responses (accept, partial accept, reject) are tracked on the SAP document
- Delivery note, invoice and goods receipt are followed in one document flow
Where it sits in SAP
Integrated with SD deliveries and MM stock transfer documents; covers generating the e-Delivery note, carrying dispatch details onto it, processing recipient responses and matching incoming e-Delivery notes with goods receipts.
Who it is for: Logistics and Shipping, Procurement, Finance
Frequently asked questions
How does the shipping team's daily work change, and where do plate and driver details come from?
The shipping user creates the SD delivery or MM stock transfer document as today; because the e-Delivery note is generated from that document, there is no re-entry in a separate tool. Plate, driver and carrier details are entered in fields on the shipping document or on an additional dispatch screen and carried directly onto the e-Delivery note. The user sees on the SAP document whether the note has been transmitted to GİB and what the response status is; the condition under which a shipment is released is defined during implementation.
What happens on the stock and invoice side when the recipient responds with partial acceptance or rejection?
The recipient's response is written to the SAP shipping document. On partial acceptance the accepted quantity is recorded and the quantity to be invoiced follows it, while a return or re-dispatch process is started for the goods not accepted. On full rejection the document moves to rejected status and the stock movement is corrected through the standard SAP return flow. Documents awaiting a response are tracked in a separate list so that unanswered delivery notes are not overlooked.
How are incoming e-Delivery notes matched to goods receipts, and what if the supplier's document differs from the physical delivery?
The supplier's e-Delivery note lands in SAP and is matched with pending goods receipts using purchase order, material and quantity information; matched documents are used as the reference during goods receipt. If there is a quantity difference between the physical delivery and the document, the user responds with partial acceptance and posts the goods receipt with the actual quantity. Unmatched e-Delivery notes, or those without an order reference, are collected in a review list and handled by the procurement team.