There are two scenarios when Batch number for Return transactions are not taken from sales transaction:

1. When return transaction is registered in POS without reference to sales transaction
2. When return transaction is registered in POS with reference to sales transaction but both transactions are posted in the same Statement

In both two scenarios when Batch number for return transaction is not taken from sales transaction there is required to setup Batch number group in Released product to enter new Batch number from sequence.

It is standard behavior but in effect it generates many new not necessary Batch numbers.

It would be better to use Default Batch number instead Batch number from sequence in such case like it is for cash&carry sales transaction.

Repro steps with 2 scenarios:

1. Register Return product operation in POS for Item with Batch number tracked (no reference to sales order),

• Upload by P job to HQ,
• Run Validation of retail transaction,
• Calculate and try to Post Statement

1. Register Sales transaction in POS for Item with Batch number tracked,

• Go to Show journal and select new created sales transaction,
• Register return transaction,
• Upload by P job to HQ,
• Run Validation of retail transaction,
• Calculate and try to Post Statement

In both cases there is presented error message in Statement:

While processing the state Customer order invoiced, generic exception encountered in retail statement xxx post aggregate controller while aggregating the transactions: 

Posting Posting Sales order: yyyy Item: zzz Batch number group is not specified on item and can therefore not automatically be created 

Posting Posting Sales order: yyyy Item: zzz Inventory dimension Batch number must be specified. 

Posting Posting Sales order: yyyy Item: zzz Update has been canceled. .

It would be better to assign Default Batch number id for return transaction instead of generating new ones from sequence number