CCH Central 2025.3 Service Pack: Release Notes
Prerequisites
Installing CCH Central 2025.3 Service Pack
This release is installed using the Central Suite Installer. This ensures that all prerequisites are in place and that all the products for which you are licenced are installed in the correct sequence.
Click here to find out more about the Central Suite Installer.
Software Enhancements
CCH iFirm Integration
Linking CCH Centrals' Apply Team Security
Implemented backend changes to prepare CCH iFirm for inheriting CCH Central’s ‘Apply Team Security’ functionality. These changes do not affect current functionality for firms using Team Security within CCH Central.
Extra Logging for CCH Central Trace file
Extra logging is included in this Service Pack, but it must be enabled with guidance, as it will generate a large amount of logs into the trace file. To enable, open the ClientFramework.exe.config file and change the value from false to true for the following:
<add key="EnableiFirmExtraLogging" value="true" />.
Once the issue is resolved, it is recommended that you disable the extra logging by changing the value to false.
Note: It is recommended to enable/disable this key under the guidance of CCH Support.
Company Secretarial link to Central
When a record is created via Company Secretarial, the draft contact in CCH Central now defaults to the first available Company, Office, and Department. This change resolves the previous issue where draft contacts lacked these details, preventing conversion to a client or AML processing.
Quality Improvements
IDV Status and Documents not syncing to CCH Central
It was reported that after an IDV check had been performed, in some instances, the information was not fed back into CCH Central, resulting in the status and document within the AML Tab not being updated.
Multilayer Associations and Pushing records to CCH iFirm
Previously, when pushing data to CCH iFirm, all levels of associated entities were included—starting from the parent, then its associations (A), followed by A’s associations (B), and so on. Now, only the parent and its direct associations (A) are pushed, preventing unintended cascading associations.
Previously, this was what was being pushed
- Tony Stark (P)
- Stark Industries (A)
- Stark Internationals (A)
- Stain Networks (A)
And
- Stark Industries (A)
- Pepper Potts (B)
And
- Pepper Potts (B)
- Morgan Stark (C)
etc
Now, only Tony Stark and his direct associations (A) are pushed.
AML - IDV History showing incorrect employee name
Previously, when an IDV check was performed, the employee displayed in the AML Tab was the name of the employee who was logged into the CCH iFirm Console, rather than the employee who had performed the check.
AML - Errors in the Event Viewer
Previously, some firms reported errors in their event viewer (iFirmxxxSync Logs), indicating that the configuration for the iFirm_LastxxSyncDate key was not present, where xx represented AccountsProduction, Document, IDV, KYB, OM, or PersonalTax.