Many retailers have their POS tenders (i.e. Cash, Credit cards, debit card, etc.)deposited into the Bank aggregated by Day, by Store (i.e. Retail Channel), and by Tender (i.e. Method of Payment). When reconciling the Bank Statement to D365 transactions, it is highly desired to have the system transactions aggregated in the same manner so that the Bank reconciliation process can match them to the bank statement.

Currently, the End of Day Statement creation process aggregates the POS payment journals by Day and by Store (by virtue of being on the EOD statement), but then aggregates by Customer and then by Tender. This leads to a situation where the payment data in the Bank module is de-aggregated versus the data that appears on the bank statement. In other words, the system creates a many (POS transactions) to one (Bank Statement transaction) situation for the Bank reconciliation function to deal with, which it can't.

Consequently, I have seen customization being built to aggregate the data or the client has to purchase a 3rd party reconciliation tool that can handle many to one matching.

Additionally, it would be beneficial to allow payment references on the payment journals, created during the End of Day Statement creation process, to be configured to pass relevant information, such as a Store ID, Tender ID, Merchant ID, etc. This will allow relevant information for bank reconciliation purposes to be available to build matching rules.