Delivery Order — entity reference

The outbound dispatch document for a customer or dealer account: what is leaving a branch, to which ship-to address, under which transporter and e-way-bill references. It is normally generated rather than keyed - from a sales Order, from an InventoryFulfilment's allocation or picking lines (one delivery per fulfilment), from an Invoice, or from claim approval and rejection (ApprovedPart and RejectedPart discriminate the two documents a single Claim produces). Every header total is a calculated roll-up over DeliveryOrderLines, and no stock moves when the document or its lines are created: the Outward movement is written only when the PerformInventoryPosting action runs. Downstream it raises the Invoice (PerformCreateInvoice), the counterparty's inbound Shipment (PerformReleaseShipment) and the GL accrual (PerformGLPosting), and visit planning turns unplanned deliveries into 'Order Delivery' visits.

Fields

Field	Label	Type	Required	What it does
`AccountId`	Account	Lookup → Account		The ship-to customer or dealer account receiving the goods. It is source-populated from the originating order, fulfilment, invoice or claim and cannot be edited afterwards, and releasing a shipment requires a Branch whose PartnerAccountId equals this account.
`AccountName`	Account Name	Text
`ApprovedPart`	Approved Part	Boolean		True on the delivery order built from the approved lines of a Claim, whose line quantities come from ClaimLine.ApproveQuantity. It is the discriminator that keeps the approved and rejected documents for the same claim apart.
`ApproximateDistance`	Approximate Distance	Decimal
`BillingAddress`	Billing Address	Text
`BillingCity`	Billing City	PickList		Values: Pune, Mumbai, Chandigarh.
`BillingCityPlaceId`	Billing City	Lookup → Place		Values: Pune, Chandigarh, Mumbai.
`BillingContactAddressId`	Billing Address	Lookup → ContactAddress
`BillingCountry`	Billing Country	PickList		Values: India.
`BillingPostalCode`	Billing Postal Code	Text
`BillingRegion`	Billing Region	Text
`BillingState`	Billing State	PickList		Values: Haryana, Maharashtra, New Delhi, Punjab.
`BillingStreet`	Billing Street	Text
`BillReturnId`	Bill Return	Lookup → BillReturn
`BranchId`	Branch	Lookup → Branch		The dispatching branch, validated to belong to PartnerAccountId and locked after creation. It is also the branch whose InventoryStock buckets the Outward posting relieves and the branch the cost journal is booked at.
`ClaimId`	Claim	Lookup → Claim		Present only on the deliveries generated from a Claim's lines. A claim produces at most two such documents - one with ApprovedPart true and one with RejectedPart true - and the service reuses the existing one for the claim rather than creating a second.
`CreatedById`	Created By	Lookup → UserAccount	Yes
`CreatedDateTime`	Created Date	DateAndTime	Yes
`DeliveredDateTime`	Delivered Date Time	DateAndTime		Actual proof of delivery in the running system comes from the generated Visit and its checklist lines rather than from this timestamp.
`DeliveryCity`	Delivery City	PickList
`DeliveryContactAddressId`	Delivery Address	Lookup → ContactAddress
`DeliveryCountry`	Delivery Country	PickList		Values: India.
`DeliveryDate`	Delivery Date	Date
`DeliveryDoneByResourceId`	Delivery By	Lookup → Resource		The resource (driver or field person) credited with performing the delivery. It is validated against the resource master on both insert and update, but nothing else in the platform reads it - it does not drive visit assignment.
`DeliveryLocation`	Delivery Location	Text		A free-text description of where to deliver, not coordinates. Route and distance calculations deliberately ignore it and take the planned position from the ship-to account's stored geolocation instead.
`DeliveryPostalCode`	Delivery Postal Code	Text
`DeliveryRegion`	Delivery Region	Text
`DeliveryState`	Delivery State	PickList		The state or province of the ship-to address, held as free text. No code writes it; it is read once, when visit planning copies it onto the generated Visit as VisitState.
`DeliveryStreet`	Delivery Street	Text
`Discount`	Discount	Currency		A header discount that cascades: modifying it re-runs discount distribution across all delivery order lines.
`DiscountGroupId`	Discount Group	Lookup → DiscountGroup
`DocumentDate`	Document Date	Date		Defaulted to the current date when the delivery is created and non-editable thereafter. It is the date the GL journal from PerformGLPosting carries, so it is the accounting date of the dispatch rather than a planning date.
`EWayBillDate`	E-Way Bill Date	DateAndTime
`EWayBillNumber`	E-Way Bill Number	Text		The e-way bill reference for this consignment.
`ExternalId`	External	Text
`FailedItemTreatment`	Failed Item Treatment	PickList
`GeneralLedgerId`	General Ledger	Lookup → GeneralLedger
`GLAccountId`	GL Account	Lookup → GLAccount
`GSTIN`	GSTIN	Text		The customer's GST registration number for this dispatch, auto-filled from the billing contact address and, failing that, from the customer account, and format-validated on both insert and update.
`Id`	Id	Guid	Yes
`InventoryFulfilmentId`	Inventory Fulfillment	Lookup → InventoryFulfilment
`InvoiceId`	Invoice	Lookup → Invoice		Set when the delivery was generated from an Invoice rather than an Order, in the invoice-first flow. Its lines then carry InvoiceLineId, which selects the ledger rule that decrements the PendingDeliveries bucket using InvoicedQuantity instead of posting a plain Outward movement.
`IsCancelled`	Cancelled	Boolean
`IsConfirmed`	Confirmed	Boolean
`IsDelivered`	Delivered	Boolean		Its only consumer is visit planning, which selects delivery orders where it is not true, so in practice every delivery stays eligible for visit generation indefinitely.
`IsGLPosted`	Is GL Posted	Boolean		Intended to record that the delivery's journals were posted, but nothing in the platform writes it - PerformGLPosting sets only IsGLPostingApproved. Look for Journal rows sourced from the document instead.
`IsGLPostingApproved`	Is GL Posting Approved	Boolean		Stamped true by PerformGLPosting immediately before the document's journals are posted through the document journal posting service.
`IsILPosted`	IL Posted	Boolean		A header-level inventory-posted flag that no code writes. Inventory posted state is tracked per line by DeliveryOrderLine.InventoryLedgerId, which is also what the posting action filters on.
`IsILPostingApproved`	IL Posting Approved	Calculated (calculated)		An approval gate for inventory posting that is never enforced: the handler collects the approved records on update but discards the result without acting on it, and PerformInventoryPosting does not consult it. Setting it true does not authorise anything on its own.
`IsInJobQueue`	In Job Queue	Boolean
`IsShipmentReleased`	Shipment Released	Boolean		To tell whether a delivery has been shipped, look for Shipment rows built from it rather than at this flag.
`JobInterfaceQueueId`	Job Queue	Lookup → InterfaceQueue
`JobQueueId`	Job Queue	Lookup
`LRDate`	LR Date	DateAndTime
`LRNumber`	LR Number	Text		The carrier's lorry receipt or consignment note number.
`ModifiedById`	Modified By	Lookup → UserAccount	Yes
`Name`	Document Number	Text
`OrderId`	Order	Lookup → Order		The sales Order being delivered. It is locked after creation, and partner account, branch and account are source-populated from it and equally non-editable.
`OwnerId`	Owner	Lookup → UserAccount	Yes
`PartnerAccountId`	Partner Account	Lookup → Account		The selling company that owns the document; it is validated against BranchId on insert, locked after creation, and becomes the SupplierAccountId of any Shipment released from this delivery.
`PerformPopulateChecklist`	Perform Populate Checklist	Boolean		No code writes or reads the column.
`PerformReleaseShipment`	Perform Release Shipment	Boolean
`PlaceOfSupply`	Place of Supply	PickList		The destination state for GST purposes. It is auto-filled from the billing contact address and, failing that, from the customer account, and comparing it with SourceOfSupply is what decides between a within-state and an outside-state supply. Values: Haryana, Maharashtra, Gujarat, Rajasthan.
`PorterContactNumber`	Porter Contact Number	Text
`PriceAsOnDate`	Price As On Date	Date
`PriceListId`	Price List	Lookup → PriceList
`RecordTypeId`	Record Type	Guid, hidden
`RejectedPart`	Rejected Part	Boolean		True on the delivery order built from the rejected lines of a Claim, whose line quantities come from ClaimLine.RejectQuantity. It is the mirror of ApprovedPart and only one of the two is ever set on a given document.
`Remarks`	Remarks	Text
`RequestedDeliveryBranchTimeSlotBookingId`	Requested Delivery Time Slot Booking	Lookup → BranchTimeSlotBooking
`RequestedDeliveryBranchTimeSlotId`	Requested Delivery Time Slot	Lookup → BranchTimeSlot
`RequestedDeliveryDate`	Requested Delivery Date	Date
`RequestedDeliveryDateTime`	Requested Delivery Date Time	DateAndTime
`RequestedDeliveryTime`	Requested Delivery Time	TimeOnly
`RoundOff`	Round Off	Currency		TotalAmount is computed purely from the line roll-ups.
`ScheduledDeliveryDate`	Scheduled Delivery Date	Date
`ScheduledDeliveryDateTime`	Scheduled Delivery Date Time	DateAndTime		The planned delivery slot that visit planning matches against a VisitPlan's start and end dates; it also becomes the generated Visit's planned start time, with the planned end one hour later. No code writes it, so it must be set by the user or an integration for planning to slot the delivery precisely - deliveries with it empty are picked up by any plan window for the same branch and partner.
`ServiceOrderId`	Service Order	Lookup → ServiceOrder		Alternative source document: a delivery raised for a ServiceOrder instead of a sales Order.
`ShippingAddress`	Shipping Address	Text
`ShippingCity`	Shipping City	PickList		Values: Pune, Mumbai, Chandigarh.
`ShippingCityPlaceId`	Shipping City	Lookup → Place		Values: Pune, Chandigarh, Mumbai.
`ShippingContactAddressId`	Shipping Address	Lookup → ContactAddress
`ShippingCountry`	Shipping Country	PickList		Values: India.
`ShippingPostalCode`	Shipping Postal Code	Text
`ShippingRegion`	Shipping Region	Text
`ShippingState`	Shipping State	PickList		Values: Haryana, Maharashtra, New Delhi, Punjab.
`ShippingStreet`	Shipping Street	Text
`SourceOfSupply`	Source of Supply	PickList		The origin state for GST purposes, auto-filled from the dispatching branch. It is only ever compared with PlaceOfSupply to derive TaxSupplyType. Values: Rajasthan, Haryana, Maharashtra, Gujarat.
`Status`	Status	PickList		All four seeded values (Draft, Registration, Delivery Checklist, Delivered) are inactive and no code writes this column, so it stays at its 'Draft' default default forever. Do not filter or report deliveries by Status; use the line-level InventoryLedgerId and the quantity roll-ups instead. Values: Insurance Issued.
`Tax1`	Tax1	Currency
`Tax1Name`	Tax Name 1	Text
`Tax1Rate`	Tax Rate 1	Currency
`Tax1Type`	Tax Type 1	Text
`TaxSupplyType`	Tax Supply Type	PickList		The GST supply classification, derived automatically by the India handler from the billing address or customer GST registration type: 'Exempt' for out-of-scope and non-GST supply, 'Export' for overseas and deemed exports, 'SEZ' for special economic zone, otherwise 'Outside State' when PlaceOfSupply differs from SourceOfSupply and 'Within State' when they match. Only the last two exist as seeded pick-list values, so the engine can legitimately store Export, SEZ or Exempt values that a picker will not offer. Values: Within State, Outside State.
`TotalAmount`	Total Amount	Calculated (calculated)		Calculated as TotalLineAmount plus line tax, falling back to TotalTaxAmount2 when TotalLineTaxAmount is zero. It ignores the header Discount and RoundOff fields, so it is not necessarily the amount invoiced.
`TotalDiscountAmount`	Total Discount Amount	Calculated (calculated)
`TotalLineAmount`	Total Line Amount	Calculated (calculated)
`TotalLineBaseAmount`	Total Line Base Amount	Calculated (calculated)
`TotalLineGrossAmount`	Total Line Gross Amount	Calculated (calculated)		The sum of the lines' GrossAmount (line amount plus tax, less post-tax discounts). This is the figure PerformGLPosting books, as Dr Unbilled Dispatch / Cr Inventory Asset.
`TotalLineTaxAmount`	Total Line Tax Amount	Calculated (calculated)
`TotalTaxAmount`	Total Tax Posting Amount	Calculated (calculated)		Calculated as the line tax total plus the header Tax1, and labelled Total Tax Posting Amount. It pairs with TotalTaxAmount2, which is the same line total minus Tax1 - the two are a plus and minus pair, not two independent tax totals.
`TotalTaxAmount2`	Total Tax Amount	Calculated (calculated)
`TransportDocumentDate`	Transport Document Date	DateAndTime
`TransportDocumentNumber`	Transport Document No.	Text
`TransporterGSTIN`	Transporter GSTIN	Text		The carrier's own GST registration number, captured for the e-way bill. It is format-validated by the India handler on insert and update, so an incorrectly shaped value is rejected at save time.
`TransporterName`	Transporter Name	Text
`TransportMode`	Transport Mode	Text		How the consignment travels, for the e-way bill; the domain model documents the intended values as Air, Road, Railway and Ship, but no pick-list values are seeded for it and no code validates or reads it.
`UIProps`	UI Props	Text
`UpdatedDateTime`	Modified Date	DateAndTime	Yes
`VehicleNumber`	Vehicle Number	Text		The vehicle registration carrying the consignment, format-validated by the India handler on insert and update. It is captured for the e-way bill and is not linked to any Asset or fleet record.
`VisitId`	Visit	Lookup → Visit		Meant to mark a delivery that has already been turned into a field visit, and visit planning skips deliveries where it is set.

