← Navan
First-time day at Navan

Map retired departments before the next payment run

You’re the solutions / forward deployed engineer. Your team is in the room. Printed Oct 17, 2026.

The export needs current department values without erasing the customer’s audit trail.

Finance needs transactions posted before payment run, while accounting needs the original source values preserved.

Who you’d be doing this for

“I’ve got 125 rejects in one queue, and finance wants them cleared before Friday.”

Evangelos Christodoulou · Expense Administrator

She administers policy and accounting mappings for a corporate expense program using corporate cards.

What is at stake

125 approved card transactions are failing the accounting export because four department values were retired. You must weigh a reusable translation layer against asking finance to reopen ERP master data.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • payment-run speed vs audit traceability
  • ERP ownership vs deployment reuse
  • queue reduction vs mapping precision

Why Navan

Navan Expense corporate card transactions only deliver real-time spend visibility when they reach the customer’s accounting process cleanly.

Written with these in mind

ERP integration specialistfinance systems implementerforward deployed engineer

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.