Supported sources

Bring the evidence in, then let the app sort out what role it plays.

Receipt Resolver does not treat every upload as just another receipt. It keeps receipts, statements, pending transaction exports, posted QuickBooks records, existing QuickBooks attachments, and exception notes in lanes with clear accounting meaning, so the reviewer can see what is proven and what still needs work.

Primary evidence

Receipts and invoices

PDFs, images, HTML, text, CSV exports, email bodies, and vendor invoices. The app looks for vendor, date, amount, tax, currency, IDs, line items, and the original source.

Strong when fields are clear. Review warnings stay visible when they are not.
Settlement truth

Card and bank statements

Statement PDFs and bank/card exports help verify posted date, charged amount, account, statement reference, descriptor, and currency conversion.

Used as the chain-of-custody bridge between receipts and the books.
QuickBooks work

Posted records and pending exports

Posted transactions can sync through the QuickBooks connector. Pending Banking rows still need a QuickBooks CSV export or statement-backed inference because the public API does not expose the Banking for-review queue.

Used to verify what is already in the books and what still needs reviewer action.
Already in QuickBooks

Existing QuickBooks attachments

Receipt and invoice files already attached in QuickBooks can be pulled into the local evidence pool when QuickBooks exposes the original attachment file.

The app parses the downloaded original locally; it does not assume QuickBooks provides trusted parsed receipt text.
Funding bridge

PayPal activity exports

PayPal data can explain why a merchant receipt amount does not match the card charge, including transaction IDs, gross/net, currency, status, and card funding lines.

Useful evidence, but still labeled as PayPal-derived when the merchant invoice is missing.
Order evidence

Amazon orders and invoices

Order history, order pages, and invoice PDFs help resolve split shipments and multiple card charges from one order.

Split-charge groups stay reviewable until the reviewer accepts the likely match.
Review required

Receipt photos, scans, duplicates, and missing receipts

Hard-to-read images, duplicate uploads, wrong-lane files, failed extraction, parser warnings, and missing receipt situations are supported as review cases, not hidden as clean matches.

The goal is honest cleanup: show the issue, resolve it, then package the decision.