# What a Receipt Total Hides: A Six-Month Data Study

## Citation

Yomio Team (2026). What a Receipt Total Hides: A Six-Month Data Study. Data extracted October 11, 2026.

https://yomio.app/en/blog/receipt-itemization-data-report

## Sample

Window: 2026-04-10T00:00:00 inclusive to 2026-10-10T00:00:00 exclusive, using the saved purchase date.
Extraction: 2026-10-11T11:43:10Z.
Sample: 15,179 approved expense records from 1,514 distinct user IDs.
All selected records join to distinct Receipt objects owned by the same user.

## Definitions

A record is a Purchase with status APPROVED, transactionType EXPENSE, a non-null receiptId, and a purchaseDate in the stated window.

The purchase-date window is applied to the saved timestamp without a user-local timezone conversion.

All selected receipt links match distinct Receipt objects owned by the same user as the expense record.

A product row is a PurchaseItem with itemType product; separate discount rows are excluded from the row count.

A category is a standard system root reached through Category.parentCode from a product row's saved categoryCode, using the hierarchy at extraction.

Category mapping excludes user-created custom categories; a record with only custom or unclassified rows has no mapped standard category.

The category-breadth chart includes records with at least one mapped standard category and counts distinct roots per record.

The grocery chart includes records with a groceries root and splits them by the presence of a householdPersonal root.

The product-row chart includes all selected records, including records with zero saved product rows.

Users are distinct saved user IDs, not verified households or unique people. A user can appear in several chart groups.


## Limits

This is a descriptive sample from Yomio, produced by the app's team; users chose which records to save.

The 152 most active users contributed 9,909 of the 15,179 records, so record-level results weight frequent contributors more heavily.

Category labels and product rows were not checked against receipt images, and approval status does not establish a manual quality check.

A product row can have a quantity above one; its count does not establish units bought or verified distinct products.

These figures do not estimate population spending, category spending amounts, product popularity, OCR accuracy, savings, or inflation.


## Files

- data.json: the release metadata and aggregate counts used by the interactive charts.
- aggregate-data.csv: the same chart counts, denominators, shares, and distinct-user counts.
- SVG and PNG files: reusable charts with source and sample notes.

Each chart partitions its eligible records.
Distinct users can appear in more than one row, so user counts must not be added.
Published row groups each contain at least 100 distinct users.
No user IDs, receipt images, exact item names, or merchant names are released.
Please credit Yomio and link to the report when citing these figures or using a chart.