These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Travel & Expense Management
- Features
- Approval desk
Approval desk
Make the expense decision visible with its reviewer, outcome and operation record.
OverviewExpense Reports Past Due×
Travel & Expense Management · Approval desk
New
Expense Reports Past Due
Expense reports
| Expense report number | Supplier | Due date | Balance due | Status | |
|---|---|---|---|---|---|
| ER-25438 | VND-234 | 10 Oct | BD-211 | Draft | |
| ER-22571 | VND-060 | 09 Oct | BD-893 | Submitted | |
| ER-89009 | VND-240 | 04 Oct | BD-813 | Approved | |
| ER-66985 | VND-018 | 04 Oct | BD-790 | Scheduled | |
| ER-71481 | VND-204 | 05 Oct | BD-848 | Paid |
6 of 6 records
BD-211Expense reports · ER-25438
DraftSupplierVND-234
Due date10 Oct
What you can do
Approval desk in the working day
Expense Reviewer opens a Submitted report and checks the supplier, organization, total and coded lines. The configured approval action guards the report status change, moves the report to Approved and creates a review decisions record plus an operation receipts record. That pairing matters: the status states the current position while the decision identifies the reviewer and the operation receipt shows whether the action ran.
How the work is organized
- Record owner. Keep the responsible organization and source identity clear before the next person acts.
- Decision point. Use the current status and the underlying lines or linked records to decide the next step.
- Evidence trail. Keep the reviewer, amount and operation outcome traceable from the business record.
A reviewer can use the decision record to explain what was approved, rejected or returned, with conditions and notes. For a disputed hotel charge, record the reason on the decision and leave a correction route that the preparer can follow. Do not make a new approval look like a continuation of an earlier decision after material line or total changes. The Controller reviews authority and exceptions.
What to agree during setup
Agree the reviewer assignment, approval limits held on team members and the circumstances in which Controller decides. Decide what a returned report needs before resubmission, and how a reviewer recognizes the same source reference in another report. An approval action should be available only to the right reviewer role in the finished setup.
The team should decide who handles corrections before the first live cycle. Give each handoff an owner and confirm that a failed action remains visible to that owner. Use one representative supplier and one exception during setup, so permissions and reports reflect the work people will actually do.
Check the handoff on an actual case
Submit a report with two expense lines and a known supplier. Expense Reviewer checks both lines, uses the approval action and confirms that the report is Approved, a decision names the reviewer and the operation receipt succeeded. Then rehearse a report whose supplier or coding is wrong: return it with notes and confirm that no reimbursement is released as a side effect.
Ask the next role to find the same case from their own screen without help from the preparer. They should be able to identify the supplier or partner, the relevant amount, the current status and the supporting decision. If a correction is needed, keep the prior result available and repeat the handoff with the corrected record.
What your team sees
- Expense Reports Pending Approval — Submitted reports waiting for a person to decide.
- Review Decision Register — Recorded decisions with their reviewers and conditions.
Follow the work through
Read Expense approval and reimbursement for the stages and rehearsal, then use implementation to assign owners and check access.
What it keeps track of
Data model- Expense reports
- Expense report header: a traveler's claim submitted, reviewed, approved and reimbursed, with supplier reference, totals and reimbursement status.
- Expense lines
- Individual expense lines on an expense report, coded to a ledger account with quantity, unit price and tax.
- Review decisions
- Approval trail: who approved, rejected or returned a bill, invoice, payment or journal entry, when and under what conditions.
- Operation receipts
- Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
- Team members
- Finance staff who prepare, review and approve finance operations, with their role and approval limit.
Who uses it
Permissions- Expense Reviewer
- Decides on submitted reports.
- Expense Preparer
- Handles corrections.
- Controller
- Owns the approval boundary and inspects failed operations.
Set up Travel & Expense Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.