CBMS Integration for Restaurant Billing in Nepal: The 2026 Guide

Last updated: 21 September 2026 · Reflects the IRD CBMS notice of Baishakh 2083 and the FY 2083/84 budget.

Most articles about CBMS integration for restaurant billing in Nepal are written for shops. A shop scans an item, prints a bill and is done. A restaurant is messier: orders change after the KOT has gone to the kitchen, tables merge and split, a corporate guest wants a PAN bill, the power goes out in the middle of dinner service, and the menu price you print has to follow VAT rules that a supermarket never worries about.

This guide covers what CBMS integration actually changes inside a restaurant, who is required to do it in 2026, the restaurant-specific billing rules most software vendors skip over, and what the integration looks like technically. I build restaurant and retail billing systems in Kathmandu, so where it helps, I have added what I learned designing them.

What CBMS Integration Means in a Restaurant

CBMS stands for Central Billing Monitoring System. It is run by the Inland Revenue Department (IRD) and receives invoice data directly from approved billing software. Instead of the IRD seeing your sales only when you file a VAT return, it sees each invoice as it is issued.

For a restaurant, three things change in practice:

• The final bill becomes permanent the moment it prints. You cannot delete it, edit it or reprint it with different numbers. A mistake is corrected with a credit note, which is also reported to CBMS.
• Your software, not your cashier, does the tax maths. Taxable amount, VAT, discount and invoice number are fixed by the system before the bill is issued.
• Your sales register and the IRD’s record should match line for line. Month-end reconciliation becomes a check, not a reconstruction.

What does not change: waiters still take orders, the kitchen still gets its KOT, and guests still get a printed bill. CBMS does not see your recipes, food cost, staff data or supplier prices — it receives invoice-level sales data only.

Does Your Restaurant Need CBMS Integration in 2026?

The threshold has moved several times, and many vendor pages still quote old numbers. Here is the sequence as of September 2026:

The hospitality exception

Hotels, restaurants and canteens have historically been treated more strictly than general trade. Several IRD-enlisted software providers report that hospitality businesses must move to computerised billing at around Rs 5 crore of annual turnover, compared with Rs 10 crore for general businesses. That is the trigger for approved electronic billing; the CBMS real-time connection is the separate threshold in the table above. Because these figures come from vendor summaries rather than a single consolidated IRD notice, confirm your category with your servicing tax office.

Below the threshold? Read this before you decide to wait

• The threshold is falling, not rising. Rs 25 crore to Rs 20 crore to a proposed Rs 10 crore within roughly three years. A busy multi-outlet restaurant group can cross Rs 10 crore faster than owners expect.
• The queue is about to grow. Only 7,158 taxpayers were connected to CBMS at the end of FY 2081/82, against roughly 3.6 lakh VAT-registered businesses. When the lower threshold is enforced, vendors and IRD offices will be busy.
• Guests increasingly want registered bills. More on that in the customer-benefits section below.

How a Restaurant Bill Travels From Table to CBMS

This is the part shop-focused guides never explain. In a restaurant, several documents are printed before the tax invoice exists — and only one of them goes to CBMS.

Restaurant Billing Rules Most Vendors Skip

Vendor pages tend to say their software handles VAT and service charge “correctly” without saying what correct means. Here is what it means in 2026.

1. Menu prices must already include VAT

Nepal’s VAT Rules require the displayed selling price — tag price or menu price — to be tax-inclusive. After the Kathmandu District Court ruling in 2022, the Department of Commerce, Supplies and Consumer Protection told restaurants to fold VAT into menu prices, and it repeated in April 2026 that adding 13% VAT on top of the bill is prohibited. Restaurants overcharging diners have been warned of fines between Rs 2 lakh and Rs 3 lakh under the Consumer Protection Act.

That means your POS has to work backwards: take the menu price, extract the VAT, and report the taxable amount and VAT separately to CBMS. The formula is simple: taxable amount = menu price ÷ 1.13, and VAT = menu price − taxable amount.

The guest pays Rs 1,356 — exactly what the menu said. CBMS receives Rs 1,200 taxable and Rs 156 VAT. If your software instead adds 13% on top and bills Rs 1,532.28, you are overcharging the guest and reporting numbers that do not match your menu.

2. Service charge in 2026

For years Nepali restaurants added 10% service charge and then 13% VAT on top of that, so guests paid 24.3% more than the menu price. That practice is effectively over. The Supreme Court annulled the Labour Act provision behind compulsory service-charge distribution in January 2023, and consumer-protection authorities say VAT and service charge must be built into the menu price rather than added to the bill.

What this means for your billing software:

• Turn off any automatic “service charge” line added on top of menu prices.
• If you share a portion of revenue with staff, handle it in payroll or internal accounting, not as a separate charge on the guest’s invoice.
• If an old POS template still shows “Service Charge 10%” and “VAT 13%” below a subtotal, update it before a consumer complaint does it for you.

3. KOTs, BOTs and pre-bills are not invoices

