4
If we use mixed payments (for example Cash + Card) and automatic settlement, the statement posting ends with an error (in Eastern Europe localization). The reason is that the EEU localization does not properly map the (multiple) payments with (one) invoice in customer balance settlement and sometimes even uses some old open customer transaction for settlement that does not originate from the statement.

In code (class RetailEodStatementPaymentJournal method setPaymentLineMark): only the first payment transaction is marked for settlement, the others are not as there is already the first one marked. Then the amounts do not match and this results in journal posting error. Alternatively if there are any open customer transactions on the same customer, the same error can occur even by normal payment.

Has been reported as a bug, issue https://fix.lcs.dynamics.com/issue/results/?q=450485 , but the correction will only ensure mapping of the first payment with the invoice, not full settlement. In my opinion, full settlement is a must-have for most retailers in EEU.
STATUS DETAILS
Needs Votes

Comments

M

This is an error which appears in such case:
While processing the state Payments posted, generic exception encountered in retail statement SHOUSTON000051 in the controller : Posting results for journal batch number 25138 Voucher SVHOUSTON000419 No transactions are selected for settlement, although Settlement type: designated transactions was selected for customer 100001, voucher SVHOUSTON000419.
Update has been canceled because of an error.

Category: End of Day and Financials