Quote to cash process with Dynamics 365 Sales and Business Central

Quote to cash is the path from a priced quote to money in the bank: quote, order, shipment, invoice, payment. Microsoft documents Dynamics 365 Sales plus Business Central as a lead-to-cash integration: Sales handles customer engagement, and Business Central owns orders, inventory, and finances (Manage customers using Dynamics 365 Sales). On Microsoft's US price list, Sales Professional is USD 65 per user per month and Business Central Essentials is USD 80, each paid yearly, as of October 2026 (Dynamics 365 Sales pricing, Dynamics 365 Business Central pricing).

The work hides in the handoffs. A quote you win in Sales does not become a Business Central order until someone also submits a sales order in Sales. A price a salesperson changes on an order can create a new price list in Business Central for that single order. Sales receives a Billed invoice when someone selects Create Invoice in Dynamics 365 Sales, and a Partial or Complete payment status after Update Account Statistics or the Customer Statistics and POSTEDSALESINV-INV jobs run, on a default 30-minute schedule you can change. Those three gaps are where finance and sales end up arguing about whose number is true.

The sections below map each step to its owner, then cover the three drift points in detail. After that comes the license math for the US and Canada, and the version of the same process that runs inside one Odoo database.

The quote-to-cash steps and who owns each record

Salesforce defines the full cycle as configure, price, quote, proposal, order, renewal, invoice, cash allocation, and analysis, and treats CPQ as the front slice (The Basics of the Quote-to-Cash Process). Buyers ask a version of the same question: "Is the quote-to-cash process the same as CPQ?" (The Basics of the Quote-to-Cash Process). The answer matters for budgeting, because a CPQ tool stops at the quote and leaves the order, the invoice, and the cash to whatever system holds the ledger.

On Microsoft's stack, the same path runs across two products, and each step has one owner. This is the table to keep open during vendor demos:

• Opportunity and quote negotiation (Document: Quote, versioned · System of record: Dynamics 365 Sales · What the other side receives: Nothing until the quote transfers)
• Activated quote (Document: Quote · System of record: Dynamics 365 Sales, then both · What the other side receives: Business Central receives the quote; Effective To maps to Quote Valid Until)
• Order (Document: Sales order · System of record: Business Central · What the other side receives: Arrives from Sales after status Submitted)
• Shipment (Document: Shipment on order lines · System of record: Business Central · What the other side receives: Item availability refreshes in Sales on a 30-minute cycle when availability sync is on)
• Invoice (Document: Posted sales invoice · System of record: Business Central · What the other side receives: An invoice in Sales with status Billed when Create Invoice in Dynamics 365 Sales is selected)
• Cash (Document: Applied payment · System of record: Business Central · What the other side receives: Payment status of Partial or Complete after the statistics jobs run)

Ownership rules per Microsoft's integration documentation (Manage customers using Dynamics 365 Sales, Integrating with Dynamics 365 Sales).

Two consequences follow from that split. The posted invoice creates the item and customer ledger entries, so accounting runs on Business Central numbers (Invoice sales). Sales runs on copies: an invoice appears there with status Billed when someone selects Create Invoice in Dynamics 365 Sales, and the Partial or Complete payment status waits on the statistics jobs. Neither system is wrong during that gap; they describe different documents.

The documented integration has three drift points. Orders drift when a win in one system must become a document in another. Prices drift when a negotiated override has to survive into the invoice. Cash drifts when the ledger's payment status has to reach the pipeline report the sales manager reads. The next sections take each drift point in turn, with the rule that governs it and the decision that prevents it.

How a quote moves from Dynamics 365 Sales to Business Central

An activated quote in Dynamics 365 Sales transfers to Business Central automatically, or when someone runs Process in Business Central. Business Central archives prior quote revisions, and the Sales field Effective To becomes Quote Valid Until on the Business Central side (Manage customers using Dynamics 365 Sales).

The step that decides your workload is the win. A Won quote becomes a Business Central sales order only if a matching sales order is also submitted in Dynamics 365 Sales. Without that submission, Business Central releases the quote and no order appears, so the win lives in the CRM and the fulfillment queue never hears about it.

