Read a receipt locally. Review it like it matters.

Prepare an image the device can read

Crop a printed English receipt closely, keep it upright and use even lighting. JPEG, PNG and WebP are accepted within the shown size and pixel limits. Remove unnecessary names, card information and unrelated material. A large compressed photo can still require significant decoded memory on a phone.

The server checks actual file type and dimensions and reprocesses the image rather than trusting its filename. Unsupported documents and disguised executable files are rejected. A host needs secure image-processing support. When a receipt is faded, handwritten or difficult to interpret, manual entry is more responsible than repeated blind retries.

A bundled engine with a finite allowance

Recognition runs in the browser using local worker code and an English model. The first scan loads those assets and may take longer than a simple form save. No external OCR key is required. Accepted capture jobs use a finite monthly allowance, with workspace-context work charged to the owner’s shared pool.

An identical active image job is reused to avoid charging the same retry twice. That does not extend retention indefinitely or guarantee recognition on every device. Keep the page open while processing and use manual entry if a worker is blocked or memory is insufficient. A service limit is a resource policy, not a claim about the image’s authenticity.

Review before any bill is created

The extraction area shows raw recognized text and editable candidate items. Remove totals accidentally interpreted as rows, add missing items and check each price. Currency is explicitly reviewed rather than guessed from a symbol. Tax and tip must match the receipt’s actual calculation basis.

The review checkbox confirms that you checked the original, then reviewed items can replace the builder draft after confirmation. Nothing is published automatically. Recognition confidence remains an estimate, and a detected total is only a prompt for comparison. Inspect the final builder calculation before creating and sharing the separate bill action.

Retain less, and manage the separate result

Temporary image retention is off by default. If selected, the copy is encrypted outside public media for up to 24 hours and can be downloaded or deleted by its owner. Request-time expiry checks deny access even if a cleanup job has not run yet. Reliable cron remains necessary for prompt physical cleanup.

Recognized raw text is not stored as a server transcript by the capture feature. The bill items you deliberately publish are different content with their own audience. Deleting the receipt job does not erase that bill, cancel a payment or verify a settlement. Review both content and storage when handling a privacy request.

Illustrative workflow: correct the draft before using it

A member crops a receipt to its printed item list and chooses not to retain an image. The local worker reads candidate text, but a total line is mistaken for an item and one amount is misread. The member removes the false row, fixes the price and checks the original currency rather than trusting a familiar symbol. Confidence is only an estimate and cannot replace that comparison.

After reviewing tax and tip, the member confirms the review and applies the items to the bill builder. The builder still needs a final calculation check and a deliberate creation step. If a temporary encrypted copy had been selected, deleting that job would remove the private receipt copy but would not erase a separately published bill. This teaching workflow explains why recognition, review, publication and retention are distinct operations; it does not claim every receipt or device produces an accurate automatic result.

Before you share

1. Prepare: crop a clear permitted image and remove unnecessary personal details.
2. Review: correct each item, amount, currency and charge before confirming.
3. Handover: inspect the separate bill’s audience and manage temporary storage deliberately.

Make the next request clear.

Create an action ↗ · Read the detailed guide · Compare current plans