Business Central Order Processing: Sales, Purchase & Fulfillment Workflows [2026]

Order Processing Overview

Order processing is the operational heartbeat of any manufacturing, distribution, or service business. Whether you’re fulfilling customer sales orders, procuring materials from vendors, or managing returns, efficient order processing reduces costs, accelerates cash flow, minimizes errors, and improves customer satisfaction. Microsoft Dynamics 365 Business Central provides comprehensive, integrated order processing capabilities spanning the entire supply chain—from customer inquiry through vendor payment.

This guide covers Business Central’s order processing workflows: sales orders, purchase orders, fulfillment and shipment, invoicing, approval controls, and advanced features like blanket orders, drop shipments, and order promising. Understanding how to leverage these features ensures your organization operates efficiently, maintains control, and scales as you grow.

Sales Quotes & Sales Orders

The sales process begins with a customer inquiry. Business Central supports two primary documents: Sales Quotes and Sales Orders.

Sales Quotes

A Sales Quote is a proposal sent to a customer outlining pricing, terms, and delivery. Quotes are non-binding (they don’t commit inventory or create GL entries). When quoting customers, salespeople can:

• Specify items & quantities: Select products, specify units requested, and BC looks up standard pricing
• Apply discounts: Volume discounts, customer-specific discounts, or promotional pricing
• Set terms: Payment terms (Net 30, 2/10 Net 30), delivery date, special instructions
• Add attachments: Specs, drawings, or technical documents
• Apply order promising: Check real-time ATP to promise realistic delivery dates

Quotes can be emailed directly to customers from BC. They include standard terms and company branding. When a customer accepts a quote, the salesperson converts it to a Sales Order with a single click. BC preserves all quote details (pricing, quantities, terms) in the order.

Sales Orders

A Sales Order is a binding commitment to deliver goods/services to a customer. Once created, a sales order:

• Reserves inventory (if applicable); ATP recalculates
• Generates a pick list for the warehouse
• Flows through fulfillment (pick → pack → ship)
• Becomes the basis for the customer invoice

Sales orders can be created from quotes, or directly if the customer calls/emails an order. Each sales order line has:

• Item: Product code, description, unit of measure
• Quantity: How many units ordered
• Unit Price: Price per unit (pulled from price list or overridden)
• Discount %: Line-level or order-level discount
• Requested Ship Date: When customer needs delivery
• Shipment Method: How items will be shipped (FedEx, UPS, freight, pickup, etc.)
• Line Type: Item (physical product), Service (non-inventory), or Charge (misc. fees)

Sales orders remain in “Open” status until fully shipped and invoiced. You can ship part of an order (backorder the rest) or hold an order pending customer approval. Once shipped, the order transitions to “Shipped” status pending final invoice.

The Order-to-Cash Cycle

The order-to-cash (O2C) cycle is the end-to-end process from order entry through payment receipt. Understanding this cycle helps organizations identify bottlenecks and optimize operations. Business Central automates and integrates each step.

Step 1: Quote & Order Entry

Salesperson quotes customer. If accepted, quote converts to Sales Order. Inventory is reserved. Cycle time: Hours to days depending on sales process.

Step 2: Pick & Pack

Warehouse staff receives pick list from the sales order. They physically locate items in inventory and move them to a packing area. BC can print pick lists sorted by location (to minimize warehouse walking) or by customer (to batch orders together). As items are picked, warehouse staff scans barcode (or manually confirms) in BC to mark items as picked. After picking, items move to packing & QC area. Warehouse staff confirms all items are present and correct. Cycle time: Hours to days depending on complexity and warehouse efficiency.

Step 3: Shipment

Once items are packed, create a Shipment document in BC. The shipment records the date, quantities shipped, tracking number (if applicable), and carrier. BC ties the shipment to the sales order. You can ship the full order or part of it (backorder logic handles the rest). Once the shipment is posted, the sales order status changes to “Shipped” and the items are deducted from inventory (cost of goods sold is recorded). Cycle time: Hours (same day pickup to days for freight).

Step 4: Invoice

Once shipment is confirmed, the shipped quantities become the basis for the Sales Invoice. The invoice records the revenue transaction (DR Accounts Receivable, CR Sales Revenue). The invoice is sent to the customer. Terms determine payment due date. Invoice cycle time: Immediate (same day as shipment) or batched (daily, weekly end-of-day invoicing).