Business Central runs the same conversion on its own when no CRM is attached. An accepted quote becomes an order or an invoice with Make Order or Make Invoice, the quote is removed, and the new document stores the original quote id in a Quote No. field (Make sales quotes).

The handoff where orders stall or get re-keyed

Salesforce names the fear in its own explainer: "Once your customer agrees to the terms, does the data have to be entered into a completely different system before it registers as a valid order?" (The Basics of the Quote-to-Cash Process). Connecting the two products is meant to end that re-entry. The standard connection gets most of the way there, with one condition that surprises buyers: a sales order created in Dynamics 365 Sales transfers to Business Central only after it reaches status Submitted, and only if sales order integration is enabled (Manage customers using Dynamics 365 Sales). Until someone submits, the order lives in Sales and finance cannot see it. This is the step where orders wait in an inbox or get re-keyed by a coordinator trying to help.

Switch on sales order processing integration and the rules tighten further. A submitted order is locked for editing unless an integration user submitted it, the Create Invoice button disappears from the order, and price calculation is skipped while the order sits in Submitted (Enable sales order processing integration). The design keeps one writer at a time. Decide before go-live who owns the submit, and what happens when a customer changes the quantity ten minutes after the win.

Integration modes matter here too. Bidirectional sales-order sync and the legacy one-way flow from Sales to Business Central are mutually exclusive, so you pick one. Under bidirectional sync, submitting the order in Sales makes the lines read-only and the order arrives in Business Central already Released (Integrating with Dynamics 365 Sales). Traceability survives either way: the order's Name field in Sales maps to External Document Number in Business Central, which is how a finance clerk walks a posted invoice back to the deal (Manage customers using Dynamics 365 Sales).

Write-in products need a decision before the first order transfers. Each one must map in Business Central's Sales & Receivables Setup to an item or resource that is not itself coupled to a Sales product, and a long write-in description travels as an extra comment line (Manage customers using Dynamics 365 Sales).

Where prices drift between the quote and the invoice

Price is the second drift point. If a salesperson changes a product's price on a Dynamics 365 Sales order and that item is later used on a Business Central sales order, Business Central creates a new sales price list for each such order (Manage customers using Dynamics 365 Sales). Every negotiated order can leave its own price list behind, and the catalog grows quietly until someone asks why margins moved.

The standard price sync also has edges. The new Business Central pricing experience syncs a sales price list to Sales only when Allow Updating Defaults is off, the price type is Sale, the amount type is Price, the lines are Item or Resource, and no minimum quantity is set. Customer-specific prices and quantity-break prices sit outside that standard sync (Manage customers using Dynamics 365 Sales).

B2B price books usually lean on those two shapes: a customer's own price and a break at a case or a pallet. Write your rules down before any vendor demo, and ask the bidder to show where each rule lives after the integration, including who may change it.

From invoice to cash: when Sales learns the money arrived

Business Central requires a full sales order rather than a direct sales invoice in three situations: when only part of the quantity ships, when shipment happens after the invoice, and for drop shipment (Invoice sales).

An example makes the rule concrete. Assume a customer orders 10 units and 6 ship this week. With 4 units still to ship, only part of the quantity has gone out, so the document is a sales order and the direct sales invoice route is unavailable (Invoice sales).

Posting does the accounting. A posted sales invoice creates item and customer ledger entries and moves the document into posted sales invoices. On terms, the invoice stays open until the payment is applied to it. If the Payment Method Code is cash or a payment service, payment is recorded at posting and the invoice closes as fully applied (Invoice sales).

Sales then catches up in two hops. Posted invoice headers and lines flow into Dynamics 365 Sales invoices with status Billed when Create Invoice in Dynamics 365 Sales is selected. Payment status in Sales, Partial or Complete, updates when someone runs Update Account Statistics or the Customer Statistics and POSTEDSALESINV-INV jobs (Manage customers using Dynamics 365 Sales). Default integration jobs run every 30 minutes, and the schedule can be changed (Integrating with Dynamics 365 Sales).

The result is a window in which finance and sales quote different cash numbers. Business Central's ledger is current once the payment is applied. Sales shows the payment after the next statistics job run, whether that is the 30-minute default, a rescheduled cadence, or a person running Update Account Statistics by hand. Settle this in the design: either Sales reports cash from Business Central's numbers, or one person runs the statistics jobs after each payment batch.

