English
Talk to a Zoho Consultant

Customer story · Zoho Creator & CRM

Connecting accounting records to service delivery

Zoho Creator brought subsidiary transaction data into Zoho CRM so a regional accounting firm could track customers, projects and renewals.

Two accounting staff at a desk bringing three separate small stacks of invoice sheets into one organised central ledger, with a laptop and calculator.

Separate subsidiaries, shared operations

The client provided accounting, corporate-secretarial and related services through several subsidiaries across Singapore and the region. Each subsidiary had its own accounting system. Staff carried out substantial manual and paper-based work, while management needed to coordinate service quality and customer information across the group.

Management established a shared operations centre for its accountants and consultants. Supporting that arrangement required customer and transaction records from the different subsidiaries, project workflows, deadline notifications and renewal reminders. Zolution was engaged to build a custom system around those requirements.

Workflow

From invoice to operational record

  1. 01Accounting systems

    Customer details and invoice transactions

  2. 02Zoho Creator

    Consolidate and process source data

  3. 03Zoho CRM

    Track customers and projects across subsidiaries

  4. 04Service follow-up

    Deadline and renewal notifications

Customer and invoice data linked to projects and renewals.

Creator connected the existing systems

Zoho Creator acted as an intermediate application between the accounting systems and Zoho CRM. It consolidated customer and transaction information, processed that data into the form operations teams needed, and synchronised it to CRM. Sales, marketing and operations could then work with customer information across the entities.

When an invoice was created in an accounting system, its data was synchronised. Creator processed the information before passing it to CRM, where staff could track project status across the subsidiaries. Management could generate reports from these records.

The architecture retained the separate accounting systems. Creator handled the movement and preparation of information between those systems and CRM.

Deadlines and renewals were part of the scope

The system requirements covered project automation, internal deadline notifications and customer renewal notices. These requirements connected the transaction records to ongoing service work: staff needed to know which projects were in progress and which customers needed attention.

Questions for a similar shared-service model

For your own project, choose one invoice and follow it through to the work your team must deliver. Use these questions to plan the process:

  • How do you recognise the same customer when two subsidiaries hold different records?
  • What service information must be available before operations can start work?
  • What happens to the project record when an invoice changes or is cancelled?
  • Which dates determine staff reminders and customer renewal notices?
  • Which subsidiary’s information may each team see?

Use an anonymised invoice, a project record and a renewal example to test the proposed data mapping before extending it across all entities.

← All customer stories

Discuss a similar requirement

Where does your team’s
work get held up?

Talk to a Zoho Consultant