HMRC Digital Platform Operator Rules: What the July 2026 Update Means for Accounting Firms and CFOs

HMRC updated its official guidance on digital platform operator registration on 21 July 2026, adding live links to the registration service, the report submission portal, and the user management interface, and refreshing the XML schema download for structured reporting. For accounting firms advising marketplace clients, CFOs overseeing platform businesses, and any firm whose crypto accounting software feeds data into multi-sided digital markets, this update is not administrative housekeeping. It is a signal that the registration and reporting infrastructure is fully operational and that HMRC is expecting compliant filings. Missing the registration window or misclassifying a platform now carries real enforcement risk.

What Makes a Business a Digital Platform Under HMRC Rules

The HMRC guidance sets out a two-limb test. A business qualifies as a digital platform if, first, it connects sellers to customers for the supply of goods or services, whether directly or through third-party arrangements, and second, it holds or can reasonably calculate the amounts paid to those sellers, or can obtain that figure from a third party.

Platforms That Fall Inside the Definition

The guidance gives three worked examples that illuminate where the boundary sits. A clothing resale app that collects buyer payments and remits them to sellers clearly qualifies: it connects parties and it knows the consideration. A holiday rental website where renters pay at the time of booking or later also qualifies, because the operator knows the rental amounts. More instructively, a taxi-booking software provider qualifies even when the driver collects the fare directly from the passenger at journey end, as long as the operator knows the booked job amount through the platform, even if additional costs agreed between driver and passenger off-platform fall outside its knowledge.

Platforms That Fall Outside the Definition

The guidance is equally precise about what does not qualify. An online marketplace that lets users advertise furniture for sale, where payment passes directly between buyer and seller by bank transfer or cash and the operator neither knows nor can reasonably ascertain the sale price, is not a digital platform. The operator connects parties, but the payment knowledge limb is not met. Separately, a cost-sharing arrangement where the platform does not allow sellers to profit from received payments, such as a ride-sharing scheme where drivers simply recover travel costs from contributing passengers, is also excluded.

For accounting firms, the practical implication is that the test is transactional and data-centric, not purely structural. A client that hosts a marketplace but routes all payments through an escrow or a third-party payment processor may still be captured if that processor's data is reasonably accessible to the operator. Auditors and CFOs should review data-sharing agreements with payment providers to determine whether the knowledge limb is engaged.

Who Must Register and When

A business that meets the digital platform definition must register with HMRC if it falls into one of the categories the guidance specifies. Where the business is structured as a partnership, the registration obligation falls on the partnership as a whole, not on individual partners acting alone.

The Seller Reporting Perimeter

Registration triggers a downstream reporting obligation. Operators must report sellers who actively supply goods or services on the platform and who meet at least one of the following criteria: they are resident in the UK, they manage property rentals located in the UK, or they are entities such as companies, partnerships, trusts, or charities that conduct more than 2,000 property rentals per year through the platform.

There is a de minimis carve-out: sellers receiving a total of 2,000 euros or less (approximately £1,700 at current indicative rates) for fewer than 30 sales of goods in a year do not need to be reported. Importantly, the guidance makes clear that this exception is narrow. It applies only to goods sales, not to property rentals or service transactions. Operators who apply the carve-out too broadly risk material reporting gaps.

The July 2026 Amendments: What Changed Operationally

The substantive legal framework predates this update, but the July 2026 amendments matter because they make the compliance infrastructure live and actionable. HMRC has now added direct links to three operational components: the registration service itself, the report submission portal, and the user management tool for controlling who within an organisation can act on behalf of the operator. Additionally, the guidance refreshes the link to the current digital platform reporting XML schema, which governs the technical format of submitted reports.

XML Schema and Systems Integration

The XML schema point is material for firms with clients running automated data pipelines. If a client's crypto accounting software or broader ERP system feeds seller transaction data into a reporting workflow, that workflow must validate against the current schema version. Schema mismatches are a common cause of rejected submissions. The July 2026 schema update should prompt a version check across any automated reporting tools in use.

Accounting firms acting as agents for platform operator clients should also verify that their agent credentials are correctly configured in the user management system, since the guidance now links directly to that function. Agent access that was set up informally or never formally registered may not carry the permissions needed to submit reports on a client's behalf.

Accounting and Tax Implications for Platform Operators

The digital platform reporting regime operates in parallel with, and feeds into, broader tax compliance obligations for sellers on those platforms. From an accounting perspective, the regime effectively creates a third-party information trail that HMRC can cross-reference against sellers' own returns. For firms auditing platform operators, this means the operator's reporting data becomes an audit-relevant record: it must be complete, accurate, and consistently applied.

Revenue Recognition and Data Completeness

Platform operators often face revenue recognition complexity under IFRS 15 or FRS 102 where they act as agent rather than principal. The digital platform reporting obligation adds a layer of data governance to that complexity. The operator must hold reliable, auditable records of amounts paid to sellers, not only to discharge the HMRC reporting duty but to support any principal-versus-agent determination in the financial statements. CFOs should ensure that the systems capturing seller payment data are the same systems, or are reconciled to the systems, that feed the statutory reporting function.

