Custom Integrations for MTD: EPOS & Booking Systems

Why custom integrations matter for MTD ITSA

From April 2026 the Making Tax Digital (MTD) for Income Tax (ITSA) programme changes how many self-employed people and landlords report their income. Rather than only keeping paper records or sending an annual Self Assessment, HMRC expects businesses above certain income thresholds to keep digital records and make regular electronic updates using MTD-enabled software. For many businesses that rely on niche industry systems — EPOS at a café, booking systems at a salon, or a property-management platform for landlords — integrating those systems with MTD-capable software removes manual work, reduces errors and creates the digital trail HMRC expects.

Who this affects and the rollout timeline

The MTD ITSA rollout is staged by income. If you are a sole trader or landlord, check the timetable below to see when you must be compliant. If you are a limited company, note that MTD for Corporation Tax is not mandated for 2026 (it is an estimated later programme) but from March 2026 commercial software is required for filing CT600s.

• April 2026: Businesses with income over £50,000 must comply.
• April 2027: Businesses with income over £30,000 must comply.
• April 2028: Businesses with income over £20,000 must comply.

Common niche systems and the data they hold

Understanding what data your sector system produces is the first step to a reliable integration. Typical examples include:

• EPOS (electronic point of sale): daily takings, VAT rates, tips, refunds and payment method breakdowns.
• Booking and appointment systems: client details, intake fees, cancellations and deposits.
• Property or tenancy management platforms: rent received, tenants’ deposits, maintenance costs and service charges.
• Event ticketing platforms: ticket sales, commissions, and promoter payouts.
• Trade-specific apps (e.g. job management or timesheet software): labour hours, materials, job expenses and mileage.

What HMRC requires — practical implications

MTD ITSA requires you to use MTD-compatible software to keep digital records and submit regular updates. Practically this means:

• Your records must be digital and reliable; scanned paper records alone are not sufficient.
• Where possible, data should be transferred automatically between systems to preserve the audit trail and minimise manual re-entry.
• All transfers should leave a clear audit trail (timestamps, user IDs, import logs) so adjustments are explainable if HMRC queries your figures.

Integration approaches: which one suits you?

There are three common routes to get niche systems talking to MTD-enabled accounting software. Choosing depends on volume, budget and technical capability.

• Native connectors – Some accounting packages provide built-in connectors for popular EPOS or booking platforms. These are easiest: less configuration, predictable monthly costs, and vendor support.
• Middleware (integration platforms) – Tools such as Zapier-style platforms or specialist middleware can map and transform data between systems. They suit businesses using multiple niche apps that lack direct connectors.
• Bespoke API integrations – A developer builds a custom link between your system and accounting software. This is best for high-volume businesses or where data mapping is complex but costs more up front and requires ongoing maintenance.

Step-by-step framework for a reliable integration

Treat integration as a small project. Follow these stages to reduce risk and keep costs under control.

• Discovery: list the systems, identify the exact data points you need (sales, taxes, refunds, fees, customer credits) and how often data must move (real time, daily, weekly).
• Mapping: match fields in the source system to your accounting categories. Agree how to handle VAT codes, tips, refunds and partial payments.
• Choose a method: native connector, middleware or bespoke. Consider total cost of ownership, including support and future changes.
• Authentication and security: ensure secure API keys, two-factor authentication for admin accounts and least-privilege access for connectors.
• Testing & pilot: run a dry run on historical data, reconcile daily totals, and test failure modes before going live.
• Go-live & monitoring: start with a limited period (two to four weeks), monitor imports, reconcile bank takings and maintain a daily log of exceptions.

Data mapping tips specific to EPOS and booking systems

Two recurring issues cause reconciliation headaches:

• Payment aggregation: EPOS often aggregates card payments across multiple tills or terminals. Map the payment methods so the accounting record matches bank settlements, not gross takings.
• Multi-rate VAT: booking systems and EPOS might mix VAT rates in one transaction (e.g. food to eat in vs takeaway). Ensure your mapping keeps VAT at the item level where possible so the VAT calculation in your accounting software stays accurate.

