A Moroccan restaurant or café meets three very different files: an individual’s daily meal, a company’s meal and a pre-booked event. The first normally ends with a sales receipt; the second often requires an invoice in the company’s identity; the third begins with an offer, may involve a receipt and ends with an invoice reflecting actual service. Using the same ‘table total’ without distinguishing those flows creates misidentified customers, lost deposits and tax that cannot be reconciled.
In brief
- The daily-service receipt should carry the heading and required lines and remain tied to order and payment.
- For a company, create its record and issue the invoice from the real sale or order without doubling the bill.
- Configure tax by validated product or service; do not correct only the global PDF total.
- A private event needs offer, count, menu, timings, terms, changes, acceptance and reconciliation of receipts.
- BelloPOS Pro combines restaurant till and documents and invoices the deposit, but does not reserve a room or capacity.
1. Choose the record by customer
The word bill does not identify the buyer. Staff must distinguish an individual, an employee paying for a company and an event organiser. Read the receipt-field and invoice-field guides, then validate heading and rates with your accountant.
| Situation | Main record | Control |
|---|---|---|
| Individual at counter | Sale receipt | Heading, lines, tax, total and payment |
| Company table | Bill then linked company invoice | Legal name, address, ICE and requested reference |
| Company delivery | Order, delivery evidence and invoice | Address, quantity, time, receipt and payment |
| Private event | Quotation/order, service record, final invoice | Count, menu, space, timings, options and changes |
| Cancellation or correction | Credit note or controlled record | Original, reason, amount, tax and relevant stock |
A restaurant receipt is not a complete company invoice where the buyer identity and required details are absent. Conversely, issuing an invoice must not create a second kitchen order or payment. Always begin with the order or sale that genuinely served the table.
2. Tax, menus and discounts: preserve the lines
A basket may contain items treated differently under applicable rules. Software adds what you configure; it does not legally choose rates for you.
- Product: Assign each item or category its validated treatment. Do not force one rate by changing the final total alone.
- Menu: Decide consistently whether it is one fixed-price item or separate lines, matching production, printing and validated tax treatment.
- Extra: Extra cheese, side, service or delivery: show it so the total and margin can be explained.
- Discount: Identify authorisation, base and reason. A global discount must not conceal a free, cancelled or returned item.
- Tip: Define till and distribution procedure distinct from sales and tax, with professional validation.
- Void: Keep who cancelled, when, why and whether before or after preparation/payment. The activity log supports control, not automatic blame.
Our restaurant POS guide covers service and the cash-variance guide reconciles voids, discounts and payments. The invoice should carry controlled service data rather than a reconstruction made at week end.
3. Three practical flows
Write a short procedure for each so an invoice request does not become an improvised exception.
- Daily sale: open table or basket, enter items, send preparation, take payment once, close and print receipt.
- Company invoice: identify the company before close where possible, then issue the invoice linked to the paid order with ICE, reference and same payment.
- Recurring company meal: agree ordering, authorised people, limit, address, receipt evidence, invoicing frequency and due date.
- Private event: create a quotation with date, space, count, menu, drinks, staff, equipment, timings, options, validity and cancellation.
- Every count or menu change receives acceptance and price effect instead of being hidden in a kitchen note.
- On event day the kitchen follows the last version and a customer representative confirms service and reservations.
- The final invoice reflects what was supplied, then allocates receipts under validated treatment and shows an explainable balance.
| Flow | Main risk | Control record |
|---|---|---|
| Individual | Wrong item, discount or payment | Receipt and close |
| Company in restaurant | Recreated invoice and double sale | Source order + company record |
| Company delivery | Disputed quantity or recipient | Order + receipt evidence |
| Event | Forgotten count, option or receipt | Accepted version + final record |
Company example: a table pays MAD 2,760 by card and requests an invoice to Atlas Formation. The PDF should carry the same lines, tax, total and payment with Atlas Formation’s identity. A second MAD 2,760 sale doubles revenue. An event additionally separates offer, changes and receipts.
Deposits and reservation: know the boundary
BelloPOS can preserve quotations, orders, deliveries, invoices, payments and balances, while its restaurant module handles tables and kitchen. It does not currently provide a specialist flow that automatically reserves a room, generates each deposit invoice, applies a schedule and settles the final invoice. Organise calendar, capacity, deposit records and accounting validation separately.
4. How BelloPOS handles the workflow
Lite covers till, catalogue, tax by product, customers, stock, receipts and history. Go adds invoice export, electronic invoicing, customer credit, roles, activity log, backups and analytics. Go may cover a counter café with occasional company invoices.
Pro adds restaurant module, tables, kitchen display, local kitchen and portable-till web apps, plus quotations, orders, deliveries, invoices, credit notes and accounting bridge. It fits a restaurant combining service, companies, events and accountant files.
The product runs offline and the current plans are one-off payments. No plan chooses tax rates or replaces event planning. Compare features on the BelloPOS pricing page.
5. Daily close and event control
Two short controls are better than a monthly reconstruction.
| Frequency | Control | Expected result |
|---|---|---|
| Every service | Orders, voids, discounts, payments and receipts | Explained till |
| Every company invoice | Source order, identity, total and payment | No double sale |
| Every event | Version, count, menu, receipts, changes and balance | Complete file |
| Weekly | Credit invoices and payments | Current customer statements |
| Monthly | Sales, credits, VAT and cash | Verified accountant export |
Mistakes to avoid
- Creating a second bill to provide the company invoice.
- Using the diner’s name instead of the legal company.
- Applying one rate to the total without checking items.
- Changing a closed bill only in the PDF.
- Confusing event receipt, discount and final payment.
- Keeping the menu change only in the kitchen notebook.
- Billing the estimate after another count was accepted.
- Presenting the restaurant module as complete event management.
Frequently asked questions
Should a restaurant provide a receipt?
For the relevant retail sale, provide a receipt with applicable details and retain the sale in history. Validate the model for your operation.
How is a company invoice made after a meal?
Find the order or sale, confirm the company record and issue the linked invoice with the same lines, total and payment, without a second sale.
Can one bill contain several rates?
The software accepts a rate per product and can mix them. Legal rate selection must be validated; do not copy a generic configuration.
How is a private event invoiced?
Begin with an accepted offer, track changes and acceptance, then invoice what was supplied and allocate receipts under the validated treatment.
Does BelloPOS automatically manage deposits?
No, not as a specialist event workflow. It handles payments, balances and documents, while you define the deposit record, calendar and treatment.
Which plan contains the restaurant module?
Pro. Lite and Go retain till functions; Pro adds tables, kitchen and local apps together with commercial documents and accounting.
What to take away
Restaurant invoicing becomes simple when the team first identifies the kind of sale. An individual receives the service receipt, a company receives an invoice from that same order and an event preserves offer, changes, acceptance and balance. Technology connects records and prevents re-entry; the restaurant remains responsible for validated rates, capacity, reservation and deposit treatment.
Sources
The figures and rules quoted above come from these pages, read on the date given in the article.
- 2026 General Tax Code, especially articles 145 and 211, read 29 August 2026
- BelloPOS receipts and invoices, read 29 August 2026
- BelloPOS quotations, orders, deliveries, invoices and credit notes, read 29 August 2026
- BelloPOS prices and plan boundaries, read 29 August 2026
Connect service, receipt, company invoice and event
Explore BelloPOS invoicing and the restaurant module, then compare Go and Pro for B2B sales and events.
Read next
Other practical guides on the same subject: