Bill check against the POS
Before anyone pays, 4u Check compares its bill with the POS check line by line. Payment is only allowed when they match. This protects both sides: a guest is never charged a wrong amount, and the restaurant never ends up with a bill that will not close.
flowchart TB
A["Guest opens the bill"] --> B["4u Check reads<br/>the POS check"]
B --> C{"Same items,<br/>same totals?"}
C -- yes --> D["Bill ready<br/>guests can pay"]
C -- no --> E["Payment held<br/>guest sees: please ask staff"]
E --> F["Table flagged on the dashboard<br/>plus a staff alert"]
F --> G["Staff see the reason and<br/>the POS total beside the QR total"]
G --> H["Staff fix it on the POS"]
H --> I["Staff press Check POS again"]
I --> BCommon reasons
Section titled “Common reasons”| Reason shown | Example |
|---|---|
| Someone changed the bill at the till | A waiter added a dessert or removed a drink on the POS |
| A line differs | A price or option is different on the POS |
| Totals differ | A charge is set up differently on the POS than in 4u Check |
| Part was paid outside 4u Check | A guest paid some at the counter |
| The check moved | The check was transferred to another table at the till |
| POS not reachable | The network is down at the restaurant |
Fixing it
Section titled “Fixing it”- Open the flagged table. The reason is shown in plain words with both totals.
- Fix the difference at the till, or confirm the POS is right.
- Press Check POS again. When the bill matches, the table is ready and guests can pay.
The “bill needs review” alert closes on its own once the table matches again.