The common failure here is a POS that assigns the tax invoice number at the pre-bill stage. Then, when the guest adds a coffee, the cashier either edits a numbered invoice (non-compliant) or voids it and creates a gap in the sequence (a red flag in an audit). Numbering should happen only at settlement.

4. Split bills, merged tables and transfers

• Split bill: each payer gets a separate tax invoice with its own number, and each one is reported to CBMS. The items or amounts are divided before settlement.
• Merged tables: merge the orders, then settle once. One invoice.
• Table transfer: an order-level change. No invoice impact if done before settlement.
• Split after settlement: the guests change their minds after the bill is printed. That is a credit note against the original plus new invoices — which is why a good POS asks “one bill or separate?” before settling.

5. Voids before billing vs credit notes after

Restaurants void items constantly: wrong dish fired, guest changed their mind, item out of stock. Before settlement, a void is an order cancellation — log it with the user, the time and a reason, and give managers a daily void report. After settlement, the only route is a credit note that references the original invoice number, states the reason, and is transmitted to CBMS as a bill return.

A high void count before billing is an operational problem. A high credit-note count after billing is a compliance signal the IRD can see. Train cashiers so that corrections happen at the order stage wherever possible.

6. Discounts, complimentary items and staff meals

• Discounts should reduce the taxable value, with VAT recalculated on the discounted amount, as in the table above. Show the discount clearly on the invoice.
• Complimentary items should still pass through the POS with manager approval and a reason, so stock and food cost stay accurate. Agree with your accountant how comps are shown on the invoice and treated for VAT; do not simply skip ringing them up.
• Staff meals belong in an internal consumption record, not as fake zero-value sales invoices that clutter your CBMS data.

7. Abbreviated invoices and PAN bills for corporate guests

Under the VAT Rules, high-volume retail businesses including restaurants may issue an abbreviated tax invoice for transactions up to Rs 10,000, showing VAT as inclusive and without requiring the buyer’s PAN. If the guest asks for a full tax invoice, you must issue one.

In practice, corporate diners and office lunches usually want a full invoice with their company name and PAN so they can claim input VAT. Your POS should let the cashier add buyer name and PAN at settlement in a few seconds — the buyer PAN is one of the fields transmitted to CBMS.

8. Credit accounts and corporate tabs

If a company runs a monthly tab with you, the invoice is still issued when the meal is supplied, not when the company pays at month-end. Record the payment against the invoice later as a receivable. Batching a month of meals into one invoice on the 30th puts your CBMS dates out of line with when the sales actually happened.

Power Cuts, Internet Drops and the Sync Queue

Dinner service cannot stop because the fibre line dropped. There are two legitimate designs in the Nepali market:

• Offline-first: the POS bills locally, keeps the invoice series intact, and transmits queued invoices to CBMS when the connection returns.
• Cloud-only: billing needs a connection, but any device with mobile data or a hotspot can take over as the counter.

Competitor guides stop there. The question that actually matters for a restaurant is: how do you know the queue has cleared? Offline billing defers the CBMS obligation; it does not remove it. Before you choose a system, check that it gives you:

• A visible “pending sync” count on the cashier or manager screen
• Automatic retries with a clear error when something fails permanently (wrong credentials, rejected data)
• A daily sync report you can compare against the CBMS portal
• Protection against the same invoice being sent twice when a retry happens
• Multi-terminal support where two counters billing offline cannot produce clashing invoice numbers

Why CBMS Bills Matter to Your Customers Now

CBMS used to be purely a compliance cost. Two consumer-side schemes are changing that, and restaurants sit right in the middle of both:

• 10% VAT refund on digital payments. The refund for paying by QR, card or wallet is currently notified for lodging, restaurant and bar businesses. It depends on an electronic invoice. The FY 2083/84 budget promises to widen it to all digital purchases, but the expanded procedure had not been published as of this update.
• The bill lottery (Taxpayer Incentive Gift Program, 2083). Consumers who collect proper bills can enter draws. Automatic entry depends on the seller’s billing being connected to CBMS — at a non-connected restaurant, the guest has to register the bill manually.

For a restaurant, that turns a CBMS-connected bill into something guests actively value. It also means a faded thermal print, a missing PAN or an unclear invoice number is now a complaint risk as well as a compliance risk.

How the Integration Works Technically

This section is for restaurant owners who want to understand what their vendor is doing, and for developers building restaurant POS systems. Neither competing article covers it.

Two endpoints, one set of credentials

• Invoices are posted to the CBMS bill endpoint, and credit notes or sales returns to the bill return endpoint, as JSON.
• Authentication uses the restaurant’s IRD taxpayer portal user ID and password, and the seller PAN in the payload must be the restaurant’s PAN.
• A successful submission returns response code 200. Anything else should be logged, retried where sensible and surfaced to a manager.
• You can verify what reached the IRD by logging in to the CBMS external portal and opening the sales register sync report.

What each transmission carries

