DDI Mandate Edit MAAP

Mandate Type

This field will hold the source area of the system that will use the Mandate. This will be set to AR, PBI or OTHER. The value PBI cannot be set by the user as this option will be automatically selected when entry to DDI mandates is made via the PBI maintenance screens.

NOTE If the entry is made from the PBI screens, then the Start/End Date, Collection Frequency, Processing Type and Collection Customer will be defaulted to the screen from the PBI details.

Start Date/End Date

These date fields will hold the mandatory start date and optional end date for the direct debit. The start date will be used as the base date for all DD collections on this mandate to derive the collection day (for example a start date of 20th May 2021 and frequency of monthly will ensure that collections are made on the 20th of every month).

Number of Collections

This field is used in conjunction with the end date and will hold the number of collections that is to be made for this DDI Mandate. If this field is not entered, then the DDI will continue collection until the mandate is cancelled by the user. If the number of collections is entered, then this will be checked to ensure that there is this number of collections within the start/end date period. If the end date has not been entered, then this will be calculated from the Number of Collections and Start Date.

Currency Code

This field will hold the currency code to be used when processing transactions. This will normally be set to the base currency of the company as direct debit processing can only be used with base currency. However, it may be set to *** which indicates that all transactions regardless of currency will be processed for this DDI. In this case, the system will perform cross currency allocation when creating the direct debit transactions. That is the DD collection transaction will be in base currency using the Mandate Rate Type and Current Effective Date.

Amount

This field will hold the value of the direct debit. This is an optional field and is only used for memorandum purposes as the value of the direct debit collection will be derived from the transactions on the customer account or from the installments on a PBI plan.

Collection Frequency

This field will determine the frequency of the direct debit collection runs. It may be set to None, Weekly, Two Weekly, Monthly, Four Weekly, Quarterly, Half Yearly or Yearly. If set to None then the collection calendar must be entered to determine the frequency of the DD runs.

Collection Calendar

This field will determine the frequency of the direct debit collection runs by using the events defined on a calendar. If not set then the collection frequency must be entered to determine the frequency of the DD runs.

Processing Type

This field will determine whether the direct debit is a one or two-stage process. It must be set to 0 – (Default from DD Processing Controls), 1-Stage or 2-Stage. If set to a one stage process, then no intervention by the user is required. If set to a two-stage process, the transactions selected for collection by direct debit may be removed from the DD before final processing to BACS. This is the equivalent of the fully/semi-automatic scheduling in the previous version of DD.

NOTE There is now no manual selection of transactions available for direct debits.

Status

This field will hold the status of the DDI mandate. The code will be assigned according to the stage of the business process in the DDI cycle. The values are:

Collection Customer

This field will hold the AR customer that is involved with the DDI mandates. A customer may only have one 'Active' AR Customer Level mandate available at any one time, although they may have multiple Active PBI mandates available. When ICA is active, there may be only one Active AR mandate per customer per element at any one time.

Collection Customer Bank Account

These fields will hold the bank account of the AR customer on the DDI mandate. They will be used as the source bank account from which the collection will be withdrawn. These fields will be the country, sort code, bank account number and name of the bank account to use. They will default from the bank account nominated as the default collection bank account on the customer.

Collection Sub-Type

This field will hold the transaction sub-type of the direct debit transaction type (type 8) that should be created when a DD collection is made for the DDI mandate. If not entered, then the collection sub-type on the DD Processing Controls will be used.

Collection Element

This field will hold the ICA element of the direct debit transaction that should be created when a DD collection is made for the DDI mandate.

Cross Element Flag

This flag will determine whether transaction with different elements may be selected on the same DD collection for the DDI mandate.

Collection Location

This field will hold the location code of the direct debit transaction that should be created when a DD collection is made for the DDI mandate.

Bank Code

This field will be used to determine the bank account of the company on the DDI mandate. The bank code will contain the target bank account to which the collection will be claimed. If not entered, then the bank code defined on the DD Processing Controls will be used.

Automatic Banking Code

This field will be used to determine the BACS processing cycle/days for the DDI mandate. The automatic banking code will contain the calendar to determine when a BACS event is available and the number of days required before BACS can process the collection. If not entered, then the automatic banking code defined on the DD Processing Controls will be used.

File Format

This indicator details the transmission file format. This indicator will initially be set to ‘Default’ (to allow the DDI Mandate to default to the indicator on the DD Controls screen MAAN) or can be over-ridden to produce files in ‘BACS’ or ‘SEPA’ format.

Rate Type

This field will be used to hold the Rate Type to use when performing currency calculations for the DDI mandate. If not entered, then the Rate Type from the AR Company Level Controls will be used.

Last Collection Information

These set of fields will hold information regarding the last successful DD collection for this DDI mandate. They will hold the last collection value, last collection date and the total number of successful and failed collections made for this DDI mandate.

Next Collection Information

This set of fields will hold information regarding the next DD Collection that is required for this Mandate. They will hold the next process date and next collection due date. The process date will be calculated as the earliest date that this collection can be issued to BACS to ensure it arrives on or after the collection due date.