Tally for restaurants

Tally for restaurants: every channel booked, already reconciled.

Most restaurant books in Tally run a month behind and are full of netted payouts. OnPlusOne turns each day's reconciled sales, payouts, deductions and bank credits into Tally vouchers, outlet by outlet, so your books match your bank before your accountant opens them.

No signup. Sample restaurant preloaded. Takes 2 minutes.

The problem

Why restaurant books in Tally rarely match the bank.

A restaurant collects money through five or six channels, and each one settles differently. Cash waits for a deposit. UPI and card settle a day or two later, card net of MDR. Swiggy and Zomato pay weekly, net of commission, fees, ads, refunds, TDS and sometimes TCS.

When these are booked in bulk at month-end, the usual shortcut is to book the payout as the sale. The deductions disappear, TDS goes unclaimed, a missing cash deposit hides inside a suspense ledger, and nobody can say which outlet is short. The fix is to book every channel daily, gross, and only after it has been matched to the bank.

Ledger setup

A ledger map for a restaurant in Tally.

ChannelLedger (typical group)What gets booked
Dine-in and takeawaySales ledgers by outlet (Sales Accounts)Daily POS sales, net of voids and cancellations
CashCash ledger per outlet (Cash-in-hand)Cash sales in, bank deposits out, so the balance shows undeposited cash
UPIUPI settlement ledger (Current Assets)UPI sales, cleared when the settlement hits the bank
Card machinesCard acquirer ledger (Sundry Debtors) and Card MDR (Indirect Expenses)Card sales, MDR charged, net settlement to bank
Swiggy and ZomatoParty ledger per platform (Sundry Debtors)Gross sales, then commission, fees, ads, refunds, TDS and TCS, then the payout by UTR
TaxesTDS receivable, TCS receivable, output and input GST (Duties & Taxes / Current Assets)Tax lines split out of payouts instead of netted off

A common structure, not the only one. Your accountant's ledger names and groups take priority, and OnPlusOne maps to them.

What gets booked

The entries restaurants usually do by hand.

Sales by channel

Dine-in, UPI, card, cash and aggregator sales booked to the right ledgers, per outlet.

Aggregator deductions

Commission, fees, ads, TDS (194-O) and TCS as separate entries, not netted off. How to read a Swiggy payout.

Bank receipts

Each payout matched to its bank credit by UTR before it is booked.

Card MDR

MDR booked as an expense against each settlement, and flagged when it is above your agreed rate.

Cash deposits

Deposits matched to daily cash sales, so a missing deposit shows up the next morning.

XML export

Download a Tally XML file for your accountant, or push directly once approved.

The daily close

What a clean day looks like in Tally.

01

Sales

Book yesterday's POS sales

One sales voucher per outlet and channel, after voids and cancellations are removed.

02

Collections

Match each channel

Cash to deposit, UPI and card to settlement, Swiggy and Zomato orders to their payout lines.

03

Deductions

Split the payouts

Commission, fees, ads, MDR, TDS and TCS booked to their own ledgers, checked against your contracts.

04

Bank

Book the receipts

Each credit booked against its channel ledger by UTR, so channel ledgers clear to zero.

05

Exceptions

Review what did not tie

Short payouts, missing deposits and wrong deductions stay open as exceptions instead of going to suspense.

Multi-outlet chains

One company or many, every voucher knows its outlet.

Chains usually keep each GSTIN as its own Tally company, or run several outlets in one company with cost centres. Either way, OnPlusOne reconciles each outlet separately and tags every voucher with its outlet, so branch-wise sales, deductions and gaps line up with the structure your accountant already has.

How it works

Reconcile first, then book.

01

Reconcile

Match every channel

Sales, payouts and bank credits are matched before anything is booked.

02

Review

Approve the vouchers

You or your accountant approve each batch.

03

Sync

Into Tally

Pushed into Tally, or exported as XML and imported in TallyPrime or Tally ERP 9.

Guides

Go deeper.

FAQ

Common questions

How do restaurants record Swiggy and Zomato sales in Tally?

Book the gross order value as a sale to a Swiggy or Zomato party ledger, then book commission, fees, TDS and TCS as separate entries against that ledger, and the net payout as the bank receipt. The party ledger should then show zero. Our step-by-step guide walks through a sample week.

Can a POS like Petpooja send sales to Tally on its own?

Many POS systems can push sales vouchers. What they do not do is check that the money reached your bank, or split aggregator payouts into commission, TDS and TCS. OnPlusOne books only after the sale, the payout and the bank credit have been matched.

Should each outlet be a separate company or a cost centre in Tally?

Both work. Outlets with their own GSTIN are often kept as separate companies; outlets under one GSTIN are often tracked as cost centres. OnPlusOne tags every voucher with its outlet so it fits whichever structure your accountant uses.

Does OnPlusOne post to Tally automatically?

It prepares vouchers and can push them, but nothing is posted without your approval. You can also export Tally XML for your accountant to import.

Which Tally versions work?

TallyPrime and Tally ERP 9, through XML import.

How is the TDS deducted by Swiggy and Zomato booked?

As TDS receivable (an asset), not as an expense. You claim it against your income tax once it shows in your Form 26AS. See our guide to TDS and TCS on aggregator payouts.

Will my accountant still need to check?

Yes. Your accountant reviews and approves. The agent removes the matching and typing, not the review.