Availability follows the same rhythm. When Automatically Synchronize Item Availability is on, a job queue refreshes item availability for coupled items every 30 minutes (Integrating with Dynamics 365 Sales). A seller quoting in Sales reads availability refreshed on a 30-minute cycle.

What the licenses cost in the US and Canada

Sales seats and Business Central seats are separate subscriptions, and a quote-to-cash setup pays for both. On Microsoft's US price list, Sales Professional is USD 65, Sales Enterprise is USD 105, and Sales Premium is USD 150 per user per month, paid yearly (Dynamics 365 Sales pricing). Business Central Essentials is USD 80, Premium is USD 110, and Team Members is USD 8, also per user per month, paid yearly, purchased through a partner (Dynamics 365 Business Central pricing). Microsoft's footnote on the Sales page adds that the core sales capability includes quotes, orders, and invoices, and that prices are informational and can differ by country (Dynamics 365 Sales pricing).

United States list prices

• Dynamics 365 Sales Professional: 65
• Dynamics 365 Sales Enterprise: 105
• Dynamics 365 Sales Premium: 150
• Business Central Essentials: 80
• Business Central Premium: 110
• Business Central Team Members: 8

US list prices as of October 2026: Dynamics 365 Sales pricing and Dynamics 365 Business Central pricing. Sales Premium includes 1,000 Copilot Credits per user on the same page (Dynamics 365 Sales pricing).

Canada list prices

• Dynamics 365 Sales Professional: 88.20
• Dynamics 365 Sales Enterprise: 142.50
• Dynamics 365 Sales Premium: 203.50
• Business Central Essentials: 108.50
• Business Central Premium: 149.20
• Business Central Team Members: 10.90

Canadian list prices as of October 2026, plus applicable tax: Dynamics 365 Sales pricing (Canada) and Dynamics 365 Business Central pricing (Canada).

Worked example at US list: assume 10 sellers who need Sales Enterprise and 25 staff who need Business Central Essentials. That is 10 × USD 105 plus 25 × USD 80, or USD 3,050 per month and USD 36,600 for the year before implementation. The same seat counts on the Canadian list come to CAD 4,137.50 per month, CAD 49,650 per year, before tax.

Put two licensing questions in writing before you sign. First, which Sales tier your integration scenario is licensed for, because the tiers price differently and the answer changes the seat math above. Second, what the low-cost Business Central seat type is licensed to do on quotes, orders, and payments, so the seat plan matches real tasks. Our guide to Dynamics 365 Sales pricing walks through the seat types in more depth.

Running the same path in one Odoo database

Odoo assembles the same cycle inside one product. Sales and accounting share one database, so the handoffs between quote and payment happen on screens inside the same system.

From quotation to Paid in one database

In Odoo 19, confirming a quotation turns it into a sales order in the same database. Create Invoice becomes available after confirmation when the product's invoicing policy is ordered quantities. Invoice what is ordered is the default; Invoice what is delivered blocks invoicing until the delivery is validated (Create quotations, Invoicing policies).

Cash closes in the same database. Accounting registers the customer payment from the invoice with Pay, and the invoice sits In payment until the payment is reconciled to a bank transaction, at which point it turns Paid. If the bank account is set as the outstanding account, a full payment can go straight to Paid (Payments).

One database removes the machinery this article has been describing: the coupling, the submitted-order gate, the 30-minute jobs, and the duplicated price lists. What you weigh against that is the option to adopt in pieces, because with Microsoft's pair the accounting can move first and the CRM later, on separate subscriptions. Odoo's own pages make parts of the trade visible: hosting on Odoo.sh, implementation, and some in-app credits sit outside the subscription (Odoo Pricing).

What the Odoo plans cost

On price, Odoo's public page lists Standard at EUR 24.90 per user per month and Custom at EUR 44.90, each a 12-month discount for initial users from EUR 31.10 and EUR 56.90 (Odoo Pricing). Both plans include Sales, CRM, and Accounting. A Light User seat is listed at EUR 7.90 and is sold through an Odoo advisor's quote. Custom is required for multi-company, Studio, and external API access. The page presents its list in euros, so get the US or Canadian dollar list in writing before you put it next to the Microsoft numbers.

