Late start
The request waits until somebody needs access for live work.
Free CRM for accountants & bookkeepersFree for two months (60-day trial) · no per-user fees
HMRC & Companies House
The work is ready to start, but the authority is not. Treat authorisation as a day-one onboarding dependency, not an admin task for later.
Built by a practising Chartered Accountant · Unlimited users · Free for 60 days
Quick answer
Start HMRC authorisation on day one, choose the correct route for the tax and service, give the client precise instructions, track any code or digital-handshake expiry, and follow up before it becomes urgent. Different services use different routes. Remindoo can organise requests and chasers, but it does not obtain authority or connect to HMRC.
Nothing makes onboarding feel slower than discovering, weeks later, that the firm cannot see what it needs. The client believes appointing an accountant was the whole process; the team assumes the code is on its way.
HMRC authorisation is not one universal route. Digital handshake, online authorisation and paper forms have different uses. The process must follow current HMRC guidance for the specific service.
The request waits until somebody needs access for live work.
A method is used without checking whether it covers the relevant tax or service.
The client receives a generic request and does not recognise the expected letter or digital step.
A code or link expires while everybody assumes somebody else has acted.
Delayed agent authorisation consumes partner attention that should be spent on judgement, relationships and developing the team. The hidden cost is context switching: a five-minute interruption often breaks a much longer block of concentrated work.
Unclear ownership creates duplicated effort. One person assumes somebody else has acted, another repeats the chase, and the partner becomes the unofficial control system. That is exhausting and difficult to scale.
Client trust can also erode. Clients rarely see the internal cause; they see slow answers, inconsistent messages or last-minute requests. A reliable process protects the relationship even when the underlying issue is outside the firm's control.
Map each tax and HMRC service required for the agreed scope.
Use the current official guidance because routes and service coverage change. [VERIFY] the selected route before issuing instructions.
Make authorisation an onboarding dependency with a named owner.
Explain what they will receive, what action to take, the expiry date and how to tell you it is complete.
Set a chase before expiry and record when the client says they acted.
Do not mark the step complete until the relevant access is visible.
A sensible fix can still fail when it is announced as a new rule and left to compete with client work. Treat the change as a small operational project. Give it an owner, a start date, a review date and a clear definition of success. Test it with a representative group before asking the whole firm to change at once.
Map each tax and HMRC service required for the agreed scope. Write down who owns this step, what evidence shows it happened and when an exception must be escalated. Ask one person who performs the work and one person who reviews it to test the wording. If they interpret it differently, the process is not yet clear enough.
Use the current official guidance because routes and service coverage change. [VERIFY] the selected route before issuing instructions. Write down who owns this step, what evidence shows it happened and when an exception must be escalated. Ask one person who performs the work and one person who reviews it to test the wording. If they interpret it differently, the process is not yet clear enough.
Make authorisation an onboarding dependency with a named owner. Write down who owns this step, what evidence shows it happened and when an exception must be escalated. Ask one person who performs the work and one person who reviews it to test the wording. If they interpret it differently, the process is not yet clear enough.
Explain what they will receive, what action to take, the expiry date and how to tell you it is complete. Write down who owns this step, what evidence shows it happened and when an exception must be escalated. Ask one person who performs the work and one person who reviews it to test the wording. If they interpret it differently, the process is not yet clear enough.
Set a chase before expiry and record when the client says they acted. Write down who owns this step, what evidence shows it happened and when an exception must be escalated. Ask one person who performs the work and one person who reviews it to test the wording. If they interpret it differently, the process is not yet clear enough.
Do not mark the step complete until the relevant access is visible. Write down who owns this step, what evidence shows it happened and when an exception must be escalated. Ask one person who performs the work and one person who reviews it to test the wording. If they interpret it differently, the process is not yet clear enough.
Keep the review short and evidence-led. Ask what is waiting, who owns the next action, which internal date is at risk, what the client has been told and whether the same exception has appeared before. The purpose is not to inspect every keystroke. It is to remove ambiguity while there is still time to act.
Days 1–30: establish the baseline. Review recent examples, speak to the people doing the work and identify the smallest repeated failure worth fixing. Agree one rule and one owner. Do not redesign the whole practice while the team is still trying to describe the problem.
Days 31–60: run the new process on live work. Record exceptions rather than quietly working around them. Check whether staff can find the right client context, whether dates are realistic and whether the client communication matches what the firm can deliver.
Days 61–90: review the evidence with the team. Keep what improved control, simplify what created administration and stop anything that merely moved the problem elsewhere. Document the final process, decide how it will be monitored and schedule the next review.
Remindoo can make each authorisation request, chase and confirmation a visible onboarding step.
Standardise requests, checks and first services.
See featureSet priority, assignee and deadline on every job.
See featureTimely prompts before work becomes urgent.
See featureStandard client messages ready to send.
See featureContext the whole team can find.
See featureWhat Remindoo doesn’t do here: Remindoo does not request HMRC authority, generate authorisation codes or confirm HMRC access.
A practical 30-minute walkthrough using your firm’s current process.
Start with a written rule for HMRC agent authorisation delay. Define what good looks like, who owns the next action, when it must happen and when the issue moves to a partner. Keep the rule short enough that the team will actually use it.
Use a small set of operational measures that prompt a conversation rather than create a league table. Look at ageing, missed internal dates, repeated rework and work waiting without a named owner. Review the trend with the people doing the work and fix the process before blaming individuals.
No. Software can make ownership, dates and evidence visible, but the firm still needs clear policies, judgement and consistent follow-through.
Choose one recurring problem, write down the current process, assign one owner and test a simpler version for four weeks before changing everything else.
It depends on the tax and service. Check HMRC's current guidance; one route does not necessarily cover every service.
HMRC states that this handshake alone does not provide authority to speak to HMRC; separate authorisation may still be needed.
HMRC says Online Agent Authorisation stopped covering VAT authorisations from 16 February 2024. Check current guidance before acting.
Check the address and route, follow HMRC's current instructions and restart or use an alternative permitted route where appropriate.
See Remindoo with your own clients, or start free for 60 days with unlimited users.
Last updated: . General guidance, not legal, tax, medical or regulatory advice. Check current primary guidance and take appropriate professional advice.
Accounting firms run on deadlines: VAT returns, payroll, confirmation statements, accounts and Self Assessment. Recording every job as a task, with an owner and a date, is the simplest way to make sure nothing is missed.
HMRC and Companies House charge penalties for late filing. A task for every deadline, with an internal date before it, gives the team a buffer.
Recorded tasks mean work continues when someone is off sick, on leave or has left the firm.
Subtask checklists make every job follow the same steps and reviews, whoever does the work.
Filters by owner, status and deadline show at a glance what is late, what is due and who needs help.
Written and reviewed by Waqas Sagar ACA FCCA FMAAT, Chartered Accountant with 18+ years in practice. Founder and MD of Accotax, an ICAEW, ACCA and AAT regulated London practice that has served over 5,000 clients, and founder of Remindoo. Guidance is general; check current GOV.UK and professional body guidance for your firm.
“With Remindoo, everything from the first enquiry to onboarding and ongoing client management is tracked in one place… It saves us hours and gives me, as a practice owner, complete visibility of where the firm stands.”
“The biggest benefit is having clients, tasks, deadlines, workflows, proposals and communication all organised in one place.”
“During my trial, the team were absolutely amazing. They helped onboard my clients, set up my settings and made sure everything was ready for me to use… they made the whole process completely stress-free.”
“It brings client information, tasks, recurring deadlines, workflows and reminders together in one place, giving us much better visibility across the team.”
Trusted by firms regulated by the following professional bodies









