Tracing disputes fail as often from record chaos as from math disagreement. Statements arrive in different formats, transfers span multiple accounts, and supporting documents may reference amounts that do not yet sit in a single chronological ledger. This stage brings selected material into one workspace.
What enters the workspace
The record set is intentionally selective. Users choose which account history, statements, and supporting documents belong to the review pass. Exit Protocol structures that selection for ledger replay — not for silent bulk ingestion without explicit user action.
Bank statements, exports, and supporting exhibits chosen by the workspace user.
Transactions ordered chronologically with account context and extraction confidence where applicable.
Material rows flagged for human review before entering deterministic tracing.
Organization steps
Upload or import the statements and exports counsel wants in this review pass.
Align deposits, withdrawals, and transfers into a chronological account history.
Mark ambiguous parsed values or missing periods for review before tracing begins.
Verify the organized set still matches the matter boundaries defined in Part 1.
Why structure matters before LIBR
Reviewable organization
Selected records, transaction order, and source references are visible before any tracing strategy is applied.
Weak organization
A final trace number with no visible ledger, no source list, and no way to test transaction sequencing.
Organized records do not replace professional judgment about completeness or authenticity. They give counsel and retained experts a shared factual surface for the tracing stage that follows.