When the store statement closing method is set to Date\Time and statements with Transaction date older than 30 days are scheduled to post statements in batch, the statements will not be added to the batch task.
There is a limitation in the RetailStatementPostChecker class to check for Transaction dates older than 30 days.
Customers who import retail transactions from legacy systems or statements with errors than need to be fixed, may need longer than 30 days to processes statements in batch. Imported statements may be too large to post manually so batch posting is needed.
We would like to see a parameter that allows customer to set their own days to check when transactions should be selected to post statements in batch.
Under Review
Ideas Administrator

Thank you for the product suggestion! We will continue to monitor this idea and the votes to determine if it will be given a position in our backlog.  -Holly Haines, Principal Program Manager



This would be very helpful to a customer of ours. We have a scenario where customers may return product and make a return against a sale over 30 days ago. This scenario seems to trigger the 30 day limit error for us. It would be great to customize the check for transaction dates so we don't have to manually post every statement that might match this scenario.

Category: Financials/Statements