Skip to main content
The Receipts tab is a dedicated inbox for the receipts on your account. Add a receipt from anywhere in the app and Dash.fi reads it, matches it to a card transaction, and files it against the resulting expense.
Receipts are part of the Expenses product. Your organisation must have Expenses enabled to use the Receipts tab.

​
When to use it

Use the Receipts tab when you want to work receipt-first rather than transaction-first:
  • Snap or upload a receipt as soon as you get it — you don’t need to wait for the card transaction to appear.
  • Review anything the AI matcher wasn’t sure about, in one place.
  • Confirm receipts the AI matched automatically before they’re submitted.
To attach a receipt to a specific transaction you already know about, the transaction-first flow in Expenses is still available. The gallery shows receipts in two columns. Each card shows:
  • A thumbnail of the receipt (or a scanning placeholder while OCR is still running)
  • The merchant name from the parsed receipt
  • The amount and currency
  • A status tag (see Receipt statuses)
Pull down to refresh. Scroll to the bottom to load more — the list pages in as you go. Tap a card to open its receipt sheet. If OCR is still running, the sheet opens on the scanning stage; otherwise it opens on the review or detail view for that receipt.

​
Filters

Three filters sit above the gallery: The tab opens on Unmatched by default so anything that needs a human decision is one tap away.

​
Adding a receipt

Tap the + button at the bottom-right of the Receipts tab, or tap Add receipt on the home screen. The receipt inbox sheet slides up with three source options: Accepted formats: JPG, PNG, PDF. Maximum file size: 10 MB per file. Photos and Files support multi-select — pick up to 10 receipts in one go. If you pick more than 10, Dash.fi uploads the first 10 and shows an alert naming the files that were skipped.

​
One receipt

The sheet uploads the file, then steps through the pipeline in the header — Merchant → Amount → Date → Matching transaction — as OCR runs and the matcher looks for a card transaction to attach it to. Once processing finishes, the sheet lands on one of these outcomes:
  • AI matched — Dash.fi linked the receipt to a card transaction with high confidence. You can confirm the match, unmatch it, or submit the expense straight away.
  • Review match — the matcher found candidate transactions but isn’t confident. Pick the right one from the list, or tap Other candidates to see more.
  • Automatic matching failed — no transaction matched. Search for the right one with Find transaction, merge into an existing expense, or keep the receipt on file for later.
  • Couldn’t read this receipt — OCR couldn’t parse the file. Try a clearer photo or a different format.
If a target transaction already has a receipt attached, Dash.fi tells you and offers to merge the new receipt into the existing expense instead of creating a duplicate.

​
Forwarding a receipt by email

Every user has a personal receipt inbox address. Forward a receipt to it from any email client and Dash.fi imports each attachment as its own receipt on your account. Attachments then run through the same OCR and transaction matcher used for camera uploads. Use this when the receipt already lives in your email — airline itineraries, ride-share confirmations, SaaS invoices, or anything a vendor sends direct to your inbox.

​
Get your inbox address

  1. On the Receipts tab, tap the + button (or Add receipt on the home screen).
  2. Tap Email a receipt at the bottom of the source picker.
  3. Dash.fi provisions your personal address the first time you open this screen — it’s shown in the format <slug>@receipts.dash.fi and is frozen for the life of your account, so it’s safe to save as a contact.
  4. Tap the copy button to put the address on your clipboard.
The receipt inbox address is personal — every user has their own. Emails you forward only import onto your own account, and other users on your organization can’t see them.

​
Forward from any email client

  1. Open the receipt in your normal email client.
  2. Forward it to your receipt inbox address. Include any attachments — Dash.fi processes attachments, not the message body.
  3. Send from the same email address you use to sign in to Dash.fi. Forwards from other addresses are rejected (see Who can send).
Refresh the Receipts tab after forwarding. Each imported attachment appears as its own receipt in Unmatched → Scanning, then moves through the same match pipeline as camera uploads.

​
Who can send

Dash.fi only accepts forwarded mail from you — the address you sign in with. Each inbound email is checked, in order:
  1. Spam and virus verdicts — mail SES flags as spam or carrying a virus is rejected.
  2. SPF authentication — the envelope sender must pass SPF. Some client-side forwards rewrite the envelope in ways that break SPF; if that happens, use Take photo or Choose file instead.
  3. Sender domain — the sender’s domain must match one of your organization’s user domains.
  4. Sender identity — the envelope sender must resolve to your Dash.fi user. Forwards from a teammate’s mailbox land on their receipts, not yours.
