HMRC self-billing needs agreement-to-invoice continuity

Resolve invoice authority at the transaction date

HMRC describes self-billing as an arrangement between a supplier and customer in which the customer prepares the supplier's invoice. Both parties must be VAT registered, and the supplier must agree to the arrangement. The useful operating object is therefore not a permanent supplier flag. For each invoice, retain the customer and supplier legal identities, their VAT registration numbers, the signed agreement identifier and version, its effective and expiry dates, the covered goods or services, any third-party processor, and the transaction that the invoice represents.

A system should test those facts at the relevant time before it labels an invoice self-billed. Agreement signed, currently effective, transaction covered, supplier identity matched, and invoice issued are separate states. If the agreement is absent, expired, awaiting review, limited to another business relationship, or tied to an earlier VAT number, route the item for accountable review instead of inheriting authority from a current master-data toggle. The article's continuity model is an editorial control recommendation; HMRC does not prescribe a particular software design.

Keep customer and supplier duties visible

HMRC says the formal agreement must authorize the customer to issue invoices on the supplier's behalf and confirm that the supplier will not issue VAT invoices for the transactions covered. That allocation prevents two invoices from silently representing the same supply, but it does not erase the supplier's role. The supplier remains accountable for output tax, should check the VAT rate used, and must notify the customer of specified changes including deregistration, a new VAT number, or a transfer of the business as a going concern.

Preserve the customer's creation and delivery evidence separately from the supplier's receipt, review, accounting, and change notices. Link the supply, invoice number, issue date, VAT date used, amount and currency, tax rate and amount, supplier details, required self-billing statement, copy delivered, payment reference, exception, and correction. A customer-issued document should not be posted twice as both a purchase invoice and a supplier sales invoice, and a portal receipt should not be treated as proof that either party completed its VAT accounting.

Branch cleanly when identity or registration changes

HMRC states that a customer must not issue self-billed invoices to a supplier that has changed its VAT registration number until a new agreement has been prepared. It also says deregistration changes whether VAT invoices can be issued and that a transfer of a business as a going concern can require a new agreement. These events need effective-dated records. Keep the old supplier and agreement history intact, open a new review, and identify which unbilled transactions fall before, across, or after the change.

Do not edit an old invoice to display the successor VAT number merely because the supplier master record changed. Preserve the originally applied identity and authority, the notification source and time, verification performed, accountable reviewer, effective boundary, items held, replacement agreement, resumed issuance, and any correction chosen by qualified tax owners. If the legal or VAT effect is uncertain, record that uncertainty. The operational workflow can protect evidence without deciding the tax treatment of a reorganization, deregistration, or cross-border arrangement.

Test agreement expiry against invoice populations

A representative test should use one supplier with a 12-month agreement, recurring transactions, an agreement review, a VAT-number change, a transaction near expiry, a late invoice, and a third-party self-billing processor. Confirm that every invoice resolves to the agreement and supplier state that applied, required fields and statement remain present, held items are visible, and a new agreement is required at the declared change boundary. Reconcile transactions covered by the arrangement to invoices issued, copies delivered, ledger postings, and exceptions rather than sampling only successful documents.

Indirect Tax Monitor reviewed HMRC's VAT self-billing guidance on September 20, 2026. The page was published July 1, 2014 and last updated December 31, 2020. It supports the described agreement, review, recordkeeping, supplier-change, invoice-content, and responsibility boundaries. It does not establish any taxpayer's VAT status, agreement validity, supply date, tax point, tax rate, invoice validity, input-tax entitlement, output-tax accounting, return treatment, correction, or compliance. Current law, complete facts, HMRC decisions, and qualified tax and legal review remain controlling.

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.