Topic results Transaction Reporter

CCH Trust Accounts
CCH Transaction Reporter 2.30
The document outlines updates for the Transaction Reporter module used with Trust Accounts, including compatibility with Trust Accounts 2020.1 and an updated help file format suitable for Windows 10. New fields related to client and fund performance metrics, securities transactions, and net income calculations have been introduced, enhancing reporting capabilities. A new FundPerformanceReport has been added to the Investment Ledger Master Reports. Notes indicate that some fields are report-specific, emphasizing targeted application in client and fund performance analysis.
More information
CCH Trust Accounts
In Transaction Reporter how should I group transactions when the same security is held more than once for a client?
Investment Ledger Reports may show the same security held multiple times for a client, risking the consolidation of transactions for separate holdings into a single entry. To mitigate this issue, it is recommended to use grouping by InvUniqueId to accurately distinguish transactions related to each unique holding.
More information
CCH Trust Accounts
How to speed up Transaction Reporter
The document emphasizes the advantages of using Filtering over Section Conditions when generating reports. It suggests that Filtering reduces the number of records included, enhancing report speed and simplifying the addition of totals.
More information
CCH Trust Accounts
How to speed up Previewing Reports in Transaction Reporter
The document advises on optimizing the report preview process during design by using a filter to display only a single client or security. This approach prevents lengthy previews that occur when all clients are displayed, streamlining the design process. Once the report is finished, the filter can be removed.
More information
CCH Trust Accounts
Date Formats in Transaction Reporter
This document provides instructions for entering dates in a specific format. It emphasizes the importance of including slashes (e.g., 01/01/2001) when inputting dates to ensure accurate validation. Failure to follow this format may result in incorrectly processed reports.
More information