Working with KKM requires a configured active cash register and permission to perform cash operations. Open the shift using your own account: the employee who opens it becomes responsible for the shift. In PEP mode, this also determines who signs the package before closing.
Before opening
- Check the selected workplace and office. Find the dashboard's “Cash register” widget and verify the device name. The device is selected automatically; there is no selector inside the widget.
- If you see “Cash register is not configured” or an unavailable message, check the connection and device assignment first. For plugin connections, the KKM Server extension must also be active in this browser.
- If the shift is already “Open”, check the cashier. Do not use another cash register to open a second shift: an office may have only one active cash shift at a time.
Open and verify the shift
- Click “Open shift”. In the “Open shift as {name}?” confirmation, check your full name. It comes from your account; there is no separate cashier name input.
- Confirm and wait for the result. The application must save the opening after the device command. Do not click again while the request is running.
- After the widget refreshes, check “Open” and the correct cashier. Under “Accounting” → “Cashier shifts”, find the record by office, device and the “Opened” period. Open it and check the number, employee, opening time and active status.
If a shift is opened again
- Opening an already active shift on the same device returns the existing record without creating a second shift.
- A closed unsigned shift on the same device may reopen with its previous number on its closing calendar day in the office's time zone. Any prepared unsigned package is cancelled; the employee reopening it becomes responsible.
- After the first signature, the previous shift cannot reopen. A normal opening creates a new shift with a new number. Signed shifts are corrected through a separate process.
If an error or state mismatch occurs
The physical cash register may have opened even if the application did not save the result. A state mismatch warning requires checking the device and shift record. No warning does not prove success. Save the device name, office, attempt time and error; contact the responsible person before new commands. Do not create another shift or repeat monetary actions just to clear the message.