Matched In-Transit Reports
We are currently building a report to pull Unmatched Supported and Matched In-Transit transactions for a specific period. During our testing we've noticed that any unmatched transactions that were supported that are now suggested matches are pulling out as "unmatched" transactions. I believe the reason for this is because support pulls from a different table than just unmatched transactions. Has anyone built a custom report and experienced anything similar?
Version (include the version you are using, if applicable):
Code Snippet (add any code snippets that support your topic, if applicable):