Skip to main content

Processing Bacs reports

FinDock processes incoming Bacs reports that are uploaded to Chatter or automatically fetched from a service bureau integration (such as SmartDebit). The Bacs reports are parsed and saved as Inbound Report records.

This article outlines the actions that FinDock carries out through Guided Matching managed rules. Additional custom Guided Matching rules can be added as needed.

Bacs report reconciliation is carried out in two phases:

  1. ProcessingHub first tries to find and match related mandate and installment records for an incoming Bacs report using Id references and processing or collection dates.
  2. FinDock then uses Guided Matching to handle report actions.

Processed inbound reports are assigned a specific status depending on the Guided Matching results. The status options are:

  • Matched: the report has been successfully processed and matched
  • Guided Review: the report type was identified and related ruleset assigned
  • Failed: there was an error processing the report
  • Manual: the report type could not be identified and requires manual review

If you add custom Guided Matching rules, you should create a rule to update the inbound report status to one of the defined Guided Matching End States.

If no such rule is created, FinDock automatically updates the status of the inbound report to Matched as part of the Manage Source rule. This is only the case when you add your own custom rules. With the default Guided Matching rules, the inbound report status after Guided Matching is as defined in the following tables.

Input Report

Input reports are generated on Day 1 (Input Day) of the Bacs 3-day collection cycle. They are an important source of information that needs to be processed as soon as possible.

CodeReasonActions by FinDock
EUnable to process transactionSet status to Manual.
LUnable to process transactionSet status to Manual.
YDDI cancelled by paying PSPReverse installment and create negative payment.

AUDDIS report

An Automated Direct Debit Service (AUDDIS) report arrives a certain number of days after the Bacs 3-day collection cycle has completed and may include similar findings as input reports.

CodeReasonActions by FinDock
1Instruction cancelled by payerSet status to Manual.
2Payer deceasedCancel mandate.
3Account transferredCancel mandate.
5No accountCancel mandate and deactivate payment profile.
6No instructionSet status to Manual.
7DDI amount not zeroNone. Contact FinDock Support.
BAccount closedCancel mandate.
CAccount transferredSet status to Manual.
FInvalid account typeCancel mandate.
GBank will not accept Direct Debits on accountCancel mandate.
HInstruction has expiredSet status to Manual.
IPayer reference is not uniqueNone. Contact FinDock Support.
KInstruction cancelled by paying bankSet status to Manual.
LIncorrect payer's account detailsCancel mandate and deactivate payment profile.
MTransaction code / user status incompatibleNone. Contact FinDock Support.
NTransaction disallowed at payers’ branchCancel mandate.
OInvalid referenceNone. Contact FinDock Support.
PPayer's name not presentNone. Contact FinDock Support.
QService user's name blankNone. Contact FinDock Support.

ADDACS report

An Automated Direct Debit Amendment and Cancellation Service (ADDACS) report informs you of DDI amendments and cancellations. ADDACS reports can arrive at any time.

CodeReasonActions by FinDock
0Instruction cancelled - refer to payerCancel mandate.
1Instruction cancelled by payerCancel mandate.
2Payer deceasedCancel mandate.
3Account transferred to a new bank or building societySet status to Manual.
BAccount closedCancel mandate.
CAccount transferred to a new bank or building societySet status to Manual.
DAdvance notice disputedSet installment(s) status to On Hold.
EInstruction amendedSet status to Manual.
RInstruction re-instatedActivate mandate.

ARUDD Report

An Automated Return of Unpaid Direct Debits (ARUDD) indicates a DDI could not be collected and includes the reason for the unpaid direct debit. Further information about these reason codes can be found from the Bacs Pay UK resources.

CodeReasonActions by FinDock
0Refer to payerReverse installment.
1Instruction cancelledCancel mandate and reverse installment.
2Payer deceasedCancel mandate and reverse installment.
3Account transferredReverse installment.
4Advance notice disputedReverse installment.
5No account (OR wrong account type)Reverse installment.
6No instructionReverse installment.
7Amount differsReverse installment.
8Amount not yet dueReverse installment.
9Presentation overdueReverse installment.
AService user differsReverse installment.
BAccount closedCancel mandate and reverse installment.

DDIC report

Direct Debit Indemnity Claim reports indicates a payer requested a payment refund under the Bacs Direct Debit Guarantee.

CodeReasonActions by FinDock
1Amount and/or date of direct debit differs from advanced noticeReverse installment.
2No advance notice received by payerCancel mandate and reverse installment.
3DDI cancelled by paying bankCancel mandate and reverse installment.
4Payer has cancelled DDI direct with service userCancel mandate and reverse installment.
5No instruction held, payer disputes having given authorityCancel mandate and reverse installment.
6Signature on DDI is fraudulent or not in accordance with account authorized signature(s)Cancel mandate and reverse installment.
7Claim raised at service users request after direct debit applied to payers accountReverse installment if not already reversed.
8Service user name disputed Payer does not recognize service user collecting Direct DebitReverse installment.