Step 5: Payment & Cash Application

Customer receives invoice and pays (check, credit card, wire transfer, ACH, etc.). Payment is received and matched to the invoice in Accounts Receivable. BC marks the invoice as “Paid.” The O2C cycle is complete. Cycle time: Depends on payment terms (Net 30 = 30 days; Net 60 = 60 days) and customer payment reliability.

O2C Key Metrics

Metric	What It Measures	Business Central Support
Order-to-Ship Time	Days from order entry to shipment	Report on sales orders showing date created vs. date shipped
Order Fill Rate	% of orders shipped complete on first attempt	Backorder report; track orders shipped partially vs. fully
On-Time Delivery %	% of orders shipped by promised date	Shipment date vs. requested ship date comparison
Days Sales Outstanding (DSO)	Average days to collect payment post-invoice	A/R aging report; invoice date vs. payment date
Order Accuracy	% of orders shipped with correct items & quantities	Track returns & credit memos; correlate to specific orders

Inventory Shipments & Fulfillment

Once sales orders are booked, the warehouse must fulfill them. Business Central supports flexible fulfillment workflows.

Pick List Generation

Create a pick list (also called a pick slip or warehouse pick) from one or more sales orders. BC generates a list of items to be picked, organized by location or by order. Example pick list:

Item	Location	Qty. to Pick	Serial/Lot	Destination
Widget ABC	BIN-A1-01	25 units	LOT-2026-0312	Staging Area 1
Gadget XYZ	BIN-B2-03	10 units	SN-1001 to 1010	Staging Area 1
Widget ABC	BIN-A1-05	30 units	LOT-2026-0405	Staging Area 2

Warehouse staff use the pick list to locate and stage items. BC supports barcode scanning to record picks in real-time, reducing errors. Alternatively, warehouse staff can manually confirm picks later.

Shipment Document

Once items are staged and confirmed as picked, create a Shipment document. The shipment records:

• Shipment Date: Date items are physically shipped
• Line Items: Item, quantity shipped (can be less than ordered if backordering)
• Carrier & Tracking: Shipping carrier (FedEx, UPS, freight, etc.) and tracking number
• Destination: Ship-to address on the sales order
• Shipping Cost: Actual freight cost (if known; can be billed back to customer or absorbed)

When the shipment is posted, BC:

• Deducts items from inventory (physical inventory adjustment)
• Records COGS (cost of goods sold) in GL
• Updates sales order status to “Shipped”
• Generates an invoice (if enabled) or marks order ready for invoicing

Partial Shipments & Backorders

When inventory is insufficient to ship an entire sales order, you can ship what’s available and backorder the rest. Example:

• Customer orders 100 units of Widget ABC
• On-hand inventory is 75 units
• Backorder (outstanding PO) for 30 units arrives in 5 days

You can ship 75 units immediately (shipment posted), leaving 25 units as backorder. The sales order remains open showing 25 units outstanding. When the backorder arrives (5 days later), you ship the remaining 25 units. BC handles this by allowing you to specify “Quantity to Ship” per order line. You can ship partial quantities multiple times until the full order is shipped.

Serial & Lot Tracking

For items requiring traceability (food, pharma, high-value goods), Business Central tracks serial numbers and lot codes. When shipping:

• Specify which serial numbers or lot codes are included in the shipment
• BC ensures the customer receives items from the specified lots/serials
• Critical for recall management: if a lot is defective, you can identify which customers received it

Sales Invoicing & Revenue Recognition

Once items are shipped, you invoice the customer. Business Central provides flexible invoicing options:

Invoice Types

• Sales Invoice (Standard): Record of sale after goods shipped. Creates AR and revenue entry. Most common.
• Pro Forma Invoice: Non-binding proposal sent to customer before order; not posted to GL. Used for estimates or quotes that need invoice-like formatting.
• Service Invoice: For service-only transactions (consulting, support, repair) without physical goods. Posted immediately upon creation.
• Recurring Invoice: Automated recurring invoice (e.g., monthly subscription or retainer). BC generates and posts on schedule automatically.

Invoice Creation

After a sales order is shipped, you can create an invoice in two ways:

