UK VAT groups need a member-period ledger

Resolve the dated member set before the tax treatment

HMRC's official guidance describes VAT grouping as treatment of two or more eligible persons as one taxable person. That treatment does not make the participating legal persons disappear. For each material date, retain the group identifier, group VAT number, member legal name and identifier, eligibility basis reviewed by the responsible tax owner, membership application or change record, HMRC response, effective start and end, and the representative member. Unknown or disputed dates should remain unresolved rather than being inferred from a current portal view.

The notice says the group VAT number can remain the same even when membership or the representative member changes. A current number is therefore not proof that a named entity belonged to the group on an earlier supply date. Build a member-period ledger that preserves additions, removals, refusals, backdating decisions, and superseded records. The ledger is an editorial control recommendation; HMRC does not prescribe a particular software model, and this article does not determine whether any person is eligible or grouped.

Apply group treatment to the actual supplier and recipient

HMRC says supplies between members of the same VAT group are normally disregarded, while its notice also explains circumstances in which that result does not apply. A system should first identify the legal person that actually supplied or received the goods or services, then resolve whether both parties were members of the same UK VAT group at the relevant time, and finally apply the reviewed treatment and exception logic. A shared group VAT number should not erase the transaction parties or become a universal disregard flag.

Retain the supply date, supplier and recipient, establishments involved where material, group and member periods, transaction type, invoice or source record, applicable guidance section or other authority selected by qualified owners, configured rule version, result, reviewer, and any later correction. Keep the member's factual identity separate from the representative member's group-return role. This decision object is membership and transaction treatment; it is not agent authority, a power of attorney, fiscal representation, managed filing, or return submission control.

Keep joins, leaves, and return effects temporal

The notice provides routes for adding and removing members, changing the representative member, and disbanding a group. It also discusses application timing, limited backdating, provisional treatment, refusal, and correction of a group return after a refused application. Those states should not be compressed into one active field. Record requested, received, provisionally treated, approved, refused, effective, removed, and corrected events separately, together with the source notice and the transaction or return populations affected.

A later membership decision can change the explanation for transactions already processed without changing what the business originally recorded. Preserve the original treatment, the later authority record, the reason an item was reassessed, the correction or disclosure path chosen by qualified owners, the affected return period, and reconciliation to the revised return or ledger. Do not backfill current membership across history or assume that every consequence follows solely from the date displayed in an internal master record.

Test one supply across a membership boundary

A useful systems test uses the same two legal persons and the same service before, during, and after a documented membership period. Add a requested membership date that differs from the effective date, an exception to ordinary intra-group disregard, a representative-member change that leaves the group number unchanged, and a later correction. Reviewers should be able to reproduce which member set and rule applied to each supply without consulting today's group view as a substitute for historical evidence.

Indirect Tax Monitor reviewed HMRC VAT Notice 700/2 on September 17, 2026. The source supports the official descriptions of single-taxable-person treatment, representative-member registration, a single group return, ordinary intra-group disregard, exceptions, group-number continuity, membership changes, and timing processes. It does not establish any taxpayer's eligibility, membership, supply treatment, liability, return, correction, or compliance. Current law, HMRC decisions, complete transaction facts, and qualified tax and legal review control those conclusions.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.