Goods, price and collection in one ledger

Yes. Lot, serial number and expiry belong to the stock movement line, together with FEFO issuing, unit-of-measure conversions, consignment, and the split of quantity into available, reserved, inbound, in transit and blocked. Traceability runs both ways: from a batch you get every customer who received it; from a complaint you reach the goods receipt and the supplier. That is a query over data rather than a search through an archive of delivery notes — a difference measured in hours on the day a supplier issues a recall.

Price lists and discounts are versioned configuration: a price list per channel or customer, a contractual discount, a volume scale and a promotion each carry a valid-from and valid-to date. The document line records which price was applied and which rule produced it, so a recap per customer is a query, not a reconstruction. A later grant — a turnover bonus, a retroactive price correction, an arrangement made after delivery — goes through a credit note as a document with its own posting, because a correction that edits an issued invoice is not a correction but the removal of a trace.

Probably not immediately, and that is worth saying plainly. Inventory operations are complete without it — receiving, put-away, transfers, reservations, picking, packing, dispatch, returns, stocktaking and handheld tasks all run on standard warehouse documents. The advanced WMS solves the problems that come from volume: bin locations and zones with capacities, directed put-away and optimised picking paths, wave and batch picking, zone replenishment, cross-docking, cycle counting and SSCC packing. Because it is configuration per warehouse rather than a second system, the decision is deferrable and reversible: switch it on at the distribution centre, leave it off at the spares store, and in neither direction is there a data migration.

Through landed costs and customs handling: duty, transport, forwarding, insurance and other dependent charges are allocated to receipt lines by a chosen key and enter the item cost. When a charge arrives after the goods are sold — which is the rule, not the exception — a backdated inventory recalculation and stock-to-ledger reconciliation are triggered, so the difference is not left as an unexplained variance until year end. The margin on goods already sold is corrected against the actual cost rather than the assumption made at receipt.

Yes — the control sits in the sales flow, on the order, before dispatch. Credit limit per partner and the statutory 45/60-day terms are part of the core, and open items, ageing and payment history are visible in Partner 360 from the same screen where the order is confirmed. Whether a breach is a hard block or a request for approval is decided by configuration and the approval chain with limits — the system enforces your policy rather than imposing one. What matters is that the decision arises while it can still be made, not after the vehicle has left.

The SEF channel sends and receives invoices in UBL 2.1 and tracks their status; VAT records are populated in the EEO and EPP structure from posted documents, and the POPDV and PP PDV XML come out of those same records rather than a separate spreadsheet. The e-delivery note via SEO is derived from the delivery note that already exists in the inventory flow — with carrier, vehicle and receipt confirmation, and a distinct flow for excise goods. Public-sector invoices go through the CRF, the goods ledger (KEP) is kept from stock movements, and APR financial statements come out of the same chart of accounts you post to. If you run a retail outlet alongside wholesale, e-fiscalisation through an ESIR with an LPFR or VPFR is there too. Underneath all of it sits the decision that cannot be added later: every rate, threshold and mapping is a record with a validity period, so correcting a March document in December follows March's rules.