Execution procedure
How WinClaw handles POS reconciliation
- 01Load POS closing data
Automatically extracts the day's closing data from OK POS.
- 02Auto-map to HQ settlement form
Converts POS columns into the HQ settlement form columns automatically.
- 03Detect discrepancies
Identifies mismatched items in the mapped values and highlights them.
- 04Request owner review
Sends discrepancy details via Telegram and waits for the owner's confirmation.
- 05Safe stop — wait before submit
Does not submit the settlement without owner approval.
- 06Record evidence
Saves the reconciliation comparison, approval log, and timestamps as an evidence package.
Reconciliation table
POS vs HQ form comparison (Mock)
| Item | POS value | HQ form | Difference | Status |
|---|---|---|---|---|
| Total sales | 1,850,000 KRW | 1,850,000 KRW | 0 | Match |
| Card payments | 1,620,000 KRW | 1,640,000 KRW | △20,000 KRW | Mismatch |
| Cash payments | 230,000 KRW | 230,000 KRW | 0 | Match |
| Discount | 45,000 KRW | 45,000 KRW | 0 | Match |
| Net sales | 1,805,000 KRW | 1,825,000 KRW | △20,000 KRW | Mismatch |
Evidence recorded
Every step is recorded
From data extraction to owner approval, every step is saved as an evidence package.
- evidence.json — timestamps for mapping, diff detection, approval request, and result
- pos-export-mock.csv — extracted POS closing data
- hq-recon-mapped.csv — auto-mapped HQ settlement form
- discrepancy-report.md — detail on 2 mismatched items
- pos-reconcile.play — script to replay the same task
Safety design
The owner always has final say
WinClaw only prepares the settlement. Submission happens only after explicit owner approval.
- No real POS account — runs on mock data only
- Settlement is never submitted without owner approval
- Owner reviews all discrepancy items directly
- Transaction details and account info are masked
- Safe stop before submit — no automatic confirmation