The Bacs Direct Debit scheme requires you to register a DDI with your bank or service bureau before it can be used to collect direct debits. This process is supported in FinDock through the Mandate Schedule object.
To use the Mandate schedule for the registration process, you need to first add the Generate Mandates button component to the page layout of Mandate Schedule. Follow the standard Salesforce procedure to modify the Lighting page layout.
To create a new DDI registration file:
- In Findock, click the Mandate Schedules tab.
- Click New to create a new schedule record.
- On the Mandate Schedule Detail page, enter your Bacs target and a processing date (date when the mandates should be active, taking DDI lead time into account).
- Set the status to ‘Scheduled’ and click Save. The detail page is refreshed with the values you entered.
- On the detail page of the mandate schedule, go to the buttons list at the right top of the page and click Generate Mandates.
- A success message is displayed and a Salesforce job is started in the background to select Bacs mandates that are pending registration.
- After the job is finished, the mandate schedule status is set to ‘Generated.’
Once the mandate schedule status changes to ‘Generated,’ you can either validate first and then create the DDI files, or you can immediately create the DDI file.
To validate the mandates first, update the status of the mandate schedule to ‘Validate Mandates.’ This tells FinDock to first validate all the associated mandates and confirm the mandates are complete according to the criteria outlined in the following table.
You can also skip this step and set the mandate schedule status manually to ‘Process.’ Potential errors will be caught later and will still block the DDI registration.
|Mandate Id||Must be > 6 and \< 18 alphanumerical characters. If the Target sub type = SmartDebit the mandateID must be of length 7.||Mandate ID must be between 6 and 18 characters|
|Mandate Id||After taking out nonalphanumeric characters should not contain only the same characters. (see example 2).||Mandate ID must not contain only the same characters.|
|Mandate Id||Should not contain “/”||Mandate ID contains \/|
|Contact > Last name||Contains at least 3 characters.||Lastname must contain at least 3 characters|
|Contact > First Name||not empty, not spaces only||First name cannot be empty|
|Contact > Address Line||not empty, not spaces only||Address line cannot be empty|
|Contact > City||not empty, not spaces only||City cannot be empty|
|Contact > Post code||not empty, not spaces only||Post code cannot be empty|
|Payment Profile > Sort code||Length 6||Sort code must be 6 digits (and thus may not be empty)|
|Payment Profile > Sort code||Only digits||Sort code can only contain digits 0:9|
|Payment Profile > Account number||Length 8||Account number must be 8 digits|
|Payment Profile > Account number||Only digits||Account number can only contain digits 0:9|
|Target||Must have a BACS target||Mandate does not contain a valid target|
|Status||Allowed values are: “Pending registration” “Pending validation” “Pending update”||Invalid mandate state|
|Payment Profile > Holdername||not empty, not spaces only||Holdername cannot be empty|
If a mandate fails validation, the status of the mandate is set to ‘Failed,’ and the error(s) is added to the field Last Status Reason.
If no errors are found, FinDock automatically progresses to the file creation stage.
The DDI file creation is triggered when the mandate schedule status changes to ‘Process.’ This initiates an outbound message which creates a Standard 18 file.
Once ProcessingHub has generated the file, it is uploaded to Chatter, and a PaymentHub File record is created to track the status of the generated file.
The mandate schedule, in turn, is updated to ‘Pending Verification.’
Under Related on the mandate schedule, you will find a list of the DDIs that have been included in the Standard 18 file.
Once the Standard 18 file is ready, you can send it to your bank for registration. Navigate to your Chatter group designated for file exchange to find the generated file that you should give to your bank or service bureau.
After the file has been accepted by your bank, return to the Mandate Schedule and change the status to ‘Verified.’ This sets the DDIs to ‘Active’ and the mandate schedule to ‘Done.’
Do not verify the run before the file is accepted by your service bureau or bank. The verification process is not easily reversible!