VPN for Tax Portals Abroad: The Filing Wasn’t Finished Until HMRC Said “Accepted”

My accounting software sent me to HMRC, HMRC approved the connection, and then the browser returned to an error page. I was in Valencia, trying to submit the first quarterly update for my UK freelance and property income before my accountant’s final review slot closed. I blamed the password, signed in again and granted the same permission a second time. The software still showed HMRC connection not completed.

My accountant was leaving for annual leave in forty-one minutes.

The legal deadline was four days away, on 7 August 2026. But she had already checked my digital records and found one duplicated maintenance expense. If I completed the software authorization while she was online, she could confirm the corrected totals before I submitted them.

If I missed her review slot, I would be handling my first mandatory update alone.

I had the figures.

I had my Government Gateway details.

I had the authenticator app.

What I did not have was a connection that could carry me from the accounting software to HMRC and back again.

The tax portal was only one part of the filing

Making Tax Digital for Income Tax became mandatory from April 2026 for qualifying sole traders and landlords with annual self-employment and property income above £50,000. For most people in the first group, the first quarterly update covers 6 April to 5 July and must reach HMRC by 7 August 2026. (HM Revenue & Customs)

The update could not simply be typed into an HMRC webpage.

I had to use compatible accounting software, connect that software to HMRC, authorize it and send the quarterly totals through the application. (HM Revenue & Customs)

That explained why my first attempts felt so strange.

The HMRC sign-in page worked.

The access code worked.

The permission screen worked.

The failure arrived when the browser tried to return control to the accounting software.

I was reaching the tax portal without completing the tax task.

The Spanish connection lost the return journey

I disconnected every VPN and tried the apartment Wi-Fi directly.

The accounting software opened a browser window.

I entered my Government Gateway credentials, approved the authenticator code and selected Grant authority.

HMRC displayed a confirmation page.

Then the browser redirected me toward the accounting application.

The page remained blank.

A few seconds later, the software displayed:

Authorization was not received

I tried again through my phone’s Spanish mobile data.

This time, the browser returned to the software, but the application still showed HMRC as disconnected.

The tax records themselves were ready. The problem was the handoff between the services.

HMRC’s authorization process sends the user through a browser and then returns the approval to the connected application. (HMRC Developer Hub) If that return fails, the successful login does not help the software submit anything.

Taxpayers abroad often describe being trapped somewhere in this chain—sometimes by identity checks or old UK numbers, sometimes by a redirect that never completes. (Reddit)

I had kept my authenticator active, so I was reaching the final handoff before losing the connection.

My accountant sent another message:

The totals now look correct. Authorize the software, then send the update while I’m here.

Thirty-four minutes remained.

The familiar provider completed the authorization

I opened the major VPN provider I normally used while traveling.

It had a long public history, extensive support and several UK locations. Those were sensible reasons to trust it with a tax submission.

I selected London.

The accounting software opened HMRC again.

I signed in, entered the code and granted permission.

This time, the redirect completed.

The accounting application changed from Connect to HMRC to:

Connected

That felt like the difficult part finished.

I reviewed the quarterly totals:

Freelance income.

Allowable business expenses.

UK property income.

Property repairs and management costs.

The duplicated maintenance payment was gone.

I selected Send quarterly update.

The software began transmitting the figures.

Then the apartment Wi-Fi paused.

The VPN reconnected through another London endpoint.

The progress screen disappeared.

When the accounting application recovered, HMRC was no longer connected.

The update status read:

Not submitted

The UK route had completed the authorization.

It had not stayed in place long enough to use it.

Another UK server restarted the process

I selected Manchester manually.

The software sent me back through Government Gateway.

Password.

Authenticator code.

Permission screen.

Redirect.

The application showed Connected again.

I submitted the update.

This time, the income totals transferred and the software reached the final confirmation step.

Then the VPN changed routes after another brief Wi-Fi interruption.

The application displayed:

Submission result unavailable

I did not know whether HMRC had received the update.

Submitting it again immediately could create confusion. Assuming it had succeeded could leave the obligation unfinished.

My accountant checked her side.

“No receipt,” she wrote. “Do not treat it as filed.”

That sentence changed the standard.

A UK server was not enough.

A successful login was not enough.

Even sending the figures was not enough.

The filing was complete only when HMRC returned an acceptance receipt that both of us could verify.

The server menu had become another tax form

The established provider offered London, Manchester, Glasgow and several automatic UK routes.

Normally, that variety would be useful.

Under the deadline, every server change created another version of the same sequence:

Reconnect.

Sign in.

Enter the code.

Grant permission.

Return to the software.

Submit.

Wait for the receipt.

The first-year MTD rules did not apply penalty points for a late quarterly update, but the update still had to be sent through the digital process. (HM Revenue & Customs)

I was not facing an instant fine.

I was facing something more ordinary: beginning a new tax system with an uncertain submission, an unavailable accountant and no receipt.

I had twenty-two minutes left.

The browser extension protected the wrong half

I briefly tried a free browser VPN extension with a UK route.

Government Gateway opened quickly.

The authenticator code worked.

The permission screen returned me to the accounting software.

But the desktop application itself was outside the browser extension.

The browser reached HMRC through Britain while the accounting software continued communicating through Spain.

The application displayed the same authorization error.

The extension had protected the visible sign-in pages.

The submission belonged to the desktop software.

I closed it.

The filing needed one full-device route from the first authorization click to the HMRC receipt.

The smaller app began with the task

I had installed OnlydogVPN^↗ before the trip but had not made it my default.

The established provider offered more locations, more ratings and a much longer public history. The smaller service had fewer UK routes and less independent history, which was why I had treated it as a backup.

But I no longer needed a larger choice of British cities.

I needed a stable connection for a sensitive account on unreliable residential Wi-Fi.

I selected that situation and chose the United Kingdom.

The connection established.

I returned to the accounting software.

It opened HMRC.

I entered my Government Gateway details.

The authenticator code arrived.

I granted the software permission.

The browser returned to the application.

Connected

I opened the quarterly update and checked the totals one final time.

Then I selected Submit.

The income figures transferred.

The expense figures transferred.

The application moved to the confirmation step.

For several seconds, nothing changed.

Then the status became:

Accepted by HMRC

A receipt number appeared beneath it.

I copied the number into the message to my accountant and downloaded the submission report.

She replied:

Receipt matches. First quarter complete.

That completed the task.

The tax portal had not merely opened. The software had been authorized, the update had been accepted and the receipt had returned to the same place where my records lived.

The route stopped interrupting the filing

The service uses an HTTP/3-based connection designed to remain stable when the underlying network weakens or changes.

The visible difference was straightforward.

The Spanish connections reached HMRC but lost the return to the accounting software.

The major provider completed the authorization but changed routes before the receipt arrived.

The browser extension covered Government Gateway but not the application sending the update.

The backup carried the complete loop.

I could not observe HMRC’s or the accounting provider’s internal security and filtering rules. I could compare where each attempt stopped.

For this filing, preserving the authorization-and-submission loop mattered more than opening HMRC through the fastest UK server.

The Wi-Fi failed after acceptance

My accountant asked me to send her the detailed submission report before she signed off for leave.

As I opened the PDF, the apartment Wi-Fi disappeared.

The laptop moved to my phone’s hotspot.

The VPN recovered.

The accounting application remained connected.

The receipt still showed Accepted, and the report finished downloading.

I sent it to my accountant.

She confirmed the property and freelance totals once more, then wrote:

All done. Enjoy Spain.

The main task had already succeeded.

The network recovery protected the smaller step afterward: preserving the evidence that it had succeeded.

Without the receipt, I would have spent the next four days wondering whether the update existed inside HMRC or only inside my software.

Tax access was not the login page

Before that afternoon, I had treated access to a tax portal as a yes-or-no question.

Can I sign in from abroad?

That was too small.

The first MTD update required a longer sequence:

Open the accounting records.

Connect the software to HMRC.

Complete identity checks.

Grant authority.

Return to the application.

Send the figures.

Receive the acceptance receipt.

A VPN could pass the Government Gateway screen and still fail the filing.

The familiar provider passed most of the sequence, but not as one continuous transaction.

The browser extension passed only the browser portion.

The smaller route kept every step attached until HMRC returned a result I could save.

The receipt settled the comparison

The established provider remained the larger and more familiar company. It offered more UK servers, more reviews and years of public operating history.

Its changing routes also turned one quarterly update into repeated authorizations and an uncertain submission.

The free extension opened the tax pages but left the accounting application outside the same route.

The smaller backup had fewer locations and a shorter public record.

It was also the option that kept Government Gateway, the accounting software and HMRC’s acceptance receipt together as one filing.

I began the afternoon looking for a VPN that could access a tax portal abroad.

The receipt number gave me the more useful standard: the connection had worked only when HMRC’s answer made it all the way back to my books.