The Recurring Mandate Schedule object represents multiple mandate registration runs.
The definition of a Recurring Mandate Schedule consists of a set of "information" fields, "mapped" fields and "scheduling" fields. The fields are the same for all record types (daily, weekly or monthly).
|Recurring Mandate Schedule Name||Enter an transparent name for the recurring mandate schedule record that incidates scope and purpose or the record|
|Status||Defines the status of mandate schedule records when they are created. Select New or Generated.|
|Run Date Conflict Strategy||Determines how FinDock handles a run date that falls outside business hours. Options are to use the previous workday or the next work day.|
|Processing Date Conflict Strategy||Determines how FinDock handles a processing date that falls outside business hours. This is only used for Bacs Direct Debit with FinDock as processor.|
|Target||Enter the bank or severice bureau account that will recieve the mandate registration files.|
|Exclude from Auto-Run|
|Repeat Frequency||Defines how often mandate schedule records are created. Enter a value 1 or more. Most often 1 is used, meaning create a record every week or every month depending on the recurring schedule type. 3 would mean create a record every 3 weeks/months.|
|Start Date||Date when this recurring mandate schedule activates|
|End Date||Date when this recurring mandate schedule ends|
|Business Hours||Select the Business Hours record that should be used in the preview to check that calculated dates are working days.|
|Run # of business Days before Proc. Date||Determines the run date of generated mandate schedules. Enter the number of days before the calculated processing date that the schedule should be run.|