Bridging Software or a Mobile App: How Uber Drivers Should Keep MTD Records

Once a UK Uber or PCO driver is inside Making Tax Digital for Income Tax, the day-to-day question is not which brand of software to buy but which shape of record-keeping to run. Two shapes are permitted. The first keeps the underlying figures in a spreadsheet and uses bridging software to file them with HMRC. The second uses a native mobile app that captures income and expenses directly on the phone and files from the same tool. Both satisfy the rules that arrive under the MTD ITSA mandate for drivers from 6 April 2026 for anyone whose qualifying income sits above £50,000, a threshold that falls to £30,000 from April 2027 and £20,000 from April 2028. Which one fits depends far more on how a driver already works than on price.

What bridging software actually does

Bridging software is a connector, not a bookkeeping system. The driver carries on recording fares, tips and expenses in a spreadsheet, and the bridging tool reads the relevant totals from that spreadsheet and submits them to HMRC as the quarterly update. HMRC is explicit that the spreadsheet and the bridging tool must be joined by a digital link, so the numbers flow across automatically. You are not allowed to read a figure off the spreadsheet and retype it into the filing screen, because that manual step breaks the digital records requirement. The rules on this and the list of recognised connectors are set out in the government guidance on compatible software.

A digital link, in plain terms, is any transfer of data between programs that happens without a human retyping it. A formula pulling a cell into another sheet counts. A copy and paste of a value does not. For a driver on a spreadsheet, this means the quarterly totals the bridging tool submits have to be linked to the underlying rows, not keyed in by hand.

The appeal is continuity. A driver who has spent three years tracking earnings in a spreadsheet they trust does not have to abandon it. They add a bridging layer, keep the familiar workbook, and stay compliant. The cost is usually low, often a few pounds per submission or a modest annual fee, which is why bridging is popular with drivers who resent paying a monthly accounting subscription for what feels like a filing button.

What a native mobile app does differently

A native app collapses the recording and the filing into one place. The driver photographs a fuel receipt at the pump, the app reads it, categorises it, and holds it against the quarter. Bank feeds pull in the Uber and Bolt payments automatically, and mileage is logged by the phone GPS as the driver moves. When the quarter closes, the update is already assembled. There is no spreadsheet to maintain and no separate connector to configure, which matters for a driver capturing dozens of small cash and card transactions across a long shift. The mechanics of building those quarterly figures are covered in the companion guide to filing quarterly updates from the road, and the discipline of daily capture is the same habit described in the bookkeeping routine for drivers.

The trade-off is that the driver commits to the app. If the subscription lapses or the provider changes its terms, the records live inside that product, and moving them elsewhere takes effort. Native apps also assume a driver comfortable running their finances from a phone, which most private hire drivers are, but not all.

The head-to-head for a working driver

The digital link is where bridging drivers slip up

The single most common bridging mistake is an innocent-looking one. A driver totals a column in the spreadsheet, glances at the number, and types it into the bridging screen because it is quicker than fixing the formula. That retype is exactly the manual step HMRC prohibits, and it means the record is not held digitally end to end. If a bridging setup ever requires copying a figure by hand, the link is broken and needs repairing before the next submission. Professional bodies have flagged this as a live area of confusion; the practical questions and answers on it sit in the ICAEW MTD for income tax guide.

It is not enough for the final submission to be digital. Every step from the original spreadsheet entry to the figure HMRC receives must be joined by a digital link. One manual copy anywhere in that chain undermines the position if HMRC ever asks how the numbers were produced.

Which one suits which driver

• Drives full time, high transaction volume, wants capture to happen automatically: a native mobile app earns its monthly fee by removing shift-end admin.
• Has kept a reliable spreadsheet for years and is confident with formulas: spreadsheet plus bridging preserves the system and keeps cost down.
• Part time, low volume, a handful of expenses a week: bridging on a simple spreadsheet is usually enough and cheapest.
• Runs mileage claims heavily under the simplified rate: a native app with GPS logging captures journeys the driver would otherwise forget.
• Wants an accountant to run the quarters: ask the accountant first, because most work in a native platform rather than a bridging setup.

Whichever shape a driver picks, the mileage side of the record deserves particular care, because it is where the largest deductions and the most common errors both sit. Capturing every business journey correctly is where mileage tracking earns its keep, and a driver who gets that right removes most of the risk from either record-keeping method.

Can you switch later

Yes, and many drivers do. A common path is to start on a spreadsheet with bridging in the first MTD year, find the shift-end data entry tedious, and move to a native app once the volume justifies the monthly cost. Switching mid-year is possible but tidier at a tax year boundary, because the opening position transfers cleanly. The one rule that holds across any switch is continuity of digital records: the new tool has to be able to account for the full year, so a driver moving in July still needs the April to June figures in a form the new software can carry forward.

There is no single correct answer. A driver who lives in a spreadsheet and files a handful of expenses is well served by bridging. A driver photographing fuel receipts between airport runs and logging hundreds of trips a month will find a native app pays for itself in time saved. The compliance bar is identical either way; the choice is purely about which one a driver will actually keep up with, quarter after quarter.