Making Tax Digital and HMRC reporting, what retention software buyers should check

What to take away

This site covers customer-success and retention software. The relevant question is not how to file VAT, but how the retention platform you buy feeds the finance systems that do.

Customer success and retention platforms hold renewal dates, contract values, usage signals, health scores and sometimes billing data. Those records feed finance systems that handle Making Tax Digital and HMRC reporting. If they are incomplete or late, the VAT return becomes harder to reconcile.

This article treats MTD and HMRC reporting as an integration and data quality test for retention software buyers. You are not buying tax filing. You are checking whether the customer success platform you choose can hand clean, dated records to finance, and whether the vendor documents that flow. Use the checklist below to judge retention software on its records.

What Making Tax Digital and HMRC reporting mean for retention software buyers

Making Tax Digital is HM Revenue & Customs' programme requiring VAT-registered businesses to keep digital records and file returns through compatible software. It is not a feature you buy from a customer success platform. It is an obligation your finance function carries, and every system holding transaction data either helps or hinders it.

That distinction matters when you evaluate retention software. A customer success platform holds renewal dates, contract values, usage signals and sometimes invoicing. If those records disagree with the ledger, someone reconciles them by hand each quarter.

HM Revenue & Customs publishes guidance on digital record keeping. For VAT, the key document is VAT Notice 700/22, Making Tax Digital for VAT: it explains digital records, digital links and the use of compatible software. Digital links must preserve an electronic link between relevant software; manually copying or re-keying VAT figures between systems does not meet that requirement. A retention tool sits upstream unless it performs a defined MTD function.

Most retention software vendors will not claim to be filing software. The useful question is what they export, in what format, and how reliably. Ask for a sample export and check whether it carries the fields your accounting system needs.

Buyers in Greater London and the South East often run several systems across sales, success and finance. Each handoff is a place where a VAT figure can drift. Fewer handoffs is usually better than a longer feature list.

Who actually carries the obligation

The company carries the obligation and remains responsible for its VAT return. If a vendor's integration drops a credit note, the business still has to address the missing record. Put written integration documentation in the contract, not just in a help centre article.

Where retention software sits in the chain

Contract signed in CRM, subscription created in billing, invoice raised in accounting, usage tracked in retention software. The retention platform is often the last to know about a mid-term upgrade or a partial refund.

The finance and CRM integration points that actually matter

Integration claims are cheap. Integration points are specific. When a vendor says it integrates with your finance stack, ask which objects move and in which direction.

Ask for the export schema and the exact records or objects transferred, not just a connector name. Check whether the transfer uses a CSV export/import or an API, and test customer, contract or subscription, invoice, credit note, refund, tax code, invoice date and tax point fields. Confirm how failed or amended records are identified.

Make the integration map concrete by listing the products already in your stack. Examples include Gainsight, ChurnZero, Totango and Planhat for customer success; Salesforce or HubSpot for CRM; Xero, Sage, QuickBooks or NetSuite for accounting; and Stripe or Chargebee for billing. These are examples to check, not a claim that every pair has a supported connector: verify the exact product, version, data direction and configuration with the vendor.

Start with the CRM integration points. You need customer and contract records flowing one way, and renewal or churn status flowing back. Without that return path, your finance team forecasts on stale numbers.

Then the accounting side. Invoices, credit notes, payments and refunds should map to named fields. Tax codes should carry through, not default to a single rate. Multi-rate and zero-rated lines are where manual fixes pile up.

A worked example helps. A subscription customer upgrades mid-quarter, receives a partial credit, then churns before renewal. Four records change: contract, invoice, credit note and churn status. If any one of them fails to sync, the quarter's numbers are wrong in at least one system.

For example, an upgrade invoice may export correctly while its later credit note loses the tax code or tax point. The ledger can then disagree with the source records even though the customer and contract synced; include that failure in the test and confirm how it is flagged and corrected.

Direction of travel

Most integrations are one-way. Bidirectional sync sounds better but creates conflicts. Decide which system is the source of truth for each field before you configure anything.

Frequency and failure handling

Real-time sync is not always safer than nightly batches. What matters is what happens when a sync fails: is there a queue, an alert, and a retry, or silent data loss?

VAT, invoicing and digital records inside customer success platforms

