A bank transaction has three dates: which one belongs in the reconciliation?

A payment instruction, a bank posting and a value date can describe different moments. Obtain the bank's field definitions before selecting a date for an import or reconciliation. A label such as transaction date may not mean the same thing in a PDF statement, downloadable file and payment confirmation.

Coutts, for example, describes separate booking, settlement or value, and timestamp fields in its transaction details. That is a useful illustration of why the fields should be retained rather than collapsed. Use the definitions supplied by the company's own bank and payment product; do not impose another bank's terminology on an unfamiliar export.

The bank reconciliation compares the ledger with a specified bank statement balance at a specified cutoff. The accountant determines the recognition and cutoff policy for the underlying transaction under the applicable reporting framework. A purchase, customer receipt and internal transfer may require different supporting evidence even if they appear in the same bank file.

Preserve the original instruction and posting dates in the working record. If a payment entered near month-end posts in the following period, explain the timing with the bank acknowledgment and subsequent statement. Do not change the original date merely to remove an outstanding item from the reconciliation.

For a hypothetical transfer instructed on the last business day of a month and credited the next month, the evidence should identify both events. The receiving account's opening balance will not necessarily include the funds. Review the treatment of money in transit with the accountant rather than counting it as cleared in both accounts.

A late instruction can appear with a later processing date because of the bank's cutoff or the payment channel's calendar. The Federal Reserve publishes service-specific holiday schedules, including ACH processing information. Those schedules do not replace the bank's own customer instructions, but they help explain why a calendar-day comparison can be misleading.

Record the time zone used by each system when investigating a boundary transaction. An export in one time zone and an approval log in another can show different dates for the same event. Retain both original values and document any conversion used in the analysis.

For foreign-currency transfers, also examine value dates and conversion details. A currency conversion and the outgoing payment can be separate events. Match their references and amounts without assuming that the displayed exchange-rate date is the date cash became available to the beneficiary.

Document which source field populates the ledger date, how the import handles time zones and which original fields remain available. Test the mapping against a normal transaction and a known cutoff example. If a bank changes its file format, review the mapping before importing a full period.

During the close, keep a short list of transactions whose dates require judgment. Attach the statement, payment evidence and the accountant's conclusion. A consistent rule with documented exceptions is easier to review than a series of undocumented date edits.

When a prior reconciliation changes after an import update, inspect the source dates before adding a balancing journal. The apparent cash difference may come from the same transaction moving between reporting periods. Resolve the mapping or cutoff issue at its source and preserve the explanation with the affected reconciliation.