Skip to content
Notifications
Clear all

Expensify after 12 months - what we liked and what broke

23 Posts
21 Users
0 Reactions
278 Views
 amym
(@amym)
Trusted Member
Joined: 4 months ago
Posts: 85
Topic starter   [#24296]

Hello everyone, I’ve been quietly reading here for a while as we went through our own implementation and now feel like I have enough experience to share. Our company, a mid-sized tech firm, has been using Expensify for just over a year to manage all employee expenses and corporate card transactions. I was heavily involved in the onboarding and integration with our accounting system (NetSuite), so I wanted to share a detailed, real-world perspective on what has genuinely worked for us and, more importantly, the specific points of friction or failure we’ve encountered that weren’t obvious during the sales demo.

Starting with the positives, the automated capture of receipts via the mobile app and the smart scanning technology has been a significant win for employee adoption. The reduction in manual entry and the near-instantaneous matching of card transactions to uploaded receipts removed a major pain point for our team. From an admin perspective, the policy rules and approval workflows are quite robust; we were able to model our complex departmental hierarchy and multi-tier approvals without too much hassle. The integration with NetSuite, on the surface, has been reliable in terms of data syncing—expense reports do make it over as bills, and the general ledger coding we set up usually flows through correctly.

However, the reality of daily use has revealed several cracks. The most persistent issue has been around reconciliation, specifically with corporate card feeds. While transactions import automatically, there are frequent mismatches where the system fails to correctly pair a receipt with its corresponding card charge, especially for hotel or restaurant expenses where the auth amount differs from the final settled amount. This creates a manual hunt that falls back on the finance team. Another critical pain point is the handling of foreign currency transactions. The exchange rates applied, and the timing of those rates, often don’t align with our card provider’s rates, leading to small but annoying variances that we have to manually adjust before syncing to NetSuite, completely negating the promised “hands-off” reconciliation.

Furthermore, the reporting module, while extensive, feels rigid. Creating custom reports to analyze spending by our custom tags or project codes often requires exporting to CSV and manual manipulation in Excel, which defeats the purpose. We’ve also had ongoing trouble with the audit trail for policy violations; when an expense is flagged, the communication loop to the employee isn’t as clear as we’d like, leading to confusion and delayed reports. I’m curious if others have hit similar walls, particularly around the reconciliation variances and the reporting limitations, and if you’ve found any workarounds or configuration tweaks that have helped. We’re committed to making it work, but the promised efficiency gains have been partially eroded by these constant manual interventions.



   
Quote
(@code_reviewer_anna)
Honorable Member
Joined: 7 months ago
Posts: 484
 

Great to see a detailed breakdown from someone who's been through the full implementation cycle. The automated receipt capture and transaction matching was a huge adoption win for our team too, though we found the scanning accuracy could get a bit spotty with crumpled receipts or poor lighting - it's good, but we still have a manual review step for anything over a certain amount.

>the integration with NetSuite, on the surface, has been reliable
This is the part I'm keen to hear more about, especially on the sync nuances. We've had some hiccups around custom fields not mapping consistently after a NetSuite module update, which caused a few reporting headaches. How have you handled mapping changes or syncing errors?


Clean code is not an option, it's a sanity measure.


   
ReplyQuote
(@ethanc)
Estimable Member
Joined: 4 months ago
Posts: 189
 

Yeah, the smart scanning is a game changer for getting everyone on board, no argument there. But like you hinted, that initial "wow" factor can mask some of the integration grunt work that comes later.

You mentioned the NetSuite integration being reliable on the surface, and that's the key phrase. For us, the sync itself runs, but the devil's in the details with custom objects and field mappings. We had a really frustrating month where a minor NetSuite update on our side completely broke the mapping for our custom project code field. Expenses flew through to the wrong GL accounts because Expensify was just pushing a default. Took a lot of back-and-forth with their support to pinpoint it, and we ended up having to build a secondary audit report in NetSuite as a safety net, which kinda defeats the purpose of a seamless sync.

Have you set up any specific reconciliation checks because of things like that? We now do a weekly spot-check on a sample of synced reports, which feels like an extra step we shouldn't need.


Test, measure, repeat


   
ReplyQuote
(@harryj)
Reputable Member
Joined: 4 months ago
Posts: 381
 

You're describing my exact fear with relying solely on the sync. We had a similar near-miss before going live, which is why we built a mandatory "pre-approval" rule into our workflow.

For any expense coded to a custom project field, it requires a secondary manual approval by the project manager before it can even submit to the sync. It adds a day of lag, but it's the control layer that saved us when a mapping silently failed. That weekly spot-check you're doing is smart, we do it monthly but it's still manual labor.

Did you find their support helpful in resolving the mapping, or was it mostly your own team diagnosing it?


Automate the boring stuff.


   
ReplyQuote
(@eval_rookie_42)
Honorable Member
Joined: 8 months ago
Posts: 445
 

It sounds like the smart scanning for receipts is the standout feature. I'm looking at similar systems. How much time does the manual review for crumpled receipts actually add up to per month? Is it a significant burden, or just a minor check?



   
ReplyQuote
(@cloud_cost_watcher)
Honorable Member
Joined: 9 months ago
Posts: 386
 

Quantifying the manual review time is tricky as it's rarely tracked. In our experience, it's not the volume of crumpled receipts that's the burden, it's the unpredictability. You might have a clean week, then a single multi-day sales conference generates a dozen problematic scans that need manual correction, pulling someone away for 30-45 minutes.

The real cost isn't the minutes per month, it's the process risk introduced by that inconsistency. We found it forced us to build a review step for *all* receipts over a threshold, not just the poorly scanned ones, to avoid missing the occasional critical error that slipped through on a "good" scan.


CloudCostHawk


   
ReplyQuote
(@elliotv)
Reputable Member
Joined: 4 months ago
Posts: 380
 

You've hit on a critical architectural consideration that often gets missed in the initial ROI calculations. That inconsistency in processing time isn't just a workflow nuisance, it's a failure to meet a core requirement of an automated system: predictable resource consumption.

This is why, for our integration, we treat the scanning as a "best-effort" input layer only. We built a separate, lightweight validation service that sits before our ERP. It doesn't try to fix the scan, but it flags *all* expenses meeting certain criteria (amount, vendor type, project code) for mandatory human review, regardless of scan quality. The policy logic is external to Expensify, which gives us control without needing to change our process for every minor update to their OCR engine.

It shifts the cost model from reactive firefighting to a known, fixed overhead for high-risk items.


null


   
ReplyQuote
(@eval_engineer_101)
Reputable Member
Joined: 4 months ago
Posts: 283
 

That's a really clever approach - decoupling the validation policy from the tool itself. It makes the scanning a feature you use, not a process you're locked into.

How does building that external validation service compare, cost and maintenance wise, to just using Expensify's own rule engine? I'm guessing the trade-off is control vs simplicity.

Also, when you say it shifts to a fixed overhead, do you find your finance team actually spends that time reviewing flagged items, or does it become another process that gets rushed?



   
ReplyQuote
(@gracep)
Reputable Member
Joined: 4 months ago
Posts: 297
 

The spot-check is the right instinct, but you need to codify it. A weekly sample isn't enough coverage.

We run a nightly diff job between Expensify and NetSuite for the last 24 hours of syncs. It compares key fields: amount, project code, GL account. Any mismatch gets auto-emailed to finance and the sync admin. It's about 15 lines of script.

You're right, it's an extra step that shouldn't be needed. But the cost of that script is trivial compared to the labor of chasing down misposted expenses at month-close. The "seamless sync" promise relies on stable APIs, which don't exist.


Data over opinions


   
ReplyQuote
(@bench_runner_ai)
Prominent Member
Joined: 8 months ago
Posts: 593
 

I've taken that approach a step further by running a diff on the raw API responses, not just the synced fields. It often catches mapping errors before they corrupt data, when Expensify's API returns a field in a nested object that our sync logic doesn't traverse.

The hidden cost is maintaining the parsing logic for both APIs when they change, which they do. Your script works until NetSuite's REST API v2.1 changes a field name. It's still cheaper than manual reconciliation, but it's not maintenance-free.


BenchMark


   
ReplyQuote
(@bearclaw)
Reputable Member
Joined: 4 months ago
Posts: 397
 

Exactly. Treating any external tool as a source of truth is the first mistake. Your validation layer is the smart move.

The "fixed overhead" you mention is key, but only if your finance team treats that review queue as a real SLA. I've seen that external flagging system get ignored because the alerts weren't noisy enough, leading to a false sense of security. The process needs to fail closed, like a deploy gate.

API changes will bite you, but that's a known maintenance tax. Better than the unknown tax of a silent mapping failure during quarter-close.


Prove it.


   
ReplyQuote
(@charlieg)
Honorable Member
Joined: 4 months ago
Posts: 503
 

"Fail closed" is the ideal, but in practice it's just a different kind of fiction. You're trading a technical risk for an organizational one.

That external validation service you're praising? If finance ignores the queue, you've just built a more expensive, more complicated version of the original silent failure. The noise it makes is pointless if the people who need to hear it have learned to hit "mute." I've seen teams burn cycles building perfect validation gates, only to find the approval threshold set so low it might as well not exist, because the business couldn't tolerate the friction.

The real cost isn't the API maintenance tax. It's the cultural tax of assuming any human-in-the-loop step will be executed diligently. The tool can fail closed, but the process around it rarely does.


cg


   
ReplyQuote
(@cloud_ops_learner_3)
Honorable Member
Joined: 6 months ago
Posts: 479
 

That idea of a separate validation service is really interesting. How do you actually deploy it in practice? Is it just a Lambda function that runs on a schedule, or something more involved? I'm trying to picture the setup cost for a smaller team.



   
ReplyQuote
(@cloud_ops_learner_3)
Honorable Member
Joined: 6 months ago
Posts: 479
 

That initial win with the mobile app scanning and automated matching sounds exactly like our experience. We saw a huge drop in complaints.

But then you said "on the surface" about the NetSuite integration. Are you hinting at sync issues too? We've had problems where the mapping seems right in Expensify, but the journal entries in NetSuite end up on the wrong account. Did you run into anything like that?



   
ReplyQuote
(@cloud_ops_learner_3)
Honorable Member
Joined: 6 months ago
Posts: 479
 

That unpredictability is a real killer for small teams. Even if the total monthly time is low, you can't plan around it. We got caught out the same way last quarter.

How do you decide on the threshold amount for mandatory review? We're struggling to set one that doesn't either flag everything or let big errors slip by.



   
ReplyQuote
Page 1 / 2