Costs you should expect

Costs vary by approach and complexity. As a rough guide for small and medium firms:

• Off-the-shelf connector subscription: £0 to £50 monthly (some are included in accounting packages).
• Middleware platforms: £20 to £200 a month depending on volume and number of tasks.
• Bespoke integration: initial build £1,500 to £15,000+ depending on APIs, workflows and reporting. Expect ongoing support/hosting from £50 to £500 a month.

Those figures are illustrative. For some very simple EPOS setups the total cost is near zero; for a multi-site hospitality group a bespoke solution is more sensible. Budget also for staff time to test and reconcile during the first few months.

Security, backups and data retention

Under MTD you must retain records and be able to show how figures were produced. Practical security and retention best practice includes:

• Use encrypted connections (HTTPS/TLS) for all API traffic and restrict IPs where possible.
• Keep logs of imports and reconciliation steps for at least the HMRC retention period (generally six years for business records).
• Implement regular backups of accounting data and source-system exports, with offsite copies and a tested restore process.
• Review user permissions quarterly and use audit trails to track changes to transactions or tax codes.

Practical checks for compliance

Before you trust an integration to drive your MTD submissions, carry out these checks:

• Daily totals from the niche system reconcile to bank lodgements and your accounting takings.
• VAT treatment matches the business policy (do not let the integration assume a single VAT rate if you sell mixed goods/services).
• Refunds and discounts are imported as negative lines and reconciled to bank refunds.
• Fees or commissions charged by third parties (ticketing platforms or card acquirers) are captured separately so gross and net figures are clear for tax adjustments.

Common pitfalls and how to avoid them

Here are frequent mistakes we see, and the fixes that work:

• Relying on CSV imports alone: manually exporting and importing CSVs can create gaps and loses the digital chain. Use automated connectors where possible.
• Poor mapping of fees and tips: misclassifying tips as sales inflates income. Map tips to the correct nominal and exclude where appropriate from taxable takings if they are staff gratuities and handled separately.
• Ignoring timezone and date mismatches: sales taken late at night may land in the next business day. Define reporting periods and timezone policies explicitly in your mapping.
• Not monitoring exceptions: failed API calls or unmapped SKUs need action. Create an exceptions workflow so someone reviews and fixes issues daily.

Audit trail and corrections

If figures change after an automated import (for example, a booking is refunded), keep the correction in the system rather than overwriting historical exports. Maintain clear notes so your quarterly MTD updates and year-end finalisation show a coherent story.

Pilot checklist for a smooth rollout

• Pick a low-risk period (a quiet month) for a pilot run of the integration.
• Compare pilot results to historical ledgers and bank statements.
• Train staff on how to flag anomalies and who to contact when something fails.
• Agree a rollback plan so you can revert to manual processing for a short time if necessary.

When to call your accountant or a developer

Speak to a professional when:

• You cannot reconcile daily totals to bank transfers.
• VAT or income categories are ambiguous in the source system.
• You need a bespoke report for tax adjustments or complex cost allocations (for example, apportioning joint-use equipment across multiple revenue streams).

Final notes — planning for the 2026 rollout

Integrations can seem technical, but treated as a small project they remove a lot of ongoing effort. Start with an inventory of your systems and a clear list of fields you need in the accounting software. Where budgets are tight, a phased approach works well—use native connectors first, add middleware for other apps and consider bespoke work only when necessary. Above all, keep your accountant involved; they will help ensure the mapping matches tax rules and that quarterly MTD updates reconcile to the figures HMRC expects.

At Tax Digital we help businesses plan their integrations so MTD obligations are met without stress. If you’d like a checklist or help scoping a pilot, contact a qualified adviser early so the technical and tax sides are aligned well before your compliance date.