System sample
Overview
Check requests, approvals, and payments before going into detail.
Monthly trend
Requests and payments
Expense mix
Category split
Check the proportions first, then move to approvals and receipts.
Recent requests
Expense requests this month
Check the request number, requester, department, and approval status first.
| ID | Requester | Department | Category | Amount | Status | Date |
|---|---|---|---|---|---|---|
| ER-2026-0409 | Emily Carter | Sales | Travel | $8,420 | Finance review | 2026-04-09 |
| ER-2026-0412 | John Miller | Marketing | Entertainment | $2,180 | Pending approval | 2026-04-12 |
| ER-2026-0415 | Sarah Lee | Engineering | Office | $1,350 | Paid | 2026-04-15 |
| ER-2026-0417 | David Kim | Operations | Training | $5,900 | Archived | 2026-04-17 |
| ER-2026-0418 | Olivia Chen | Finance | Travel | $4,680 | Returned | 2026-04-18 |
Request entry
Request form
Enter the record first, then confirm approval and payment.
Request form
The order matches the workbook so review is easier.
Recent entries
New submissions appear here right after entry.
| ID | Requester | Type | Amount | Status |
|---|---|---|---|---|
| ER-2026-0420 | Emily Carter | Travel | $6,420 | Pending approval |
| ER-2026-0419 | John Miller | Entertainment | $2,180 | Finance review |
| ER-2026-0418 | Sarah Lee | Office | $1,350 | Paid |
Line items
Expense details
Each row can be traced back to the original receipt.
| Date | Project / Cost center | Merchant | Category | Amount | Tax rate | Status |
|---|---|---|---|---|---|---|
| 2026-04-20 | Tokyo project | Harbor Hotel | Hotel | $2,160 | 6% | Needs review |
| 2026-04-19 | Kanto route | Sunline Air | Travel | $3,580 | 9% | Pending approval |
| 2026-04-18 | Client visit | North Shore Dining | Meals | $680 | 6% | Archived |
| 2026-04-17 | Internal training | Aster Office Supplies | Office | $1,350 | 13% | Paid |
| 2026-04-16 | Promotion event | Blue Arc Events | Entertainment | $2,900 | 6% | Returned |
Approval flow
Workflow steps
Each step keeps an owner and a time marker.
Submit request
Make sure the ID, department, amount, and receipt are filled in first.
Department review
The manager confirms business necessity before finance sees it.
Finance review
Check receipts, tax rates, and policy limits one by one.
Pay and archive
After payment is done, store the record and attachments together.
Current queue
Show where the request is stuck on one screen.
| ID | Owner | Current step | Wait time | Status |
|---|---|---|---|---|
| ER-2026-0412 | Jordan Lee | Department review | 2 days | In progress |
| ER-2026-0418 | Olivia Chen | Finance review | 1 day | Needs attention |
| ER-2026-0409 | Emily Carter | Pay and archive | 0 days | Done |
Approval notes
Keep rejection reasons, comments, and reminders together.
- Apr 18 09:20The receipt header is missing the department name. Please resubmit after correction.
- Apr 17 16:05The entertainment expense is within policy, so it can move forward after the amount check.
- Apr 16 11:42Travel receipts are complete, so the payment step can begin now.
Auto alerts
Alert rules
Let the system point out the issue first, then hand it to a person.
If the request amount is over policy, mark it as needing review.
If a receipt or attachment is missing, ask the requester to complete it.
If a step is stuck for more than two business days, notify the owner automatically.
Same receipt number, same amount, and same date are marked as duplicates.
Message copy
See how the alert reads for the requester, approver, and finance team.
Settings
Master data
Set the dropdown values first so input stays consistent.
Settings form
These defaults are used by the next screens.
Backup
Export and restore
Check the format first, then decide how to connect it later.
JSON export
Useful for offline archiving and environment migration.
{ "exportedAt": "2026-04-28", "module": "expense-reimbursement-log", "records": 58 }
Import guide
Check the ID, date, amount, and status before import.
Guide
How to read this sample
The copy is read only, so teams can confirm the flow first.
Important note
There are no backend edit actions here. The goal is to study structure, order, and screens.
If you later connect a real system, keep the request, approval, and payment stages first, then add attachments, alerts, and backup later.