Luxembourg subsidiary of a French group: organising the close and the reporting

A Luxembourg subsidiary of a French group lives with two clocks.

The first is local: annual accounts under Lux GAAP, approved by the shareholder, filed with the Trade and Companies Register within seven months of the year end. The second is the group’s: a consolidation package expected a few days after closing, in the group’s framework, with its own rules and its own chart of accounts.

These two clocks run neither at the same speed nor in the same language. Most of the friction we see comes from that, not from any technical difficulty.

I. Two frameworks, two purposes

Luxembourg statutory accounts serve a legal and tax purpose: they are the basis for computing tax and for distributing dividends. They remain in principle prepared under Lux GAAP.

The consolidation package serves a financial reporting purpose: it feeds the group accounts, prepared under IFRS or French standards. It does not replace the statutory accounts and does not contradict them: it adjusts them.

Confusing the two leads to two symmetrical errors: producing the package from the group accounts and then having to rebuild statutory accounts, or producing the statutory accounts without anticipating the adjustments and discovering in February that six months of information is missing.

II. The adjustments that always come back

Whatever the activity, the same differences appear from one year to the next. Anticipating them turns a reconstruction into a simple carry-forward.

• Fixed assets and depreciation: useful lives and methods chosen locally often differ from group policy. The difference is permanent and should be tracked in a dedicated schedule, not recomputed each year.
• Provisions: Lux GAAP and IFRS do not share the same recognition criteria. A local provision may be reversed on consolidation, and vice versa.
• Leases: under IFRS 16, a contract expensed locally becomes a right-of-use asset and a liability. It is the adjustment that most surprises service subsidiaries.
• Trade receivables: the IFRS 9 expected loss model requires a provision from the outset, where local practice often waits for the incident. A provision matrix by ageing bracket is enough, but it has to exist.
• Exchange differences: the default exchange accounts in an ERP frequently point to the wrong categories, which distorts the group notes.
• Deferred tax: every adjustment generates one. It is the line most often forgotten, and the one the auditor looks at first.

III. Intercompany balances, where the time goes

Reciprocal entries are rarely wrong. They are rarely reconcilable, which is not the same thing. Three causes recur.

• Cut-off dates: an invoice issued on 31 December on the French side and posted on 2 January on the Luxembourg side creates a difference that is perfectly explainable and perfectly blocking.
• Currencies: two entities translating, one at the spot rate and the other at the closing rate, never land on the same amount.
• Undocumented recharges: a management fee with no written agreement raises a transfer pricing problem before it raises a consolidation problem.

The remedy is not accounting but organisational: a monthly reconciliation, not an annual one, and an identified contact on each side. Groups that do this close in days; the others in weeks.

IV. A timetable that holds

The reverse planning that works starts from the group deadline, not from the statutory filing date.

The order matters: the package goes out before the statutory accounts are final. That is normal, provided the differences between the two are tracked and explained, rather than discovered later.

V. What the auditor looks at

Whether it is the Luxembourg statutory auditor or the group auditors, three points attract the attention.

• The audit trail: every adjustment must be supported by a document, not by someone’s recollection.
• Consistency between the two sets of accounts: a reconciliation from the statutory result to the contributed result must exist and tie to the cent.
• Judgement: provisions, useful lives, IFRS 9 forward-looking scenarios. These choices must be explainable, not merely applied.

An unsupported provision is a fragile provision. That holds in consolidation as much as in statutory accounts.

VI. Why the adviser matters

A poorly supported Luxembourg subsidiary produces correct local accounts and a package the group cannot read, or the reverse. Either way, the French finance department spends its time translating.

The gain does not come from any particular technique. It comes from an adviser who knows both frameworks, understands what a French consolidation team needs and knows what Luxembourg filing requires, without having to be told either.

Conclusion

Keeping the books of a Luxembourg subsidiary of a French group is not keeping Luxembourg books and filling in one more schedule. It is running two frameworks in parallel, with two timetables and two audiences.

Done properly, it is invisible: the group gets its package on time, the filing is made within the deadline, and the auditor asks no questions. Done in a rush, it ties up the group finance department for weeks.

At Ease Advisory we keep accounts under Lux GAAP and IFRS, produce consolidation packages and prepare financial statements through to review. The firm’s founder worked in a Big Four practice and has worked with both frameworks for thirteen years: both accounting languages are spoken here. A subsidiary to take over or a close to secure? Let us talk before the next reporting date.

Need support on this? Discover our accounting & reporting service in Luxembourg or contact Ease Advisory.