Implications Where Digital Assets Are Involved

Platforms that facilitate transactions settled in cryptocurrency, stablecoins, or tokenised assets face an additional layer of complexity. The HMRC guidance does not explicitly carve out crypto-denominated transactions, which means that where a platform connects sellers and buyers and holds or can calculate the sterling equivalent of crypto payments, the digital platform reporting obligation likely applies. The sterling equivalent at the point of transaction is the relevant measure for both the reporting threshold and the seller's underlying tax liability. Firms advising clients in this space should be reviewing whether existing crypto accounting software captures per-transaction sterling values in a format that can be extracted and formatted against the XML schema.

This intersects with broader UK developments in digital asset regulation. The question of how UK rules apply to cross-border digital asset platforms is live and evolving, as explored in our analysis of US and UK alignment on tokenised assets and what it means for CFOs. Separately, firms tracking how distributed ledger infrastructure interacts with financial reporting frameworks will find relevant context in our piece on DLT in financial market infrastructure: accounting and compliance implications.

Practical Steps for Accounting Firms and CFOs

The operationalisation of the registration and submission infrastructure in July 2026 sets a clear action sequence for any practice with digital marketplace clients.

Immediate Actions

First, apply the two-limb test to every relevant client. The classification is not always obvious, particularly for hybrid platforms that combine listing services with optional integrated payment features. Document the analysis and the conclusion, because an incorrect self-assessment that a platform falls outside the definition is a potential compliance failure.

Second, for clients that are confirmed operators, check registration status against the live HMRC service now linked in the updated guidance. If a client has not registered and the obligation has already arisen, voluntary disclosure and late registration should be considered promptly.

Third, review the XML schema version in any automated reporting pipeline. A schema mismatch does not simply delay a submission; it may result in a rejected report treated as a non-filing by HMRC.

Medium-Term Governance

CFOs of platform businesses should embed the digital platform reporting cycle into the annual compliance calendar alongside VAT, corporation tax, and payroll reporting. The seller data collection, aggregation, threshold testing, and submission steps each have lead times that need to be accounted for. Firms that handle this reactively at year-end risk data quality failures, particularly where seller relationships are large in number or where payment data sits across multiple systems.

Agent access and user permissions in the HMRC portal should be formally reviewed. The July 2026 update's addition of the user management link is an invitation to tidy up access controls that may have been set informally. From an internal controls perspective, ensuring that only authorised personnel can submit platform reports is a basic governance requirement that auditors will increasingly scrutinise.

Finally, where a client's platform handles crypto-denominated transactions, the intersection of digital platform reporting and crypto tax obligations warrants a dedicated review. The appropriate crypto accounting software configuration, the sterling conversion methodology, and the schema output format all need to work in concert. This is a technically complex area where a joined-up approach between tax, accounting, and technology advisers is likely to produce better outcomes than each function working in isolation.

Frequently Asked Questions

Does the digital platform reporting obligation apply if my client's platform only lists goods without handling payments?

No. Under the HMRC guidance, the definition requires both that the platform connects sellers to customers and that the operator holds or can reasonably calculate the amounts paid. A pure listing or advertising platform where payment flows directly between buyer and seller and the operator has no access to transaction values does not meet the second limb and is not a digital platform for reporting purposes.

What is the de minimis threshold, and does it apply to all transaction types?

The de minimis exemption covers sellers who receive 2,000 euros or less (approximately £1,700) for fewer than 30 goods sales in a year. It does not apply to property rental transactions or service income. Operators should not apply the carve-out to those categories, or they risk under-reporting.

How does the XML schema update affect automated reporting pipelines?

HMRC's July 2026 guidance update includes a refreshed link to the current XML schema for digital platform reports. Any automated system that generates report files needs to validate output against this current schema version. Submissions using an outdated schema may be rejected, which HMRC could treat as a non-filing. A version check should be carried out immediately.

Does the obligation apply to platforms that process crypto or stablecoin payments?

The HMRC guidance does not explicitly exclude crypto-denominated transactions. Where a platform connects sellers and buyers and the operator holds or can calculate the sterling equivalent of payments made in cryptocurrency or stablecoins, the reporting obligation is likely to apply. The sterling value at the time of the transaction is the relevant measure. Firms should review whether their current crypto accounting software captures per-transaction sterling values in a schema-compatible format.

What should a firm do if a client has not yet registered but the obligation has already arisen?

The appropriate course is to assess the registration obligation as a matter of urgency, register using the live HMRC service now linked in the guidance, and consider whether a voluntary disclosure is needed in respect of any reporting periods already missed. Acting promptly and transparently is generally treated more favourably by HMRC than a failure identified through compliance checks.

Source: HMRC / GOV.UK