One reference. Several operational feeds.

Finance and support need to follow a transaction across payment, accounting and webhook records. This concept brings the related evidence into one read-only investigation, grouped by source.

My contribution

I led product and interaction direction across statements, investigations and access, collaborating with Kenneth Fallon. This is a concept redesign, not a deployed replacement.

Keep investigation separate from action

An operator begins with a payment reference, reviews matching records across feeds and opens the relevant detail. Grouping results by source preserves their context rather than flattening different records into one ambiguous status.

Make statement work inspectable

The statement workspace combines search, merchant records, generation, paid and published states, and bulk actions. Scope and permission boundaries sit beside the work they affect.

Explain permissions in product language

Access controls group the permissions an operator needs, expose change states and provide reset paths. The proposal aims to make configuration understandable before an operator commits it.

Outcome and capture notes

The concept gives stakeholders a concrete workflow to evaluate. The gallery uses actual React/MUI repository components with fictional records, captured 1 November 2026. Production rollout, live enforcement and measured operational improvements are outside this case. Platform: React, TypeScript, AWS and Cognito.