Engineering & integration
Bring an acquired company's data into a controlled reporting model. Preserve source history, map accounts and entities, and separate acquired contribution from comparable operating performance.
The problem
Common signals
Concrete output
Document source owners, extract cadence, entity identifiers, fiscal calendars, currencies, reporting cutoffs, and available history. Keep legal acquisition date, reporting inclusion date, and data availability separate so partial periods remain visible.
Map accounts, companies, locations, customers, and products at the required reporting grain. Retain original source codes, unmapped records, effective dates, and the reviewer responsible for classification changes.
Implement approved file, database, or API ingestion with source versioning, duplicate detection, validation, and a replacement policy. A corrected submission updates the active view without destroying the previously approved pack.
Show existing-company change and acquired contribution separately. Add explicit currency, calendar, reclassification, and elimination adjustments where required. Reconcile the bridge to the consolidated total and retain the approved basis of comparison.
Scope variants
Connect a bounded set of finance sources and KPIs for the incoming entity. Deliver its reconciled contribution, mapping record, unresolved exceptions, and approval path before expanding into detailed operating data.
Build a reusable source-request checklist, staging model, mapping review, and acceptance record for a platform business. Preserve business-specific exceptions instead of forcing every acquisition into the same assumptions.
Maintain a reporting path across legacy and target systems. Define the source of authority by entity and period, reconcile overlap, and test the reporting handoff before switching the active source.
Delivery approach
Agree the entities, periods, measures, reporting currency, and treatment of partial periods. Confirm which historical comparisons are supported by actual records and which require an explicitly labeled assumption.
Check completeness, uniqueness, signs, units, and source totals before transformation. Review unmapped accounts and duplicate entity keys with the people who understand the acquired company's records.
Compare the incoming contribution and consolidated measures to approved source reports. Keep adjustments separate from raw actuals, preserve any elimination entries, and make unresolved differences visible to the reviewer.
Test a late file, a corrected prior period, a changed mapping, and the next scheduled extract. Release with source ownership, exception handling, documentation, and a defined process for onboarding the next entity.
Technical context
Engagement fit
Anonymized proof
Permadyn's anonymized reporting accounts describe financial and operating source context, definitions, and governed review. The acquisition guide provides a fictional revenue bridge to make the method inspectable; it does not claim a named acquisition integration or a client growth result.Explore representative work
Questions
No. A shared reporting model can start with approved extracts or interfaces from the existing systems. The first requirement is an agreed data contract and reconciliation path, not a single ERP vendor.
Retain the reporting population for each period and identify the incoming contribution separately. For example, a fictional base moving from 50 to 55 plus 15 of acquired revenue reaches 70: 40% reported growth, but 10% growth within the unchanged base under the stated assumptions.
Retain the gap and explain its effect on the comparison. Use actual, estimated, and pro forma labels deliberately. The finance owner must approve any supplementary assumptions before they enter a management view.
Yes, with an appropriate scope and approved access. Location hierarchies, service dates, claims maturity, labor periods, and acquired reporting cutoffs need explicit treatment. The healthcare private equity page describes those operating distinctions.
Agreed source and output totals reconcile; mappings and adjustments have owners; duplicate and late-source cases behave as intended; and a reviewer can reproduce the released figures. The acceptance record also lists unresolved exceptions and whether they block publication.
Describe the incoming company, source systems, and first reporting decision. Start by defining the data and reconciliation work needed for an accepted combined view.
Discuss an acquisition reporting gapThe packaged engagements and delivery models make the commercial boundary visible without forcing every project into the same shape.