My claims
An expense reimbursement portal is where employees claim back work spending with the receipt attached and finance approves or rejects each claim with a reason. Finance's home page counts the month's claims and how many are still waiting.
Pattern: RequestsDescribe it to Pory
“Staff should be able to claim expenses with a photo of the receipt, finance approves or rejects each one, and we want to see how many claims come in each month.”
My claims
In plain English
An expense reimbursement portal is where employees claim back work spending with the receipt attached and finance approves or rejects each claim with a reason. Finance's home page counts the month's claims and how many are still waiting. 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 (employee and finance) that shows only what that role should see, and flat pricing with unlimited employees.
What it does
Receipts used to arrive as crumpled paper in an envelope, or a blurry photo in a DM captioned "can you process this?". In Pory an employee enters what it was for, the amount, the category and the date, attaches the receipt, and watches the claim move from Submitted to Reimbursed. Finance stops matching photos to spreadsheet rows.
Approving a claim meant opening the spreadsheet, finding the receipt in someone's email and writing a separate reply to explain a no. Finance opens the claim in Pory, checks the receipt against the amount, and approves or rejects it with a note on the claim itself. The employee sees the answer and the reason without a follow-up email.
Month-end started with someone counting spreadsheet rows to see how many claims were still open. Finance's home page in Pory shows how many claims have come in, how many are waiting on a decision and how many are approved, and the numbers move as claims do. Nobody tallies anything by hand before the close.
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 employees, flat price.