Application path narrative
A written walk of the live till: each prompt, each skip, each supervisor code. We attach ticket numbers from the walk so a later reviewer can replay the same motion. This paper is the core of a control walkthrough.
Working papers
Every engagement produces a set of papers you can file. This page is the map of that set—so you know what you are requesting before we draft the letter.
A written walk of the live till: each prompt, each skip, each supervisor code. We attach ticket numbers from the walk so a later reviewer can replay the same motion. This paper is the core of a control walkthrough.
A sample of tickets rebuilt from the product sheet and lined up with till printouts. Each mismatch names the field—rate, fee, rounding, campaign code. Request this with an interest and fee engine review.
Approve, refer, decline, and override cases with the inputs that still exist. If the person who overrode cannot be named, that absence is the finding. See credit decision trail testing.
Tickets the store booked against funding lines that arrived, arrived net, or never arrived. Reconciling items are listed with store and shift where still visible. Pair with merchant settlement reconciliation.
Screen inventories, consent copies, and a short catalogue of voids, reversals, and force-posts. These annexes sit behind the narrative so the file stays readable. Related work: disclosure audit and exception testing.
Tell us the product and whether we can sit at a till. We will say which papers fit and what the letter will cost to produce.