Employee
Sees only their own claims.
- Pages
- Home, My claims, Payments, Expense policy
- Can start
- Claim an expense, New claim
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
Pory gives every employee and finance a sign-in of their own. Each employee sees only their own claims. It covers claim → finance approval. Claims, expense payments, pay dates and finance team live in Pory's own database, so there's no spreadsheet to keep in sync.
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 Paid. 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 came in each month, 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.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own claims.
Sees every claim in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Live figures over the records a viewer is allowed to see.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited employees.