How a Leading North American Commercial Vehicle Manufacturer Managed Return Purchase Orders and Warehouse Return Movements in Dynamics 365 Finance & Operations

1. The Problem: Why Return Purchase Orders Matter

In any supply chain, orders don’t always go as planned. Quality issues, over-shipments, damage, and spec mismatches happen. When they do, the warehouse receives material that doesn’t meet requirements—and the system needs to reflect that.

A Return Purchase Order is not just a procurement transaction. It’s an operation that touches procurement, inventory management, warehouse operations, and finance. Miss a step, and you create:

1. Inventory mismatch — on-hand quantities that don’t match physical stock
2. Supplier master data drift — invoices tied to prices that no longer apply after returns
3. Warehouse disruption — excess stock, blocked pallets, confusion on what’s usable
4. Finance rework — accruals and liabilities out of sync

This guide walks through how D365 F&O handles Return Purchase Orders, with focus on the warehouse return movement process that keeps physical and system inventory in sync.

2. The Core Flow: Return Purchase Order in D365 F&O

Step 1: Create a Purchase Order Return

When material needs to be returned to the supplier:

1. Navigate: Accounts Payable → Purchase Orders → All Purchase Orders
2. Select the original PO
3. Action: Click Return Order (in the Ribbon, or Create menu)
4. System creates a return order linked to the original PO, with:
   1. Supplier reference intact
   2. Quantities that can be adjusted (typically the original received quantity is pre-populated)
   3. Line item details copied from the original PO
   4. Status = Open

Step 2: Warehouse Return Movement

Once the return order exists, the warehouse must physically move material out of active inventory. In D365, this happens via Transfer Journal or Movement Journal, depending on your configuration.

3. Warehouse Return Movement Options

Option A: Transfer Journal (Used in Most Implementations)

Used when material physically moves from one warehouse/location to another (e.g., floor → return staging area).

1. Navigate: Inventory Management → Journals → Transfer Journal
2. Create new journal entry
3. Add lines:
   1. From warehouse: where the inventory currently sits
   2. To warehouse: return staging/quarantine area
   3. Item number, quantity, UOM
4. Assign to Return Purchase Order (optional reference field)
5. Post
6. System adjusts on-hand in “From” warehouse, increases in “To” warehouse

Option B: Inventory Adjustment Journal

Used if you’re removing defective/unsaleable inventory entirely (scrap, damage).

1. Navigate: Inventory Management → Journals → Inventory Adjustment
2. Create new journal
3. Add lines:
   1. Item, warehouse, quantity
   2. Mark as “Loss” or “Damage”
4. Post
5. On-hand reduced; writeoff recorded

4. The Critical Step: Linking Movements to Returns

This is where many implementations stumble.

Solution:

1. Before posting the movement journal, reference the Return Purchase Order number in a comment or custom field
2. Or: Use a dedicated warehouse location code (e.g., RETURN_TO_[SUPPLIER_CODE]) that signals items are earmarked for return
3. Approach: Set up a return staging warehouse that acts as a holding area—all items destined for supplier return sit there until the truck pulls up

5. Configuration: Setting Up Return Movements

1. Warehouse & Location Setup

Ensure you have locations for returns:

Configuration path: Warehouse Management → Setup → Warehouse → Locations

2. Item Setup

For items subject to returns:

1. Tracking dimensions: Ensure Batch/Serial number tracking is enabled (if required by supplier)
2. Inventory model: FIFO/LIFO affects which “batch” of returned goods is removed first
3. Return shelf life: Consider tracking how long material can sit before it degrades

3. Journal Setup

Create journal templates:

Configuration path: Inventory Management → Setup → Journal Names and Lines

4. Return Purchase Order Policies

Enable auto-receive on return: (Optional) Some orgs automatically post the return to accounts payable when the return order is confirmed. Verify this matches your financial close process.

6. Common Challenge: Trade Agreement Alignment After Returns

From field implementations of supplier returns:

Controls:

1. Upon return processing completion, close the original PO lines in D365 (Status = Cancelled) to prevent future reference
2. Create a new PO at the updated trade agreement price for any remaining quantities needed
3. Maintain an audit trail by documenting the price adjustment and reason in the Return Purchase Order comments
4. Governance: Run monthly PO aging reports to identify trade agreements no longer in use before they create matching exceptions

Configuration: Accounts Payable → Purchase Orders → All Purchase Orders → Establish a review workflow or monthly reconciliation process to close obsolete PO lines

7. Warehouse Practices for Return Purchase Orders

1. Staging & Visibility

1. Segregate returns: Don’t commingle returned goods with active inventory
2. Label clearly: Use batch/lot labels tied to the return order number
3. System flag: Mark the warehouse location as “HOLD” or “RETURN” until shipped back

2. Receiving & Quality

1. Inspect on receipt: QA verifies the reason for return (damage, quality, overshipment)
2. Document in system: Update the return order with inspection findings (custom field or note)
3. Hold period: Set a grace period (e.g., 30 days) before scrapping items if supplier doesn’t arrange pickup

3. Shipping & Reconciliation

1. When the return is shipped, post a Transfer Journal from return staging → shipped location (or adjust on-hand)
2. Update Return Purchase Order status to “Shipped” (in your process)
3. Request RMA/credit note from supplier; link to return order for finance reconciliation

8. Configuration Checklist

9. Issues & Resolutions

10. Integration Considerations (Multi-System Environments)

If you’re integrating D365 F&O with a legacy system (e.g., IMS):

1. Return orders in D365 must sync with the legacy system’s PO master
2. On-hand inventory sync must account for items in “RETURN” staging (mark as unavailable for allocation)
3. Financial posting should trigger credit memo generation in legacy system
4. Testing: Perform a bi-directional return (create in D365, verify in legacy; vice versa)

11. Reporting & Monitoring

Reports

1. Return Orders Aging: Items in return staging >30 days
2. Return Purchase Order Summary: By supplier, by reason (damage/overshipment/quality)
3. Return-to-Revenue: Track how many returned items came back as new orders
4. Finance: Return credits posted vs. returns shipped (variance analysis)

Monitoring

1. Weekly review of return staging inventory (free up space, identify bottlenecks)
2. Monthly supplier scorecard (return rates, RMA responsiveness)
3. Finance close: reconcile posted returns to received credits

12. FAQs

Conclusion

Return Purchase Orders are often overlooked in implementation planning, but they affect operational health. Configuring the return process properly ensures:

1. Inventory accuracy (physical and system stay in sync)
2. Supplier accountability (documentation of what was returned and why)
3. Finance accuracy (credits post on time; variances don’t cascade)
4. Warehouse efficiency (space freed up, confusion reduced)

The key is connecting the dots: return order → warehouse movement → supplier shipment → credit receipt. Miss any step, and the entire loop breaks.

Questions for Your Implementation?

When setting up Return Purchase Orders in D365, ask yourself:

1. Do we have dedicated return staging areas, or do returns sit mixed with active inventory?
2. How do we handle partial returns (e.g., return 10 of 100 units)?
3. What’s the approval workflow (does warehouse mgmt approve, or procurement)?
4. Who owns the “return to supplier” process—procurement or supply chain?
5. How do we track RMA numbers from suppliers?

Document your answers early, and your returns process will run like clockwork.