Option A: Automatic Invoice (Recommended)

Configure sales order posting to automatically create invoices when shipment is posted. This is the most efficient workflow and reduces manual steps. Invoices are created instantly with all order details pre-populated.

Option B: Manual Invoice

After shipment, manually create a Sales Invoice by referencing the shipment. You can batch invoices (e.g., daily end-of-day invoicing) or invoice as you go.

Invoice Content & Details

The invoice includes:

• Invoice Date & Number: Date invoice is issued; unique invoice number (sequential or custom format)
• Bill-To & Ship-To Addresses: Customer name, address, and shipping destination
• Line Items: Item description, quantity shipped, unit price, line amount, discount applied
• Subtotal, Tax, Total Amount Due: All mathematical totals
• Payment Terms: Due date, early settlement discount (if any)
• References: Original sales order number, shipment tracking number

Revenue Recognition & Accounting Treatment

Under accrual accounting (and IFRS 15 / ASC 606 revenue recognition standards), revenue is recognized when:

1. Goods are shipped (control passes to customer), or
2. Services are delivered, or
3. Performance obligations are satisfied

When a sales invoice is posted in Business Central, the following GL entries are recorded:

• Debit: Accounts Receivable (asset) — the customer owes you
• Credit: Sales Revenue (income) — revenue is recognized
• Debit: Cost of Goods Sold (COGS expense) — cost of the goods shipped (recorded when shipment posts, not invoice)
• Credit: Inventory (asset) — inventory is reduced by the shipped quantity

This double-posting (shipment posts COGS, invoice posts revenue) ensures accurate profit margin recognition.

Advanced Revenue Recognition

For complex scenarios, Business Central supports:

• Milestone-Based Revenue: Invoice based on project milestones (not shipment). Common in professional services and construction.
• Prepayments (Deposits): Customer pays deposit before goods ship; invoice reduces the prepaid amount.
• Revenue Deferral: For subscription or multi-period services, revenue is recognized ratably over the service period (not all at once).

Purchase Requisitions & Purchase Orders

Just as sales orders manage customer orders, purchase orders manage orders to your vendors. The process begins with a Purchase Requisition.

Purchase Requisitions

A Purchase Requisition (also called a Purchase Request) is an internal document requesting that procurement acquire goods/services. Requisitions can originate from:

• Inventory: When stock falls below reorder point, system auto-generates requisition
• Manufacturing: Production order needs materials; requisition created automatically
• User Request: Any employee can request purchases (office supplies, equipment, etc.)
• Blanket Order Releases: Release against pre-negotiated blanket order

A requisition contains:

• Item & Quantity: What’s needed and how much
• Requested Delivery Date: When it’s needed
• Preferred Vendor (Optional): Which supplier to buy from (BC may suggest based on price/lead time)
• Cost Center/Account: What GL account to charge (Expense or Inventory)

Approval Workflows for Requisitions

Organizations typically enforce approval controls on purchases:

• Under $500: Immediate approval (no human review)
• $500–$5,000: Manager approval
• $5,000–$50,000: Director approval
• Over $50,000: VP/Executive approval

Business Central routes requisitions through approval workflows based on amount. Approvers receive notifications and can approve/reject via email or portal. Once approved, the requisition can be converted to a Purchase Order.

Converting Requisition to Purchase Order

An approved requisition is converted to a Purchase Order (PO), which is sent to the vendor. The PO is a binding commitment to the vendor. The PO contains:

• PO Date & Number: Unique identifier
• Vendor Name & Address: Supplier and delivery location
• Line Items: Item description, quantity ordered, unit price, total cost
• Delivery Terms: Requested delivery date, shipping method, FOB terms
• Payment Terms: Payment due date (e.g., Net 30)
• Special Terms: Quality requirements, inspection procedures, etc.

Once the PO is created, it is typically emailed or transmitted to the vendor (EDI, API, or email). The vendor uses the PO to fulfill the order.

The Procure-to-Pay Cycle

The procure-to-pay (P2P) cycle mirrors the order-to-cash cycle but from the buyer’s perspective. Understanding each step helps organizations manage cash flow and vendor relationships.

Step 1: Requisition & Approval

Internal request for goods/services is submitted. Routed through approval workflow. Once approved, ready to convert to PO. Cycle time: Hours to days depending on approval workflow.

