The practice portal
One login for every client: prepare, review and file, with the client approving on the record before anything is submitted. Built to spec, tested in CI against the negative cases, and opening as a private pilot after final security and agent-authority checks — here is exactly how it works, and what it doesn't do yet.
Company filing: Companies House test-proven · HMRC recognition in progress. Self Assessment: Preparation live · filing with recognition. Prepare and validate for HMRC and Companies House in one guided workflow — HMRC filing switches on with our software recognition.
One engagement, start to finish
Six steps, each naming the control you'll actually see. The practice prepares; the client always approves; only then does anyone file.
- 1
Set up the practice
Create your organisation and invite colleagues by email, each with a role. Every member must have two-factor authentication switched on — the portal refuses to act for an account without it.
On screen: "Run a practice on GoTaxes" → organisation name. A members list with each role, an Invite box with a role picker, and a warning until two-factor is enabled on the account.
- 2
Engage a client — by their consent
Invite the client by email and choose the services you're engaged for: accounts + Corporation Tax, confirmation statements, Self Assessment, Money records. The client accepts the link with their own login — that acceptance is the engagement. You cannot attach a client unilaterally, and you only ever see the services they agreed to.
On screen: "Invite a client": name, email and service tick-boxes. The client's row reads "awaiting their consent" until they accept; then their filings and deadlines appear under your practice.
- 3
Prepare
A preparer enters the figures, runs the pre-flight checks against the published schemas and business rules, and generates the documents — but cannot submit. The job moves from draft to prepared.
On screen: Each client's filings listed with a status chip and "Open job" (or "Open return" for Self Assessment); the workflow buttons you see depend on your role.
- 4
Review
A reviewer checks the work and marks it reviewed → client. While a job is under review its figures are read-only to preparers; if something is wrong, send it back with one click and the trail records who did what.
On screen: "Mark reviewed → client" on the job; the chip changes; a send-back action for the reviewer.
- 5
Client approval — on the record
The client sees "Awaiting your approval" in their own portal and opens the review page: what the document is, who prepared it, the accounts and computations to open, the key figures, any outstanding warnings, and the declaration — rendered word for word from the server, never paraphrased. Approve enables only once every document has been opened, the declaration is ticked and a name is typed. The approval is stored immutably with the name, the timestamp and a digest of the figures as they stood. Change a figure afterwards and the job reopens for a fresh approval.
On screen: One review page: the documents, the figures, the warnings (or "No outstanding warnings"), the declaration in a box with a tick and a name field, and the Approve button.
- 6
File
With the approval on record, a reviewer, admin or owner submits through the official government gateways. The client's own Government Gateway or Companies House credentials are entered at that moment and never stored; practice staff never use a client's credentials. Prepare and validate for HMRC and Companies House in one guided workflow — HMRC filing switches on with our software recognition.
On screen: The filing card with the submit action, the government acknowledgement once it returns, and the receipt filed against the job.
Six roles
Submission always needs a reviewer or above AND the client's recorded approval — the practice prepares, the client still approves.
| Role | Can |
|---|---|
| owner | everything, including billing, members and offboarding |
| admin | manage members and clients, plus everything below |
| reviewer | prepare, approve for submission and submit |
| preparer | enter figures, run checks, generate documents — cannot submit |
| read-only | view only: audit, insurers, trainees |
| client-director | the client's own login: sees their own resources, approves what the practice prepared, supplies their own credentials at filing time |
The portfolio dashboard
A query over the clients you're engaged for — no separate data to keep in step.
What it shows
- ✓Every client's accounts, CT600, Corporation Tax payment, confirmation statement, Self Assessment and MTD quarterly deadlines, sorted by urgency
- ✓A status chip per filing: draft, prepared, reviewed, client-approved, submitted, accepted or rejected
- ✓"Client action needed" flags — missing UTR, missing approval, credentials needed
- ✓Assist workspaces and documents for the same clients, one click away
Billing on a ladder
How the practice pays
- ✓Practice-pays (default): one annual price for the practice on a per-client ladder — £189 a year up to 12 active clients, £319 up to 50, £549 up to 150; larger practices talk to us
- ✓Seats are free — pricing is per client, never per member
- ✓Client-pays: the client pays their own filing price exactly as a direct customer would, and the practice simply manages the work
- ✓Government fees (the £50 confirmation-statement fee, for example) always pass through at cost
- ✓Pilot pricing — confirmed with pilot practices before general release
Security, stated plainly
The portal rewrote who may see what, so the controls are the product.
In place today
- ✓Two-factor authentication required for every practice member
- ✓Re-authentication with your password for member removal, client offboarding and billing changes
- ✓Offboarding a member revokes their sessions immediately; offboarding a client detaches the practice but never deletes the client's data — it's theirs
- ✓Every cross-tenant query goes through the authorisation helpers, and CI runs a negative-authorisation suite: practice A must get a 404 on practice B's resources, on unaffiliated personal resources, and on an engaged client's resources outside the agreed services
- ✓Every workflow transition writes an audit entry with the acting user and the organisation
- ✓A portal role is never statutory authority: your 64-8, agent services and Companies House authorised-agent relationships are recorded separately and never inferred from a role
Not built yet
So you can plan around it. These are on the list for after the pilot, in the order pilot practices ask for them.
Not in the portal today
- ○Bulk CSV client import — clients are invited one at a time today
- ○A multi-organisation switcher — one practice per login is shown; the API already supports several
- ○White-label or practice-branded emails
- ○SMS or WhatsApp reminders — email reminders exist
- ○API access and per-seat pricing
- ○Cross-organisation client transfers
- ○Agent MTD through the Agent Services Account, and identity-verification services (these need ACSP registration)
Join the pilot
The portal opens as a private pilot with a small number of practices, once the final security and agent-authority checks are done. Register interest and we'll be in touch; if you already have a GoTaxes account with two-factor enabled, the portal is where a practice is created.
Security in detail →What we support →Assist for client documents →Pricing →