FinSnap

Reconcile corporate card statements in minutes.

Visit Website
May 21, 2026 Why receipt matching is harder than it looks

I used to think receipt matching was mostly a date + amount problem.

In practice, it gets messy fast.

A few examples:

  • A receipt date may differ from the card posting date by one or two days.

  • The vendor name on the receipt rarely matches the vendor name on the card statement exactly.

  • Tips can change the total.

  • Foreign currency transactions may show different amounts depending on the statement view.

  • Hotel receipts can contain deposits, reversals, taxes, room charges, and restaurant charges on the same folio.

  • Some receipts show subtotal and tax clearly. Others bury it in tiny text or split it across pages.

  • Some “receipts” are really confirmation emails, screenshots, invoices, or order summaries.

That is why I think the useful part of automation is not just saying “matched.”

It needs to explain why it matched:

“This receipt was matched because the vendor name is similar, the receipt date is one day before the posting date, and the total is within the expected range.”

And it needs to know when not to force a match.

I’m building FinSnap around that idea: fast matching where the evidence is clear, and a review workflow where it is not.

For people who deal with expense or card reconciliation: what are the receipt edge cases that still waste the most time?

Comment

May 20, 2026 I built FinSnap to clean up corporate card reconciliation

Corporate card reconciliation is simple in theory, but annoying in practice.

Statements are exported from one system. Receipts are collected somewhere else. Reviewers compare vendors, dates, and totals by hand. Missing receipts get tracked in email or spreadsheets. Tax details and GL codes often need manual cleanup before the file can go into the accounting system.

FinSnap turns that into a shorter review workflow:

  • Upload the card statement.

  • Add the receipts.

  • FinSnap reads the files, suggests matches, explains why each match was made, extracts tax details, and suggests GL coding.

  • The reviewer stays in control and can override anything.

  • When complete, the session exports to Excel for upload into the accounting system, with organized receipt files saved for support.

I’m building this for businesses that do not have a clean end-to-end expense platform, or where corporate cards are still handled as a standalone month-end process.

Curious how others are handling this today. Is corporate card reconciliation still painful, or has your team solved it with another tool?

Comment

About

My wife's work team has to match receipts to hundreds of corporate card transactions every month. I saw this as a great project to automate and get rid of mundane time-consuming work, not well served by other offerings