Quote-to-cash for distributors on Dynamics 365

By Emil Björk · Microsoft business apps consultant, Gothenburg

How the quote-to-cash cycle runs for a wholesale distributor on Dynamics 365 — quoting in the ERP versus in Sales, the pricing stack, credit and margin control, order confirmation, fulfilment, invoicing and collections, and where CPQ and price-optimisation ISVs come in.

Updated 2026-09-02

Distributors live on volume, thin margin, and speed. A quote-to-cash process that takes three systems and two re-keys is not a process, it is a cost. Dynamics 365 can run the full cycle inside the ERP — quote, order, credit check, pick, ship, invoice, collect — and the main design question is what, if anything, the CRM app adds. This guide walks the cycle for a wholesale distributor and is blunt about the ISV boundaries. For the multi-warehouse side of fulfilment see multi-warehouse fulfilment; for the industry overview, Dynamics 365 for wholesale distribution.

Where the quote lives

There are two places a quote can be created: the ERP (Supply Chain Management sales quotations or Business Central sales quotes) and Dynamics 365 Sales. Distributors should default to the ERP.

The ERP quote has the real prices, the real stock, the customer's real credit position, and converts to a sales order without integration. A quote in Dynamics 365 Sales has the opportunity, the contact history, and the pipeline, and it converts to a sales order only through Dual-write, a connector, or an integration, all of which have to carry the pricing outcome across. For a distributor doing hundreds of transactional quotes a day, that integration is a liability.

The case for Sales is account management, not quoting: territory planning, opportunity tracking on new-account wins, activity history, and marketing follow-up. Distributors that run Sales successfully use it for the relationship and let the ERP own every priced document. The wholesale distribution overview discusses this split.

The pricing stack

Distribution pricing is where the ERP earns its licence. Supply Chain Management's stack, from the bottom up:

  • Base sales price on the item.
  • Trade agreements — price and discount journals by item, item group, or all items, against customer, customer group, or all customers, with quantity breaks, date ranges, and currency. Line discounts, multiline discounts, and total discounts stack according to the discount parameters.
  • Sales agreements — contractual commitments by quantity or value with a customer, which the sales and purchase agreements guide covers.
  • Unified pricing management — the newer rule-based pricing engine shared with Commerce, which adds price components, margin-based and attribute-based pricing, and a clearer evaluation trace than legacy trade agreements. Distributors implementing today should evaluate it rather than defaulting to trade agreements.
  • Rebates and trade allowances — accrued off the invoice, covered in trade allowance and rebates.

Business Central's stack is simpler — the price and discount lists of the new pricing experience, with customer price groups, campaigns, and quantity breaks — and adequate for most SMB distributors.

What neither product does: price optimisation (what should the price be for this customer and item given elasticity and competitor data), and guided selling for complex product mixes. Both are ISV territory. A distributor asking for "AI pricing" is asking for an ISV or a data-science project over the ERP's transaction history.

Margin and credit control at order entry

Two checks belong on the sales line, not in a month-end report:

  • Margin visibility and floors. Supply Chain Management can show cost and margin on the line and alert on lines below a threshold; enforcing a floor needs a small extension or a workflow. Business Central shows profit on the line and needs an extension to block. Either way, the sales desk should see the margin and someone should own the exceptions.
  • Credit check. Supply Chain Management's credit management module runs blocking rules at order entry, confirmation, picking, packing slip, or invoice, with a release workflow. It is genuinely good and under-used. The credit and collections guide covers it. BC has credit limits with a warning or a block, and the customer credit limits guide covers the options.

Confirmation, EDI, and self-service

Large customers send orders by EDI and expect acknowledgements, ASNs, and invoices back the same way. Neither product ships an EDI translator; the pattern is an EDI ISV or a managed EDI service mapped to the sales order and packing slip entities, and the EDI guide covers the BC side. The order confirmation, once posted, is the commitment the customer holds you to, so the price and delivery date on it must be final — confirm after credit check and ATP, not before.

For smaller customers, customer self-service in Supply Chain Management or a Power Pages portal over BC gives order entry, order status, and invoice copies without a phone call. The customer self-service guide describes the first-party option. It is basic; a distributor whose customers expect a B2B web shop with rich search and personalised catalogues is looking at Commerce's B2B storefront or a partner e-commerce platform.

Fulfilment through invoice

From confirmed order to invoice, the flow is standard: release to warehouse, pick, pack, ship with packing slip or shipment, invoice. The distribution-specific decisions:

  • Invoice timing. Per shipment, daily per customer, or on a summary schedule. Supply Chain Management's summary update parameters and BC's combine-shipments both handle consolidated invoicing; choose per customer group and stop arguing about it.
  • Charges. Freight, handling, and small-order surcharges as auto charges on the order rather than manual lines, so they are consistent and tax-correct.
  • Direct delivery for lines the distributor does not stock, which the drop-ship patterns guide covers.

Collections

The cycle ends when cash arrives. Supply Chain Management's collections workspace, aging, collection letters, and interest handle a large ledger; BC's reminders and finance charge memos handle a smaller one. Distributors with thousands of small accounts benefit from customer payment portals and card-on-file, both partner territory. The single highest-impact habit is disputing invoices at line level in the system rather than in email, so that the dispute is visible to the collector, the salesperson, and the customer.

Measuring it

Quote-to-order conversion, order-to-ship time, invoice accuracy (credit notes as a share of invoices), and days sales outstanding. All four come out of the transaction tables in Power BI; none of them come out of the box as a distributor dashboard. Build the four measures in the first month after go-live and review them weekly; they will show where the re-keying still hides.

Further reading

Related guides

Spot something wrong or want a topic covered? Send a correction or a topic request — both are welcome.