Receipts I keep losing between the purchase and the expense report
An honest look at the Friday-night ritual of finding last month's coffee shop receipts, plus why retrieval fails harder than saving ever did.

You save a receipt three different ways and still spend an hour or more on the last Friday of the month digging for it. The receipt isn't lost, it's scattered across Telegram saved messages, the Lyft email you forwarded yourself, an Apple Notes folder, and a screenshots dump. Retrieval, not storage, is the actual job.
It's 4:47pm on the last Friday of May. The Concur tab is open in one window, the accountable plan spreadsheet your manager prefers is in another, and the deadline your AP team set is end-of-day. You search Gmail for "receipt" and get 3,400 results, most of them Trader Joe's loyalty emails and Costco coupons. You switch to Telegram, scroll the messages you forwarded to yourself, and there it is: the PDF from the WeWork in Austin you billed against the client visit. Except the dinner with the prospect is missing. You took a photo of the paper check. The photo is somewhere in a camera roll that has 14,832 images, sorted by date, untagged, with no idea which Tuesday in April you actually went.
What actually breaks on receipt night
The breakage isn't laziness. You saved every receipt. You forwarded the Lyft email to yourself the second you stepped out of the car. You photographed the dinner check on the way to your hotel. You screenshotted the Amazon Business order confirmation. You even messaged the WeWork PDF into Telegram with a one-word caption: "austin."
The breakage is that each item went to a different surface based on what was easiest in the moment. The Lyft email went to Gmail because Lyft already emails you. The dinner check went to your camera roll because your hand was the closest scanner. The Amazon order went to a screenshot because the confirmation page was right there. The WeWork PDF went to Telegram because it was on your laptop and Telegram was open. Six receipts, four surfaces. Now, twenty-six days later, you're the one who has to reconstruct which surface holds what.
Your camera roll alone is a known disaster zone. If you've ever lost a photo of a parking ticket inside a screenshot folder of five thousand photos, you already know the shape of the problem: capture was free, retrieval is a forensic exercise. The last-Friday archaeology can easily eat an hour or more, all unbillable.
Why "I'll deal with it later" never works for receipts
The standard answer is to use Expensify or Fyle or Ramp and let the corporate card auto-categorize. That works beautifully if your employer pays for it and if every transaction goes through that one card. In practice, the dinner where the card reader was down went on your personal Amex. The flight you booked through your spouse's Chase Sapphire because the points were better went through Gmail. The taxi in a small town that took cash went on a paper receipt you photographed at the next stoplight.
Accountable plan reimbursements under the IRS rules require contemporaneous records with date, amount, business purpose, and vendor. The IRS doesn't care whether you used SAP Concur or a shoebox, but your AP team cares deeply about format. So every month you translate four save surfaces into one spreadsheet, and the translation is the bottleneck. An hour or more per month, hours across the year, all unpaid.
The split brain: capture in seconds, recall in minutes
The mental model most of us inherited from filing cabinets is "save it in the right folder and you'll find it." That model breaks the moment receipts arrive on six different rails. Telegram is good for things you want to send yourself in two taps. Gmail is good for things vendors already email you. Camera roll is good for things in the physical world. None of them are good at the question you actually ask later: "what did I spend on the Austin trip in April?"
That question is semantic, not structural. It's not "show me file X in folder Y." It's "show me everything related to a specific trip on a specific week, regardless of where I stuffed it." The shift from keyword search to meaning search is what makes the difference. If you've ever tried to search notes by meaning instead of keyword, you know the gap between "find the file named austin.pdf" and "find anything tagged or implied or hinted about Austin." Receipts live in that gap.
This is what people mean by the hard drive fallacy: we built our save habits around storing things, and we still don't have good habits around recalling things. Storing is solved. Recalling is where the lost hour goes.
What a calmer end-of-month looks like
The honest version of a calmer process has three parts. First, pick one save surface that you actually use, not the one a productivity blog told you to use. For a lot of US-remote workers that's Telegram, because it's already on every device, you can paste a PDF or forward an email into a saved-messages thread in two seconds, and it works offline. Second, when you save, give the item a one-line context: "austin client visit, day 2 dinner, paid personal Amex." Three seconds at capture buys you three minutes at retrieval. Third, when end-of-month hits, search by what you remember about the situation, not by the file name or vendor. "That dinner with the prospect" is what you remember. "ChiliBourbon_Receipt_04-17.pdf" is not.
dEssence sits in this third part. It's a small web product that takes anything you send to it via Chrome extension, Telegram bot, or the web app at dessence.ai, and lets you ask in your own words later. Save the WeWork PDF to the Telegram bot with the caption "austin client visit"; a month later, ask "what did I expense on the Austin trip" in plain English and get the receipts back without scrolling. Four save surfaces collapse into one query, and the long Friday turns into a short one. It's memory you don't have to maintain: no folders, no tags, no organizing.
Honest about dEssence
Two things to flag honestly. dEssence is still in beta. There's no native iOS or Android app yet, so on mobile you're using the Telegram bot or the web app in Safari or Chrome, which is fine for receipts but not as polished as a dedicated camera-roll scanner would be. The free tier also caps how much you can archive, which matters if you're trying to migrate three years of receipts in one Friday. Expensify, for what it's worth, is genuinely good at OCR'ing line items off receipts and pushing them into accounting software, which dEssence doesn't try to do. If your goal is fully automated expense coding tied to a corporate card, Expensify is the right tool. If your goal is "stop losing the receipt between save and submit," dEssence is closer to that.
Frequently Asked Questions
Q: Can I just use Apple Notes for all my receipts?
You can, and a lot of people do. The friction shows up at retrieval. Apple Notes does keyword search on titles and visible text, and it's quick for things you remember the exact words of. For receipts where you remember the situation but not the vendor name, it tends to fall short. A note labeled "April expenses" is only useful if you remember to look in April.
Q: What if my employer requires Expensify or Concur?
Use Expensify or Concur as the system of record, that's the one your AP team reads. The question is what you use during the month, between the purchase and the submission. dEssence or any equivalent recall tool lives in that gap. You still copy the final entry into Concur on Friday.
Q: How do I handle paper receipts I photographed?
Photograph the receipt, then immediately send the photo to your chosen save surface with a one-line caption naming the trip and category. The caption is the entire trick. Without it, the photo lives in your camera roll forever. With it, you can ask for it in plain English a month later.
Q: Is there a privacy concern with sending receipts through Telegram?
Telegram cloud chats are not end-to-end encrypted by default, only secret chats are. For receipts that include card numbers or sensitive amounts, treat saved messages the way you'd treat email: fine for most things, not the place for full card data. Most reimbursable receipts are not that sensitive, but worth knowing before you forward.
Q: What if I forget to add a caption when I save?
That's where semantic recall earns its keep. dEssence indexes the content of what you save, not just the caption, so a receipt without a caption is still searchable by the items it contains, the vendor name on the PDF, or the date. It's slower than a captioned save but not lost.
If end-of-month archaeology is costing you an hour you'd rather spend on actual work, dEssence is worth a small experiment. It's free during beta, no card required, and the trade is honest: beta polish, capped free archive, no native mobile app, but the recall question that breaks Apple Notes and Gmail search is exactly the question this is built for. Save it, forget it, ask for it later.