The job of this console
Review, approve or bounce, send toward reimbursement. Confirm the employee still sees the same claim.
Finance · Expenses
Expenses (Finance View)
Finance operations view of employee expense claims — the same expense records employees submit, not a second petty-cash book.
Scroll to Flowcharts. Scenario: Review an employee expense as finance.
Claims ops
Employee expenses, finance seat
This is the finance view of the same claims employees submit. It is not vendor AP and not a petty-cash sidecar.
Finance → Expenses (finance view)
Route
/finance/expenses
Org flag expensesEnabled
Finance Manager · Admin
Seat at the table
Finance managers. Employees use Payroll → Expenses (employee). Payroll may pay via reimbursements.
The working rhythm
Filter pending, open, decide, watch pay path.
Moments that bring you here
Month-end claims. A duplicate receipt. Policy breach. After travel week.
ⓘ
One expense entity
Two menus, one record. Vendor invoices remain supplier bills.
Flowcharts
1 — Ops on employee claims
Review claims, decide, employee queue matches.
flowchart TD
A[Open Finance expenses] --> B[Filter claims]
B --> C[Open claim]
C --> D[Approve or bounce]
D --> E[Employee expenses + reimbursements]
- 1OpenFinance → Expenses.
- 2FilterPeriod and status.
- 3DecideSame expense record.
- 4Pay pathReimbursements / payroll.
Overview
Finance expenses is the ops seat on employee claims. Employee expenses is self-service. Vendor invoices are suppliers.
How to use
1. One claim entity
Two seats.
2. Receipts
Sensitive — masking.
3. Not AP vendor bills
Wrong register.