When preparing reporting packages for German parent companies, local finance teams often face a familiar challenge: the figures in the local statutory accounts are correct, yet additional adjustments are still required before consolidation.
The reason is straightforward. A reporting package is not simply a copy of the local financial statements. Its purpose is to transform local statutory accounts into financial information that complies with the group’s accounting framework and reporting requirements. The same business transaction may therefore be presented differently in HB1 and HB2 reporting due to differences in accounting policies, presentation requirements and group accounting instructions.
Based on our experience supporting HB2 reporting package audits, several topics tend to recur year after year. Understanding these areas early can help finance teams improve reporting quality, reduce review comments and facilitate a smoother year-end reporting process.

A Different Lens on the Same Numbers
One common misconception is that a reporting package can be prepared simply by mapping local trial balances into group accounts.
In practice, most reporting differences do not arise from bookkeeping errors. Instead, they result from differences between local statutory accounting and group reporting requirements. As a result, adjustments and reclassifications are often necessary before the figures can be consolidated at group level.
The following areas account for a significant portion of the adjustments commonly identified during HB2 reporting package reviews.
| Topic | Local Statutory Reporting | Group Reporting Perspective |
| Expense classification | Based on local account structure | Reclassified according to group reporting requirements |
| Fixed assets | Local depreciation policy | Group-specific useful lives and capitalization rules |
| Revenue recognition | Local accounting treatment | Subject to group accounting policies |
| Provisions | Local assessment | Additional provisions may be required |
| Deferred tax | Local recognition approach | Subject to group instructions |
| Lease accounting | Right-of-use assets and lease liabilities may exist | May require reversal under HGB reporting |
| Intercompany balances | Gross presentation | Net presentation may be required |
Common HB2 Adjustments in Practice
While the specific requirements may vary from group to group, the areas listed above consistently represent the most common sources of GAAP differences between HB1 and HB2 reporting. Below we share several practical observations and recommendations for each area.
Expense Reclassification
Common Observation
One of the most common differences between local statutory reporting and group reporting relates to expense classification.
While local financial statements often present expenses according to business functions, group reporting may require expenses to be classified according to their economic nature. As a result, personnel costs, depreciation and service-related expenses are sometimes mapped differently in the reporting package.
Auditor’s Recommendation
- Review mapping logic annually rather than relying solely on prior-year mappings.
- Consider the economic nature of transactions when assigning HB2 accounts.
- Discuss unusual classifications with the group accounting team before submission.
Fixed Asset Depreciation Adjustments
Common Observation
Differences frequently arise because local accounting policies and group accounting policies apply different useful lives, residual values, capitalization criteria or depreciation start dates. In some cases, expenditures capitalized under local accounting standards may need to be expensed under group accounting policies.
Auditor’s Recommendation
| Key Area | Recommended Practice |
| Useful lives | Review annually against group policies |
| Residual values | Reconcile with group assumptions |
| Capitalization rules | Assess significant additions individually |
| Depreciation calculations | Maintain a dedicated HB2 calculation schedule |
Revenue Recognition Differences
Common Observation
Revenue recognition remains one of the most sensitive areas in reporting package preparation.
Certain revenue recognition methods accepted under local accounting standards may not be permitted under the group’s accounting framework. Consequently, revenue and profit may require adjustment before consolidation.
Auditor’s Recommendation
- Review significant customer contracts before year-end.
- Assess whether local revenue recognition is consistent with group requirements.
- Prepare supporting calculations for material GAAP differences.
Provision Adjustments
Common Observation
Provision calculations are often straightforward in principle. However, practical challenges may arise when the underlying assumptions or source data are incomplete, outdated or inconsistent with group requirements.
Inventory provisions, bad debt provisions and warranty provisions are among the most common areas requiring attention.
| Provision Type | Common Challenge |
| Bad debt provision | No calculation performed or methodology not documented |
| Inventory provision | Calculation based on incomplete inventory data |
| Warranty provision | Assumptions not aligned with accounting manual |
| Other provisions | Insufficient supporting documentation |
Auditor’s Recommendation
- Reassess key assumptions at each reporting date.
- Ensure supporting schedules align with the latest Accounting Manual.
- Document significant judgments and estimates.
Deferred Tax Adjustments
Common Observation
Deferred tax treatment varies considerably among groups.
Some groups require deferred tax recognition at reporting package level, while others apply specific restrictions at single-entity level. As a result, deferred tax calculations frequently become an area of discussion during the reporting process.
Auditor’s Recommendation
- Review group instructions before preparing deferred tax calculations.
- Document temporary differences clearly.
- Maintain a reconciliation between GAAP differences and deferred tax balances.
Lease Accounting Adjustments
Common Observation
Under the New Lease Standard, local entities may recognize right-of-use assets and lease liabilities. However, certain HGB reporting packages require these balances to be reversed for consolidation purposes.
Auditor’s Recommendation
- Maintain a dedicated lease reconciliation file.
- Prepare supporting calculations for any HB2 adjustments.
- Review group accounting requirements before year-end reporting.
Intercompany Balance Reclassification
Common Observation
Local books typically present receivables and payables separately. For group reporting purposes, certain intercompany balances may need to be presented on a net basis. This is particularly relevant for consolidation reporting.
Auditor’s Recommendation
- Reconcile intercompany balances regularly throughout the year.
- Ensure related-party disclosures are complete.
- Confirm netting requirements with the group accounting team.
Practical Checklist Before Submission
Before submitting a reporting package to the group auditor, finance teams may find the following checklist helpful:
| Question | Status |
| Is the account mapping complete and documented? | □ |
| Are all GAAP differences supported by calculations and evidence? | □ |
| Have key provisions been reassessed under group policies? | □ |
| Does retained earnings reconcile to the prior-year reporting package? | □ |
| Have intercompany balances been reconciled? | □ |
| Has all non-financial information been completed? | □ |
| Has the latest Accounting Manual been reviewed? | □ |
Key Takeaways for Finance Managers
Successful reporting package preparation is not about minimizing adjustments. It is about identifying GAAP differences early, documenting them properly and ensuring compliance with the Group Accounting Manual before submission.
Finance teams that invest time in understanding group reporting requirements, maintaining robust supporting documentation and proactively communicating with group accounting teams typically experience fewer review comments and a smoother year-end reporting cycle.
Ultimately, a high-quality reporting package is not only a compliance requirement. It is also an opportunity to strengthen reporting transparency, improve consolidation efficiency and build confidence in the financial information reported to the group.
How can we help you?
Mandy Li
Manager