Capture every date label exactly
Store each source date separately under the institution's own label. Do not merge transaction, posting, processing, settlement, and value dates into one generic field before verifying their definitions.
Retain the statement period, available time zone, and source type as context. The issued PDF, online history, receipt, confirmation, and export may each represent a different stage of the event.
Use transaction date for the underlying action
Transaction date often identifies a customer action such as a purchase, transfer instruction, or withdrawal. For remote orders, subscriptions, foreign activity, and other payment types, bank convention or disclosure may assign a different event to that label.
Use transaction date to help match a receipt or merchant record, not to infer ledger posting. When the source supplies both transaction and posting dates, preserve both.
Transaction date evidence record
Use this record whenever one event spans a cutoff or carries multiple date labels.
Source dates
Capture every date under its original label from statements, receipts, history, or transfer evidence.
Event status
Classify authorization, pending, posting, settlement, reversal, and refund as separate states.
Period rule
Identify the date controlling period assignment and show that it reproduces the issued record.
Verification
Keep the statement entry, receipt or confirmation, observation time, and any unresolved conflict.
Use posting date for statement-period membership
Posting date generally marks the bank's ledger entry. Activity from a weekend can reach the ledger on a later business day, causing a month-end purchase to appear on the following statement.
Reconciliation must follow the date basis used by the issued statement. If rows are organized by posting date, regrouping them by transaction date can cross the cutoff and break the balance calculation.
Preserve value and settlement dates as distinct evidence
Value date may govern interest or another account treatment without matching posting date; settlement date may mark completion within a payment system. Meanings depend on institution, account, payment rail, and jurisdiction.
Never derive value date from transaction date or replace posting date with it. Retain it only from a source or official confirmation and state the purpose for which it is being used.
Track changing event states without creating unsupported transactions
A pending authorization may appear, change value, disappear, and later settle. Use merchant, value, card reference, and timing to link states without counting authorization and final posting as two completed expenses.
Refunds and reversals commonly carry later dates than their original events. When evidence establishes the relationship, link the events but keep all posted rows required to reconcile the statement.
Select a date field according to the decision
Use posting date to reproduce a statement built on postings, transaction date to compare customer actions and receipts, and value date only for its verified institutional purpose. Any reporting date should be derived without overwriting source fields.
Disclose the grouping rule with period comparisons. Switching between transaction and posting dates can materially change trends around weekends, holidays, payroll, and month-end boundaries.
If the expected row is still absent after the posting window, use the missing bank statement transaction checklist to check the statement period and source document.
Sources for this decision
Terminology used by banks and payment systems evolves. Check each code in issuer material for this statement.