Making Tax Digital is discussed as a tax-team problem and accounts payable as a finance-ops one. They rest on the same foundation, and seeing the overlap saves duplicated effort.
Making Tax Digital and accounts payable are usually discussed in separate rooms. MTD is treated as a tax-team obligation about how returns are filed, and accounts payable as a finance-operations concern about how suppliers get paid. That separation hides a real overlap, because both rest on the same foundation: clean, digital, well-structured records of what a business buys and pays.
HMRC's MTD programme requires businesses to keep digital records and submit through compatible software, with digital links preserved end to end rather than data being copied by hand between systems. It is already in force for VAT and is extending to Income Tax Self Assessment in phases. The thread running through all of it is that the record must be digital, connected and auditable, from source document to submission.
Where MTD and accounts payable meet
Purchase invoices are tax records. The VAT you reclaim and the costs you deduct flow from the bills your suppliers send and the payments you make against them. So the quality of your accounts payable data is, directly, the quality of the data MTD depends on. If your AP process loses invoices in inboxes, re-keys figures between systems, or carries duplicate and unverified suppliers, the digital record MTD assumes is compromised at source.
The overlap gets sharper with e-invoicing. The UK's move towards structured, PEPPOL-aligned electronic invoices is the same impulse as MTD: machine-readable data, digital links, fewer manual touch-points. An accounts payable function that can receive and validate structured invoices is most of the way to the connected digital record MTD wants, and a function that still depends on PDFs and manual entry is fighting both battles by hand.
The risk of treating them separately
When MTD sits with tax and accounts payable sits with finance ops, two things go wrong. Effort is duplicated, because both teams build their own ways of capturing and tidying the same supplier and invoice data. And gaps open, because each team assumes the other owns data quality. The result is a digital record that is technically compliant but operationally fragile, accurate enough to file yet too messy to trust for anything else.
The better framing is that there is one underlying asset, a clean and connected record of suppliers, invoices and payments, that serves tax compliance, fraud control, and cash-flow visibility at the same time. Build that once and MTD, e-invoicing and good AP hygiene stop competing for attention.
What good looks like
A connected accounts payable network gives you that single asset. Suppliers are verified once and kept current, so the entity behind every invoice is known. Invoices and payment behaviour are captured as structured data rather than scanned images, so digital links hold from source to submission. And the audit trail is continuous, so when HMRC, an auditor or your own board asks how a number was reached, the answer is one query rather than an archaeology project.
This is the same data discipline that supplier verification and e-invoicing readiness call for. Do it for one purpose and you have done it for all of them. See how the network keeps records clean and connected.
The takeaway
Do not plan for Making Tax Digital and accounts payable as two projects. Plan for one clean, digital, verified record and let it serve both. The businesses that see the overlap will spend less and carry less risk than those that build the same foundation twice. For how MTD obligations apply to your business specifically, confirm the current HMRC requirements; this is an overview, not tax advice.