Skip to content

[BC Idea][Subscription Billing]: Sales orders pass on information on subscriptions #6320

@miljance

Description

@miljance

BC Idea Link

https://experience.dynamics.com/ideas/idea/?ideaid=569f77f4-84b8-f011-aa43-6045bd77b604

Description

Goal
Enhance the Subscription entity to support full lifecycle traceability by automatically inheriting key metadata from upstream Sales Orders and Posted Sales Invoices. This ensures that downstream service, marketing, and sales processes have immediate access to the original transaction context without manual data entry.


User Story
As a Sales or Account Manager at a company selling hardware and software subscriptions, I need to see the original purchase details (who sold it, who manufactured it, and the financial trail) directly on the customer's subscription record.

Currently, during sales campaigns, our team lacks the "original sale" context needed to gauge customer satisfaction or identify upsell opportunities efficiently. Having this data centralized on the subscription allows us to execute targeted outreach based on the specific vendor or salesperson involved.


Requirement
Enable a seamless data flow from the Sales Order to the Subscription record. Since subscriptions are triggered upon delivery - which often occurs before the final invoice is generated - the system must support a two-stage update process:

  1. At Delivery: Populate the subscription with order-level metadata.
  2. At Invoicing: Update the existing subscription record with the Posted Sales Invoice Number once the posting is finalized.

Proposed Schema Changes:
Add the following fields to the Subscription table/page:

  • Salesperson: To track ownership for commissions and follow-ups.
  • Sales Order Number: For direct link to the originating document.
  • Vendor & Manufacturer: To filter subscriptions by supply source.
  • Posted Sales Invoice Number: To bridge the gap between subscription management and finance.

I will provide the implementation for this BC Idea

  • I will provide the implementation for this BC Idea
    Internal work item: AB#612906

Metadata

Metadata

Labels

ApprovedThe issue is approvedBCIdeaIssue related to a BCIdeaLinkedIssue is linked to a Azure Boards work item

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions