Bacs for FinDock is an implementation of the Bacs Direct Debit payment scheme. It supports collecting one-time and recurring payments using payment schedules and the FinDock Payment API.
This implementation also supports a variety of file and report types for handling Bacs direct debit payment management and reconciliation.
- FinDock is installed and configured.
- A working connection to ProcessingHub and WebHub.
To complete the Bacs configuration, you need to add at least one Bacs target (account). For more information, see Creating Bacs targets.
The Bacs extension generates mandates as Direct Debit Instructions (DDIs) when required, such as for direct debit collection runs.
If a recurring donation or opportunity (recurring payment or installment) is created, a mandate is automatically created with an org-specific Id (7 characters) and status “Pending registration.”
For more information, see Registering Bacs mandates.
The Bacs Direct Debit scheme does not allow multiple transactions for the same mandate on the same date. If you have transactions like this, FinDock automatically aggregates to a single direct debit installment all transactions for each mandate-date combination.
After a payment schedule run for a Bacs target has generated and/or selected installments that meet the schedule’s criteria, FinDock checks if there are installments with the same mandate-date combination.
If such installments are found:
- An aggregated installment is created with an open amount equal to the sum of the open amounts of the individual installments.
- The payment method of the individual installments is set to Aggregated Installment.
- The individual installments are linked to the aggregated installment.
- The original installments are removed from the payment schedule.
If a payment is received for the aggregated installment, it is split and distributed to the original individual installment. Both the aggregated installment and linked individual installments are set to Collected, and all open amounts are set to zero. In addition, a corresponding negative payment is created for the aggregated installment to keep the sum of all payments equal to the actual direct debit payment amount.
If an aggregated installment is reversed, a negative payment is created and distributed across the original individual installments. The status of these installments is set to Reversed, and the open amount is set to the original value.
The payment method of the original installments is set back to direct debit, allowing them to be recollected. The for the Aggregated Installment positive payment is created in order to keep the sum of all Payments equal to the actual money flow.
- Keep in mind when confirming the direct debit to the customer or donor that you mention the total amount rather than the amount of the single transaction.
- Aggregated installments are not eligible for Gift Aid since they are not separate payments or donations.
- In order to keep your reports in line with actual expected and/or realized cash flow, exclude aggregated installments from your reports. Use the field
paybacs__IsAggregated__cto filter out installments that are aggregated installments.
- For the same reporting reasons, NPSP Opportunities are not created for an aggregated installment.
- Do not recollect Aggregated installments after a reversal, but recollect the Original Installments.
As part of the Bacs package, there is a Bacs-specific 'Processing Date" (
paybacs__BACS_Processing_Date__c) that needs to be added to the Payment Schedule layout. Use this field to define the target processing date for the installments in a payment schedule according to the official Bacs processing calendar.
If you don't use the Processing Data field, FinDock falls back to Collection Date and uses that to inform the Bacs network to process the direct debit collection on the next possible processing date.
When a Bacs report is uploaded to ProcessingHub (via Chatter), the records in that file are matched against installments in the system. If a value is provided in the field ‘Bacs processing date’ on a payment schedule, then FinDock matches incoming Bacs reports on that field instead of using the collection date.
For Bacs Direct Debit payments initiated through the FinDock Payment API, FinDock performs a sort code & bank account check to avoid failed payments due to incorrect code or account values. The checking is done automatically, so no additional work is needed to use. However, you do need to design your own solution for how to handle the error message if a customer or donor enters incorrect information.
In addition to the automates API check, you can add the FinDock Lightning component Check Sort Code and Bank Account to your Payment Profile layout to do the same validation when manually entering payment information.
To set up manual sort code and bank account checking:
- Go to a Payment Profile record.
- Click the settings cog in the upper right and select Edit Page.
- Drag the Check Sort Code and Bank Account component to your page layout.
- Click Add Filter under Set Component Visibility to the right.
- Click Advanced and under Field, click Select.
- In the pick lists, select Record, then Record Type, then Name, and click Done.
- Add an equal operation with "Bank Account" as the value, then click Done.
- Click Save in the upper right to save the layout change and component filter settings.
The component will now appear on payment profiles with UK bank accounts, but it is not visible for other payment profiles. To validate a sort code and bank account, just click the Validate button.
To test your Bacs configuration, you can use the following messages with the Payment API.