Payroll eligibility data is outside the expense flow that reviewers use to assess mileage and per diem.
The customer needs less spreadsheet work at close, while the first integration must remain usable beyond one payroll setup.
Who you’d be doing this for
“Every close I’m opening payroll sheets just to check whether a claim should be here.”
Radu Olaru · Expense Administrator
She reviews mileage and per diem claims for a European field workforce and reconciles them against payroll-held eligibility records.
What is at stake
64% of mileage and per diem claims need a payroll spreadsheet check before approval. You must weigh a narrowly testable pilot against an integration pattern the next customer can reuse.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- first-version speed vs reusable integration design
- payroll data minimization vs eligibility coverage
- manual control vs reduced spreadsheet work
- mileage scope vs per-diem learning
Why Navan
Navan Expense supports international mileage and per diem, and a reusable customer integration can bring those claims into the same controlled expense process as other spend.
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.