An accounting and bookkeeping client portal is where clients upload the documents their accountant needs and see each return's status, and the practice reminds them before every filing deadline.
Pattern: RequestsDescribe it to Pory
“We're a bookkeeping and tax practice with 150 small-business clients. Each client should upload their documents, see the status of their returns, and get reminded before deadlines.”
My documents
| Document | Return | Type | File | Status | |
|---|---|---|---|---|---|
| Business bank statements, Jul 2025 – Jun 2026 | Asante Joinery company accounts 2025–26 | Bank statements | 12 files | Uploaded | |
| Van and tool receipts | Asante Joinery company accounts 2025–26 | Receipts | 0 files | Requested | |
| Employer payment summary | Kofi Asante personal tax return | Payroll summary | 1 file | Accepted | |
| Last year's return | Kofi Asante personal tax return | Prior-year return | 0 files | Requested |
Showing 1–4 of 4
In plain English
An accounting and bookkeeping client portal is where clients upload the documents their accountant needs and see each return's status, and the practice reminds them before every filing deadline. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (client and accountant) that shows only what that role should see, and flat pricing with unlimited clients.
What it does
Documents arrived as phone photos in a group chat, a shoebox of receipts and one email titled "stuff". In Pory each client sees the documents their return still needs, uploads each file to its row and says what it is. Your team stops matching attachments to clients by guesswork.
Every busy season the phones fill with clients asking whether their return has gone in. Each client sees their own returns move from Waiting on documents to In preparation to Filed, with open queries flagged on the way. Your accountants spend October preparing returns instead of reporting on them.
Client folders on a shared drive worked until someone dragged a file into the wrong one. Each client signs in and sees only their own returns and documents, however many businesses you look after. A sole trader never sees the café next door's bank statements.
Deadline reminders were a mail merge someone remembered to send, usually late. Each return carries its filing deadline, and Pory reminds the client ahead of that date, in the portal and by email. Nobody on your team has to remember to chase, and fewer returns go in the night before.
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited clients, flat price.
