Built so a partner can let an agent near a filing.
Minns holds a practice's data in London, keeps every credential away from every agent, binds each approval to the exact figures the approver saw, and writes down who did what and when. These are the controls, as they are built.
Questions a reviewer or insurer asks that this page does not answer: ask us and we will put the current position in writing.
Three things to know first.
- Credentials never reach an agent
- HMRC tokens, Companies House keys and bookkeeping credentials live in the control plane. An agent asks the control plane to read the books or submit a return; it never holds the key, so a prompt, a note or a record can never leak one.
- An approval is bound to what was seen
- A person approves a return, a release or a chase against the page, the control and the figures in front of them. If any of them changed since, the approval does not carry and the work is prepared again.
- Everything is written down
- Every action an agent took, what it read, what it drafted, who approved what and when, and the receipt HMRC gave. One trail per client, kept for the reviewer and the insurer.
What is built, control by control.
Hosted in London
Your agents run and your data is held on our infrastructure in London. Traffic reaches it over TLS, behind Cloudflare.
Secrets stay in the control plane
HMRC agent services tokens, Companies House API keys and Xero, QuickBooks and Sage credentials are stored once, in the control plane, and used there. No agent, prompt, workspace or log holds one.
Card details are hidden everywhere
A payment card number is recognised wherever it appears, in a page an agent reads, a form it fills, a message, a capture, and shown as hidden. Nothing in Minns types a card number into anything.
Named approvals, checked
Every submission to HMRC or Companies House, every email released to a client and every status set to approved or filed needs a named person. The approval checks the page, the control and the values against what the approver saw.
Governance per client
A client the firm would rather work by hand is kept from the agent with one switch. The agent is told so and stops. The board records who kept the client and when.
Erasure that reaches every record
When a firm or a person leaves, their data is removed from every collection that held it under one set of rules: the board, the facts, the portal, the mail, the proposals, the jobs. A collection without a rule cannot be added, so nothing is left behind by accident.
The path from a request to a filing.
01
A person at the firm asks, or the morning job runs
Each person signs in as themselves. The agent works under that person's name, or under the firm's standing jobs, never anonymously.
02
The agent reads through the control plane
Books, board, registers and the firm's guidance come through calls the control plane makes with its own credentials. The agent sees the data, not the keys.
03
The agent drafts and prepares
A chase, an answer, a return pack, a note. Each is saved as a draft or a proposal on the client's file, visible to the firm.
04
A named person approves
The approval records the person, the time, the page and the figures. A changed figure, control or page makes it void.
05
The control plane acts and keeps the receipt
The submission to HMRC, the email to the client, the status change. The receipt and the log line join the client's trail.
What is held, and who can reach it.
| Data | Where it is held, and who sees it |
|---|---|
| The client's books | In the books engine in London, pulled through the firm's connection. Seen by the firm's people, the client's own people in their portal, and the agent unless the client is kept from it. |
| The deadlines board and the trail | In the control plane in London. Seen by the firm; each client sees their own dates and approvals. |
| HMRC, Companies House and bookkeeping credentials | In the control plane, used there. Seen by no person and no agent after they are entered. |
| Client mail and portal messages | In the control plane. Seen by the firm and the client concerned; the agent drafts replies, a person releases them. |
| Payment card numbers | Shown as hidden wherever they appear. Never stored in a note, a capture or a record. |
| A client who has left | Removed from every collection on the firm's request, with the list of what was removed given back. |
Straight answers.
- Where is our data held?
- On our infrastructure in London. Agents run there too.
- Does an agent ever hold our HMRC token?
- No. Tokens and keys stay in the control plane and are used there. An agent asks the control plane to read or submit, and never sees the credential.
- Can a client be kept away from the agent entirely?
- Yes. One switch on the client. The agent is told the firm works that client by hand and goes no further; the board shows who set it and when.
- What does the audit trail hold?
- Every action the agent took and what it read, every draft, every approval with the person, the time and the figures, and every receipt from HMRC or Companies House, per client.
- Is our data used to train a model?
- Not by us. Your clients' books, mail and records are used to do your clients' work and for nothing else. Ask us for the written position on the model providers we use.
- Do you hold a certification?
- Ask us. We will send you the current position in writing, with the controls on this page as they stand today.
Ask us the hard questions.
Send us your reviewer's or insurer's list. We answer each point against the controls as built, in writing.