Business Central alone, Sales plus Business Central, or Odoo

Three configurations cover the decision.

• Finance leads, pipeline lives in spreadsheets, quotes are few but large: Business Central alone
• Sellers need pipeline stages, shared quotes, and account history before an order exists: Dynamics 365 Sales plus Business Central
• You want quote to payment in one database and one system to train: Odoo

Business Central alone already runs the full cycle: quote, Make Order or Make Invoice, posted invoice, applied payment (Make sales quotes, Invoice sales). If the sales motion is relationship-led and the quote count is modest, this is the lean answer, and our Business Central implementation page shows how we phase it.

Add Dynamics 365 Sales when the pipeline needs structure the ledger cannot provide: stages, targets, and a quote several people shape before it hardens. Budget for the second license on every seller seat, the coupling work, and the price-list discipline described above. One caution from Microsoft's documentation: Business Central integrates only with Dynamics 365 Sales, and other Dynamics 365 apps that change the Sales data model, such as Project Service Automation, can break the integration (Manage customers using Dynamics 365 Sales). Our Dynamics 365 Sales implementation page covers the coupling and rollout in phases.

If the internal debate keeps circling which system should hold which process, our guide to ERP and CRM overlap sorts the boundary by process owner.

What to decide before you connect the two systems

Whether you connect Sales to Business Central or standardize on one product, six decisions decide how well the numbers agree:

1. The submit step. Name who submits the sales order in Dynamics 365 Sales after a win, and who covers when they are out.
2. Price rules. List every customer-specific price and quantity break, and mark which ones the standard sync can carry.
3. Write-in products. Map each one to a Business Central item or resource before the first order transfers.
4. Document type. Decide where a direct invoice is enough and where partial shipments or drop shipments require a full order.
5. Job cadence. Keep the 30-minute default or change it, and assign the statistics jobs that carry payment status to Sales.
6. Payment truth. Agree which number the month-end meeting uses, and how stale it may be.

Partner tiers deserve one clarification and then a lower priority. Microsoft's Solutions Partner designations and Odoo's Ready, Silver, and Gold levels describe a vendor's program standing, which says little about who sits across the table in week three. The tests that decide are concrete: the named consultant who will run your phases, the hours behind the fixed part of the quote, references from Sales-to-Business Central couplings at companies your size, a written phase plan with an acceptance step per phase, and ownership of configuration and code when the work ends. Ask every bidder for those five in writing.

This is the work we do. When we scope a Sales-to-Business Central coupling, the phases follow the Flectic Accelerated Delivery Framework, and our target for a first usable phase is 8 to 12 weeks, sized on your own price rules and document volumes. If the re-key step is costing you days every month, bring ten recent quotes and the invoices built from them to a call, and we will map which steps belong in Business Central, which ones earn Sales its seat, and what phase one should contain.

How Flectic can help

Flectic implements Dynamics 365 Sales for sales teams of 20 to 100 people in the US and Canada that quote in one system and bill in another. We set up quotes on the opportunity and convert won deals into Business Central sales orders. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call with Flectic to map the quote-to-cash handoff and scope the Dynamics 365 Sales implementation.

Sources

• Manage customers using Dynamics 365 Sales, Microsoft Learn, October 2026
• Integrating with Dynamics 365 Sales, Microsoft Learn, October 2026
• Enable sales order processing integration, Microsoft Learn, October 2026
• Make sales quotes, Microsoft Learn, October 2026
• Invoice sales, Microsoft Learn, October 2026
• Dynamics 365 Sales pricing, Microsoft, October 2026
• Dynamics 365 Sales pricing (Canada), Microsoft, October 2026
• Dynamics 365 Business Central pricing, Microsoft, October 2026
• Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026
• Create quotations, Odoo, October 2026
• Invoicing policies, Odoo, October 2026
• Payments, Odoo, October 2026
• Odoo Pricing, Odoo, October 2026
• The Basics of the Quote-to-Cash Process, Salesforce, October 2026