For accountancy and advisory
AI prepares the pack.
A partner signs it off.
Get a partner's approval on everything an agent prepares, without chasing anyone for it, and keep the record a file review will ask for. Before an agent posts a journal or sends a letter in a partner's name, it stops to ask that partner — on their phone or from an email — and waits for the answer. The approved pack reaches the client behind their own sign-in, not as an attachment.
No card required · Approvals on every plan · Secure by default
What you get
What Deliverd changes for accountancy and advisory.
A partner's approval, without the chasing
Management accounts, a year-end pack, a letter to a client: the agent asks the partner who owns it and carries on when they answer, wherever they are.
How: Your AI asks before it acts ↓Nothing posted or sent that no partner saw
An agent about to post a journal or send a letter declares it first and waits. With no rules a partner decides every one; rules can settle the routine cases and send the rest to a person.
How: A check before the agent acts ↓The file review's answers, already kept
Who was asked, what they were shown, what they decided and when, exported as one pack rather than rebuilt from a folder and a mailbox.
How: One pack for the auditor ↓The situation
What this looks like today
The agent prepared it; a partner has to own it
A journal posted, a letter in a partner's name, a pack sent to a group finance director: each is a decision the partner owns and the agent would make alone. The pause has to be a question the agent asks a person, not a prompt in a tool.
The most sensitive thing you produce travels the least safely
An attachment is a copy with no owner. Once it is sent, it can be forwarded, kept after somebody leaves, and read by whoever ends up with the mailbox.
Retention is a policy nobody can evidence
You have an obligation about how long records are kept, who approved them and who saw them. What you can actually produce is a folder and a best guess.
How it works
Deliverd for accountancy and advisory
Everything below ships today. Where something needs a paid plan, it says so.
Your AI asks before it acts
An agent that needs a decision puts it to a named person and waits: what it wants to do, why, how risky it is, and what to read first. They approve, approve with changes, reject with a reason, or ask the agent a question — on the page, from an email link, in Slack or Teams, or from a push notification on a phone — and a colleague can cover their approvals while they are away. It can also ask for a review, or for information it is missing, the same way.
Sign-off before it leaves
A publishing rule can hold work for a partner's approval: the version is stored and scanned, the client sees nothing until someone with the authority says so, and the decision is on the record. Off by default; switch it on for agent publishes, for anything addressed outside the firm, or both.
Opened with the client's own sign-in
Readers authenticate with the identity their organisation already uses, including SAML and OpenID Connect single sign-on. Nobody gets a password to remember, and nobody gets a file to leave with.
A workspace per client
Segment who can reach what, so an analyst on one engagement cannot browse another. Access is decided per report and evaluated on every request, assets included.
A check before the agent acts
Before a consequential action — a payment, a deployment, a message to a customer — the agent declares what it is about to do and waits for the answer. A named person decides, or your organisation's rules settle the routine cases and send the rest to a person; with no rules, every one goes to a person. Afterwards the agent records what ran, and the record is checked against what was allowed.
On every plan; policy rules included in Business Starter, Business and Enterprise
A record of who opened it
Views, versions, access changes and share links are written to an audit trail you can export — which is the difference between believing a client saw something and being able to show it.
An address, not an attachment
The work lands on a URL you can send. It stays put, so the link you shared at the kick-off still opens today's version rather than a copy of what it looked like in March.
It looks like your firm
Your name and logo, on your own verified domain, with notifications sent from your domain once it is verified. On the paid plans the reader sees your practice rather than ours.
A second thought, where it matters
Your organisation writes rules for requests that touch someone's job, money, health or privacy, or that cannot be undone. When one matches, whoever decides sees the concern first and has to say why it is right to go ahead; a rule can also ask more people to agree, or refuse. Ethics rules only add oversight — none of them can approve anything — and they are on every plan.
The right person can ask
Somebody who needs a report and cannot open it asks for access from the page itself, and whoever owns it decides. Better than the alternative, which is a copy forwarded out of goodwill.
Rules your firm sets once
Publishing policies run on every publish and share: no external sharing for a classification, a ceiling on how long a link may live, a workspace that must be named. A tester shows what a publish would do before anyone tries it.
One pack for the auditor
Every step of a piece of work — who was asked, what they said, what was decided and when — exported as a single timeline in JSON, CSV or PDF. It carries a digest and the head of the hash-chained audit trail, signed with a published key, so anyone can check a copy offline, and the export itself is on the record.
When deletion has to stop, it stops
A matter opens and routine destruction becomes the wrong thing to do. Place a hold — on the whole organisation, one project, one task, one person’s material or one report, over a date range if you need one — and the retention schedule suspends, the organisation cannot be closed, and what the hold covers cannot be deleted: a report’s data, a task, a retracted comment’s attachments. Refused in the database, not by a setting somebody has to remember. Released with a reason, and both ends are on the record.
Included in Enterprise
Questions
Accountancy and advisory and Deliverd.
Can an agent posting a journal or sending a client letter be made to ask first?
Yes. The agent asks a named partner with request_approval, or declares the action at a gate, and waits. With no rules a partner decides every one; rules can settle the routine cases and send the rest to a person. A gate is advisory: the agent asks and then performs the action itself, and its execution record shows whether what ran matches what was allowed.
Can we separate one client's entities from another's?
Yes. Workspaces segment access, and each report is granted to named people, groups or a whole organisation. The decision is checked on every request rather than at the link.
What happens when someone leaves the client?
If they signed in through their employer's identity provider, removing them there ends their access at once — there is no separate password to revoke and no file already on their laptop.
How long is the record kept?
Audit and view history are retained for a period set by your plan. On Enterprise, an administrator can lengthen the audit history to up to ten years.
Can a client ask for access rather than emailing us?
Yes. Someone who cannot open a report can request access from the page itself, and whoever owns it approves or declines. The request and the decision are both recorded.
Can an agent's request touching personal data, or a letter in a partner's name, get a second look?
Yes. The starter ethics rules include “Health and personal data”, which asks whether there is a lawful basis and whether only what is needed is being used, and “Messages sent in someone else's name”, which asks whether the recipient would be misled about who wrote it or what it commits to. They arrive switched off; once on, whoever decides sees the concern first and has to give a reason to approve.
Nothing leaves without a partner. Now the agent knows it too.
Let the agent prepare the pack, put the sign-off in front of the partner, and deliver it to an address the client opens with their own sign-in.