Orders

A draft order references the immutable accepted quote version and, where required, its executed and verified contract. It retains the sold-to account, channel end customer, purchase-order number, addresses, requested date, payment terms and billing method.

Staged delivery can use several orders from one accepted proposal. Order allocations record the quantity and net term value consumed from each accepted source line, so a second order draws only the remaining authorized scope. A generator cannot copy the full sale into every delivery order.

Repeated acceptance or release messages reuse their existing business result. The source quote version, order allocation and downstream delivery each have a stable identity for reconciliation.

The order’s value reconciles to its accepted allocation. Header discounts cannot vanish because an order line copied only the old line-level unit price. Tax treatment is retained separately from net commercial value so schedules and invoices apply it once.

Recurring term amounts and one-time charges remain distinguishable even when the order is billed upfront. These are billing obligations attached to the accepted sale, rather than permission to invoice an arbitrary order-header amount.

Deal Desk reviews Orders Awaiting Confirmation before approving an order. Required purchase-order details, billing contact, addresses and requested delivery information must be complete. A term sale needs its executed contract and recorded verification; a one-time no-term sale follows the accepted quote.

Credit review includes the account’s valid open invoices and outstanding committed order exposure, along with the proposed order. Confirmed but uninvoiced work consumes available credit, preventing several orders from independently passing against the same unused limit. Billing Specialist controls account holds and supplies the relevant collection context.

The review binds the exact order revision and its accepted allocation. Material changes require renewed commercial authority, credit evaluation and confirmation. General access to draft order lines does not permit rewriting a released sale.

Deal Desk releases the confirmed order through the configured ERP or provisioning connection. The payload includes product and option values, quantities, allocated prices, service periods, bundle relationships, parties, purchase order and contract reference.

Event deliveries records the destination outcome separately from local release. A missing acknowledgment does not justify creating another order remotely. Stable identity, supported destination deduplication and reconciliation of uncertain outcomes govern retries. The returned external reference links support work to the same order in each system.

The release can create a draft billing schedule for review when that downstream stage is enabled. A quoting-only implementation leaves contract, order or billing generation under its explicit cutover controls until those stages are authorized.

Fulfillment events record actual shipment, provisioning or customer acceptance against the affected line, with quantity, time, source and evidence. A first partial shipment does not imply full delivery. Customer acceptance is its own event when a milestone requires it.

Milestone policy specifies whether full completion or proportional quantity releases the obligation. Repeated events cannot fulfill or bill the same units twice; corrections link back to the original event. Service commencement and later billing completion also remain distinct.

Post-release commercial changes use a linked amendment and bounded change allocation. A cancellation releases eligible future obligations without a new charge order. A replacement retires superseded unfulfilled and unbilled allocations before reserving its new scope. Fulfilled quantities and posted invoices remain history; cancellation affects only the remaining authorized scope and follows any required credit or refund path.

An order closes after its delivery, acceptance and billing obligations are reconciled. Orders Awaiting Confirmation supports the release queue, while Billing Backlog identifies released value without a working billing plan. Sales Rep can follow the order outcome without taking over Deal Desk’s release authority.