In plain terms: the seller PAN, the buyer’s name and PAN where given, the fiscal year, the invoice number and date, the total sale, the taxable amount and the VAT, other tax fields where they apply, and a flag saying whether the submission was real-time or delayed. For a credit note, the reference to the original invoice and the reason for return are included.

The restaurant-specific traps

• Password changes break the sync. If the accountant rotates the IRD portal password, the POS starts failing silently unless it alerts someone. Put “update POS CBMS credentials” on the password-change checklist.
• Multi-outlet groups under one PAN share one set of CBMS credentials but need separate invoice series per outlet or terminal that never collide.
• Fiscal-year rollover. Numbering restarts every Shrawan. Tables that open on the last night of Ashadh and settle after midnight need a clear rule for which fiscal year the invoice falls in.
• Idempotency. A retry after a timeout must not create a duplicate record. Keep the invoice number as the unique key and store the CBMS acknowledgement against it.
• Store the credentials encrypted. The POS holds the keys to the restaurant’s tax account. Treat them accordingly.

Lessons From Building a Restaurant POS

I built DinePosAi, a restaurant management system for Nepali restaurants with separate Admin, Waiter and Kitchen roles and a real-time kitchen display. I have also designed an offline-first billing system for Nepali retail where the counter must keep working with no internet. A few things from that work that I would pass on to any restaurant owner:

• Separate the order from the invoice in the data model. The first design decision in a restaurant POS is that an order is a living object and an invoice is a frozen one. Once that separation is clean, KOT changes, table transfers and split bills stop being compliance problems.
• The kitchen screen is where most voids start. When the kitchen can mark an item unavailable in real time, waiters stop taking orders that will be cancelled later, and your pre-bill void count drops.
• Offline mode needs a local numbering authority. The hardest part of offline billing is not saving the bill; it is guaranteeing that two devices never issue the same invoice number while disconnected. Ask your vendor how they solve it.
• Cashiers need one screen, not three. If adding a buyer PAN, splitting a bill or applying an approved discount takes more than a few taps during a Friday rush, staff will find workarounds — and workarounds are what break compliance.

Questions to Ask a Restaurant POS Vendor About CBMS

Before shortlisting, check that the product is on the IRD’s enlisted list — our IRD-approved billing software list in Nepal explains how to verify it. Then ask:

Frequently Asked Questions

Is CBMS integration mandatory for all restaurants in Nepal?

No. As of September 2026, CBMS real-time integration is mandatory for businesses with annual turnover above Rs 20 crore, and the FY 2083/84 budget announced a reduction to Rs 10 crore for businesses issuing electronic invoices. Hospitality businesses are widely reported to face a lower trigger for computerised billing itself. Smaller restaurants can integrate voluntarily.

Are KOTs sent to CBMS?

No. Kitchen and bar order tickets are internal production documents. Only the final tax invoice issued at settlement, and any credit note issued against it, are transmitted to CBMS.

Can a restaurant add 13% VAT and 10% service charge on top of menu prices?

Consumer-protection authorities say no. Menu prices must be inclusive of VAT, and adding VAT and service charge on top of the bill has been declared prohibited, with fines reported between Rs 2 lakh and Rs 3 lakh for overcharging. Your POS should extract VAT from the inclusive price.

How do I cancel a restaurant bill after it is printed?

You cannot delete or edit an issued invoice. Issue a credit note that references the original invoice and records the reason. The credit note is sent to CBMS as a bill return, and the original invoice stays on record.

What happens to CBMS sync during a power cut or internet outage?

An offline-capable POS keeps issuing invoices locally and sends the queued invoices to CBMS when the connection returns. Check that your system shows the pending queue and alerts you if any invoice fails to sync.

Does each split bill need its own invoice?

Yes. When a table pays separately, each payer receives a separate tax invoice with its own number, and each invoice is reported to CBMS.

Can my restaurant issue an abbreviated bill instead of a full tax invoice?

Under the VAT Rules, restaurants may issue an abbreviated tax invoice for transactions up to Rs 10,000, with VAT shown as inclusive and no buyer PAN required. If the guest requests a full tax invoice, you must provide one.

Why would a guest care whether my bill is CBMS-connected?

Because the 10% VAT refund on digital payments currently applies to restaurants, bars and lodging and depends on an electronic invoice, and automatic entry into the government bill lottery depends on the seller being connected to CBMS.

The Bottom Line

CBMS integration for restaurant billing in Nepal is less about the connection to the IRD and more about getting the restaurant workflow right before the invoice is issued. Keep orders flexible and invoices frozen, extract VAT from inclusive menu prices, drop the add-on service charge, issue one invoice per payer, correct mistakes with credit notes, and make sure you can see your sync queue. Get those right and the CBMS part runs quietly in the background.

If you are still at the approval stage, read how to get IRD approval for billing software in Nepal first. If you are comparing systems, start with the IRD-approved billing software list and put every shortlisted vendor through the offline demo above.