YouTube2Text

Navan Expense: Spring 2026 Product Release On-Demand Webinar — Transcript

by Navan · 10,253 words · 1,610 segments · language en · Watch on YouTube

Full transcript

  1. 0:00All righty.
  2. 0:01We're going to get started. So, hello
  3. 0:03everybody.
  4. 0:04Uh welcome to the Navan Spring Expense
  5. 0:07Product Release Webinar. Uh I'm Josh
  6. 0:09Truck on the Navan Expense and Payments
  7. 0:11Product Marketing team, and I will be
  8. 0:13your MC for today. So, it's great to see
  9. 0:15so many folks coming in, and we have
  10. 0:17more trickling in by the second, so we
  11. 0:19appreciate you being here. Uh excited to
  12. 0:21showcase what the team's been building
  13. 0:23and delivering to thousands of customers
  14. 0:25across the globe. So, just a few quick
  15. 0:28reminders before we get started.
  16. 0:31Uh Google Chrome will likely be uh give
  17. 0:33you the best experience. Uh if you have
  18. 0:35questions, we highly encourage them
  19. 0:37throughout. Please pop them in the Q&A
  20. 0:39tab at any time. Uh some of our product
  21. 0:42experts might answer your questions
  22. 0:44during, but we'll also have a dedicated
  23. 0:46Q&A section at the end. Um one other
  24. 0:49reminder, what we're covering today is
  25. 0:51confidential information. So, if you're
  26. 0:53a Navan customer and you want to go
  27. 0:55deeper into anything we discuss, please
  28. 0:57reach out to your account manager.
  29. 0:59Uh if you're not a Navan customer and
  30. 1:01you want to learn more, we can set up
  31. 1:03time with a member of our sales team or
  32. 1:05product team. Just mention that in your
  33. 1:07Q&A question, as well.
  34. 1:09Uh and yes, we will email you a
  35. 1:12recording after. Uh we'll also send a
  36. 1:14survey at the end to let you know or to
  37. 1:16ask about your experience and see how we
  38. 1:18can continue to make these better and
  39. 1:19better.
  40. 1:22Next, so here's the team we're rocking
  41. 1:24with today. So, I'm joined by six
  42. 1:27wonderful members of the Navan Expense
  43. 1:29product team, including Chief Product
  44. 1:31Officer Yuval Refua.
  45. 1:36Oop. So, let's get into what we'll cover
  46. 1:37today. So, Yuval will kick us off with a
  47. 1:40look at Navan's expense vision uh and
  48. 1:42some shifts we're seeing in the market.
  49. 1:44Uh then we'll dive into four release
  50. 1:46areas, all built for trust, speed, and
  51. 1:48scale across your expense workflows.
  52. 1:51With that, I will pass it over to Yuval.
  53. 1:55Thank you, Josh. Hi, everybody. Nice to
  54. 1:57see you. I'm Yuval. I'm the CPO for
  55. 2:00payments and expense.
  56. 2:02And I'm really excited to tell you today
  57. 2:04about our vision and the latest product
  58. 2:06launches that we're doing.
  59. 2:08Let's get the next slide.
  60. 2:10Um so commerce is moving really faster.
  61. 2:14And the old expense model supported by
  62. 2:16the legacy systems is broken. It's
  63. 2:18inefficient. It's reactive and
  64. 2:21ultimately very risky to rely on.
  65. 2:24Usually, the first thing that happens is
  66. 2:26somebody swipes their card. Then finance
  67. 2:29teams chase policy, coding,
  68. 2:32reconciliation, and compliance after the
  69. 2:34fact.
  70. 2:35Good luck catching out of policy spend
  71. 2:37with that system.
  72. 2:39Uh it causes admin to react way too late
  73. 2:42with limited visibility and control,
  74. 2:44taking up to 60 days to identify a
  75. 2:46violation and close the books. While
  76. 2:49employees waste time submitting expenses
  77. 2:52and going back and forth with reviewers.
  78. 2:55For those employees, many of the legacy
  79. 2:58products show how broken the model is.
  80. 3:01It takes 45 minutes to book a trip and
  81. 3:0420 minutes to submit an expense. And
  82. 3:06that's before all the back and forth.
  83. 3:09I remember early in my career all the
  84. 3:11information I had to copy from other
  85. 3:13system and paste it into my expense
  86. 3:15system just in order to submit an
  87. 3:16expense report.
  88. 3:18So, moving on to the new world. Next
  89. 3:20slide.
  90. 3:22Um organizations need a proactive
  91. 3:26control before the spend happens. For
  92. 3:28employees, it should be quick and easy.
  93. 3:31They need a way more like experience. It
  94. 3:34needs to be simple, seamless, and low
  95. 3:36effort. That's why Navan built an
  96. 3:38intelligent layer that works in the
  97. 3:40background for employees, getting all
  98. 3:43the necessary data for them to automate
  99. 3:45the expense process. For admins,
  100. 3:48it's the complete opposite. They need a
  101. 3:51Formula 1 style of visibility and
  102. 3:53control with telemetry information
  103. 3:56coming at them, controlling every spend
  104. 3:58at scale. This is how they really
  105. 4:00squeeze those extra seconds from every
  106. 4:03lap.
  107. 4:04Admins want to control every dollar
  108. 4:06spent, but they need a product to
  109. 4:08enforce it at scale.
  110. 4:10To do that, we need to give them a
  111. 4:12system to partner with that they can
  112. 4:14trust, verify, ask questions, and
  113. 4:17identify anomalies.
  114. 4:19And because Navan expense is built on
  115. 4:22deep travel foundation, that trust layer
  116. 4:25comes with rich context, flexibility,
  117. 4:28and unified infrastructure.
  118. 4:31So, jumping into the next slide.
  119. 4:33Um today, we will show you exactly how
  120. 4:37we're delivering on this promise with
  121. 4:39products that we launch. The question
  122. 4:41that we always ask is how can we be the
  123. 4:44trusted partner for our admins and
  124. 4:47users? We'll talk about four things that
  125. 4:49we're delivering to customers. First,
  126. 4:52once you configure your policy and audit
  127. 4:54checks, our AI adapts your risk
  128. 4:57tolerance. It auto codes expenses for
  129. 5:00you and automates reviews.
  130. 5:02This is exactly
  131. 5:04what our policy and audit engine is all
  132. 5:05about.
  133. 5:07Next, AI-powered admins
  134. 5:10will make sure the right decisions are
  135. 5:12going to the right people. We'll suggest
  136. 5:15actions for admins on context, perform
  137. 5:18supervised tasks, and do the work when
  138. 5:20it makes sense.
  139. 5:22Third, for users to rely on the Waymo
  140. 5:26experience, we need to meet them where
  141. 5:28they are.
  142. 5:29Expense chat agents allow our users to
  143. 5:32drop receipts and context in their about
  144. 5:34their expenses, and we'll handle the
  145. 5:37rest in seconds.
  146. 5:39And lastly,
  147. 5:40trust has to work everywhere. Everywhere
  148. 5:43your business operates, whether that's
  149. 5:45ensuring European employees get expense
  150. 5:48advances, reclaiming VAT, tracking
  151. 5:51mileage, and more.
  152. 5:54With that said, I'll pass it over to
  153. 5:55Thomas to walk you through our policy
  154. 5:58and audit engine and show you exactly
  155. 6:01what proactive control looks like in
  156. 6:02practice.
  157. 6:05Amazing. Yeah, thank you Yoval and and
  158. 6:07yeah, thanks everybody so much for
  159. 6:08joining. I'll always love to have such a
  160. 6:10good group here.
  161. 6:12Um
  162. 6:12Josh, can we go to the next slide?
  163. 6:16Yeah, so I do want to start with this
  164. 6:18this poll.
  165. 6:19You know, I think as a former finance
  166. 6:21and accounting person myself, I have a
  167. 6:22lot of
  168. 6:23thoughts on this, but I'm curious to
  169. 6:24hear what kind of keeps keeps people up
  170. 6:26at night during during month-end close.
  171. 6:39Curious what the results are. Okay,
  172. 6:41chasing employees for missing receipts
  173. 6:43and information. Yeah, that's
  174. 6:45that's the
  175. 6:46the one we tend to hear the most, that's
  176. 6:47for sure.
  177. 6:48You know, I think it's
  178. 6:49kind of a constant battle and there's a
  179. 6:51lot that we're doing on our side to try
  180. 6:52to help, you know, fetch receipts
  181. 6:55automatically, remind people as much as
  182. 6:57we can, but but yeah, it's definitely,
  183. 6:59you know, always part of the job.
  184. 7:02Next slide, Josh.
  185. 7:05Cool. So,
  186. 7:07you know, I think
  187. 7:09just just to kind of level set a little
  188. 7:10bit on on kind of the next things we'll
  189. 7:12we'll we'll we'll talk about here is,
  190. 7:13you know, I think for finance and
  191. 7:14accounting teams, you know,
  192. 7:16a lot of times
  193. 7:18people don't get into finance and
  194. 7:19accounting
  195. 7:20in order to,
  196. 7:21you know, do all of this kind of menial
  197. 7:23work that
  198. 7:25that has to happen. There's a lot of
  199. 7:26other reasons why you kind of get into
  200. 7:27finance and accounting in the first
  201. 7:29place and I think a lot of the old way
  202. 7:30of managing expenses,
  203. 7:32you know, required
  204. 7:34disconnected systems and a lot of
  205. 7:37a lot of manual reviewers. So, yeah,
  206. 7:39third-party audit tools or a lot of
  207. 7:41manual coding or kind of rules-based
  208. 7:44coding that that, you know, got really
  209. 7:45complex and out of hand. Um, all sorts
  210. 7:48of reviewers that had to check
  211. 7:49transactions one by one to find,
  212. 7:52you know, audit issues or policy issues
  213. 7:54or coding issues. Um, you know, I think
  214. 7:57the vision that we have for Navan for
  215. 8:00finance and accounting teams is, you
  216. 8:02know, the ability to set up policy and
  217. 8:04audit checks up front in real time and
  218. 8:06have the software actually enforce those
  219. 8:09on your behalf. And also have agents
  220. 8:11that go through and code transactions,
  221. 8:13um, you know, based on your past
  222. 8:15patterns and based on transaction
  223. 8:16context and trip context and other
  224. 8:18things that we'll talk through after
  225. 8:19this. Um,
  226. 8:21so yeah, Kylie at Pendo, she's she she's
  227. 8:23great. Uh, she's she's their head of
  228. 8:25global accounting and, um, you know,
  229. 8:27really has seen a lot of benefit to to
  230. 8:29the use of Navan in terms of, um, you
  231. 8:32know, the way it's able to automate
  232. 8:34the approval and review of transactions,
  233. 8:36which has saved them a lot of work,
  234. 8:37which is great. Um, but yeah, with that,
  235. 8:40let's let's jump into,
  236. 8:41uh,
  237. 8:42to our audit engine, um, and kind of
  238. 8:44some of the more recent things we've
  239. 8:46built around that. So,
  240. 8:48today, um, you know, you can configure,
  241. 8:51if you go into policy settings flag
  242. 8:53management, you'll see kind of all of
  243. 8:55our audit flags. So, you know, of
  244. 8:58course, in our policy section, you can
  245. 8:59set up policy limits and receipt
  246. 9:01requirements and things like that. You
  247. 9:02know, that's kind of one part of it, but
  248. 9:04there's also all sorts of audit checks,
  249. 9:06right? So, excessive tipping or
  250. 9:08cigarettes, uh,
  251. 9:10on a receipt or, um, you know, booking
  252. 9:12amount mismatch or things like that.
  253. 9:14There's kind of this extra extra added
  254. 9:16layer where admins can go in and turn
  255. 9:19these flags on or off, set, configure
  256. 9:22different thresholds, um, for kind of
  257. 9:24your risk tolerance and and and your
  258. 9:25policy. Um, you know, I think a common
  259. 9:27example of this is late submission. So,
  260. 9:30if, uh, if your policy is that people
  261. 9:32can't submit after 60 days after the
  262. 9:34transaction has occurred, you can kind
  263. 9:35of set that threshold right here.
  264. 9:37Um and you know, I I I do want to call
  265. 9:39out one thing that that we've shipped
  266. 9:41recently
  267. 9:42um in here as well, which is the
  268. 9:43anti-corruption and bribery check. You
  269. 9:45know, I think this is it is pretty
  270. 9:46company specific, but you know, a lot of
  271. 9:48companies in order to comply with the
  272. 9:50Foreign Corrupt Practices Act
  273. 9:52kind of need um
  274. 9:54to screen transactions, you know, to to
  275. 9:57to find uh participants that are
  276. 9:59sanctioned or that are government
  277. 10:00employees. Um and you know, we're we've
  278. 10:03partnered with um with the London Stock
  279. 10:06Exchange Group uh
  280. 10:07to basically bring that directly into
  281. 10:09Navan at as an audit check. So, um
  282. 10:13yeah, this really gives you a lot of
  283. 10:15control up front to tell Navan, "Hey, go
  284. 10:17enforce all these policies on my
  285. 10:19behalf." And you know, that on top of
  286. 10:21our policy engine has has has led to the
  287. 10:23fact that 73% of transactions today
  288. 10:25flowing through Navan are completely
  289. 10:27touchless. Um and you know, we're we're
  290. 10:29trying to up that percentage as much as
  291. 10:31we can.
  292. 10:34Next slide, Josh.
  293. 10:36Yeah, I think that this is one part of
  294. 10:37this that I that I talked about, you
  295. 10:39know, we have agents um
  296. 10:41that screen receipts, L3 data, um
  297. 10:44transaction data um to find prohibited
  298. 10:47items. So, one thing for example is, you
  299. 10:50know, you you can flag uh
  300. 10:52transactions that have cigarettes or
  301. 10:54alcohol or gift cards on them for
  302. 10:55example. And of course, that's
  303. 10:56semantics. So, if it's
  304. 10:58if there's a receipt that says uh
  305. 11:00Marlboro Reds, you know, that's going to
  306. 11:02be flagged as, you know, cigarette being
  307. 11:04on the on on the transaction. Um you can
  308. 11:06also even do it by specific keywords
  309. 11:08that you care about. So, these are some
  310. 11:10of the keywords that a lot of our
  311. 11:11customers have kind of um decided to
  312. 11:13flag. And uh you know, anything around
  313. 11:16upgrades or massages or maybe um you
  314. 11:19know, dry cleaning at a hotel that
  315. 11:21people want to flag. There's a lot of
  316. 11:22customization here that you can really
  317. 11:23set up up front.
  318. 11:28Great. Um
  319. 11:30so, let me go through that that's kind
  320. 11:31of the audit engine. I think that
  321. 11:33I'd love to go through kind of our
  322. 11:34coding agent here because this is one of
  323. 11:36the more exciting things I think that
  324. 11:37we've been able to launch recently. Um,
  325. 11:39you know,
  326. 11:41pre-the world of AI, um, you know, you
  327. 11:44could kind of work to auto code
  328. 11:46transactions using,
  329. 11:47um, the MCC code of the merchant or, you
  330. 11:49know, the name of the merchant and and
  331. 11:51and different rules and things like
  332. 11:52that. And, you know, we've we definitely
  333. 11:54worked on that model for a while, but,
  334. 11:56um,
  335. 11:57the latest models, the most advanced
  336. 11:59models have gotten us to a point where
  337. 12:00we can really, really get intelligent
  338. 12:03about how we code transactions to the
  339. 12:05right expense type. Um, I have some
  340. 12:07reasoning examples up there.
  341. 12:09Uh, you know, for for for those that are
  342. 12:11that are interested, you can definitely
  343. 12:12read through it. But, um, you know,
  344. 12:14we're at a point now where we can code
  345. 12:16transactions to the right expense type
  346. 12:18with 90 plus percent accuracy,
  347. 12:20um,
  348. 12:21using receipt data, L3 data,
  349. 12:23transactional data, the user's role, the
  350. 12:26calendar invite, um, all sorts of
  351. 12:28things. I mean, you can see one example
  352. 12:30here is that, um,
  353. 12:32somebody registered for the McDonald's
  354. 12:34Worldwide 2026 conference. You know, in
  355. 12:36that case, McDonald's was the merchant,
  356. 12:38but our agent was able to see that, uh,
  357. 12:42that the receipt was for this conference
  358. 12:44and that the description included,
  359. 12:47um, some details about the conference.
  360. 12:49So, it was able to code it to
  361. 12:50conferences instead of meals.
  362. 12:52Um, I think that's just one one small
  363. 12:54example, but it really means that with
  364. 12:56all of the data we have as Navan, again,
  365. 12:58trip data, L3 data, receipt, all sorts
  366. 13:01of other things, you know, your past
  367. 13:02coding, um,
  368. 13:04we can really, really get much, much
  369. 13:05better here. And, we rolled this out
  370. 13:07fully for manual transactions as well as
  371. 13:09card transactions, um, yesterday. So,
  372. 13:12um,
  373. 13:13definitely a lot going on here, and, uh,
  374. 13:15I think the second part of this that I
  375. 13:17really want to double down on is that
  376. 13:20our, you know, kind of model and and and
  377. 13:23our agents are working to get smarter
  378. 13:25over time. So, we've we've basically
  379. 13:27built
  380. 13:28an ability for
  381. 13:30admins to come in and learn and and and
  382. 13:33kind of
  383. 13:34prompt the AI or give it training.
  384. 13:37Um so, today as an admin, if you go in
  385. 13:39and edit an expense type on a
  386. 13:40transaction, we'll actually prompt you
  387. 13:42to
  388. 13:43tell us why you updated it, you know, as
  389. 13:46if you're training someone new,
  390. 13:47basically.
  391. 13:48Um and then we take that and we can feed
  392. 13:49it back into our models to help get make
  393. 13:51the coding more and more accurate over
  394. 13:53time. So, I think that's I hope that's
  395. 13:55something that our admins can take
  396. 13:57advantage of.
  397. 14:04Do you want to hop into a straight demo,
  398. 14:05Thomas?
  399. 14:06Yeah. Yeah, let's do it.
  400. 14:09Cool. So, I'll I'll I'll demo two things
  401. 14:11today.
  402. 14:12Um
  403. 14:13I think I'll I'll I'll start here on the
  404. 14:14um on the flag management side. Um you
  405. 14:17know, I think this is something that
  406. 14:19hopefully most of your of you are
  407. 14:20familiar with, but yeah, if you go into
  408. 14:22configuration policy settings and flag
  409. 14:24management, you can kind of come in here
  410. 14:26and see all of our different audit
  411. 14:27flags, including the new um
  412. 14:30um
  413. 14:30kind of uh corruption and bribery check.
  414. 14:33And from here, yeah, you can set
  415. 14:35different thresholds, toggle these on or
  416. 14:37off for ones that you care about or
  417. 14:38don't care about, um
  418. 14:40set different things. So, if you want to
  419. 14:42catch keywords, like I said, or
  420. 14:44different um prohibited items on on
  421. 14:46transactions, you can catch that as
  422. 14:47well.
  423. 14:48I think this is another one I want to
  424. 14:49highlight, which is um auto-verifying
  425. 14:51receipts. So, receipts that are blurry
  426. 14:53or invalid, um you know, we're able to
  427. 14:56catch those as well um
  428. 14:58through through our audit checks. So,
  429. 15:00definitely something I think that's
  430. 15:01that's great for admins to leverage.
  431. 15:03Um
  432. 15:05I'll touch real quick as well on the um
  433. 15:07coding agent. So, I think
  434. 15:11you know, I love hearing feedback from
  435. 15:13finance and accounting teams as much as
  436. 15:14I possibly can, and so we track this
  437. 15:15very closely. But today, like I said, as
  438. 15:17an admin, if you come in here and you
  439. 15:19change uh the expense line item on on
  440. 15:21something, we'll prompt you to tell us
  441. 15:23why you made that change.
  442. 15:25Um, so you could say, you know,
  443. 15:27"Changed it because,
  444. 15:29you know, it was
  445. 15:30uh
  446. 15:31this user usually transacts at gas
  447. 15:34stations for gas."
  448. 15:36Whatever you want to say. Um, and once
  449. 15:37you submit that, that comes actually to
  450. 15:39me and our team in real time and we're
  451. 15:41able to feed back that feed that back to
  452. 15:42the model to improve the coding for you
  453. 15:44in the future.
  454. 15:46Um,
  455. 15:47so yeah, that's it on on our coding
  456. 15:50agents and um
  457. 15:52and and and our audit engine. And uh
  458. 15:54I'll pass it off to the next team.
  459. 15:59Thank you, Thomas. Um, great to meet you
  460. 16:01guys. I'm Pauline. I'm a product manager
  461. 16:04um on the expense admin team and I'm
  462. 16:06excited to kind of walk you guys through
  463. 16:08some of the exciting stuff that we're
  464. 16:09working on. Um, the way I like to think
  465. 16:12about this is, you know, here at Navan,
  466. 16:15we make um tracking and managing
  467. 16:18expenses very easy across the org. Um,
  468. 16:22up to I'd say like 75% of expenses by
  469. 16:25your employees are usually like
  470. 16:27auto-approved by the policy that you set
  471. 16:29up. Um, but today I will be spending
  472. 16:32some time talking about the 25% of these
  473. 16:35expenses that will go through manual
  474. 16:37reviews. And you know, at the end of the
  475. 16:38day, um you can only automate so much. I
  476. 16:41think the reason why these policies
  477. 16:43exist is to kind of um
  478. 16:46communicate to the org um the different
  479. 16:48ways they should be spending, but you
  480. 16:50know, for the ones that fall out of
  481. 16:52policy, how do we, you know, as admins
  482. 16:55review these in a more efficient and
  483. 16:57quicker way? I'll be chatting through a
  484. 16:59couple of um recent uh features that we
  485. 17:02shipped, but also focus a lot on some of
  486. 17:04the AI features that we have in the
  487. 17:06pipeline.
  488. 17:08So, to get started, um we wanted to uh
  489. 17:12run a poll. I think I kind of uh have a
  490. 17:14sense of the answer here um given the
  491. 17:17earlier poll as well, but I wanted to
  492. 17:20know what usually delays admins from
  493. 17:25easily, quickly resolving flagged
  494. 17:27transactions. Um, are you chasing
  495. 17:30employees? Oh, I lost the Okay, chasing
  496. 17:33employees, you're waiting for manager to
  497. 17:35approve, or there's just a lot of
  498. 17:37flagged transactions that pile up. So,
  499. 17:39pretty consistent, there's a lot of
  500. 17:41chasing, um, employees for a missing
  501. 17:43receipt, missing fields, missing
  502. 17:45information.
  503. 17:46Um, so I'm excited to chat through some
  504. 17:48of the efforts that we have, um, to make
  505. 17:50that, uh, easier.
  506. 17:52So, next slide. So, one of the things
  507. 17:54that we shipped recently, and this is
  508. 17:56kind of a result from one of the big
  509. 17:59pain points that we're hearing from a
  510. 18:01lot of admins, is while Navan makes
  511. 18:03expenses and expense tracking very easy,
  512. 18:06sometimes it's too easy. And, you know,
  513. 18:08managers will, um, go in and just
  514. 18:11approve things, um, so they're not the
  515. 18:13bottleneck, but sometimes they make the
  516. 18:15wrong approval. You know, sometimes the
  517. 18:16user, the employee doesn't hasn't
  518. 18:18provided the receipt yet, they haven't
  519. 18:20provided, you know, an updated, um, list
  520. 18:22of participants. And a lot of these
  521. 18:24wrong approvals actually cause a lot of
  522. 18:26downstream work and cleanup for the
  523. 18:28admin.
  524. 18:29Um, and especially since we just uh,
  525. 18:32shipped, you know, the ability to
  526. 18:34require review for all transactions, um,
  527. 18:37the number of transactions that and like
  528. 18:40kind of enter into the managers review
  529. 18:42queue, um, is is growing. Uh, so we
  530. 18:46recently shipped, um, kind of
  531. 18:49a contextual approval experience. So,
  532. 18:52previously, when a manager goes in and
  533. 18:53approves transactions, we have an
  534. 18:56optional, um, field for them to provide
  535. 18:59a note for the admin. Now, if we see
  536. 19:01that it's still missing information,
  537. 19:03then we require managers to, um, add
  538. 19:06more context or add more justification
  539. 19:08to that. Um, in addition to that, we
  540. 19:11also ship a ready to approve toggle um
  541. 19:14on the right here you can see.
  542. 19:16Um, so this one allows the manager to
  543. 19:19have a default view of flagged
  544. 19:21transactions that filters for the ones
  545. 19:25where all of the required documentation
  546. 19:28and receipts are available before
  547. 19:29managers go in and approve. This way
  548. 19:31it's easier for managers who
  549. 19:33understandably aren't as familiar with
  550. 19:35the product as maybe an admin is, um, to
  551. 19:38just know exactly where and what they
  552. 19:41need to approve and what when it's ready
  553. 19:43for for approval. Um, we've seen a lot a
  554. 19:46very promising results so far. Um, so
  555. 19:49we've seen uh like a 70% reduction in
  556. 19:52non-compliant approvals, i.e. like wrong
  557. 19:55approvals, um, because a lot of these
  558. 19:58workflows are a lot clearer.
  559. 20:00Um, and we also see a 50% reduction in
  560. 20:03time to approve transactions for for
  561. 20:06managers. So a lot of this we we think
  562. 20:09is because, you know, showing the ready
  563. 20:11to approve only queue for managers. It's
  564. 20:14so easy and simple for them that they
  565. 20:16can just go in and and kind of go
  566. 20:18through everything that needs approval
  567. 20:19without having to deal with, you know,
  568. 20:21trying to understand context for every
  569. 20:23single transaction.
  570. 20:26Next slide, Josh.
  571. 20:28Um, this is something that's coming.
  572. 20:31We're we're currently in a closed beta.
  573. 20:32If you guys are interested, please reach
  574. 20:34out to us so we can also onboard you.
  575. 20:36But we are bringing Navan to a Slack
  576. 20:39near you. Um, we know a lot of our uh
  577. 20:41customers use Slack as their main
  578. 20:43communication and collaboration tool
  579. 20:45within the org. Um, so we wanted to
  580. 20:48bring Navan to Slack um to make it
  581. 20:51easier for your employees and for your
  582. 20:53managers and approvers, um, to, you
  583. 20:55know, go through all of their tasks, um,
  584. 20:58on on Navan.
  585. 20:59Um, so for approvers, we're going to,
  586. 21:02you know, introduce a way for approvers
  587. 21:04to see all of their um ready to approve
  588. 21:06transactions with all of the context
  589. 21:08needed.
  590. 21:09And then for the employees, we make it
  591. 21:12easier for them to also see all of their
  592. 21:14flag transactions. They can upload the
  593. 21:16receipt, they can you know, add a
  594. 21:18description, add participants all
  595. 21:21without leaving Slack which we you know,
  596. 21:24we are hoping will bring down these like
  597. 21:26compliance times even even more.
  598. 21:30Okay, I want to spend some time chatting
  599. 21:33about the AI workflows that were you
  600. 21:36know, thinking about building internally
  601. 21:39and a lot of these are actually already
  602. 21:40in beta. So same kind of nudge through
  603. 21:43reach out to your AMs if you guys are
  604. 21:45wanting to
  605. 21:47take part in this beta program.
  606. 21:49But our vision really for admin AI is to
  607. 21:53automate all of the routine and
  608. 21:55predictable busy work that come with you
  609. 21:58know, manual reviews of expenses and
  610. 22:00empower admins to focus on a lot of the
  611. 22:03high impact
  612. 22:05kind of strategic governance type work
  613. 22:08without having to be bogged down by you
  614. 22:10know, chasing people, reviewing expenses
  615. 22:12that are likely you know, most of the
  616. 22:15time is is going going to be approved.
  617. 22:17And so a couple of things that you know,
  618. 22:19we have here is focused on
  619. 22:23making the spend review process a lot
  620. 22:26more automated
  621. 22:28and introducing you know, AI that learns
  622. 22:31from your past actions, your
  623. 22:34organization's policy and then comes up
  624. 22:37with these suggestions to make to make
  625. 22:40your lives like a lot easier. So one of
  626. 22:43these is the first one is suggested
  627. 22:44replies. So this is you know, touches on
  628. 22:46that chasing component where admins you
  629. 22:50know, most of the time spend a lot of
  630. 22:52time chasing employees for receipts, for
  631. 22:55missing information, missing
  632. 22:57participants.
  633. 22:59And you usually do that today through
  634. 23:01Navan. Um, you can request more
  635. 23:03information on transactions. And so now
  636. 23:05we automate that part and, you know,
  637. 23:07propose a message for you so that you
  638. 23:10can you don't even need to think about
  639. 23:12it. You can just send the message that
  640. 23:14we um, propose and then that model also
  641. 23:16learns from past messages that you've
  642. 23:19sent and picks up on your, you know, the
  643. 23:21way the the tone you use and the way you
  644. 23:24craft sentences um, so that it's very
  645. 23:26aligned to the admin's um, style. Uh,
  646. 23:29we're currently in a beta for this and
  647. 23:31we're up to 40% like acceptance and so
  648. 23:34that means, you know, 40% of the
  649. 23:36suggested responses are mostly accepted
  650. 23:39by admins from the get-go. Um, and we're
  651. 23:41looking to bring this up um, even more.
  652. 23:44The second part is about um, automated
  653. 23:46transaction routing. Um, and so this is
  654. 23:48where the AI um, we we we basically see
  655. 23:53um, what's the activity within
  656. 23:54transactions and we are able to
  657. 23:57automatically route, you know, a
  658. 23:59transaction where you have maybe a
  659. 24:01requested information back to flagged if
  660. 24:03we see that the employee has provided
  661. 24:05all the information. So this is where,
  662. 24:08you know, you can imagine an admin um,
  663. 24:10leaving a note for the user to add the
  664. 24:13receipt and add participants for this
  665. 24:15um, meal expense and once the user
  666. 24:18provides those information, we
  667. 24:20automatically either run it through the
  668. 24:22policy and maybe it gets auto approved
  669. 24:25or if it still flags the uh, if the
  670. 24:27policy still flags it, it goes back to
  671. 24:30your flag queue so the admin doesn't
  672. 24:31need to kind of think about, okay, what
  673. 24:33are the transactions that I've um, open
  674. 24:36requests on. They they immediately see
  675. 24:38everything in one place.
  676. 24:39Um, lastly, uh, we also have suggested
  677. 24:42actions. Um, so this is where we um,
  678. 24:45take it a step further um, through the
  679. 24:48your spend review process and look at
  680. 24:51the flag transactions and suggest
  681. 24:52actions based on your policy and, you
  682. 24:56know, your your personal tolerance for
  683. 24:59for for these like um policy flags.
  684. 25:02Um so, for instance, you might have a
  685. 25:05org policy that says that meals have to
  686. 25:09be under $25, but, you know, within the
  687. 25:12admin team, you know that if it goes
  688. 25:13over by 10%, usually um if it's, you
  689. 25:16know, justified, you see all the
  690. 25:17participants, you will go ahead and
  691. 25:19approve it anyway. And so, we pick up on
  692. 25:21these very nuanced um actions and
  693. 25:25nuanced like logic and apply it to the
  694. 25:28suggested action um so that you don't
  695. 25:30need to spend a lot of brainpower really
  696. 25:33understanding each transaction and um
  697. 25:36making a decision based off of that. So,
  698. 25:38this is what we have right now in beta.
  699. 25:41Um some of the things that we're
  700. 25:42planning to do in, you know, the next
  701. 25:44few months is taking this a step further
  702. 25:47and maybe, you know,
  703. 25:48where where you don't even need to go in
  704. 25:50and see the transaction or um generate
  705. 25:53like an action. We automatically, you
  706. 25:56know, you log into Navan, we give you
  707. 25:58everything you need to do based on um
  708. 26:00our assessment, and you click a button
  709. 26:02and then go through all of your open uh
  710. 26:04open transactions. So.
  711. 26:07Um
  712. 26:09yeah, Josh, next slide.
  713. 26:14Okay.
  714. 26:15Um so, to kind of wrap up, um a lot of
  715. 26:18what we've talked about is related to
  716. 26:21really streamlining your process from
  717. 26:23when the user, the employee, swipes
  718. 26:25their Navan card to um posting to your
  719. 26:28ERP. Um a lot of what Thomas talked
  720. 26:30about is about, you know, strengthening
  721. 26:33that automation arm and making sure that
  722. 26:35a lot majority of the transactions are
  723. 26:37auto-approved. A lot of what I talked
  724. 26:38about is, you know, that 25% of
  725. 26:41transactions that need to go through
  726. 26:43manual uh approval and you know,
  727. 26:45introducing ways to make that faster. Um
  728. 26:48so, next we have Amanda and she uh who's
  729. 26:51going to be talking about spend that
  730. 26:52happens outside of your Navan corporate
  731. 26:55cards
  732. 26:56and how we help you manage that better.
  733. 27:02Thank you for that
  734. 27:04Pauline. Hey everyone, my name's Amanda
  735. 27:07and I'm super super excited to share
  736. 27:09more about what the user experience is
  737. 27:11like.
  738. 27:12I'm one of the PMs on the user
  739. 27:13empowerment team. So very very excited
  740. 27:16to chat with you all today.
  741. 27:18Before I actually get into that Josh if
  742. 27:20you wouldn't mind staying on the
  743. 27:21previous slide.
  744. 27:23I wanted to just provide a little bit
  745. 27:25more context while people are filling
  746. 27:27this in.
  747. 27:28For those of you who have used Navan in
  748. 27:30the past you're probably familiar with
  749. 27:32our card solution. And if I do say so
  750. 27:34myself it is rather seamless and
  751. 27:35magical.
  752. 27:37But if you submit more out of pocket
  753. 27:38reimbursements with your personal card
  754. 27:41historically it's a little bit more
  755. 27:42tedious when it comes to setting setting
  756. 27:44up reimbursements. So if you're someone
  757. 27:47that tends to like to pile up receipts
  758. 27:49towards the end of the month it does
  759. 27:51take quite some time to get your
  760. 27:52reimbursements ready to go. And so that
  761. 27:54kind of leads into this question that we
  762. 27:56have in the poll asking the room here
  763. 27:58how long do you think it takes on
  764. 27:59average to submit an out of pocket
  765. 28:01expense.
  766. 28:03And interestingly enough majority of the
  767. 28:05users here are saying one to five
  768. 28:07minutes. But Josh if you wouldn't mind
  769. 28:09sharing the response that we see is
  770. 28:12actually closer to 11 and a half
  771. 28:13minutes. And this is in a general
  772. 28:15average right? So
  773. 28:17we have people who are submitting faster
  774. 28:19but generally people who take a bit more
  775. 28:20time.
  776. 28:21So that kind of gauges a little bit of
  777. 28:23why we went about solving this issue and
  778. 28:25that's where I would like to Josh if you
  779. 28:27wouldn't mind next slide introducing
  780. 28:30expense chat where our goal is to help
  781. 28:32you fill out your out of pocket expenses
  782. 28:35through the chat way. And what does that
  783. 28:36mean? We're trying to replace the
  784. 28:38current manual form process and clicking
  785. 28:41between multiple fields with a simple AI
  786. 28:43conversation. And as the end user what
  787. 28:45do you have to do? It's rather simple.
  788. 28:47You either have to drop in your receipts
  789. 28:49or provide as much context as you want
  790. 28:51regarding a mileage or any team outing
  791. 28:54or meal that you want into a chat and
  792. 28:56the agent handles the rest. So, what our
  793. 28:58agents are going to be doing is we're
  794. 29:00going to be looking at receipts, pulling
  795. 29:02in any relevant data regarding your
  796. 29:04transactions, your merchants, any tax or
  797. 29:06itemized uh line items. We'll also look
  798. 29:09at the individual user's information.
  799. 29:11What that means is if you have any
  800. 29:13bookings on Navan, we'll pull that
  801. 29:14information in. If you
  802. 29:16expense in the past as well, we'll also
  803. 29:18look at any expensing behavior and apply
  804. 29:20that to your transactions. All you have
  805. 29:23to do is validate and get those
  806. 29:24submitted.
  807. 29:25But, if for whatever reason you want to
  808. 29:27make any changes, how you can do that?
  809. 29:30I'll show you in a bit, but it's
  810. 29:31actually really simple.
  811. 29:33You can either type that into chat or I
  812. 29:36can show you a little bit more about our
  813. 29:37sneaky little shortcut function, which
  814. 29:39is super convenient when you have a
  815. 29:41bunch of transactions that you want to
  816. 29:42get submitted in one go.
  817. 29:44I'll make a call out that right now
  818. 29:46we've actually launched this chat
  819. 29:47function a little over a month ago for
  820. 29:50users that are primarily in the US and
  821. 29:52on the web app, but very quick soon
  822. 29:54we're going to be releasing out to the
  823. 29:56rest of EMEA as well as um moving over
  824. 30:00to mobile down the line. So, some
  825. 30:02exciting things to look out for.
  826. 30:04And Josh, would you mind sharing next
  827. 30:07slide?
  828. 30:08Like I said earlier, we've had this chat
  829. 30:10out for a little over a month now. We've
  830. 30:11been very, very pleased with how the
  831. 30:13user responses have been so far. So, on
  832. 30:16the top you just have some sample user
  833. 30:17sentiments of either users that were bit
  834. 30:20hesitant about an AI first chat function
  835. 30:23to all those that were super excited to
  836. 30:25play around with what chat means.
  837. 30:27Um on the bottom here you're going to
  838. 30:28see some high-level metrics of what
  839. 30:30we've seen so far. Particularly happy
  840. 30:32about the over $9 million submitted
  841. 30:34already in the last 9 weeks.
  842. 30:36The middle number 56 seconds is one of
  843. 30:39my favorites where we have a user that
  844. 30:41in one conversation and under a minute
  845. 30:43was able to get 24 expenses successfully
  846. 30:46filled in and submitted for their admins
  847. 30:48to review.
  848. 30:49And then the last number is our average
  849. 30:51customer satisfaction score right now of
  850. 30:53around 90, which is great.
  851. 30:55And then on the right over here, this is
  852. 30:57just a sample of how our users have
  853. 31:00already started adapting and learning
  854. 31:01how to get their expenses even more
  855. 31:04quickly ready to get submitted. So, this
  856. 31:06is a sample mileage transaction that has
  857. 31:08many, many stops.
  858. 31:10And traditionally, you may have to click
  859. 31:11between multiple different fields, look
  860. 31:13up the exact address, specify the route,
  861. 31:16but all you have to do is what we're
  862. 31:17calling one shot. Provide your entire
  863. 31:19story into one message, and the agent
  864. 31:21gets everything ready, and you just have
  865. 31:23to click submit. So,
  866. 31:25super convenient experience, and I think
  867. 31:28rather than saying more, I would love to
  868. 31:30dive into a demo.
  869. 31:34So,
  870. 31:36if you all can see my screen, this is an
  871. 31:38example of a user's um expense
  872. 31:41environment. So, how to actually access
  873. 31:43this chat? Right now, um if you click on
  874. 31:46new transaction, and if you either start
  875. 31:48from adding a receipt, typing in
  876. 31:50details, or log mileage, you'll be
  877. 31:53presented with an option to experience
  878. 31:55our chat. And every single time you
  879. 31:58submit a manual reimbursement, we ask
  880. 31:59you this up front, but eventually we'll
  881. 32:01move this out of the individual entry
  882. 32:03points. But let's say for now on to
  883. 32:05generative AI.
  884. 32:07And this is my landing screen. And you
  885. 32:10can either start typing in information
  886. 32:11on the bottom here, or let's grab a
  887. 32:13couple receipts.
  888. 32:15So, let's just grab three random ones
  889. 32:18that I have ready.
  890. 32:20And I can get those submitted.
  891. 32:25So, what's happening right now is our
  892. 32:27agents in the background are going to be
  893. 32:29going through multiple tool calls. So,
  894. 32:31what that means is we're going to first
  895. 32:32look at any receipt data that we can
  896. 32:34capture from our OCR, which includes
  897. 32:37anything from transaction date, amount,
  898. 32:39currency, items, etc.
  899. 32:42And from there, we're going to hand off
  900. 32:44now to looking at the actual user
  901. 32:46information. So, we're going to look at
  902. 32:47if this user has any trips on Navan that
  903. 32:50might have already
  904. 32:51that have been on the same transaction
  905. 32:53date, any calendar event, for example,
  906. 32:56that we can also tie this expense to if
  907. 32:58you have a calendar connected. And then
  908. 33:00the most magical piece is filling in any
  909. 33:03last remaining information that
  910. 33:06we can pull based on your expensing
  911. 33:08history. And so here, we have three
  912. 33:10transactions.
  913. 33:11And what's nice about chat, it now tells
  914. 33:14you, "Oh, you have two transactions that
  915. 33:16are missing a required field for
  916. 33:18fruits." And so, let's do a sample of a
  917. 33:21couple edits here.
  918. 33:23So,
  919. 33:24not by default right now, our Teleferic
  920. 33:27Barcelona transaction is a meals for
  921. 33:28myself. But I actually want to edit it
  922. 33:31to, let's say,
  923. 33:33is a Let's say team event.
  924. 33:37And I want to add Yuval and
  925. 33:44I will take this transaction. And this
  926. 33:46is multiple changes in one message. And
  927. 33:49we could we can see this happening live
  928. 33:51here on the right. So, both of these
  929. 33:53fields are going to get updated, expense
  930. 33:56type and participants.
  931. 33:59There we go.
  932. 34:00And we can take one last look here of
  933. 34:03Okay, cool. So, the remaining last field
  934. 34:05that I have required is fruits. And so,
  935. 34:08I teased a little bit earlier of our
  936. 34:09shortcut, and we also mentioned this
  937. 34:11here. So, rather than typing in, "Show
  938. 34:13me what options I have for fruits." or
  939. 34:15"I want to do this." I can actually
  940. 34:16backslash
  941. 34:18and just search up the field. And I can
  942. 34:20either make that change for all receipts
  943. 34:22or individual one, but let's just say
  944. 34:23all. I don't want to change it to guava.
  945. 34:26Same thing here. We're going to see the
  946. 34:28chat make an update to both transactions
  947. 34:31live. And that's going to satisfy the
  948. 34:33receipt missing required field
  949. 34:34requirement.
  950. 34:40Awesome. And then I can just
  951. 34:42double-check that everything is filled
  952. 34:44in.
  953. 34:45And all I need to do now is just submit.
  954. 34:48And the last thing that I need to do now
  955. 34:50is the agents are going to be validating
  956. 34:53every transaction one by one just to
  957. 34:55make sure that one, there's no more
  958. 34:57missing information that is needed, and
  959. 34:59then two, just validating that this
  960. 35:00receipt is actually ready to go and to
  961. 35:03get submitted.
  962. 35:04And once it's submitted, it is up to the
  963. 35:07admins to then go in and review.
  964. 35:10And I actually did a sample of what
  965. 35:12we're calling a multi-message
  966. 35:14conversation, but we've actually seen
  967. 35:16our users, funny enough, presenting all
  968. 35:19of this information up front in one
  969. 35:21single message. So, you also have an
  970. 35:23interaction of basically two messages.
  971. 35:26And there we go. That's a sample view of
  972. 35:29how Expensify works. Happy to answer any
  973. 35:31questions in the
  974. 35:33Q&A.
  975. 35:35And I hand it off to Shruti.
  976. 35:44Hey everyone. Hi. My name is Shruti.
  977. 35:47And on the same lines of what Amanda
  978. 35:49just presented, talking about the user
  979. 35:52experience. Josh, next slide, please.
  980. 35:55I am incredibly proud of what we've
  981. 35:58launched when we talk about receipts and
  982. 36:00specially a dedicated space for receipts
  983. 36:03to sit. And with that being said, I
  984. 36:05directly want to jump into the demo
  985. 36:07because there's so much to talk about
  986. 36:09when we talk about receipt inbox.
  987. 36:15So, receipt inbox is basically in a
  988. 36:19line, a dedicated space for you to see
  989. 36:21your receipts. And it not only just
  990. 36:24stores your receipts, but it actually
  991. 36:26understands the receipt in terms of your
  992. 36:28incoming transactions. Now, in an ideal
  993. 36:31world, we have multiple flavors of
  994. 36:32transaction where you have an initial
  995. 36:35auth, posted auth, you give a tip, the
  996. 36:38transaction gets
  997. 36:39uh you know, updated to the current
  998. 36:41amount, and this is exactly where
  999. 36:43Receipt Inbox comes into play because we
  1000. 36:45do understand all types of transactions,
  1001. 36:48and we understand the receipts and the
  1002. 36:50data that comes in with the receipt. So,
  1003. 36:52what we've introduced when we say when
  1004. 36:54we talk about an inbox for receipts is
  1005. 36:57um unattached and recently attached
  1006. 36:59folders to your receipt inbox.
  1007. 37:02Unattached basically acts as a perfect
  1008. 37:05space for the frequent travelers that
  1009. 37:07some of you are, where you have a
  1010. 37:09receipt, grab and go,
  1011. 37:12put it in the receipt inbox, come back
  1012. 37:14later, and create a new reimbursement.
  1013. 37:16And that's exactly what I'm going to do
  1014. 37:17here. I click on the receipt, which is
  1015. 37:20already sitting in my unattached inbox,
  1016. 37:23and I just say new reimbursement, and
  1017. 37:27wait for the magic to happen. It creates
  1018. 37:28a transaction, there's a receipt
  1019. 37:30attached, submit. Now, take it with a
  1020. 37:33grain of salt. I'm using my demo
  1021. 37:35account, so obviously it's going to have
  1022. 37:36some flags, but in an ideal situation
  1023. 37:38where everything is configured
  1024. 37:39correctly, you should be able to submit
  1025. 37:41it, and you should be able to get your
  1026. 37:43money in your bank account.
  1027. 37:45Uh what happens when you want to like
  1028. 37:50send a few receipts, and you want like a
  1029. 37:53couple of transactions to like match?
  1030. 37:55So, let's say you have the Amex connect
  1031. 37:57card that we have, and you have a posted
  1032. 38:00transaction that gets submitted into
  1033. 38:02your uh expenses, and then you get a
  1034. 38:04receipt, right? Like it's all not always
  1035. 38:06in like a sequential manner. So, Receipt
  1036. 38:09Inbox is actually addressed to cater
  1037. 38:11that edge case as well, where we take
  1038. 38:13care of your posted or an initial auth
  1039. 38:17transaction, and we automatically match
  1040. 38:20your incoming receipts so that you don't
  1041. 38:22have to do the mix and match of receipts
  1042. 38:25to the transaction. So, I'm just going
  1043. 38:27to quickly show you like just adding a
  1044. 38:29few transactions here. So, you go to new
  1045. 38:31transaction flow, you add in your
  1046. 38:33receipts. I have a Chipotle receipt here
  1047. 38:36and a Starbucks one, and I'm just going
  1048. 38:38to upload it.
  1049. 38:39It gives me a cool little option of like
  1050. 38:41create two transaction. I click on it.
  1051. 38:44Uh
  1052. 38:46till it's, you know, uploading the
  1053. 38:48receipts. I also want to like quickly
  1054. 38:49call out and say that what we are doing
  1055. 38:51with Receipt Inbox V2, which is
  1056. 38:53basically coming in May, is we are
  1057. 38:56allowing users to basically uh upload
  1058. 39:00and go on the fly. So,
  1059. 39:02same thing. You can just like click
  1060. 39:04here.
  1061. 39:05It's a Starbucks receipt. I want to
  1062. 39:06attach it to a transaction. I already
  1063. 39:08have it posted. Boom, attach.
  1064. 39:12As simple as that.
  1065. 39:14Um with Receipt Inbox V2, we want to
  1066. 39:16give the end users the ability to like
  1067. 39:19upload and walk away. So, you should be
  1068. 39:20able to like close your mobile app,
  1069. 39:22close your web tab, and like come back,
  1070. 39:25and we will handle your uploads. You can
  1071. 39:27upload as many receipts as you want. We
  1072. 39:30do allow concurrent uploads, so watch
  1073. 39:31this space for more. And with that being
  1074. 39:34said, I will pass it back to Josh.
  1075. 39:44Thanks, team. And I will tap in Thomas
  1076. 39:45and Nadav to talk about some of our
  1077. 39:47global compliance updates.
  1078. 39:51Hey.
  1079. 39:52Yeah, sounds great. Um thanks so much,
  1080. 39:54everybody. Yeah, I'm I
  1081. 39:56um kind of manage a lot of our
  1082. 39:58international
  1083. 39:59uh products and features across per diem
  1084. 40:02and mileage and receipts and things like
  1085. 40:04that. So, I'll jump into that next.
  1086. 40:08Cool. Yeah, so, you know, I think um
  1087. 40:10Navan from day one has always been a
  1088. 40:12global company. I think especially
  1089. 40:14especially given the travel side of the
  1090. 40:15house, you know, we've always had to
  1091. 40:16operate super globally and so we want to
  1092. 40:18make sure that the expense product kind
  1093. 40:20of reflects that as well. And you know,
  1094. 40:22there's a lot of different requirements
  1095. 40:24and regulations and um things that we
  1096. 40:26have to comply with to allow our
  1097. 40:27customers to use us across the globe and
  1098. 40:29um
  1099. 40:30I'll I'll start here, I think.
  1100. 40:32Um expense advances is something that
  1101. 40:35that we built to support a lot of
  1102. 40:36customers across, you know, really
  1103. 40:38across the globe. Um you know, for
  1104. 40:39example, in Poland, this is actually a
  1105. 40:42um
  1106. 40:43you know, a a regulatory requirement to
  1107. 40:45allow for this. So, um this is live now.
  1108. 40:47So, uh this feature essentially allows
  1109. 40:51um users to request funds up front um
  1110. 40:54before they actually go on their trip so
  1111. 40:56that, you know, they're not having to
  1112. 40:57come come out of pocket for companies
  1113. 40:59that don't want to use uh corporate
  1114. 41:01cards in those regions. So, um this is
  1115. 41:03something that that the companies can
  1116. 41:04set up now in their policy.
  1117. 41:07And then um so, I'm breezing through
  1118. 41:09these a little bit, but I'll I'll I'll
  1119. 41:10jump through mileage offset as well.
  1120. 41:12This has been a big ask um across the
  1121. 41:14globe, too, where um
  1122. 41:16you know, a lot of different uh tax laws
  1123. 41:19and just
  1124. 41:20regulations require um
  1125. 41:22you know, commute
  1126. 41:25uh distance to not be counted in in
  1127. 41:27mileage, basically. So, we've built this
  1128. 41:29feature that that that basically allows
  1129. 41:32um the user to deduct uh their commute
  1130. 41:36from the actual mileage claim um which
  1131. 41:38which allows you to be more uh compliant
  1132. 41:41in in different regions.
  1133. 41:44And then I'll jump into per diems next.
  1134. 41:46Um
  1135. 41:47you know, each country, especially in
  1136. 41:48Europe, has all sorts of different
  1137. 41:50requirements around around per diem and
  1138. 41:52we um
  1139. 41:53we
  1140. 41:54launched Austrian per diems recently and
  1141. 41:56um Polish per diems. So,
  1142. 41:59in Poland, there's a lot of regulation
  1143. 42:00around um bringing in their central bank
  1144. 42:03exchange rates as well as different uh
  1145. 42:06rolling clock rules that you have to
  1146. 42:08apply when submitting. Um so, we just
  1147. 42:10launched this recently as well so that
  1148. 42:13um you know, anyone claiming per diem in
  1149. 42:15Poland is is is fully compliant over
  1150. 42:17there.
  1151. 42:20And then I'll I'll I'll go through
  1152. 42:21flexible reimbursements as well before
  1153. 42:23passing it off to to Nadav. Um
  1154. 42:25but you know, now that we've kind of
  1155. 42:28built this product out um
  1156. 42:31admins can reimburse employees directly
  1157. 42:34uh
  1158. 42:34across EUR and GBP currencies from those
  1159. 42:36different bank accounts. Um so that
  1160. 42:38that's been a big unlock for for a lot
  1161. 42:40of our European clients.
  1162. 42:43And I'll pass it off to Nadav.
  1163. 42:46Thank you, Thomas. I'm Nadav from uh
  1164. 42:49Navan's commerce invoicing team.
  1165. 42:52Um and as you may have noticed, we are
  1166. 42:54currently in a global shift where a tax
  1167. 42:56authorities are moving from checking
  1168. 42:58paper to controlling data.
  1169. 43:00By 2027, most EU countries will mandate
  1170. 43:03structured invoicing.
  1171. 43:05This means that if your invoice in E in
  1172. 43:08Europe is not government mandated
  1173. 43:10digital file,
  1174. 43:11it's legally void.
  1175. 43:13And Navan, we just we don't just track
  1176. 43:15these mandates. We're building the
  1177. 43:17products to help you ensure your travel
  1178. 43:19program remains remains audit ready.
  1179. 43:22While most travel management companies
  1180. 43:24use a model where they invoice you
  1181. 43:25directly for travel spend,
  1182. 43:27uh it makes the TMC the seller in the
  1183. 43:30eyes of the tax office. It breaks the
  1184. 43:33legal link between you and the actual
  1185. 43:34supplier, which is the hotel or the
  1186. 43:36airline,
  1187. 43:37which makes it impossible for you to
  1188. 43:39reclaim VAT
  1189. 43:40in Europe.
  1190. 43:41Navan is different. We ensure the
  1191. 43:43invoicing remains directly between you
  1192. 43:45and the supplier,
  1193. 43:47which is the only way to protect your
  1194. 43:49full right for that refund.
  1195. 43:52Our three-layer strategic approach for
  1196. 43:54invoicing is that we always try to
  1197. 43:57invoice on behalf of the supplier.
  1198. 43:59So, for major partners like Lufthansa
  1199. 44:01Group and Deutsche Bahn, we issue legal
  1200. 44:04tax invoices directly in their name.
  1201. 44:06This means that you are able to get your
  1202. 44:08invoice directly in Navan within the
  1203. 44:10product without any complications.
  1204. 44:13We also have technical readiness to
  1205. 44:14issue these compliant invoices anywhere
  1206. 44:17in Europe as long as we get the
  1207. 44:19commercial
  1208. 44:20approval from the suppliers themselves.
  1209. 44:24When we don't have that approval from
  1210. 44:25the supplier,
  1211. 44:26we do automated retrieval, which means
  1212. 44:29we try to get the invoices directly from
  1213. 44:32the systems in Europe, so you don't have
  1214. 44:34to chase them.
  1215. 44:35And when that is not possible, we will
  1216. 44:37generate a receipt with an XML. This
  1217. 44:40will be the fallback for any transaction
  1218. 44:42in Navan in Europe.
  1219. 44:44So, this ensures that regardless of the
  1220. 44:46supplier, you always have a digital
  1221. 44:48audit file required by the new EU
  1222. 44:51mandates.
  1223. 44:52As the mandates go into place, we are
  1224. 44:54tracking them very closely and we're
  1225. 44:55making sure that Navan and you are ready
  1226. 44:58well ahead of the time the mandate goes
  1227. 45:00into practice.
  1228. 45:02That was a little bit about invoicing,
  1229. 45:04and now we're handing back to Josh.
  1230. 45:09Great. Thanks, Inder and team. Uh so, if
  1231. 45:12everybody wants to join me again, uh
  1232. 45:13we've got about 14 minutes uh for some
  1233. 45:15Q&A. Uh and thank you to everybody who
  1234. 45:18submitted questions throughout, uh and
  1235. 45:20to our speakers who've answered quite a
  1236. 45:21number of the questions live, and happy
  1237. 45:23to address a few more of them here.
  1238. 45:25Uh so, one question I saw come in, uh
  1239. 45:28Thomas, I think this is for you, uh is
  1240. 45:30what's the difference between
  1241. 45:31rules-based coding and AI coding?
  1242. 45:35Oh, yeah. Um it's a good question. So, I
  1243. 45:37mean, you know,
  1244. 45:39on in in I I I kind of spoke to this a
  1245. 45:41little bit during the beginning of what
  1246. 45:42I was talking about the the coding
  1247. 45:43agent, which is, you know, a lot of
  1248. 45:45pre- the pre-AI world allows you to say,
  1249. 45:48"Look, you know, based on MCC code X,
  1250. 45:50code to expense type Y or merchant X
  1251. 45:53expense type Y." Um and I think there's
  1252. 45:55still for sure a place for that. You
  1253. 45:57know, there's certain just accounting
  1254. 45:58rules that you want to basically just be
  1255. 46:01perfect and like never fail and always
  1256. 46:04be the exact same thing across the
  1257. 46:05board, but especially with merchant
  1258. 46:07data, there's a lot more nuance
  1259. 46:08involved. I mean, a lot of people been
  1260. 46:09talking about Amazon, for example, you
  1261. 46:11know, you can't really create a merchant
  1262. 46:12rule without Amazon cuz you can buy
  1263. 46:14anything on Amazon. Um I mean, even Home
  1264. 46:16Depot, maybe you stop by Home Depot and
  1265. 46:17you get a snack instead of buying tools.
  1266. 46:20You know, there's a lot of nuance there
  1267. 46:22and I think um where AI can really help
  1268. 46:26is it it it can reason like a human
  1269. 46:28being. Um you know, and and it can look
  1270. 46:31across it can take the time to kind of
  1271. 46:33look across all of the transaction data
  1272. 46:34and the receipt data to make a decision.
  1273. 46:37Um so you don't really have to
  1274. 46:39set these super rigid rules. Um that's
  1275. 46:41that's kind of the goal. Again, I I I I
  1276. 46:43do think there is a
  1277. 46:44world where both exist,
  1278. 46:46uh but but I think AI can generally make
  1279. 46:49much smarter decisions.
  1280. 46:51Great. Uh another one came in. Pauline,
  1281. 46:54I believe this one's more for you, but
  1282. 46:56how can we audit the reasoning for why
  1283. 46:58the agent suggested an action related to
  1284. 47:01uh some of the admin AI work?
  1285. 47:04Yeah, so a couple things. Um within the
  1286. 47:07suggested action,
  1287. 47:09um we will show
  1288. 47:11uh a list of kind of the rationale and
  1289. 47:13the thinking that went behind a
  1290. 47:15suggestion. So in that way, you kind of
  1291. 47:17understand why an the agent is
  1292. 47:20suggesting the action that it's
  1293. 47:22suggesting. Um the second part of that
  1294. 47:24is being able to kind of correct and
  1295. 47:28instruct the agent to um apply certain
  1296. 47:31exceptions or um change the logic for
  1297. 47:34certain merchants, and that's also
  1298. 47:37something that you can do within that
  1299. 47:38flow.
  1300. 47:39Um so, yeah.
  1301. 47:43All right, great. Uh just had another
  1302. 47:45one come in. Uh Thomas, probably for for
  1303. 47:48you, but it goes to whoever wants to
  1304. 47:49take. Um are you putting in solutions to
  1305. 47:51help medical device companies track
  1306. 47:52sunshine reporting requirements and NPI
  1307. 47:55numbers of doctors?
  1308. 47:58Oh yeah, that that's an interesting
  1309. 47:59question. Uh
  1310. 48:00It's a great one cuz it's it's it is top
  1311. 48:02of mind for us.
  1312. 48:04You know, I don't have
  1313. 48:06a strong timeline yet, but I think we're
  1314. 48:09we we're hoping this year to definitely
  1315. 48:13have the ability to comply with and
  1316. 48:14support Sunshine Act
  1317. 48:16companies so that you can yeah, you can
  1318. 48:17pull in NPI numbers and things like that
  1319. 48:19for for pharma companies.
  1320. 48:23All right, great.
  1321. 48:24One probably for Amanda. If I have
  1322. 48:27multiple expenses I want to create in
  1323. 48:29the expense chat,
  1324. 48:31do I need to upload multiple images of
  1325. 48:33individual receipts?
  1326. 48:35So, great that you asked that question,
  1327. 48:37Josh, because Expense Chat actually, on
  1328. 48:39top of being able to support different
  1329. 48:41expense types in one conversation, also
  1330. 48:43allows you to send one photo in of
  1331. 48:45multiple receipts, and our agents will
  1332. 48:48parse and split into multiple expenses.
  1333. 48:51So, for example, if I have five receipts
  1334. 48:53in one image, I have five transactions
  1335. 48:55that could get created, all with the
  1336. 48:57respective snapshot of the receipt and
  1337. 49:00that data captured at the transaction
  1338. 49:02level. So,
  1339. 49:03yeah.
  1340. 49:05All right, great. I know we got a few
  1341. 49:07slacks about or sorry, not slacks,
  1342. 49:09slacks on the brain. A few messages on
  1343. 49:11here about the capabilities of approval
  1344. 49:14in Slack going to other systems like
  1345. 49:18Microsoft Teams. So, Pauline, if you
  1346. 49:20want to speak to that.
  1347. 49:21Yes.
  1348. 49:22So, we're getting huge demand for
  1349. 49:24Microsoft Teams and it's on our team's
  1350. 49:26road map.
  1351. 49:27And so, after we roll out Slack and
  1352. 49:32you know, address a lot of the most
  1353. 49:33common workflows for managers,
  1354. 49:35approvers, and users, we're planning to
  1355. 49:38extend that capability on the Teams.
  1356. 49:42All right, great.
  1357. 49:43One other one here. Is there an option
  1358. 49:45to consider a user on a trip from
  1359. 49:48entering mileage and their calendar
  1360. 49:50integration? To my knowledge, it's
  1361. 49:52considered a trip in a flight, hotel, or
  1362. 49:55rental is booked. So, numerous expenses
  1363. 49:57are considered not on trip when they did
  1364. 50:00travel.
  1365. 50:01Yeah, I'll take that one.
  1366. 50:03Uh it's one of my favorite features. The
  1367. 50:04reason I love this feature so much is
  1368. 50:06because of its name. We called it but
  1369. 50:08I'm on a trip. Uh so, users actually
  1370. 50:11have the ability
  1371. 50:13uh to say if they're not on a trip to
  1372. 50:15say yes, I am actually on a trip and you
  1373. 50:17know, you can set it up in policy where
  1374. 50:19it goes over to the manager approval to
  1375. 50:21say yes, you know, I approve this user
  1376. 50:22is actually on a trip even though they
  1377. 50:24don't have a hotel or a flight booked.
  1378. 50:26They took their car, you know, they're
  1379. 50:27expensing.
  1380. 50:29Um and then you can consider all of
  1381. 50:30those expenses as part of a specific
  1382. 50:32trip.
  1383. 50:35Pretty great. Uh one more back to I
  1384. 50:38think back to you, Pauline, on Slack. I-
  1385. 50:39is the Slack integration mainly used for
  1386. 50:41communicating to users about info needed
  1387. 50:43or flagged transactions?
  1388. 50:46Um all of the above. So, basically, what
  1389. 50:50happens is we will for managers and
  1390. 50:52approvers, we send them a notification
  1391. 50:55for every expense that's flagged that
  1392. 50:58has all the receipt um participants, all
  1393. 51:01that information provided by the user
  1394. 51:02and is ready for that stamp of approval.
  1395. 51:05Um and so, within that transaction, the
  1396. 51:09approver can either approve, reject, or
  1397. 51:12request more information. So, if they
  1398. 51:15wanted to request more information, they
  1399. 51:16can do that on Slack. They can just
  1400. 51:17simply reply to that transaction message
  1401. 51:20um and that will log that response and
  1402. 51:23then also reflect it on on Navan.
  1403. 51:27All right, great. Uh and one from the
  1404. 51:30receipt inbox side, Shruti. Um
  1405. 51:33how are you addressing data privacy when
  1406. 51:35it comes to adding receipt photos or
  1407. 51:37photos from someone's library?
  1408. 51:40Oh, yeah, for sure. I think privacy is
  1409. 51:42definitely, you know, not an
  1410. 51:44afterthought for us. We definitely take
  1411. 51:46that into when we you know build up the
  1412. 51:49architecture. So you know we make sure
  1413. 51:51like you know we are going by the
  1414. 51:53compliance taking users consent user has
  1415. 51:55verified that personal email before they
  1416. 51:57send us all the data and that's how we
  1417. 52:00use AI to like match the receipt or the
  1418. 52:03photos that they are sending in in a
  1419. 52:04very
  1420. 52:06simpler safe way.
  1421. 52:09Got you. Thanks.
  1422. 52:11And then one for I think this is for you
  1423. 52:14Nav Nav out there but so our current
  1424. 52:16agency sends us one consolidated monthly
  1425. 52:19invoice for all of our travel spend.
  1426. 52:22So why does Nav out provide individual
  1427. 52:24supplier invoices instead?
  1428. 52:26Yeah, it's one of those classic
  1429. 52:28trade-offs you have between the build
  1430. 52:31back models and between the Nav out
  1431. 52:33agent model. So when an agency sends you
  1432. 52:36one big invoice you they legally become
  1433. 52:38the seller and you're not able to
  1434. 52:40reclaim VAT for that invoice. And Nav
  1435. 52:43out we provide the original supplier
  1436. 52:44invoice when we can
  1437. 52:46so you can always have the invoice for
  1438. 52:48VAT reclamation. That being said there
  1439. 52:50is definitely things to that can be used
  1440. 52:52for the consolidated receipt definitely
  1441. 52:55in terms of reconciliation which is
  1442. 52:56something that we're looking also to add
  1443. 52:58to our product within the next few
  1444. 52:59months.
  1445. 53:02Got you. That's great.
  1446. 53:04One more I saw come through actually we
  1447. 53:06have time for a few more.
  1448. 53:08Once the expense is approved by the
  1449. 53:10manager and maybe later it's realized
  1450. 53:12that is wrongly approved can the manager
  1451. 53:15recall the expense or reject it again so
  1452. 53:18kind of going back at it as a as a
  1453. 53:19postmortem.
  1454. 53:21Yeah, I mean
  1455. 53:22managers do have the ability to go back
  1456. 53:24and do that. I mean I
  1457. 53:26if I remember correctly there are some
  1458. 53:27rules around once a reimbursement has
  1459. 53:29already fully occurred
  1460. 53:31that you know we we there some locking
  1461. 53:34that happens where a manager can't go
  1462. 53:35back and kind of like re
  1463. 53:38re claw back the reimbursement but
  1464. 53:41usually you know if they're able to do
  1465. 53:43it on on a
  1466. 53:45pretty short timeline, you know, they
  1467. 53:47can they can action kind of reject the
  1468. 53:49transaction after the fact.
  1469. 53:53Got you. Great.
  1470. 53:54All right, let's see what other ones are
  1471. 53:55flying in here.
  1472. 53:58I think this one's for you Pauline. Can
  1473. 54:00the agent use our policy documents to
  1474. 54:03make decisions?
  1475. 54:06Yes, and I'm assuming by policy document
  1476. 54:09you're referring to the policy that you
  1477. 54:11have set up within Navan.
  1478. 54:14In which case yes, that is one of the
  1479. 54:15inputs that the agent will be looking
  1480. 54:17at. A few other inputs that we consider
  1481. 54:20is you know the users the employees
  1482. 54:22spend history, like how often are they
  1483. 54:25going over the spend limit, how
  1484. 54:27compliant are they, all of that factor
  1485. 54:29into this decision. We also take a look
  1486. 54:31at
  1487. 54:32you know the admins specific like
  1488. 54:35threshold and
  1489. 54:37and and activity. So as an admin, are
  1490. 54:39you more likely to approve things that
  1491. 54:41are just 5% over threshold, more likely
  1492. 54:44to reject if it's over 20%? Each each of
  1493. 54:47those kind of
  1494. 54:48buckets will play into the final
  1495. 54:50suggestion that we that we make.
  1496. 54:55Got you.
  1497. 54:56Awesome.
  1498. 54:57I think one question from from David
  1499. 54:59down here that that that I thought was
  1500. 55:00was interesting and I I could take an
  1501. 55:01initial shot at it and and and Pauline
  1502. 55:03you can follow up.
  1503. 55:05David said what's the difference between
  1504. 55:06my company's T&E policy and what you
  1505. 55:08needed for the Navan T&E policy?
  1506. 55:11You know, I think
  1507. 55:12the thinking in here is there's a lot of
  1508. 55:14rules that you can code into Navan
  1509. 55:16directly for sure that that try to
  1510. 55:18reflect your policy, but what our agents
  1511. 55:20trying to do is actually look at your
  1512. 55:22policy documentation and take into
  1513. 55:24account more nuanced rules or policies
  1514. 55:27or things that you can't just directly
  1515. 55:29code into software. So we'll kind of
  1516. 55:31look at the while the agent take into
  1517. 55:33account the document itself when making
  1518. 55:36suggestions.
  1519. 55:40Nice. Any others that you guys saw that
  1520. 55:42you wanted to address off the bat?
  1521. 55:49Um the this one from Bonnie on the Slack
  1522. 55:53integration. I think
  1523. 55:54Bonnie had something that that yeah that
  1524. 55:56that we're that we're working on right
  1525. 55:57now um and that that we're hoping to
  1526. 55:59ship very soon.
  1527. 56:00But it's not available today at least
  1528. 56:02for
  1529. 56:04what we're doing.
  1530. 56:04>> not yet live. Um it's in beta, Bonnie.
  1531. 56:06So if you want to
  1532. 56:09uh have your org kind of enrolled, feel
  1533. 56:11free to reach out to your AM and we're
  1534. 56:13we'll be happy to to add you guys to the
  1535. 56:15beta.
  1536. 56:16Mhm. Cool. All right, I I think we've
  1537. 56:18got time for maybe one more here. Uh
  1538. 56:21Aaron said if if an expense is itemized
  1539. 56:23for personal expenses, is there an
  1540. 56:25option in the works to send to the
  1541. 56:27manager for approval rather than
  1542. 56:29requiring the admin to approve?
  1543. 56:33Yeah, that that's an interesting
  1544. 56:34question. I guess um you know, the the
  1545. 56:36approval
  1546. 56:38um
  1547. 56:39flows are kind of dependent on what on
  1548. 56:40on what you set in policy. So if you
  1549. 56:42know, if um if a transaction's flagged
  1550. 56:45and the manager set as the approver, you
  1551. 56:46know, it'll go to them. And if if it's
  1552. 56:48for an admin, it'll go to the admin. So
  1553. 56:49it it it should really depend on who the
  1554. 56:51approver was, you know, at at the time
  1555. 56:53that the transaction occurred.
  1556. 56:57Great. Uh so thanks for all the all the
  1557. 56:59questions. I think last thing just for
  1558. 57:00you all just to to wrap us up here. So I
  1559. 57:03guess how are you thinking about like
  1560. 57:04everything we covered today? How is it
  1561. 57:06really enhanced by Navan's travel
  1562. 57:08infrastructure uh and data set?
  1563. 57:11Yeah,
  1564. 57:12I think that's the magic of you know,
  1565. 57:15what we have because
  1566. 57:17at the end of the day, if you think
  1567. 57:18about expensing, most of the expensing
  1568. 57:20that people do, 90% of the expense that
  1569. 57:22people do, they do while they travel.
  1570. 57:24Uh so the travel really brings a lot of
  1571. 57:27context into the expense itself.
  1572. 57:30Um at the end of the day, when you're
  1573. 57:31submitting an expense, the most
  1574. 57:33important thing that admins are trying
  1575. 57:35to get answered is why did you submit
  1576. 57:38this expense?
  1577. 57:40Uh, and we're asking that why from a lot
  1578. 57:42of different reasons, you know, what
  1579. 57:43client does it belong to, how do I bill
  1580. 57:45it to, what expense type is it? Uh, can
  1581. 57:47you give me a receipt? And it's all
  1582. 57:49about that story. And travel really adds
  1583. 57:52a lot of context cuz it already knows,
  1584. 57:54you know, why you're going to where
  1585. 57:56you're going and why you're flying and
  1586. 57:57the fact that you're on a trip. Um, and
  1587. 57:59it really rounds up the whole expense
  1588. 58:01story.
  1589. 58:04Great. So, with that, I think we'll
  1590. 58:06we'll wrap. So, really appreciate
  1591. 58:08everybody joining today. Loved all the
  1592. 58:10questions and appreciate our our team
  1593. 58:12for showing up. Uh, if you're a
  1594. 58:14customer, a few things coming up for
  1595. 58:15you. So, next month we have an ERP
  1596. 58:17specific webinar we're going to host.
  1597. 58:19So, we'll send out some invites to that.
  1598. 58:21Um, we're also have our monthly expense
  1599. 58:24admin office hours next month as well.
  1600. 58:26Uh, where we'll kind of dive into some
  1601. 58:28of the recent releases, things upcoming,
  1602. 58:30and answer some of your tactical
  1603. 58:31questions as well. Uh, there's going to
  1604. 58:34be a survey that I'll show right as I
  1605. 58:36end this webinar, but again, appreciate
  1606. 58:38everybody, uh, and have a great rest of
  1607. 58:41your day.
  1608. 58:43Thanks, Dean.
  1609. 58:43>> Awesome.
  1610. 58:44Thanks, y'all.

About this transcript

This page contains the full transcript of Navan Expense: Spring 2026 Product Release On-Demand Webinar by Navan, generated from the public captions YouTube serves with the video. The transcript has 10,253 words across 1,610 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.