Home / Help Center / pos-app-restaurant / rest-finance / Comp Register
🎁 rest-finance

Comp Register

Comp Register is a dedicated, restaurant-specific log for complimentary meals and courses — richer than the general Void & Comp Log, capturing table, covers, guest name, who requested it, the comp reason/type/description, and a full approve/reject workflow with a per-reason cost breakdown sidebar.

📍 Menu path: Finance & Payments → Comp Register
👤 Who uses it: All roles with the Billing feature enabled

Overview

Distinct from the general Void & Comp Log: Comp Register is restaurant-only and captures more context per entry — covers (guest count), guest name, who requested the comp, and a separate comp type (Starter, Main Course, Dessert, Beverages, Full Meal, Wine/Alcohol, Cake/Add-On, Custom).

Status flow: Pending Approval → Approved or Rejected (via the inline Approve/Reject buttons for pending entries), and a separate Applied status exists in the data model for comps that have been credited to a bill, though this page does not itself change a comp to Applied.

The sidebar "Cost by Reason" panel ranks every Reason used (from a fixed list — Birthday Celebration, Anniversary Celebration, VIP Goodwill, Guest Complaint Resolution, Quality Issue — Food/Service, Long Wait Apology, Wrong Order Delivered, Staff Error, Marketing/Influencer, Corporate Hospitality, Manager Discretion) by total value across all comps, not just the filtered list.

A Print action generates a printable report of the currently filtered comps plus the full by-reason cost breakdown, useful for a manager or owner review.

Before You Start

Step-by-Step Guide

1 Log a complimentary meal

  1. Open Finance & Payments → Comp Register and click "+ Log Comp".
  2. Enter Date, Table (required, free text — e.g. "T-5", "Bar", "Private Room"), Covers, and Guest Name.
  3. Pick a Reason and Comp Type, add a Description (e.g. "Chocolate fondant + candle"), and enter the Value in ₹ (required, must be greater than 0).
  4. Enter Requested By (required — staff name and role) and, if already approved, Approved By and Status.
  5. Add Notes if needed and click "Log Comp".

2 Approve or reject a pending comp

  1. Find a row with the "Pending Approval" badge and click "Approve" in its action column.
  2. Type the manager's name in the inline field and confirm (✓) — the row updates to Approved with that manager's name shown underneath the requester.
  3. Alternatively click "Reject" to mark the comp Rejected without recording an approver.

3 Review cost by reason and print

  1. Check the "Cost by Reason" sidebar to see which reason is driving the most comp value overall.
  2. Use the search box, status chips, and date filter to narrow the main table, then click "Print" for a printable report of the filtered comps plus the full by-reason totals.

Every Field & Button, Explained

Field / ButtonWhat it does
TableRequired free text — table number, "Bar", "Private Room", etc.
CoversNumber of guests at the table for this comp; defaults to 2.
Guest NameOptional — useful for repeat VIP guests.
ReasonRequired, chosen from a fixed list covering birthdays, VIP goodwill, complaint resolution, quality issues, apologies, staff errors, marketing, corporate hospitality, and manager discretion.
Comp TypeWhat was comped: Starter, Main Course, Dessert, Beverages, Full Meal, Wine/Alcohol, Cake/Add-On, or Custom.
Value (₹)Required, must be greater than 0 — the cost basis used in KPIs and the Cost by Reason sidebar.
Requested ByRequired — the staff member (with role) who asked for the comp.
Approved ByFilled automatically by the inline Approve action, or can be typed directly when logging/editing a comp that is already approved.
StatusPending Approval, Approved, Rejected, or Applied.

Tips & Best Practices

Troubleshooting & FAQ

I can't save a new comp record.
Table, Requested By, and a Value greater than 0 are all required — the form will show a toast naming whichever one is missing.
A comp still shows Pending Approval after I edited it.
Editing a record does not automatically change its Status — use the Approve/Reject buttons for pending records, or explicitly set the Status field in the edit form.