What is the CCH Connector and what does it do?

What is the CCH Connector?

The standard client and user data used by Glide is often held in an existing practice/tax system such as CCH, and our connector provides a near real-time (every 15 minutes) integration between these systems and Glide.

The CCH connector allows your team to create/update data within CCH and then have that data replicated in Glide.

When a new client is created or an existing client is updated, SQL triggers add an entry into the glideInt database. Every 15 minutes, the connector will run one SQL select statement to read the rows created by the triggers since the last sync that need processing. Where records have been created or updated, a separate SQL statement will then extract the new information from the CCH database, which is passed to the Glide API. The connector will also look for new users and updates to existing users every time it runs.

The connector uses read-only credentials to the CCH database. Therefore, there is no risk of data loss; it does not and cannot create or change data inside your CCH system.

What does it do?

The connector in its default configuration will integrate the information listed below. We have principally included the core data required to ensure Glide functions correctly, as well as a small number of data fields that are stored in a standard fashion within CCH and the responsibilities tab. Responsibilities can be linked to Glide staff allocations at the client level, which in turn can automatically populate the job positions and job holders.

Custom fields can not be included as standard; however, we are familiar with the structure, and should they require integration and can provide this service for a small time-based fee.

• Client data:
  • Unique/permanent CCH client identifier (this will then link the clients on the 2 systems).
  • Client code.
  • Client name.
  • Client type (see notes below).
  • Company number (incorporated clients) - the Glide API connects to the Companies House API to obtain an accurate:
    • Incorporation date.
    • Year-end date for the next set of Accounts to be filed.
    • Made up date for the next Confirmation Statement to be filed.
  • Partner responsible.
  • Manager responsible.
    • Any other positions on the responsibilities tab can be linked.
  • E-mail address.
  • Mobile phone number.
• User data:
  • Unique/permanent CCH user identifier (this will then link the users on the 2 systems).
  • User code.
  • User name.
  • User initials.
  • User e-mail address.

Note that the CCH system does not provide an open API to enable reliable two-way communication; therefore, data updates should be made in CCH (not Glide), and these will then be automatically reflected in Glide. You can lock down these fields in Glide to make them read-only.

If you wish to create clients in Glide before they exist in CCH, for example, if you have a prospect flow in Glide, then you can do so, so long as the client codes are the same on both systems. When the CCH client is first sent to the Glide API, it will merge with the existing client with the same client code.

If you use our Xero integration or client-created webhook trigger, then new clients and client updates coming from CCH will immediately be shared with Xero or sent to the webhook.

Client type notes:

We take note of the CCH contact type when creating a new client, and this can be mapped to do the following:-

• Choose the Glide client type.
• Activate or deactivate workflow sub-systems.
• Choose workflow routes.

This is likely to create a more accurate presumption that the Glide defaults; however, it remains a default presumption, and this is not the same as the factually correct answers. It is therefore important that a team member reviews the newly created client and confirms the settings. This can be incorporated as part of an onboarding flow.

If you have a formal onboarding solution which issues engagement letters and has an accurate awareness of the services that are engaged for a client, then it would be desirable to integrate this system with Glide. This can be in addition to the CCH integration.