Step 2: Purchase Order

Approved requisition converts to PO. PO is sent to vendor. Vendor confirms receipt and shipping schedule. BC tracks PO status: Open, Partially Received, Fully Received. Cycle time: Immediate (PO creation).

Step 3: Goods Receipt & Inspection

Vendor ships goods. Your receiving team receives the physical shipment, inspects it for quantity and quality, and records the receipt in BC. The goods receipt document ties the shipment to the PO. Cycle time: Hours to days depending on goods volume and inspection rigor.

Step 4: Invoice Matching (Three-Way Match)

Vendor sends invoice. Your accounts payable team matches the invoice against the PO and goods receipt. BC automates this three-way match: Does the invoice quantity match the ordered quantity? Does the invoice price match the PO price? Does the invoice date align with the receipt? If all three match, the invoice is ready for payment. If there are discrepancies (e.g., invoice price is higher than PO, or quantity doesn’t match), the invoice is flagged for review. Cycle time: Days (manual matching takes time).

Step 5: Payment

Once the invoice is matched and approved, payment is scheduled. On the due date (per payment terms), a payment check or ACH is issued to the vendor. Payment is recorded in GL and marked against the vendor invoice. Cycle time: Depends on payment terms (Net 30 = 30 days; Net 60 = 60 days).

P2P Key Metrics

Metric	What It Measures	Business Central Support
PO-to-Receipt Time	Days from PO issuance to goods received	Receipt date vs. PO date; tracks vendor delivery performance
Receiving Accuracy	% of receipts matching PO quantity without discrepancies	Track receipt variance to quantity ordered
Invoice Accuracy	% of invoices passing three-way match on first submission	Track matched vs. exception invoices; exception rate
Days Payable Outstanding (DPO)	Average days before paying vendor invoices	Track invoice date vs. payment date; vendor aging report
Invoice Exception Rate	% of invoices with discrepancies requiring manual review	Report on invoices with quantity/price variances

Goods Receipt & Three-Way Matching

Accurate goods receipt and invoice matching are critical to payment controls and inventory accuracy. Business Central automates this process.

Goods Receipt Posting

When goods arrive from a vendor:

1. Receiving team inspects shipment for completeness and quality
2. Create a Goods Receipt (Purchase Receipt) document in BC tied to the PO
3. Scan items or manually confirm quantities received
4. Specify any discrepancies (damaged goods, quantity short, etc.)
5. Post the receipt

When the goods receipt is posted, BC:

• Adds the received quantity to inventory (at the specified location/bin)
• Records a GL entry: Debit Inventory, Credit A/P (accrual for unpaid goods)
• Updates the PO status to “Partially Received” (or “Fully Received” if all items received)

Three-Way Matching

Three-way matching is the process of validating that:

1. Purchase Order (PO) matches Receipt: Quantity ordered = quantity received?

2. Purchase Order (PO) matches Invoice: Invoice price matches PO price? Invoice quantity matches received quantity?

3. Receipt (GR) matches Invoice: Invoice quantity matches receipt quantity?

Example of three-way match:

Document	Item Widget ABC	Quantity	Unit Price	Total	Status
Purchase Order	Widget ABC	100 units	$10.00	$1,000	Ordered
Goods Receipt	Widget ABC	100 units	—	—	Received
Vendor Invoice	Widget ABC	100 units	$10.00	$1,000	Match!

All three documents align: 100 units at $10 = $1,000. Invoice is approved for payment.

Handling Exceptions

When discrepancies are found, they must be resolved before payment:

Scenario 1: Invoice Price Higher Than PO

PO Price: $10/unit. Invoice Price: $11/unit. This could be an error or a price increase. Contact vendor to confirm. Either: (a) require a credit memo for the difference, or (b) issue a PO change order to approve the new price.

Scenario 2: Quantity Received Less Than Ordered

PO: 100 units. Receipt: 95 units. Invoice: 100 units. Discrepancy: 5 units short. Contact vendor. Either: (a) wait for the 5 units to arrive and post a follow-up receipt, or (b) issue a credit memo for 5 units and close the PO.

Scenario 3: Goods Damaged on Receipt

