Making automatic merging even better!

Ted Harris
Ted Harris Expensify Success Coach - Admin, Expensify Team, Expensify Student Ambassador Posts: 359 Expensify Team

We know that one of the biggest annoyances when it comes to reporting expenses paid for by a credit card is making sure they’re merged with the line-item receipt. We think we’ve long been the best solution for this, but there are always improvements to be made. In January we announced that we’d begin automatically merging more transactions after they’d been submitted - there was no reason not to merge when they were simply awaiting an Approver’s eye.

Today we can happily announce that even after exporting to a CSV file, we’ll also automatically merge expenses on reports of any age, in any state besides Reimbursed.

What about after I export to my accounting integration?

It’s a great question! For the most part, in order to let our accounting integrations do their thing, we have to limit the merging after export to just CSV’s. This is simply because our live connections are already doing some intelligent stuff behind the scenes.

For instance, when a report is exported to QuickBooks online with both Reimbursable and Non-reimbursable transactions and you’re using Expensify ACH to reimburse your employees, those reimbursable transactions are already set in stone to be reimbursed and marked as paid in QuickBooks - if we were to completely change the reimbursable total of the whole report by automatically merging another expense in, it would cause more headaches - and we’re all about reducing those!

Is this change retroactive?

It’s not going to affect any transactions already in Expensify. If you currently have transactions on a report created more than 90 days ago, or that’s been exported to a CSV - these are still following the old automatic merge rules, and would need to be manually merged.