IRD-enlisted billing, filed to CBMS on its own.

Yes. TableSathi is enlisted with the Inland Revenue Department under the Electronic Billing Procedure 2074 — enlistment number 8301671 — which is the listing the department maintains for software permitted to issue electronic invoices. It is worth being precise about the words, because vendors use them loosely: enlistment covers the software, while registration for PAN or VAT is something your own business does directly with the IRD. TableSathi being enlisted does not register your cafe; it means the bills your cafe issues come from software the department has listed, and that those bills can be filed to CBMS.

The turnover thresholds are lower for hospitality than for business generally: NPR 5 crore in annual turnover for hotels, restaurants and canteens, against NPR 10 crore for a general business. Below the threshold you may still use enlisted software and many cafes choose to; above it, issuing invoices from software that is not enlisted is the offence. Most cafes on TableSathi are below the threshold today, which is why CBMS filing is off by default and enabled per cafe — we turn it on with you when your turnover, or your accountant, says it is time. Confirm your own position with the department or your accountant rather than relying on any vendor page, this one included.

CBMS is the Inland Revenue Department’s Central Billing Monitoring System — the service that receives electronic invoices as they are issued, so the department sees the bill at roughly the same time your customer does. TableSathi sends each issued invoice and each credit note, with the seller PAN, the fiscal year, the invoice number and the amounts. It does not send your menu, your costs, your supplier prices or your staff records; only the document itself. Filing happens after the bill is printed, so the customer is never kept waiting at the counter for a government API.

No, and it should not be. Once an invoice is issued it is a tax record, so TableSathi will not let it be edited or removed — including by you. The lawful correction is a credit note, which reverses the original as a separate document rather than rewriting history. In TableSathi a credit note carries its own number sequence, prints as its own document, and is filed to CBMS against the invoice it corrects. A credit note is also held back until the invoice it references has itself been filed, because filing a note against an invoice the department has not yet seen is indistinguishable from a genuine failure.

The bill prints and the sale completes, exactly as normal. The filing record is written in the same database transaction as the invoice, so nothing can be sold without a record of it existing; only the network call to CBMS is deferred. A sweep retries pending filings at 1, 5 and 15 minutes, then every hour until they land, so a morning with no connection resolves itself once the line is back with nothing for you to do. Anything genuinely ambiguous — a request that may or may not have been recorded — is set aside for a person to check rather than re-sent, because a duplicate credit note is a harder problem than a late one.

For filing your returns, TableSathi gives you what the sales side needs: the sales register (बिक्री खाता) and the purchase register for a Bikram Sambat tax period, exported as a pair because they are filed as a pair, plus the filing report for a fiscal year. What TableSathi is not is a general ledger — it does not keep your full books, run payroll, or handle non-cafe income, so a business with a broader set of accounts will still have an accountant and may still have accounting software. The difference is that the restaurant-side numbers arrive already correct and already filed, instead of being re-typed from a pile of bills.