Could a transaction have been automated or scheduled?¶

Yes. Standing orders, direct debits, subscriptions, recurring card payments and software workflows can execute after an earlier instruction, without fresh human action at the transaction time.

Instruction and execution are separate events¶

A user may schedule a transfer long before it runs. A merchant can submit later charges under an existing authority, and a service may retry a failed payment automatically. Trading software or APIs can create transfers from preset rules.

The displayed time may represent execution, processing or posting rather than creation of the authority. Recurring and merchant-initiated payments may not require re-entry of credentials or fresh authentication.

Attribute the underlying instruction¶

Preserve the payment type, status, schedule or mandate, creation and change history, account and endpoint used, authentication, notifications and configuration or API logs. Compare earlier payments and communications.

Automation neither proves innocence nor removes responsibility. Identify who created, authorised, controlled or knowingly maintained the instruction, and distinguish that event from each later execution.