Check a receipt CSV against its source files.
A tidy CSV is useful only when its rows agree with the source documents. Check the file mapping first, then dates, totals and currencies. Keep the original evidence available throughout the review.
Updated 10 November 2026 · Receipt Workbench free beta
Know what each row represents
Receipt Workbench exports one CSV row for each confirmed document included in the ZIP. A row describes a whole document, not its individual line items. Explicitly excluded documents do not receive rows.
The columns are original_name, archive_path, client, vendor, date, amount, currency and sha256. The first two connect an input file to its renamed copy. The middle fields reflect your review, and the checksum supports a file-integrity check.
Start by comparing row count with document count. Follow each archive path to its copy. A complete-looking list cannot reveal a receipt that was never selected for the batch.
Check a concrete example
Suppose a fictional receipt reads MAPLE CREEK BAKERY, dated 18 October 2026, with subtotal USD 17.00, tax USD 1.75 and total USD 18.75. Its reviewed CSV values should include 2026-10-18, 18.75 and USD. A row containing 17.00 would describe the subtotal instead of the document total.
Return to the source when the proposed fields disagree. Correct the field in the workbench, confirm it again and make a fresh export. This keeps the filename and CSV consistent. Editing only the downloaded spreadsheet would not rename its matching document copy.
Treat dates and currencies explicitly
Do not resolve a date such as 03/04/2026 by guessing. Establish the intended date from reliable context before confirmation. A payment due date is not automatically the document date.
Likewise, a dollar symbol does not establish USD. Check the currency before using the amount. Keep different currencies separate when reviewing totals; the beta does not convert them or supply exchange rates.
Amounts use a decimal point and two decimal places. A credit note can have a negative amount. Verify that your spreadsheet has interpreted numeric cells as intended before calculating with them; display and import settings can vary.
Understand protective formatting
A merchant name can contain commas, quotes or other characters. CSV quoting keeps those characters inside their field. Text that could be interpreted as a spreadsheet formula receives a protective apostrophe, which some viewers may display. Validated amounts retain their numeric decimal form, including a negative sign.
The SHA-256 column is calculated from the source file bytes included in the archive. It can help compare a copy with an independently calculated file checksum. It does not certify the merchant, prove payment or show that an extracted total is correct.
Use the list for the job it supports
This CSV is a handover manifest, not a guaranteed import file for accounting software. It contains no posting rules or tax classification. Check your recipient’s requirements before making downstream changes.
These instructions follow the current beta’s export format. Read the privacy explanation, then use the handover checklist and filename examples to review the package as a whole. Your originals stay unchanged.