Skip to main content

Registering Bacs mandates

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.

Schedule mandate creation#

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:

  1. In Findock, click the Mandate Schedules tab.
  2. Click New to create a new schedule record.
    New mandate schedule
  3. 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).
  4. Set the status to ‘Scheduled’ and click Save. The detail page is refreshed with the values you entered.
  5. On the detail page of the mandate schedule, go to the buttons list at the right top of the page and click Generate Mandates.
  6. A success message is displayed and a Salesforce job is started in the background to select Bacs mandates that are pending registration.
    New mandate schedule generated
  7. 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.

Validate mandates#

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.

FieldCriteriumError message
Mandate IdMust 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 IdAfter taking out nonalphanumeric characters should not contain only the same characters. (see example 2).Mandate ID must not contain only the same characters.
Mandate IdShould not contain “/”Mandate ID contains \/
Contact > Last nameContains at least 3 characters.Lastname must contain at least 3 characters
Contact > First Namenot empty, not spaces onlyFirst name cannot be empty
Contact > Address Linenot empty, not spaces onlyAddress line cannot be empty
Contact > Citynot empty, not spaces onlyCity cannot be empty
Contact > Post codenot empty, not spaces onlyPost code cannot be empty
Payment Profile > Sort codeLength 6Sort code must be 6 digits (and thus may not be empty)
Payment Profile > Sort codeOnly digitsSort code can only contain digits 0:9
Payment Profile > Account numberLength 8Account number must be 8 digits
Payment Profile > Account numberOnly digitsAccount number can only contain digits 0:9
TargetMust have a BACS targetMandate does not contain a valid target
StatusAllowed values are: “Pending registration” “Pending validation” “Pending update”Invalid mandate state
Payment Profile > Holdernamenot empty, not spaces onlyHoldername 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.

Create DDI files#

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.’ Mandate schedule 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. Mandate schedule related mandates

Send DDI registration 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!

Mandates activated