VAT is where retention software most often overreaches. A platform may store a contract value including VAT, but that does not make it a compliant invoicing system. For a full VAT invoice, check for the supplier's name, address and VAT registration number; a unique sequential invoice number; the date of issue and tax point; the customer’s name and address; a description of the goods or services; and the applicable VAT rate, amounts and total VAT.

Digital records requirements mean the underlying transaction data must be preserved digitally with links intact. If your retention platform is the only place a renewal value exists, and it overwrites history on each edit, you have a records problem.

Ask vendors how they handle record versioning. A contract that changed price three times should show three changes with dates, not one current figure. This is basic audit hygiene and it is often missing.

The Data Protection Act 2018 sets out how personal data must be processed and stored. Retention platforms hold contact details, usage history and sometimes notes about individuals, so the vendor is a processor and you are the controller.

The Data (Use and Access) Act 2025 amends parts of the UK data-protection framework. Ask vendors which provisions and processes apply to your use of the platform, and how they handle subject access requests.

This is not a reason to avoid a platform, but it is a reason to read the data processing agreement properly.

Check that the data processing agreement contains the processor terms required by UK GDPR Article 28, including documented instructions, confidentiality and security, controls on subprocessors, assistance with data-subject rights, and provisions for returning or deleting data and supporting audits. The Information Commissioner's Office (ICO) is the UK's data-protection regulator. A controller generally has one month to respond to a subject access request, so agree how the vendor will provide the information needed within that timeframe; extensions can apply in some cases.

What a compliant record looks like

A dated entry, the amount before and after tax, the tax treatment applied, and a link to the invoice it relates to. If a platform cannot show all four, it is not holding a digital record in the sense that matters.

Where VAT treatment gets lost

Discounts applied after invoicing, mid-term seat changes, and annual prepayments split across periods. Each one needs a rule, not a workaround.

Reconciling subscription billing with HMRC reporting cycles

Subscription billing and VAT reporting run on different clocks. Billing is continuous, often monthly or annually in advance. VAT returns are periodic, usually quarterly. Someone has to bridge that gap.

The bridge is a reconciliation, and it should be repeatable without a spreadsheet rebuilt from scratch each quarter. If your retention software holds the subscription schedule, it should be able to produce a period view that matches your accounting periods.

Timing differences are the main source of pain. An annual invoice raised in March may cover eleven months of the following year. Recognising revenue and accounting for VAT are separate exercises, and platforms often blur them.

Ask how the platform handles part-periods, upgrades, downgrades and cancellations mid-cycle. Each creates a proration calculation, and each proration has a VAT consequence.

Before you sign anything, price the whole arrangement. pricing models vary widely, and per-seat structures can make finance integrations expensive at scale. It is worth understanding how they interact with the number of finance users you need.

Buyers also underestimate the cost of making integrations work. The article on customer success software attribution methods covers attribution, while hidden costs are another procurement consideration. A full view of customer success software costs and pricing is a sensible input to any vendor comparison.

The quarterly close

Set a cut-off date, freeze the period, export from retention software and billing, then reconcile to the ledger. Document the exceptions. Repeat the same process next quarter.

What to automate first

The export itself, then the comparison, then the exception report. Automation of a broken process just produces faster errors.

A named integration checklist for UK finance and CS teams

Use this as a working document. Each line should have a named owner and a test result before contract signature.

Now the checklist to run before you sign.

Add a field-level export test before signature: verify that invoice numbers, issue dates, tax points, net amounts, VAT rates and VAT amounts survive the transfer, and that credit notes and refunds can be matched to the original transaction. Record the tested format, field mapping, exceptions and pass or fail result.

Two more items belong on the list for most UK buyers. First, confirm the vendor's own compliance posture, since you are handing over customer data. Second, check what happens at contract end: can you export everything in a usable format, and how long does the vendor retain it afterwards?

For the software check, use GOV.UK's 'Find software that's compatible with Making Tax Digital for VAT' service. Treat its compatibility information as a starting point: confirm that the exact products, connector and configuration in your stack transfer the records required by your process.

Running the test

Pick a real quarter, not a demo dataset. Ask the vendor to run the export with your fields and your tax codes. If they cannot, you have your answer.

Who signs off

Finance signs off the reconciliation, operations signs off the workflow, and both should see the test results before the contract goes to procurement.

Common questions

Official sources:

• HMRC guidance on Making Tax Digital for VAT tertiary legislation
• HMRC VAT Notice 700/22 on Making Tax Digital