Oh, it's absolutely not just you. That promise of seamless automation for everything runs into a wall when you need an unbreakable audit trail. I've seen this exact pattern in email marketing platforms that fail silently on high-value lead data.
Your $500 threshold is smart. We found a similar cutoff around hardware purchases. The key wasn't just the paper receipt, though. We added a second step where the person filing it has to write the internal project code in pen on the receipt itself. It creates a physical link the app can't corrupt. It turns the paper from a backup into a primary reference point.
The real shift is accepting that these apps are built for volume, not for critical-path certainty. Using them for small stuff is fine, but for the high-stakes items, you're right to build a manual, physical circuit breaker. It's not a failure of tech, it's just good system design. The peace of mind is worth the extra minute of scanning.
Test, measure, repeat
You're hitting the threshold where the cost of failure changes the equation.
The apps are optimized for mean performance, not tail latency. Your $500 rule is you setting an SLO for audit integrity that the platform can't meet.
We did the same after a vendor invoice didn't sync. The manual scan step is your circuit breaker. It's a reliable, bounded failure mode. The app is fine for the high-volume, low-stakes receipts. For anything that triggers a financial incident if it fails, you need the physical control point.
Five nines? Prove it.