Case studies

Drawn from live use of the platform. Client names are withheld.

The same receipt, counted twice

Problem: A crew member sent one contractor receipt twice — once as an itemized list, once as the payment confirmation. Both were logged, and one landed with no name attached.
Solution: Deliveries are now keyed to the message itself rather than the delivery attempt, pages of the same receipt are grouped, and identical totals inside a short window are flagged for a keep-or-remove decision.
Result: Five duplicate pairs were found and corrected across three workspaces, removing $2,875.96 of overstated spend, and new duplicates surface for review instead of hiding in the totals.

Problem: Several senders had no Telegram username, only a phone number, so their receipts were logged as 'Unknown' and could not be filtered by person.
Solution: Senders are identified by their permanent numeric Telegram ID. Unrecognized senders are queued so an administrator can link them to a real account in one click, and historical receipts are swept in at the same time.
Result: Every historical receipt now belongs to a named person, and person filters, dashboard drill-ins, and exports agree with each other.

Problem: Spend by vendor and by person was only assembled at month-end from a pile of photos, long after the money was committed.
Solution: Totals, budgets, and a spend calendar update as receipts arrive, with threshold alerts, a monthly digest, and a plain-language question box over the same filtered numbers.
Result: Overspend is visible on the day it happens rather than weeks later, and month-end is a review instead of a reconstruction.