Actions

Action	Label	Type	What it does
`BulkDelete`	Delete	Delete	Delete the selected records.
`Clone`	Clone	ServerAction (`Clone`)	Create a copy of this record
`Delete`	Delete	Delete	Delete
`DeleteInList`	Delete	Delete	Delete in a list page
`Edit`	Edit	Edit	Edit
`EditInLine`	Edit	EditInline	Edit in page.
`EditInList`	Edit	Edit	Edit
`EditListHeader`	Edit	EditInline	EditListHeader
`EWayBill`	E Way Bill	ServerAction	Seeded as a server action but dead: the row carries no ServerActionName, so dispatch falls back to the action name 'EWayBill', which the delivery order handler does not list among its supported actions. The e-way-bill fields on the document (EWayBillNumber, EWayBillDate and the transport details) are manual capture only.
`New`	New	New	New
`PerformCreateInvoice`	Create Invoice	ServerAction (`PerformCreateInvoice`)	Creates an Invoice from the delivery order's lines that still have PendingInvoiceQuantity above zero, and refuses with 'No pending invoice quantities found in delivery order lines to create invoice' when none do. A second, stricter gate lives inside the invoice service, which re-queries the underlying order lines and can still refuse when the order side is fully invoiced even though a delivery line looks pending.
`PerformGLPosting`	Post General Ledger	ServerAction (`PerformGLPosting`)	Force-sets IsGLPostingApproved to true on the document and then posts it through the document journal posting service with the DeliveryOrder purpose: Dr Unbilled Dispatch / Cr Inventory Asset for TotalLineGrossAmount, dated DocumentDate and keyed on AccountId. It has no validation gate of its own, and it does not set IsGLPosted or GeneralLedgerId - neither field is written anywhere in the platform.
`PerformInventoryPosting`	Post Inventory	ServerAction (`PerformInventoryPosting`)	The action that actually moves stock for a delivery: it collects the lines whose InventoryLedgerId is still empty and runs the inventory posting engine over them. Four mutually exclusive seeded rules pick the movement by provenance - picking-sourced lines post Outward and decrement Picked, allocation-only lines post Outward and decrement Allocation, plain lines post Outward only, and invoice-sourced lines decrement PendingDeliveries using InvoicedQuantity. Each posted row also updates the branch's InventoryStock buckets and the ItemLot counters, and hands the row to the finance cost engine, which rebuilds the perpetual cost layers for that item and branch and books an Outward movement as Dr Cost Of Goods Sold / Cr Inventory at the engine cost. Nothing posts when the lines are first created: all four ledger settings have OnCreate false.
`PerformPopulateChecklist`	Populate Checklist	ServerAction (`PerformPopulateChecklist`)	Materialises checklist lines for the delivery from the CheckListTemplate whose Type is 'Delivery' (the mapping the checklist service holds for the DeliveryOrder entity), stamping each created line with RelatedEntityType DeliveryOrder and the delivery's id.
`PerformReleaseShipment`	Release Shipment	ServerAction (`PerformReleaseShipment`)	Creates the counterparty's inbound Shipment from this delivery's lines with quantity above zero, swapping the party roles: the delivery's PartnerAccountId becomes the shipment's SupplierAccountId, the delivery's AccountId becomes the shipment's PartnerAccountId, and the shipment's branch is the Branch whose PartnerAccountId equals that account - so it fails with 'No branch found for account ... to create shipment' when the customer is not a partner account with a branch in the same system. Each shipment line copies the item, SKU, quantity and PurchaseOrderLineId, but not DeliveryOrderLineId, so the delivery line's ShippedQuantity roll-up has nothing to sum. It does not set IsShipmentReleased, which no code path ever writes.
`PrintDO`	Print DO	Print	A Print-type action rather than a server action, so it renders the delivery note through the platform's print pipeline and changes no data.
`SelectiveReleaseShipment`	Selective Release Shipment	ServerAction (`SelectiveReleaseShipment`)	Creates a Shipment for chosen lines and quantities instead of the whole delivery order. Args carry DeliveryOrderLines with id and requestedQuantity; each requested quantity is validated against the line quantity, and the action refuses when no selected line has quantity above zero.

