Manual Point-of-sale audit
The POS audit log tracks sensitive actions performed on the Swifto POS application — cash register openings and closings, ticket cancellations, discounts granted, corrections, cash movements, logins. Each action is timestamped and sent to the back-office for complete traceability of field activity.
Overview
The point-of-sale audit log records the sensitive actions performed by cashiers on the Swifto POS application — those that affect money, stock or the organization of the day. These events are sent to the back-office, where the manager and accounting review them to keep a faithful view of what happened at the counter.
Business goal
- Track sensitive field actions
- Identify the author, the register and the timestamp
- Detect abnormal cancellations and discounts
- Support internal control and audit
Target audience
- POS manager — monitors cashier activity
- Accounting — reconciles movements and Z reports
- Administrator — audits in case of anomaly
Position in the cycle
The audit complements register sessions and cash register statements (Z): it documents who did what and when, whereas the Z summarizes the financial totals.
Access and navigation
The audit log is viewed in the back-office, in the Cash Registers menu. The list can be filtered by period, by register (terminal), by cashier and by action type, to quickly find a specific event.
Combine the filters to target, for example, all discounts granted on a register over the past week.
What the audit tracks
Each event records the author (the cashier), the register concerned and the precise timestamp. Here are the sensitive actions tracked:
| Action | What is tracked |
|---|---|
| Register opening | Session start with the declared float. |
| Register closing | Session closing and issuing of the register Z report. |
| Ticket cancellation | Cancelled ticket, with the amount and the reason if any. |
| Discount granted | Discount applied to a sale and its amount. |
| Correction | Modification of a line or an in-progress ticket. |
| Cash movement | Cash in / cash out (deposit, withdrawal). |
| Login / logout | Access to the application by a cashier on a terminal. |
Always attributed to a named user — each action is tied to the logged-in cashier and their register, which makes accountability clear.
Viewing the audit
The list displays events from newest to oldest, with the date and time, the register, the cashier, the action and a detail. Each row can be read at a glance.
POS Audit Log — CAISSE-MENZAH1
| Date/time | Register | Cashier | Action | Detail |
|---|---|---|---|---|
| 12/07 08:31 | MENZAH1 | Salah B. | Opening | Float 100.000 TND |
| 12/07 10:14 | MENZAH1 | Salah B. | Discount | - 5.000 TND on ticket #142 |
| 12/07 11:02 | MENZAH1 | Salah B. | Cancellation | Ticket #148 · 18.500 TND |
| 12/07 13:20 | MENZAH1 | Salah B. | Movement | Cash out 50.000 TND |
| 12/07 19:05 | MENZAH1 | Salah B. | Closing | Register Z report issued |
The detail gives the amount, the ticket number or the reason depending on the action type, for a direct check without opening another screen.
What it's for
The audit log is an internal control tool: it helps spot unusual behavior and reconcile the reported field activity with the financial statements.
Internal control
Check that sensitive actions comply with your procedures.
Anomaly detection
Spot abnormally frequent cancellations or discounts.
Concrete example — several ticket cancellations close together on the same register, at the end of the day, deserve a check: the audit lets you find the author and the exact timestamp.
Synchronization
Audit events are produced in the field by the Swifto POS application. They are kept locally, then sent to the back-office upon reconnection (or in real time if the network is available). The back-office merely displays them: it does not create them.
Field origin
The action is recorded on the register at the moment it occurs.
Upload
Sent to the back-office upon reconnection, queued while offline.
Read-only
The back-office views the log, without modifying it.
Offline — even without a network, the register keeps logging actions; they are sent as soon as the connection is restored. See Swifto POS synchronization.
Business rules
Unmodifiable audit trail — events can be neither modified nor deleted; they form a reliable, tamper-proof record.
The source is the field — the audit is generated by the Swifto POS registers; the back-office is only a viewing point.
Duplicate-free reception — the same event sent multiple times (due to network retransmission) is only recorded once.
Faithful timestamping — each event carries the time of the action on the register, regardless of when it was sent to the back-office.
FAQ & Tips
Can I edit or delete an audit entry?
No: the audit trail is unmodifiable by design. It keeps its evidentiary value, even for the administrator.
A field action doesn't appear yet?
The register was probably offline: the event will be sent upon reconnection. Check the terminal's network status.
How do I find all of a cashier's discounts?
Use the cashier + action type "Discount granted" filters over the desired period.
Tip — a regular check
Check the log at the end of the day, alongside the cash register statements (Z): discrepancies are often explained by a tracked action.
Related pages · Cash Registers
