When enabling Collections process automation / Pre‑dunning for the first time, Dynamics 365 Finance currently evaluates all invoices that have never gone through the Pre‑dunning step, which can include historical overdue invoices and trigger unintended mass communication. Please add an optional “First run / Initialization” safeguard that allows customers to (a) exclude overdue invoices (e.g., only process invoices where Due date > Run date), and/or (b) set an initialization cut‑off date and mark older invoices as already processed for Pre‑dunning without sending communications. This would align Pre‑dunning with its intended “ahead of due date” purpose while preserving existing behavior for ongoing runs.