Dynamics Community Forum Thread Details

Retail POS Return on Customer Order Invoiced Fails at Statement Posting

Dear Dynamics 365 Commerce Community,

I am facing a recurring issue related to POS Return transactions on items that are Batch-tracked, and I would appreciate any insights from those who have encountered or resolved a similar scenario.

Scenario:

- A customer returns an item from POS (either as a "Return by receipt" referencing an original Customer Order, or as a Blind Return).
- The item is Batch-tracked (Inventory Dimension Group has Batch Number dimension set as Active & Primary).
- The return transaction is captured in POS and aggregated correctly, but fails during Statement Posting at HQ.
- Error Message:
  
  "While processing the state Customer order invoiced, generic exception encountered in retail statement XXX-XXXXXX in the controller: Posting"
  "Batch number group is not specified on item and can therefore not automatically be created."
  "Inventory dimension Batch number must be specified."
  "Update has been canceled."
  
  Root Cause Analysis:
  The system fails to automatically resolve the Batch Number during the posting of the return transaction. When the return is linked to an original Customer Order invoice, the system is expected to inherit the batch number from the original sales line — however, it does not do so in our case. For blind returns (without referencing an original receipt), the system has no batch number to reference, and without a valid Batch Number Group or a Default Batch ID configured, it cannot create or assign one automatically.
  
  What We Have Already Tried (All Configurations Are in Place):
- Batch Number Group — A valid Batch Number Group is created and assigned to our item.
- Accounts Receivable Parameters — Auto Batch Reservation is set to "Yes", and Reservation is set to "Automatic".
- Commerce Parameters — "Use default batch ID when batch numbers are not found" is enabled, and a valid Default Batch ID is configured for the relevant items.
- Despite all of the above, the system does not automatically pick up or generate a Batch Number during the return posting, forcing our store staff to manually register/enter the batch number on the return line from within POS — which is neither a supported nor a practical workflow.
  
  The Question:
  Is there a standard or supported way in Dynamics 365 Commerce to enable automatic batch number resolution on POS return transactions (both return-by-receipt and blind returns) without requiring manual batch entry at the POS level? Or is this a known limitation that requires a customization/extensions to resolve?
  
  If anyone has successfully implemented a similar scenario — or is aware of a configuration/patch/customization approach — I would greatly appreciate your guidance.
  
  Thank you in advance for your time and support.
  
  Best regards,

Categories:

Dynamics 365 Commerce

Hi MPOS Activation,

1) Issue
- POS return transactions for batch-tracked items are successfully created (Return by receipt or Blind return)
- Transactions are aggregated correctly but fail during statement posting in HQ

Error messages include:
- "Batch number group is not specified on item and can therefore not automatically be created."
- "Inventory dimension Batch number must be specified."
- The system does not automatically populate the batch number during return processing
- Store users are forced to manually enter batch numbers in POS, which is not a practical or scalable solution

2) Reason
- Batch-tracked items require a valid batch number dimension for all inventory transactions
- During POS return posting, the system must either:
- Retrieve the batch number from the original sales transaction (return by receipt)
- Or generate/assign a batch number (blind return scenario)
- In Commerce, batch information is not always stored or passed fully through the channel database and CRT in a way that allows automatic resolution during returns
- Even with configuration such as:
- Batch number group assigned
- Auto batch reservation enabled
- Default batch ID configured
- These settings primarily affect supply-side transactions, not POS return flows
- For blind returns, no historical reference exists, so the system cannot infer a batch
- For return-by-receipt scenarios, batch information may not be propagated correctly from the original order to POS return processing
- As a result, the framework requires manual batch input to complete the inventory transaction

3) Resolution
Standard behavior:
- D365 Commerce does not fully support automatic batch resolution for POS returns in all scenarios
- Manual batch entry is often required for batch-controlled items

Recommended configuration checks:
- Ensure batch number group allows manual entry where applicable
- Verify that batch dimension is included in storage and tracking dimension groups
- Confirm that batch information is correctly stored on original sales lines and available in HQ

Design/workaround options:
- Restrict POS returns for batch-controlled items to Return by receipt only
- Train users to capture batch number during return in POS
- Use return reason codes or workflows to control process

Advanced solutions (customization required):
- Extend CRT (Commerce Runtime) to:
- Retrieve batch number from original transaction for return-by-receipt
- Automatically assign a default batch for blind returns
- Implement validation or lookup logic in POS to assist users in selecting correct batch

Alternative process:
- Perform returns for batch-controlled items directly in HQ instead of POS
- Or use controlled return flow via customer service/warehouse

Conclusion:
- This is a known functional limitation in standard Commerce behavior
- A fully automated solution typically requires customization or process redesign

For a more detailed answer, please provide more information.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References: