ORIGINAL COMPANY-CONTEXT PRACTICE
Consolidate subsidiary reports without losing local meaning
Original practice scenario: A hypothetical diversified holding group receives monthly subsidiary reports with different account codes and currencies. Design a reconciled analytical dataset.
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
Keep original submissions separate from the standardized reporting view. Consolidation requires an effective mapping and explicit measurement rules, not just appending spreadsheets with similar column names.
Work through it
- Define each submission by subsidiary, reporting period, version, currency and source account; reject duplicate keys and retain the original file reference.
- Apply versioned account mappings and approved period-specific conversion inputs, preserving unmapped accounts as exceptions rather than dropping them from the result.
- Aggregate at the intended reporting grain and reconcile both source and mapped totals, treating intercompany eliminations as separately identified adjustments.
Tradeoffs to discuss
- Central mappings improve comparability but can hide useful local distinctions; retaining both local and consolidated dimensions supports review at additional storage cost.
Common pitfalls
- Never join a source row to multiple active mappings and accidentally multiply its amount.
- A later resubmission must supersede a known version rather than appear as another month of activity.