From itemized receipt to shareable split

SettleTab is a live Android app that turns scanned or manually entered bills into editable, itemized splits and shareable totals for everyone at the table. Creating and managing splits requires an account, with email/password or Google Sign-In.

Receipt processing proposes an item list that people can correct. SettleTab's application logic then calculates what each participant owes; extraction does not decide the final amounts.

A group can agree on a bill total and still disagree about each person's share. Individual and shared items, tax, tip, and an imperfect receipt all need checking.

SettleTab brings capture or manual entry, review, assignment, calculation, and sharing into one flow. A scan reduces typing, but its output remains editable before anyone settles on a split.

The product goal is a clear path from receipt input or manual entry to a reviewed bill, participant totals, and a breakdown people can share.

• Reduce repetitive receipt entry
• Keep extracted items editable
• Use reviewed items as the input to split logic
• Keep final calculations reproducible

As Founder & Lead Developer at DivWeavers, I led SettleTab's engineering across the Flutter app, receipt workflow, split calculation, Supabase backend, sharing, subscriptions, notifications, testing, and Android release infrastructure.

Receipt recognition can be incomplete or wrong, while the people settling a bill expect totals they can inspect and reproduce. That makes correction a primary path rather than an exceptional state.

• Physical receipt input is not consistently structured
• Extracted values require review
• Financial rules must remain deterministic
• The workflow must stay understandable when automation is imperfect

Flutter handles capture, manual entry, review, assignment, and summary. Supabase provides authentication, PostgreSQL data, private receipt storage, realtime collaboration, and server functions. Receipt processing proposes bill data; Dart application logic divides shared items equally, allocates tax and tip proportionally, and reconciles rounding.

Configured server providers are tried in order, with on-device text recognition attempted after cloud analysis fails. People can correct proposed items or enter a bill manually. Local writes can be queued for later synchronization after sign-in; cloud features still need connectivity.

SettleTab is live on Google Play. A finalized split can be sent as an itemized breakdown through the device share sheet. Once saved online, it can also be viewed on a read-only browser page without installing the app or creating an account.

Saved groups, balances, history, and settlement records support repeat bills. External payment destinations may be opened, but SettleTab does not transfer money. OneSignal is used for production push notifications, and RevenueCat implements subscriptions and the Pro entitlement.

The live Android workflow turns receipt images or manual bill items into editable, itemized splits and shareable totals. Join codes support collaborative item assignment, while saved groups carry balances across bills.

SettleTab demonstrates mobile engineering across receipt input, backend data rules, collaboration, and sharing. The important boundary is that automation proposes bill data while application code calculates the amounts owed.

Probabilistic extraction is most useful when the user can inspect what it produced. Financial behavior remains easier to trust when the final rules are ordinary, reproducible product logic.