Guest reimbursements need finance context without turning guests into employees.
Administrators need a simple claim path while finance needs policy, payment, and reconciliation records that hold up at close.
Who you’d be doing this for
“I spent Friday matching guest payments to a spreadsheet because finance needed them in the close file.”
Boubacar Okafor · Expense Administrator
Manages employee expense compliance and manually coordinates non-employee reimbursements for a corporate expense program.
What is at stake
Guest reimbursements sit outside the expense record, forcing finance to rebuild their trail at close. You have to choose a first scope that helps administrators without weakening payment and audit controls.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- guest simplicity vs finance-ready records
- payment speed vs policy context
- narrow pilot scope vs reusable workflow
- administrative adoption vs legal reviewability
Why Navan
Navan Expense already connects expense records to payments and reconciliation, making guest reimbursement a gap in the same finance workflow.
Written with these in mind
Not your kind of problem? 54 more at Navan, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.