Receipt confirms goods arrived but 10 units are damaged. Record the receipt for good quantity (90 units) and create a Return Order for damaged goods. Return them to vendor and request credit memo.

Blanket Orders & Framework Agreements

For recurring or long-term purchases, Business Central supports Blanket Orders (also called Purchase Agreements or Framework Orders).

Blanket Order Structure

A Blanket Order is a master agreement with a vendor for a specific product (or category) with pre-negotiated pricing and terms. Rather than issuing a new PO for each purchase, you issue “releases” against the blanket order.

• Blanket Order Characteristics: Long-term agreement (3 months to 1 year); specific item and pricing; negotiated terms; no immediate liability
• Releases Against Blanket Order: Individual orders (releases) against the master agreement; each release is a binding PO; amounts roll up against blanket agreement

Blanket Order Workflow

Step 1: Negotiate & Create Blanket Order

Procurement negotiates pricing and terms with vendor. Create a Blanket Order in BC specifying:

• Vendor name and terms
• Item and pre-negotiated unit price (e.g., Widget ABC at $10/unit)
• Blanket order quantity (total units available over agreement period, e.g., 10,000 units over 6 months)
• Agreement period (start date and end date)
• Payment terms, shipping method, etc.

Step 2: Issue Release Against Blanket Order

When procurement needs to order units, create a “Blanket Order Release” (a PO) that references the blanket order. Specify quantity and delivery date. BC validates the release against the blanket order: Is the unit price locked in at the blanket order price? Is the cumulative quantity within the blanket order limit? Once validated, the release is sent to the vendor.

Step 3: Receive & Invoice Against Release

The vendor fulfills the release. Goods receipt and invoicing flow as normal: receipt matches the release PO, invoice matches the release and receipt, payment issued.

Blanket Order Example

You negotiate with a supplier for 1,000 units of Widget XYZ at $50/unit over 6 months (blanket order created 2026-03-01 through 2026-08-31).

Release #1 (2026-03-15): Order 300 units, delivery 2026-04-01

Release #2 (2026-04-20): Order 400 units, delivery 2026-05-15

Release #3 (2026-06-10): Order 300 units, delivery 2026-07-01

Total released: 1,000 units at $50 = $50,000 (all at locked-in price, no price increases during the agreement period).

Benefits of Blanket Orders

• Price Certainty: Negotiate price once; all releases use locked-in price
• Volume Commitment: Vendor knows total purchase volume, often willing to offer better pricing
• Administrative Efficiency: One master agreement instead of multiple POs
• Flexibility: Specify delivery dates per release based on actual need (just-in-time)

Drop Shipments & Special Orders

In a drop shipment scenario, you (the reseller) take the customer order but the vendor ships directly to your customer. You never physically handle the goods.

Drop Shipment Workflow

Step 1: Customer Order

Customer places a sales order with you for a product. Mark the sales order line as “Drop Shipment.”

Step 2: Automatic PO Creation

When the sales order line is marked as drop shipment, BC automatically creates a linked purchase order to the vendor. The PO is sent to the vendor with instructions to ship directly to your customer.

Step 3: Vendor Shipment

The vendor ships the goods directly to your customer with packing slip showing the customer’s order number (not a PO number). Your customer receives the goods.

Step 4: Receipt & Invoicing

You receive notification from the vendor (or your customer) that goods were shipped. Post a goods receipt in BC against the PO. BC automatically posts a shipment against the corresponding sales order. The sales order is marked as shipped.

Step 5: Customer Invoicing & Vendor Payment

Invoice your customer for the goods (you set the markup). Pay the vendor per the PO. The difference between the vendor’s price and what you charged the customer is your margin.

Drop Shipment Advantages & Considerations

Advantages:

• No inventory holding costs (vendor holds inventory)
• Lower working capital (you don’t pay until you invoice the customer)
• Ability to offer products you don’t stock
• Streamlined fulfillment (vendor handles logistics)

Considerations:

• You lose direct control of fulfillment (vendor quality/timing impacts customer satisfaction)
• Customer visibility into actual cost (if shipment is not opaque)
• Returns must be coordinated between you, customer, and vendor

Order Promising & Available-to-Promise

Order Promising (Available-to-Promise, or ATP) is a critical feature that prevents overselling and improves customer satisfaction. ATP shows sales teams exactly how much inventory they can promise to customers without over-committing.