Lookup filters

Filter	Lookup field	Notes
Branch For Partner Account	`BranchId`	PartnerAccountId = __target.PartnerAccountId
Customer Account Filter	`AccountId`
Executive Filter	`DeliveryDoneByResourceId`
Partner Account Filter	`PartnerAccountId`

InterfaceQueue — looks up via JobInterfaceQueueId
Branch — looks up via BranchId
Order — looks up via OrderId
Resource — looks up via DeliveryDoneByResourceId
ContactAddress — looks up via DeliveryContactAddressId
DiscountGroup — looks up via DiscountGroupId
Visit — looks up via VisitId
InventoryFulfilment — looks up via InventoryFulfilmentId
Place — looks up via ShippingCityPlaceId
UserAccount — looks up via CreatedById
Place — looks up via BillingCityPlaceId
PriceList — looks up via PriceListId
UserAccount — looks up via ModifiedById
UserAccount — looks up via OwnerId
ContactAddress — looks up via BillingContactAddressId
Claim — looks up via ClaimId
ServiceOrder — looks up via ServiceOrderId
Invoice — looks up via InvoiceId
GeneralLedger — looks up via GeneralLedgerId
BranchTimeSlot — looks up via RequestedDeliveryBranchTimeSlotId
ContactAddress — looks up via ShippingContactAddressId
Account — looks up via AccountId
Account — looks up via PartnerAccountId
BranchTimeSlotBooking — looks up via RequestedDeliveryBranchTimeSlotBookingId
GLAccount — looks up via GLAccountId
ProductDemo — referenced by via DeliveryOrderId
Journal — referenced by via SourceRecordId
Visit — referenced by via DeliveryOrderId
InventoryLedger — referenced by via ParentRecordId
VisitTaskActivity — referenced by via DeliveryOrderId
Invoice — referenced by via DeliveryOrderId
CreditNote — referenced by via DeliveryOrderId
DeliveryOrderLine — referenced by via DeliveryOrderId

Delivery Order — entity reference

Fields

Actions

Lookup filters

Related entities

Related topics