Reconstructing a Transaction Timeline From Mixed Sources

Source files are rarely tidy. Bank PDFs run across page breaks, exchange receipts arrive as separate emails, contracts describe an intention without confirming settlement, and personal correspondence often references a payment in a way that does not match the bank's wording. The first task is to isolate the discrete events buried inside each document and record them in a common format.

Where a transfer notice expresses intent and a separate receipt confirms settlement, the two are kept apart. Formal settlement data carries the weight; intent records carry context. The file shows both, with the distinction visible — not collapsed into a single line that hides which one is doing the work.

International transfers routinely cross time zones and book on different calendar days at either end. Execution timestamps and settlement timestamps add another layer; a trade can execute on Friday and settle on Tuesday in a way that looks like two separate events if read without care.

All timestamps are normalised to a single UTC reference, with the original local time preserved alongside. Execution and settlement are recorded as separate marks on the same transaction rather than two transactions, which prevents the same money appearing to move twice.

Cross-border transfers usually involve a conversion, and the rate is not always written on the receipt. The sender's debit and the receiver's credit then differ, sometimes by a small spread, sometimes by a larger one if an intermediary clipped a margin nobody mentioned.

The file records both the sent and received amounts exactly as the sources state them and notes the variance. Where the rate is explicit, it is included. Where it is not, the gap is left visible rather than back-calculated from a market rate that the parties may or may not have actually used.

Wire transfers often pass through correspondent banks, intermediary clearers and internal entities before reaching the named beneficiary. The receipt the user has in front of them may name a clearing house rather than the ultimate counterparty, which is a routine artefact rather than a sign of anything sinister.

Every identifier in the chain — routing numbers, account designations, institutional codes — is extracted and mapped. Where the chain is complete, the route is documented end to end. Where an intermediary obscures the next leg, the file records the visible chain and names the missing piece, rather than asserting a destination it cannot confirm.

Long histories almost always contain gaps. A bank changed providers, a venue purged old data, a paper statement was thrown out during a move. The honest move is to mark the gap and tell the reader what would close it.

Outgoing transfers that lack a matching incoming receipt are classified as initiated rather than completed. Periods with no available source material are left blank in the ledger with a note explaining why. The timeline never invents continuity to look complete, because a clean-looking but invented timeline is the kind of file that collapses under the first close question.