ATP Calculation

ATP is calculated in real-time as:

ATP = On-Hand Inventory – Committed Sales Orders + Open Purchase Orders

Example:

• Widget ABC: 100 units on-hand
• Committed sales orders: 60 units (already promised to other customers)
• Open purchase orders (arriving in 2 days): 80 units
• ATP = 100 – 60 + 80 = 120 units available

Sales teams can safely promise up to 120 units. Without ATP, they might promise 100 units (all current inventory), not knowing that 60 are already committed. When the order is processed, inventory would go negative, causing backorders and customer dissatisfaction.

ATP Workflows

Scenario 1: Customer Wants Immediate Delivery

Sales team checks ATP. 120 units available, but only 100 units are on-hand today. They can promise 100 units for immediate shipment, with 20 units backordered arriving in 2 days (when the PO arrives).

Scenario 2: Customer Flexible on Delivery Date

Sales team checks ATP and proposes: “I can promise 100 units for shipment today (current inventory), or I can promise 180 units if you’re willing to wait 2 days (when the PO arrives).” The customer opts for 150 units arriving tomorrow (partial delivery today, remainder when PO arrives).

ATP Configuration

In Business Central, ATP is configured per item:

• Include On-Hand Inventory: Yes (default)
• Include Committed Sales Orders: Yes (default) — reduces ATP by amount already promised
• Include Scheduled Receipts (POs): Yes (default) — increases ATP by incoming goods
• Include Planned Orders: Optional — if you have planned replenishment orders, include them in ATP
• Include Safety Stock: Yes (if configured) — reserves safety stock, reduces available ATP

Organizations can also set minimum ATP per item (e.g., “always reserve 10 units of critical items for emergency orders”).

Returns & Credit Memos

Customer returns are inevitable. Business Central provides streamlined return and credit memo processes.

Return Order Workflow

Step 1: Return Order Entry

Customer calls to report damaged goods or requests a return. Create a Return Order in BC specifying:

• Customer
• Items being returned (item code, quantity, reason)
• Return date
• Restocking fee (if applicable; e.g., 10% for non-defective returns)
• Receiving location (where to receive returned goods)

Step 2: Receive Returned Goods

Customer ships goods back. When received, post a receipt against the Return Order. The returned items are added back to inventory (at the specified location, possibly quarantine area for inspection).

Step 3: Generate Credit Memo

Once returned goods are received and inspected, generate a Credit Memo. The credit memo is the inverse of a sales invoice:

• Credit Memo = negative sales invoice
• When posted, it reduces AR (customer owes you less) and reduces revenue

If a restocking fee was specified, the credit memo amount = (original invoice price – restocking fee). Example:

• Customer originally purchased 10 units at $100 each = $1,000
• Returned 3 units (not defective, just didn’t want them)
• Restocking fee: 10%
• Credit memo amount: (3 × $100) – 10% = $300 – $30 = $270
• Customer receives $270 credit; company keeps $30 as restocking fee

Warranty & Defective Return Handling

For defective goods under warranty, the return process is similar but no restocking fee is charged. The full purchase price is credited. Example:

• Customer purchased 5 units at $200 each = $1,000
• All 5 units arrived defective
• Return Order created, goods received back
• Credit memo generated for full $1,000
• No restocking fee (warranty coverage)

Approval Workflows & Authorization Controls

Organizations enforce controls on orders to prevent unauthorized spending and ensure financial discipline. Business Central supports configurable approval workflows.

Sales Order Approvals

Sales order approvals are typically used for high-value orders or orders to high-risk customers (new customers, customers with credit holds, etc.).

Common Sales Order Approval Rules:

• Orders over $100,000 require manager approval
• Orders to new customers (not in system > 30 days) require manager approval
• Orders to customers with past-due invoices require manager approval
• Orders to customers requesting extended terms (Net 90 instead of Net 30) require director approval

When a sales order triggers an approval rule, the order status becomes “Pending Approval.” The designated approver receives a notification (email or in-app). The approver can:

• Approve: Order proceeds to normal processing (fulfill, ship, invoice)
• Reject: Order is returned to the salesperson with rejection reason. Salesperson can revise or cancel.
• Delegate: Forward to another approver if the original approver is unavailable

