Weekend food orders do not feel like a budget item. One dinner on Friday, a lunch on Saturday, and a Sunday night order each look like a treat. The SMS amount includes the meal, a fee, a tip, and sometimes a rain charge. The price you remember was often only the dish. By Monday the Sheet can show a cluster that rivals a kirana run. Kharch Log catches those UPI alerts on Android without a bank login. See the weekend as one number before the third order, not after the money is gone.
Look at Friday to Sunday, not the whole month
Filter delivery from Friday through Sunday, not the whole month, when you want the habit. A monthly total hides a party inside a pattern. If three weekends in a row are high, it is a habit. If one weekend has a guest, write guest in the note so you do not set the cap from a party. Swiggy, Zomato, and a restaurant QR can share one category. The brand is not the point. The repetition is. Give them one category the first time each payee appears.
Include the small add-ons. A fee and a tip are in the SMS even when you remember only the dish. Do not edit the SMS amount down to the menu price. That flatters you. If you want the split, put the fee in the note and leave the amount as the bank took it. Two orders that felt small can be much larger after fees. Four of those become a real bill. Use the debited number. The menu price is why the weekend surprises you.
- One category for Swiggy, Zomato, and restaurant QR orders
- Leave the SMS amount alone, even if the menu price was lower
- Write guest in the note when the weekend was not a normal habit
- Fees and tips stay inside the debited total
Set the cap before you are hungry
Write a weekend food cap on Friday afternoon, before you are hungry. A cap made at night is a wish. The cap includes fees. If you share an order, the cap is your share, and the note says who owes you. Their later UPI is a repayment, not a ticket for another order. If the cap is gone by Saturday lunch, Sunday is home food. Check the filter on Saturday morning. A Monday review cannot change the Sunday order you already placed.
A delivery pass is not free. The pass fee is a row in the month it is charged. If you bought it to save fees, weekend totals should fall by more than the pass. If they do not, the pass trained you to order more. Note the pass date. Do not smear the pass across meals by editing each SMS. Keep meals at the bank amount and the pass as its own row. A wallet top-up is a transfer until an order actually uses it. Otherwise you count the meal twice.
The third order is the decision
The third weekend order is the decision, not the first. The first can be a tired Friday. The third means the pattern is set. Look at the weekend filter before you place it. If you still order, note that you were over the cap. Do not delete the row. A missing row teaches you nothing. The SMS stays. Your job is the category and the note. Next weekend, last weekend's total in the header is harder to ignore than a resolution.
Weekday office orders are a different note from weekend dinners. Mixing them makes you blame Saturday for a desk habit. If lunch is reimbursed, mark the row and clear it when the credit arrives. Weekend orders are rarely reimbursed. Keep those in the number you compare with the cap. A canteen payment and a Sunday order are both food, and they are not the same decision. Use two notes so the filter can separate them. The leak you can change this week is the one at home.
- Check the weekend filter before order number three
- Mark over cap in the note instead of deleting the row
- Weekday office food gets a different note
- Clear a reimbursed lunch when the credit arrives
Five minutes on Monday
On Monday, sort weekend delivery by amount and read the top three. If fees are a large share, the next meal is a pickup or food at home. If one order was a group bill, the note should already say who owes you. Add any cash tip the SMS missed. Write the weekend total under the cap. That pair is the record. Do not rebuild the cart from the app. The bank amount in the Sheet is enough.
If four Mondays are over the cap, lower the cap or change Friday. Raising the cap to fit the habit turns the leak into the budget. A lower cap works only if you look on Saturday. You can name two delivery weekends in the month and write the dates. The other weekends are a blank filter, not a speech. When that filter starts filling, you see it the same day. The SMS arrives before you have talked yourself into calling it a one-off.
Questions people actually ask
Should I track small drink deliveries too? Track it if it is on the same apps as dinner. Small drink orders can spend the cap without one large meal. A small UPI repeated four times still needs a category. You do not need a long note. Skip a rare cash drink if you want. Do not skip the UPI rows. The SMS already captured them. You only add the category.
We split one order. Who logs the dinner? The person who paid logs the full SMS as delivery, with the share in the note. The other person logs their UPI as a transfer, not as a second dinner. If both log dinner, the meal is doubled. When the share arrives, match it to the order date. Your cost is the SMS minus what came back. One dinner, then settlements.
Does a coupon mean I can skip the row? No. Log the SMS amount, which already includes the discount. Do not also record the menu price as if you paid it. If an offer reduced the debit, the smaller debit is the truth. A coupon that did not change the debit is not savings. The weekend total after discounts is the money that left. The struck-through price in the app is not a row.
Treat Friday to Sunday delivery as one number, including fees, and check it on Saturday before a third order. Mid-month leaks are the subject of catching leaks before month end. The Kharch Log features page shows how those UPI SMS land in your Sheet. Write the weekend total under the cap on Monday, then leave it.