For: the project lead and every stakeholder

What does each person need to see, and decide?

The starting point for v2. Four assumed roles, what each would want to see, and the decisions the August data puts in front of them.

Finance officer

assumed

Wants to see: File checks and the row ledger; aggregator table; exceptions grouped by pattern
Decides: Re-upload or accept a run; explain items
Pages: Upload · Aggregators · Review

Finance manager

assumed

Wants to see: Patterns with suggested reasons; fees against contract; cash observations
Decides: Accept or send back; confirm a loss; close the month; set fee rates
Pages: Review · Fees · Cash · Reports

Store manager

assumed

Wants to see: Own items by day and shift; cash observations; delivery operations
Decides: Add context; agree a deposit routine; ask for staff refreshers
Pages: My store · Cash · Operations

Admin (HR liaison)

assumed

Wants to see: HR report: confirmed losses by POS user, with evidence; download log
Decides: Download the HR report; record the hand-over to HR
Pages: HR report

Leadership

assumed

Wants to see: One page: what each aggregator earned and cost; what is unexplained
Decides: Renegotiate or grow aggregators; accept the open value; set v2 priorities
Pages: One-page · Patterns

Decisions needed

Each row says what the data shows, who decides, and the options. Answers become the v2 spec; until then the prototype shows a reasonable default.

	Decision and what the data shows	Who decides	Options	Default for now
D1Q3	What should v1 be for first?The data supports five outcomes: missed payments, inter-punches, fee checks, cash observations (audit only), and sales patterns	Project lead, client	All five as views (this prototype) · pick two or three for v2 depth	Keep all five as views; go deep on review and reports assumed
D2Q9	Who does reconciliation today, and can they walk us through it?Every role in this pack is assumed (tagged assumed)	Project lead	Name a person · keep assumed roles	Assumed roles assumed
D3new	Is the Glovo KES 385 difference a price list gap?327 Glovo orders are exactly KES 385 lower on the POS than in Glovo (more at 2× and 3×)	Finance manager, store	Price list out of date · packaging or bag fee · something else	Shown as one pattern to explain as a group assumed
D4Q8	Where is Glovo's commission, and what rates did we sign?Glovo's export has no fee columns; other rates are August averages	Project lead, client	Upload Glovo's invoice · enter contract rates	Expected rate = August average assumed
D5new	Was the KES 250K order on 26 Aug really paid in cash?Observed cash difference is KES 373K; one take-away sale of 500 meals explains KES 250K of it. Cash reconciliation is outside the first version; may we show the audit-only cash view?	Finance manager, store	Show the audit view · hide cash until a later version	Audit view: facts only, no matching assumed
D6Q5	Will each upload include the bank statement?Without it the trail stops at what providers report (M-Pesa sweeps: KES 8.37M)	Client	Yes, monthly · later	Trail stops at providers assumed
D7new	What are the M-Pesa and card records with no POS sale?321 M-Pesa (KES 347K) and 175 card payments are not on the POS	Finance officer	Other M-Pesa tills on the same number · sales not rung up · timing	Listed as Missing POS assumed
D8Q6	Who receives the HR report, and how is the hand-over recorded?The HR report lists confirmed losses only, by POS user, for HR review; the system never deducts pay (s.19)	Client, with HR advice	Admin downloads and logs the hand-over · later: email or payroll link (separate requirement)	Admin download, hand-over logged assumed
D9Q4	How often, and which branches first?Multi-branch from the start; August has one branch's POS data, and the meal-card export already lists 41 other branches	Project lead, client	Monthly · weekly (matches Uber payouts) · daily; which second branch to test with	Monthly; a second branch's files to test the branch rules assumed
D10Q7, Q10	Where will it run, and how long do we keep files?Uploads hold customer phone numbers and names (masked after cleaning)	Project lead	Hosting choice · retention period	See System Design assumed
D11new	Who confirms the branch map?Each provider account (delivery-app store ID, M-Pesa till number, card terminal) must be tied to one branch before matching	Client, HQ finance	HQ finance supplies it · read from provider portals	Mapped to Hurlingham, tagged assumed assumed

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.