August 2026 / Settings
Draft run · not closedPrototype v0.2 · real August data, masked
For: HQ admin · J8
Which reasons can people choose?
Reconciliation reasons and other settings, managed without code changes.
Decisions this view supportsThe starting list of reasons · Who may change settings
Add reasonChanges need a second admin's approval and are logged
Reconciliation reasons
The dropdown on every explanation and manual match. Grouped so matching reasons stay apart from stock and sales adjustments. A reason is deactivated, never deleted, so past records keep their wording.
| Reason | Group | State | Used | |
|---|---|---|---|---|
| Inter-punch | Matching | Active | 0 | Edit Deactivate |
| Timing | Matching | Active | 0 | Edit Deactivate |
| Price or packaging difference | Matching | Active | 0 | Edit Deactivate |
| Duplicate payment | Matching | Active | 0 | Edit Deactivate |
| Overpayment | Matching | Active | 0 | Edit Deactivate |
| Underpayment | Matching | Active | 0 | Edit Deactivate |
| Payment allocation correction | Matching | Active | 0 | Edit Deactivate |
| Wrong branch allocation | Matching | Active | 0 | Edit Deactivate |
| Other | Matching | Active | 0 | Edit Deactivate |
| Returns | Sales adjustment | Active | 0 | Edit Deactivate |
| Spoilage | Sales adjustment | Active | 0 | Edit Deactivate |
| Damaged goods | Sales adjustment | Active | 0 | Edit Deactivate |
| Shortage or missing items | Sales adjustment | Active | 0 | Edit Deactivate |
| Sales adjustment | Sales adjustment | Active | 0 | Edit Deactivate |
Other settings hereUsers and roles (home branch, HQ or branch); the branch map; expected fee rates; the amount tolerance (KES 1) and M-Pesa window (15 minutes).
Built from the pipeline run of 10 Oct 2026 (Payments.xlsx + POS export). Customer details are masked and cashiers are shown as pseudonyms. Items tagged "assumed" rest on assumptions in the spec.