Help us shape the future of our products by submitting your own ideas and reviewing ideas submitted by other users. If you see an idea you like, feel free to vote it up and add any comments that you feel would be beneficial.
This is a collaborative community, so please join in, contribute your innovative ideas and help our product teams to shape their roadmaps and future product development.
Our teams will review the ideas which have received the most votes on a regular basis, meaning that not all ideas will receive updates. When an idea has received enough votes, the status will be updated to 'Under Review' and then a decision made.
Our account auditors are requiring ever more stringent control of deposit/ledger movement we're increasingly finding it difficult to reconcile certain types of ledger/deposit movement between stocklink and the journal.
The TransactionGUID column in LedgerDepositDet is the key for us to effectively audit what occurs on each transaction and also easily spot where any issues have arisen from but we're having problems with this because of either the way that the column is back-populated by the loyalty web service after a transaction is completed (document RFC 1) or because it isn't implemented at all for certain functions (document RFC 2).
Having these 2 changes would functionally mean every entry in ledgerdepositdet would be directly reconcilable to a media line in the journal's reporting_medias_fact table at a transactional level, allowing reconciliation at a mass scale, highlighting any technical problems easily and avoiding business week end of week issues relating to media totals not matching ledger/deposit entries.
