← Navan
Complex day at Navan

Commit tax corrections after accounting exports lock

You’re the software engineer. Your team is in the room. Printed Oct 17, 2026.

Committed accounting exports are colliding with later tax corrections.

Finance needs current tax totals while the ledger needs a permanent and explainable record.

Who you’d be doing this for

“My controller asked why the ledger says one amount and the report says another.”

Ato Tetteh · Expense Administrator

Owns policy review and accounting readiness for a multinational corporate expense program.

What is at stake

Some approved expense reports now show tax totals that differ from their committed accounting exports. You must weigh a fast correcting path against auditability and finance review.

Why it isn’t already fixed

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

  • fast correction vs. committed ledger integrity
  • automation scale vs. finance review
  • event replay safety vs. close-time urgency
  • current expense data vs. permanent accounting history

Why Navan

Expense reports connect card and reimbursement spend to accounting systems where tax totals must remain reconcilable through close.

Written with these in mind

distributed systems engineerpayments engineerbackend reliability 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.