28 apr

Route delivery note


E-invoicing in Germany: How to implement the obligation with SAP Business One

Of the Route delivery note Is the delivery document for one in SAP Business One Drop shipment English: Drop ShipThe goods go directly from the supplier to the customer, without touching your own warehouse. Although the company acts as the seller, neither physical warehousing nor order picking takes place in-house.

Context

Technically, the stock-in-transit business is handled via the transit warehouse (Magazzino di dropshipping) is depicted, which is marked as such in the master data of the warehouse. A customer order for this warehouse generates via the Procurement assistants or, upon copying, a suitable order is automatically created for the supplier with the customer's address as the delivery address. The consignment note then documents that the goods have physically arrived at the customer's premises – without any stock movement in the company's own warehouse, because the drop-ship warehouse is not managed by stock. The posting logic is correspondingly simplified: no material costs to inventory upon delivery, but rather the normal billing (Output invoice to customer: Debtor to Revenue + VAT) and in parallel the supplier's incoming invoice (Expense to Creditor). The Margin This results from the difference; the assumption of risk (transport, returns) is to be regulated contractually between the retailer, supplier, and customer.

Demarcation

The route delivery note is not identical to a regular delivery note from a stocked warehouse: it has no stock effect and no goods issue posting in one's own warehouse. It also differs from Goods Receipt from an order, which usually documents receipt at one's own site. Compared to a Commissioned goods or a classic Consignment store In the drop-shipping business, no warehousing takes place at all – the goods are transported exclusively from the supplier directly to the end customer.


ReAct and RLEF

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...
Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
RLHF

RLHF and reward models: AI hype or what the approval process in SAP Business One has to do with it

Key takeaways: The article covers the application of artificial intelligence in the context of SAP Business One and fundamental AI topics. Thanks to ...
AI Webinar

AI – Answers from SAP Business One – without SQL, without IT ticket

Live webinar on 30 July 2026, 14:00–14:30 | Live demo via Microsoft Teams | Duration: 30 minutes „How were the sales...".
Wird geladen …