Connect reporting and processes after an acquisition

You can keep useful local systems while connecting group reports and selected operating processes. The first task is to establish what each business records and what leadership needs to compare.

Cass & York builds data connections and internal tools across existing applications. For an acquisition, the work includes local record identity, common definitions, and the handoffs the group wants to share.

Start with the first management report

This fictional example involves North Services, acquired on July 15, and South Services, which has been in the group all year. North's system contains January through September activity.

A September operating comparison can include both businesses' September records once the event definitions are checked. A year-to-date ownership-period view needs a rule for North's pre-acquisition activity. Label the two views clearly and retain the source coverage behind each.

Record the acquisition date, reporting cutoff, and missing historical periods during onboarding. Those details should travel with the data rather than live in someone's email.

Local identifiers also need their context. North / Accounting A / invoice 1042 is different from South / Accounting B / invoice 1042. Customer names alone cannot determine whether accounts belong to the same legal entity or customer group.

Make the local categories comparable

Exterior wash

• Proposed group category: Exterior cleaning
• Onboarding decision: Confirm the service scope before mapping.

Building wash

• Proposed group category: Exterior cleaning
• Onboarding decision: Include only equivalent work.

Maintenance

• Proposed group category: Unresolved
• Onboarding decision: Inspect what the category contains.

“Maintenance” stays unresolved until someone familiar with the local operation explains it. A chart that displays the difference is more useful than a category mapping that hides it.

Share an approval while keeping the crew schedule local

Suppose the group wants the same completion evidence before billing review. In this proposed process, North's coordinator still works in the local scheduling application.

When a job is completed, a connected review queue brings its job reference and required evidence into the shared process. The local reviewer approves or returns the item. A missing signed form goes back to the local employee responsible; it does not disappear in a group total.

If the item remains unresolved beyond the group's chosen review period, the queue escalates it to the named group reviewer. That person sees the documents, local decision, and remaining question. The crew schedule stays local, while evidence requirements and escalation become common.

This process needs both local and group users to try the same item. Access must let the group reviewer inspect the affected business without granting every local employee access to every company.

Reuse the onboarding work

For North, the onboarding proposal starts with the reports leadership requests, the local applications, and one approval that is difficult to trace. Local operations and finance explain the records; group users define the comparison and review they need.

The proposed onboarding package contains the source map, company and customer identifiers, service mappings, reporting dates, import checks, and the shared approval sequence. South could then be onboarded using that package, with its differences recorded explicitly.

Shared operating reports and approvals are distinct from formal financial consolidation. Accounting treatments, intercompany eliminations, and cost allocation need finance ownership and a separate specification.

The initial delivery could combine a comparable group view with one shared review process. It should make both the reconciled records and unresolved differences visible. Plan the first business to connect.