Receipt corrections and card matching can create two records for one purchase.
Fast event processing protects timely expense capture, while one durable record protects policy review and accounting accuracy.
Who you’d be doing this for
“I had to explain why one lunch showed up twice when finance was already closing the books.”
Poul Andersen · Expense Administrator
Reviews policy exceptions and prepares corporate-card expenses for accounting export.
What is at stake
One card purchase can produce two expense records after a receipt correction. You must protect fast matching without letting policy and accounting work split across duplicates.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast event handling vs. single-record integrity
- receipt edit visibility vs. duplicate prevention
- safe replay behavior vs. silent partial writes
- clean exports vs. source-level correctness
Why Navan
Corporate-card expense flows depend on receipt intelligence, policy auditing, and accounting integrations agreeing on the same expense record.
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.