Receipts imported this way are locked to you as the creator — only you can see them in your Receipts tab, and the resulting expense is submitted from your account when you’re ready.

​
Supported attachments

Dash.fi sniffs the attachment bytes rather than trusting the file extension, so renaming a file won’t change how it’s processed. Inline signature images (CID-referenced HTML assets) are ignored. There’s a per-email cap on the number of attachments processed; anything beyond that is skipped. If an email arrives with no supported attachment at all, the whole email is rejected and no receipt is created.

​
Email statuses and outcomes

Every email that reaches your address is recorded so you can trace what happened to a receipt you forwarded. Rejection reasons Dash.fi records: Per-attachment outcomes on an accepted email:

​
Several receipts at once

When you pick more than one file, the sheet switches to a batch view. Upload phase. The header reads Uploading receipts with an Uploaded X of Y progress bar. Dash.fi uploads up to three files in parallel and adds each one to the list below as its bytes land. Scan phase. Once all uploads finish, the header switches to Scanning receipts and each receipt gets its own row. The row is named after the file until OCR reads a merchant off the receipt, at which point the merchant replaces the filename. Each row shows one of three states: Rows resolve independently, so faster receipts tick over to a check while slower ones keep spinning. If a file fails to upload — too large, wrong format, or past the 10-receipt cap — the batch carries on without it and an alert above the list names the files that were dropped and why. Summary. When every row has settled, the sheet lands on a Scanned N receipts summary with a line per outcome:
  • N matched automatically — the matcher linked these to a card transaction on its own.
  • N need confirmation — the matcher found candidates but wants you to pick one.
  • N without a match — no candidate transaction matched.
  • N still processing — the scan deadline passed before the pipeline finished. These keep working in the background and appear in the gallery once they resolve.
  • Couldn’t read <filenames> — OCR or matching failed on these files.
Tap Review receipts to close the sheet and return to the gallery, where each receipt is now a card you can open individually to confirm the match, pick a candidate, or find a transaction.
Prefer the desktop for large stacks? The web app’s Receipt inbox accepts drag-and-drop and multi-select with the same per-row progress and summary behaviour.

​
Viewing and downloading a receipt file

You can open the underlying receipt file — image or PDF — from the receipt sheet on the Receipts tab. The same option is available in the comparison, review, and search views inside the transaction expense sheet.
  • Images open in a full-screen viewer. Pinch to zoom, drag to pan, tap ✕ to close.
  • PDFs open in the in-app browser.
  • Other file types hand off to your device so you can download or open them in another app.
Dash.fi mints a fresh download link each time you open the file, so the link never expires while a sheet is left open.

​
Deleting a receipt

Delete a receipt when it’s a duplicate, was uploaded by mistake, or you no longer need it on file. Deleting removes the receipt and its scan, and any expense that only existed to hold the receipt is removed with it. This can’t be undone.
Receipts on an expense that’s already been submitted or confirmed are locked — you can’t delete them from the mobile app. Handle those from the web app, or unsubmit the expense first.

​
Delete one receipt

  1. Tap a receipt in the gallery to open its sheet.
  2. Scroll to the bottom of the sheet and tap Delete receipt.
  3. Confirm in the Delete receipt? dialog.
The sheet closes and the gallery refreshes.

​
Delete several at once

  1. Long-press any receipt in the gallery to enter selection mode. Dash.fi selects that receipt and swaps the filter bar for a Cancel / N selected / Select all header.
  2. Tap more receipts to add them to the selection, or tap Select all to select every deletable receipt currently loaded.
  3. Tap Delete N receipts in the bar at the bottom of the screen.
  4. Confirm in the Delete receipts? dialog.
Locked (submitted or confirmed) receipts are dimmed and can’t be tapped in selection mode. Select all skips them as well. Tap Cancel at any point to leave selection mode without deleting anything.

​
Receipt statuses

  • Expenses on mobile — attach a receipt starting from a transaction and submit the expense
  • Transactions on mobile — browse and filter card activity
  • Receipt inbox — the same inbox on the web app, including Forward by email for forwarding receipts from your desktop email client