Close out any table in a few taps. The cashier sees every unpaid order grouped by table, generates an itemised bill with the CGST/SGST breakdown, records how the guest paid, and the table frees itself — receipt ready to share or print.
Unpaid orders grouped by table, itemised bills with tax, and a receipt you can share in a tap.
GST billing without a separate billing system. The cashier sees every served, unpaid order grouped by table. Generate an itemised bill with subtotal, CGST/SGST and total, record the payment as cash, card or UPI with an optional reference, and the table releases itself. The receipt is ready to share or print.
When ordering lives in one system and billing lives in another, someone re-keys every order into the billing machine at the end of the meal. It is slow, it is error-prone, and at a busy close it is where the queue at the counter builds.
Re-typing means totals that do not match the kitchen, tax worked out by hand, and a table that stays "occupied" in everyone's mind long after the guest has paid and left. And a lost paper receipt is a guest you cannot help when they ask for it later.
Because DinePilot already has the order, billing is a continuation of it, not a re-entry. The cashier sees every served, unpaid order grouped by table, and generates an itemised bill with subtotal, CGST/SGST and total in one step — no re-keying, no separate tax calculation.
Record the payment as cash, card or UPI with an optional reference, and the table releases itself back to available. The receipt is ready to share with the guest or print on the spot, and it stays on the order if it is ever needed again.
No hardware to buy and no technical skills required — just a few steps to go live.
The cashier sees every served but unpaid order, grouped by table, so closing out starts from what is actually owed.
One step produces an itemised bill with subtotal, CGST and SGST broken out, and the total — no manual tax maths.
Mark it paid by cash, card or UPI, with an optional reference note for a card slip or UPI transaction.
Payment releases the table back to available and the receipt is ready to share with the guest or print.
Billing runs on the order you already have, so nothing is re-keyed and nothing has to be reconciled at close.
Every bill breaks out CGST and SGST against the subtotal automatically — no hand calculations, no second device.
Cash, card or UPI, each with an optional reference, so the record matches the slip or the transaction.
Settling the bill releases the table for the next guest, so nothing stays blocked after payment.
Not a competitor comparison — a comparison with the paper-and-shouting workflow most restaurants run today.
Step
The usual way
With DinePilot
Producing the bill
Usually — Re-key every line into the billing machine at the counter, at the busiest moment of the meal.
With DinePilot — The order is already there. The bill is generated from it in one step.
GST
Usually — Worked out by hand, or on a second device with its own settings to keep in step.
With DinePilot — CGST and SGST broken out against the subtotal automatically, on every bill.
Several rounds on one table
Usually — Multiple slips that someone has to find and add together.
With DinePilot — Unpaid orders are grouped by table and billed as one itemised total.
Recording how they paid
Usually — A note in a book, if at all, so the cash-card-UPI split is a guess.
With DinePilot — Cash, card or UPI with an optional reference, stored against the payment.
Freeing the table
Usually — Someone has to remember to tell the floor the table has paid.
With DinePilot — Settling the bill releases the table back to available on its own.
A lost receipt
Usually — Gone. You cannot reissue what was only ever on paper.
With DinePilot — The receipt stays attached to the order and can be shared or printed again.
It helps every dine-in restaurant, but these are the rooms where the difference is largest.
If the pinch point of your night is bill settlement, the re-keying step is what is causing it. Removing it removes the queue.
Anywhere the bill has to show a CGST and SGST breakdown correctly, every time, without depending on someone doing the arithmetic at speed.
Bars, pubs and long-session dining, where grouping several unpaid orders into one bill is the difference between one slip and five.
If you have never been able to say what share of your takings is UPI, this is where that number starts existing.
Real screenshots from the DinePilot staff app — no mockups, no marketing renders.
Receipt
Unpaid orders
Takings at a glance
Three moments from an ordinary week, and what happens differently in each.
The cashier opens the unpaid orders grouped by table. All three of table 8's rounds are there. One step produces the itemised bill with subtotal, CGST, SGST and total. Nothing was typed twice, and the guest is not waiting while someone reads a ticket into a machine.
The guest pays by card. The cashier records it as card with the slip number in the reference field. At close, the card total in DinePilot and the machine's settlement report are checkable against each other line by line rather than as two lump sums.
The receipt is still on the order. It can be shared or reprinted without anyone reconstructing what was ordered from memory — which matters more than it sounds when the guest is expensing it.
What the restaurants who get the most out of this do — and what trips up the ones who don't.
DinePilot records how a guest paid; it does not take the payment. There is no gateway and no online settlement from the guest's phone today — that is on the roadmap, not in the product, and we are not a payment provider or a party to your money. If accepting payment inside the app is a requirement for you right now, this is the honest limit of what billing does, and it is better said here than discovered at a counter.
Ask us anything else — we reply to every message.
Yes. Every bill is itemised with the subtotal, a CGST and SGST breakdown and the total, worked out for you — there is no separate tax calculation or second device involved.
Not yet. Today the cashier records how the guest paid — cash, card or UPI — with an optional reference, and DinePilot handles the bill, the tax and the receipt. Letting guests pay from their own phone is on our roadmap.
Cash, card and UPI, each with an optional reference note so a card slip number or UPI transaction id can be kept against the payment.
Yes. Once the bill is settled the receipt is ready to share with the guest or print on the spot, and it stays attached to the order if it is ever needed again.
Unpaid orders are grouped by table, so multiple rounds on the same table are billed together as one itemised total rather than as separate slips.
It releases itself. Recording the final payment moves the table back to available automatically, so the floor map is ready for the next guest without a manual step.
It is software that produces an itemised bill for a table with the CGST and SGST worked out for you. Because DinePilot already holds the order, the bill is generated in one step — no re-keying into a separate till — and you record whether the guest paid by cash, card or UPI.
DinePilot is one connected system — here is what works alongside this.
Every order — QR or waiter-taken — in one filterable list, from placed all the way to completed.
Today's revenue, average order value, top sellers and peak hours — updating as the service runs.
A colour-coded floor map that keeps itself up to date — available, reserved, occupied or cleaning.
Written for owners rather than for us — free to read whether or not you ever use DinePilot.
Set up your restaurant, print your QR codes and take your first order today. Starter is free.
No card required · Nothing to install for your guests