Purchase Order Approvals

Purchase order approvals enforce spending controls and ensure budget compliance.

Common Purchase Order Approval Rules:

• POs under $1,000: No approval required (auto-approve)
• POs $1,000–$10,000: Manager approval
• POs $10,000–$50,000: Director approval
• POs over $50,000: VP/Executive approval
• POs over budget: Budget owner approval (in addition to amount-based approval)

When a requisition is created, BC checks approval rules and routes accordingly. Approvals are tracked, and approved requisitions convert to POs automatically or via user action.

Multi-Level Approvals

For complex organizations, approvals can have multiple levels. Example:

1. Manager approves POs up to $10,000
2. Director approves $10,000–$100,000 (and verifies manager approved if under $10,000)
3. VP approves over $100,000

BC supports sequential (one approver after another) or parallel (multiple approvers simultaneously) approval models.

Inter-Company Orders & Transactions

For organizations with multiple companies/subsidiaries in the same Business Central instance, inter-company orders allow one company to buy from or sell to another internally.

Inter-Company Sales Order Scenario

Company A (US) needs materials. Company B (Mexico) manufactures them. Rather than manual journal entries, BC streamlines inter-company orders:

Step 1: Company A Issues Purchase Order to Company B

Company A creates a purchase order to Company B for 500 units of Product X at $100/unit = $50,000.

Step 2: BC Automatically Creates Matching Sales Order

In Company B, BC automatically creates a corresponding sales order to Company A for the same 500 units at the same price.

Step 3: Company B Ships & Invoices

Company B processes the sales order: ships goods, creates a sales invoice. The invoice records revenue in Company B’s GL (AR to Company A, Sales Revenue).

Step 4: Company A Receives & Is Invoiced

Company A receives the shipment, posts a goods receipt (inventory increases). BC automatically matches the inter-company invoice. Company A’s GL records: Inventory (asset) and AP to Company B (liability).

Step 5: Settlement & Consolidation

At month-end, the two companies reconcile and settle via bank transfer or journal entry. In consolidation, the inter-company transaction is eliminated (no external revenue/expense recognition).

Inter-Company Configuration

To enable inter-company orders:

• Configure each company as a “vendor” in other companies
• Set up inter-company journal accounts (AP/AR for inter-company clearing)
• Enable inter-company posting and auto-matching
• Define inter-company pricing (cost plus % markup, or list price)

Benefits of Inter-Company Orders

• Transparency: Track internal transactions; visibility into supply chain
• Accuracy: Automatic matching eliminates manual reconciliation
• Efficiency: Automated GL posting; no need for manual inter-company journals
• Consolidation: System automatically eliminates inter-company transactions for consolidated reporting

Order Processing Best Practices

To optimize order processing in Business Central:

• Standardize Processes: Establish consistent sales and purchasing workflows. Avoid ad-hoc variations.
• Enforce Approvals: Use approval workflows to prevent unauthorized orders and maintain financial discipline.
• Leverage ATP: Train sales teams to use order promising to avoid overselling and backorders.
• Automate Where Possible: Auto-generate invoices from shipments, auto-match three-way invoices, auto-post receipts.
• Monitor Metrics: Track O2C cycle time, P2P cycle time, DSO, DPO, fill rates, and exception rates. Identify bottlenecks monthly.
• Manage Exceptions: Address discrepancies (short shipments, invoice mismatches) quickly to maintain vendor relationships and cash flow.
• Plan for Seasonality: Anticipate seasonal demand swings; manage ATP and safety stock accordingly.
• Collaborate with Partners: Share demand forecasts with key suppliers to improve lead times and reduce safety stock.

Conclusion

Business Central’s comprehensive order processing capabilities—spanning sales quotes through payment collection, and purchase requisitions through vendor settlement—provide organizations with the control, visibility, and efficiency needed to operate at scale. By mastering the order-to-cash and procure-to-pay cycles, leveraging approval workflows and order promising, and managing returns and inter-company transactions effectively, organizations can accelerate cash conversion, reduce operational friction, and strengthen both customer and vendor relationships. Whether you’re a distributor managing complex SKU volumes, a manufacturer coordinating materials and production, or a service firm tracking project-based work, Business Central’s order processing engine is purpose-built to support your operations.