Forwarding receipts

The fastest path is email. Every jar has an inbox address; receipts forwarded there land in the right jar, get extracted, and join the running ledger without you opening anything.

The inbox address

Each jar has a single forwarding address of the form jar@splitjar.app — the routing happens through subject lines and the sender being a known member. The address is shown on your jar’s home page.

Forward any of:

• The receipt email itself (Uber, Airbnb, restaurant POS confirmations)
• A photo of a paper receipt as an attachment
• A PDF invoice

Most receipts are extracted in under ten seconds.

What gets extracted

The model reads:

• Vendor (with a Maps query when it can recognise the place)
• Total in the original currency, plus tax/tip if itemised
• Date and time
• Line items, when present
• Currency — defaults to the jar’s base currency if the receipt doesn’t say
• Split hints from your subject line (“split with Steve and Rod”) or handwritten markings on the receipt

You don’t have to phrase anything in particular. The pipeline is forgiving.

When something needs review

Receipts are held for a quick human look when:

• The model’s confidence dipped below 85%
• The forwarded email had a long thread (we held the most likely receipt)
• The sender’s domain didn’t pass authentication
• It’s the first receipt we’ve seen from that sender in this jar
• The structured extraction failed twice running

You’ll get a “review needed” email with a one-line reason. You can reply directly with corrections — “split 3 ways between me, Rod and Steve”, “vendor is actually X”, “amount was 42.50 GEL” — and we’ll apply them.

Web uploader

If forwarding isn’t convenient, the web app accepts direct uploads of images and PDFs. Same pipeline, same outcome.

Replies

Every “review needed” email is reply-able. The reply edits the receipt; you don’t need to log in to make a small correction.