Direct answer: Source provenance is the record of where a reported trust-account fact came from and how it changed. For reconciliation, that means linking balances, transactions, adjustments, and exceptions to the exact bank-statement, trust-journal, or client-ledger source version and location. Provenance makes the packet reviewable, corrections reproducible, and automation appropriately accountable.
Key takeaways
- Keep raw sources unchanged and store normalized records separately.
- Link every material exception to the relevant source row or statement entry.
- Record transformations and manual overrides.
- Use source versions so later exports do not rewrite earlier closes.
Provenance is more than file storage
Saving a PDF or CSV is necessary but not enough. The system should know which file, account, period, page or row, and stable transaction identifier supports a value. It should also record how imported text and amounts were normalized.
When two source records conflict, provenance lets the reviewer see both rather than accepting a blended result that hides the discrepancy.
Normalization without losing evidence
Different systems use different date formats, amount signs, reference fields, and client identifiers. A canonical record makes calculation possible, but it should retain the original value and transformation details.
Manual mapping decisions deserve the same treatment. If an operator assigns an unfamiliar description to a matter, record who made the mapping and why, then require review if the decision affects a consequential exception.
What the reviewer should experience
A reviewer should move from an exception or reported balance to the supporting entries without searching through unrelated files. The interface should show the source name, date, amount, nearby context, and any later correction.
That traceability improves review speed, but it does not convert the software into an auditor or legal adviser. The human reviewer still decides what the evidence means.
Frequently asked questions
Why keep the original value after normalization?
It lets reviewers verify the transformation and protects against a parser or mapping error becoming invisible inside a canonical record.
Should source files be editable in the reconciliation system?
A safer pattern keeps raw sources immutable and records corrections as new source versions or controlled adjustment records.
Sources and further reading
This article is operational education, not legal advice. Trust-account rules and retention requirements vary by jurisdiction. Confirm the requirements that apply to your firm and accounts.