DD Company Edit MAAN

Use the Company screen to identify your business controls for Direct Debiting. These controls may only be created if the DD flag has been set on the system controls and will be used as a base set of controls for all modules using this company code.

Screen Fields

OIN Code

This field will hold the Originator’s Identification Number (OIN) which is a unique number given to participants who are authorised to use the Direct Debit Scheme. An OIN is synonymous with a BACS User Number.

Mandate Numbering Indicator

This field will indicate the type of numbering that is required for the DDI Mandate. It may be set to 0 (Manual Entry Required) or 1 (Automatic Generation Required).

Mandate Prefix

This field will indicate the prefix code to use when automatically generating the DDI Mandates. If entered, then all automatically generated DDI Mandate References will start with this Mandate prefix.

Mandate Suffix Length

This field will indicate the length of the suffix to use on the DDI Mandate Reference when automatically generating the DDI Mandates. It must be entered when automatic numbering can be used and the total length of the prefix and suffix must not be greater than 18 characters.

Next Mandate Suffix

This field will indicate the next suffix number to use when automatically generating the DDI Mandate References. It must be entered when automatic numbering can be used.

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 from which the collection will be claimed.

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.

File Format

This is used to identify the default file format that will be used for all DDI transmissions to the bank. This default value will be applied to all new DDI Mandates initially and can be changed subsequently. The default value will initially be set to ‘0’ (BACS).

BEM User

This field will be used to identify the user to be notified for Direct Debit BEM events from DDI responses. When using AR BEM events, this will be the default user to receive BEM messages if no Credit Manager user is specified on the Customer Controls.

Notification Days

This field will be used to identify the number of days that a customer must be notified before the first collection of a Direct Debit can be taken. The system will ensure that a DDI must be created at least this defined number of days before the start date of the DDI.

Auto Submission

This field will be used to automatically submit a new DDI for BACS approval. When a new DDI is created, the status of the DDI will be ‘new’, the user must then separately request that the DDI is transmitted to BACS. This flag will automatically set the status of a new DDI to 'awaiting BACS approval'.

DD BACS Transmission in Use

This field will determine whether new DDI Mandates will have transmission files sent to BACS for verification. If this flag is not set, then a DDI will have a status of 5 (Active) without the need to submit the BACS Transmission process. This flag should be left blank when the DDI authentication is performed outside the system.

DD BACS Update Transmission in Use

This field will determine whether amended DDI Mandates will have transmission files sent to BACS for verification. If this flag is not set, then a DDI can be amended without the need to submit the BACS Update Transmission process. This flag should be left blank when the DDI authentication is performed outside the system.

See also

Accounts Receivable Home Page

System Controls Home Page