Group Finance and Tax Teams
How do businesses ensure invoice compliance across multiple legal entities?
Organizations operating through multiple legal entities must ensure each entity issues invoices in its own name with its own VAT registration number, archives its own invoices separately, and complies with the regulations of its jurisdiction. Shared service centers can process invoices on behalf of multiple entities but must maintain strict entity separation in invoice records and compliance reporting.
How must invoice records be separated between legal entities?
Invoice record separation requirements for multi-entity groups:
- Separate VAT registrations: Each entity has its own VAT number; invoices issued in entity name and number
- Separate Peppol IDs: Each entity registered with its own Peppol participant ID
- Separate archives: Invoice archives organized by legal entity; cross-entity access controlled
- Separate VAT returns: Each entity files its own VAT returns based on its own invoice records
- Entity-specific formats: Country of incorporation determines format requirements per entity
- Intercompany separation: Intercompany invoices between entities must be arm's length and independently compliant
Frequently Asked Questions
- Can a shared service center use one Peppol access point for all group entities?
- Yes, a shared service center can operate a single Peppol access point that manages participant IDs for multiple legal entities. Each entity still has its own participant ID registered in the SMP under its own identifier. The SSC access point routes inbound invoices to the appropriate entity processing queue and sends outbound invoices from the correct entity participant ID. This is the standard architecture for large corporate groups using a centralized AP function.
- How do mergers and acquisitions affect invoice compliance for acquired entities?
- When a business is acquired, its invoice compliance obligations do not transfer automatically. The acquired entity's VAT registrations, Peppol participant IDs, PDP subscriptions, and invoice archives remain the acquired entity's legal responsibility. Post-acquisition integration planning must include: assessment of the acquired entity's compliance status, integration timeline for systems, migration of participant IDs to the acquirer's access point, and decision on whether to retain the acquired entity's VAT registration or deregister and transfer its supplies to the acquiring group entity.