Following a settlement file from capture to the bank
A single capture can pass through batching, fees, and a file format before the acquirer sees it. The audit question is whether anyone can still show the path.
Take a familiar item: a card capture that must appear in tonight’s settlement. In many Malaysian stacks the amount begins at the terminal or the checkout, is authorised, is captured later, is batched with a fee rule, and is then shaped into the file the acquirer expects.
Each hop is a chance for a silent change. A partial capture that the application records as full. A currency conversion applied twice. A filter that drops zero-amount voids in one hop and keeps them in the next. A manual “plug” entered because yesterday’s reconciling item was never cleared.
When we trace a figure we ask for the file that actually left, not a rebuilt file from a later date. We compare record counts and control totals at each hop. We read the fee and routing rules in force on the run date, not the rules as they exist today. If the application overwrites history, that fact itself becomes part of the letter.
Operations teams that keep a trail pack from a prior review usually close faster. Teams that treat the payment application as a black box spend settlement week reconstructing the same path under time pressure.