Platform · Groups and subsidiaries
One invoice. Two companies. Neither can read the other.
A group relationship is a billing arrangement, not a permission. Each controller files its own return, answers its own requests, and carries its own liability — and the parent does not get a window into the subsidiary because it happens to pay.
LagosPay Limited
RC 1544019 · ultra high level
SwiftRemit
RC 1698442 · extra high level
What the group relationship does and does not give you
Sharing a parent is not a lawful basis for sharing data
It is the assumption that produces most intra-group breaches: a head-office analyst pulling a subsidiary’s customer table because everyone reports to the same board. Group-wide rules can make a transfer lawful; a shared logo cannot.
One invoice, paid by the parent
The commercial relationship sits at group level, so finance deals with one bill instead of two.
Each company keeps its own registers
Separate activities, separate suppliers, separate retention rules. They are separate controllers under the Act and the product treats them that way.
Each files its own annual return
And can sit at a different tier. SwiftRemit is extra high level; LagosPay is ultra. One return does not cover both.
The group can see who exists
Names and tiers of sibling workspaces, so a group administrator knows what the estate contains. That is identity, not contents.
The parent cannot read the subsidiary’s records
Not activities, not requests, not people. Paying the bill does not widen a read, and there is no administrator setting that changes this.
Being in a group is not a lawful basis
Moving customer data between two companies needs a basis and, across a border, a mechanism — exactly as it would with a stranger.
TR-013 · group reporting to parent
Sending data to your own parent is still a transfer
LagosPay Holdings is in the United Kingdom. Monthly reporting to it leaves Nigeria, needs a mechanism, and appears on the register beside every supplier — because the Act does not care that you own the recipient.
What people assume
It stays inside the group
So nobody registers it, nobody assesses it, and it never appears in the notice. The first time it surfaces is when an auditor asks who receives management reporting.
What the register says
Registered, February 2026
Group-wide rules signed, approved, no expiry. Done properly it is one of the cleanest entries on the transfer register — and it took a signature, not an assumption.
Group-wide rules are the one mechanism built for exactly this. They bind every company in the group to the same standard, which is why a regulator accepts them — and why they take months rather than an afternoon.
What a subsidiary sees on its own billing page
That it is billed through the group, not a plan it does not hold
A subsidiary opening billing and seeing an invoice it cannot pay, on a plan nobody there chose, is how finance teams end up filing support tickets about their own company structure. Asiri says where the invoice actually goes.
And a workspace with no group entry stands alone — which is the ordinary case, and has to stay the cheap one.
SwiftRemit · billing
Billed through LagosPay Group
- Plan
- Held by the group
- Invoice goes to
- LagosPay Group
- This workspace pays
- Nothing directly
- Registers shared
- None